WIndows 10 Blue screen WHEA_UNCORRECTABLE_ERROR

ModMonster

Reputable
Aug 31, 2015
428
0
4,960
Occasionally when playing StarWars Battlefront 3 , I'll get a blue screen of death that says: WHEA_UNCORRECTABLE_ERROR. some people say I need to clear BIOS to factory defaults, but I don't think its a problem. The only thing changed in the BIOS is my 4.5Ghz 4690k OC. But I ran OCCT for 6.5Hr without ANY errors. it ran really smooth except for one or two lag spikes. Any ideas? Also CHKDSK and SFC /Scannow do get errors.
 
Solution
Someone mark this is as solved: I was able to fix this, but typing in Administrator CMD DISM /online /Cleanup-image /StartComponentCleanup. Then I downloaded Microsoft's WIndows 10 Media creation tool and re-updated to Windows 10. This did not affect my files nor most of my settings.
The most common reason for WHEA errors is insufficient voltage for an overclock. Eliminate the overclock and see if the BSOD goes away. Just because your system is stable for a short while in OCCT, doesn't make it 24/7 stable. I've seen systems that can run Prime95 stably for days on end, but BSOD while gaming or just browsing with Chrome. Different work loads play a huge role here.

As for your errors on CHKDSK and SFC, what errors does it give? Just note, it's not uncommon for BSOD's to cause corruption on storage media. So the BSOD's could be the symptom of the problem and not the problem itself.
 

ModMonster

Reputable
Aug 31, 2015
428
0
4,960
Well, I decided NOT to turn off the Overclock, and just wait for it to crash again. SO that I can properly diagnose what is actually causing the crash. But I WAS able to fix CHKDSK errors, but the SFC /Scannow errors still exist (even in Administrator & Safe Mode). Any ideas? I have tried DISM /online /clean-image /restorehealth, but it just pulls up a message that it could not call for files.
 
If you still have the USB stick with Window on it, try running sfc with it mounted. If not remake it if you can. If you installed the original version of Windows 10 from the key, but then Windows 10 updated in November to 1511, then you'll need to do a media creation for 1511.

It's possible that for some reason it's looking to the original install location to replace the file with and not finding it.
 
No, don't do a re-install. Just have the USB mounted (in a USB port) when you re-run sfc. This is just a guess, but maybe when sfc finds the corrupt files it looks to the system reserved partition and doesn't find them, so maybe it'll look for the install media.