Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
Your socket temp was getting way up there on that last screenshot, my money is on the board.
Yeah... you mean the CPUTIN don't you? It stuck at 65°C after 15min while running prime bend. Do you know where exactly that sensor is located? I'm asking because i've seen discussions about the CPUTIN-value that always seem to be a lot higher than the CPU-"package"-temp just like in the screenshot.
So far i've rised the RAM voltage to 1.55V (in bios it was set to "auto" with a range from 1.25V to 1.9V)
I don't have a spare-computer to test all the parts seperately but i'll give it a try to remove the RAM-sets one after another.
It was using all 16 g of ram? Have you run a virus scan, maleware scan etc???I just experienced something. I started checkdisk for one of my hdds. While waiting i started playing pathofexile when i noticed that didn't run as fast as i experienced sooner. I barely played for 5min and the display-driver crashed. When i was able to close it i looked in the taskmanager and the mmc.exe was eating my whole RAM.
Might be a big clue to a RAM-failure, what do you think?
Meanwhile i closed mmc and everything works normal... (so the failure was not because of the voltage, but also it didn't solve it)
It was using all 16 g of ram? Have you run a virus scan, maleware scan etc???
I just experienced something. I started checkdisk for one of my hdds. While waiting i started playing pathofexile when i noticed that didn't run as fast as i experienced sooner. I barely played for 5min and the display-driver crashed. When i was able to close it i looked in the taskmanager and the mmc.exe was eating my whole RAM.
Might be a big clue to a RAM-failure, what do you think?
Meanwhile i closed mmc and everything works normal... (so the failure was not because of the voltage, but also it didn't solve it)