Uncorrectable Error

Associate
Joined
1 Apr 2016
Posts
3
The Short Story:
I have recently build a PC for myself but have been having trouble. It was fine to start with, but after about a day the trouble started. I experienced a shut down while I was playing a game and was shown a blue screen giving me the error WHEA_UNCORRECTABLE_ERROR. Since then I have tried a multitude of things, none of which have fixed anything, and I still receive the same blue screen after powering the computer up. Any ideas of what might be causing this?

Specs:
i7-5820k
Gigabyte X99-SLI
Gigabyte 980ti
Corsair RM850ti (formerly Corsair CX600)
Kingston 120GB SSD
WD 1TB HDD
16GB RAM
D-Link wifi card
Samsung optical drive
(The CPU, motherboard, cooler and RAM all came in an overclockers bundle, the rest are from Amazon)

The Long Story:
Initially, after I received the blue screen I did the usual 'turn it on and off again' routine. After the third or fourth time doing this, a second blue screen follows the first, saying that a win32 file was missing. Therefore, I used the BIOS to boot from my windows 10 CD, deleting the original widows partition and reinstalling windows. However, it crashed again, showing the same blue screen.
After some research, I thought that perhaps my over clock in conjunction with an inadequate power supply might be causing it, so I turned down the overclock. This seemed to have worked, but after a few hours it crashed again.
In a last desperate attempt, I replaced my PSU with a better, more powerful one and returned my GPU for a new one. However, I still get the same blue screen. Any ideas?
 
What memory?
Some memory requires more than standard volts
Has it got XMP profile set correctly in the bios?
Welcome :)
 
The RAM is rated for 2400Mhz, so 4000Mhz (if that was even correct which i doubt as that is bloody high) would certainly be giving errors, I would have expected the PC not to boot at all with that ram at 4000Mhz.
 
Yes, I thought so too. I must have messed up when I originally tried to reverse the overclock on my CPU. It seems to be running as normal for now though. Fingers crossed that it stays that way!
Thanks!
 
Back
Top Bottom