WIndows 10 Blue screen WHEA_UNCORRECTABLE_ERROR

ModMonster · Mar 7, 2016

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.

techgeek · Mar 7, 2016

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 · Mar 7, 2016

I'll try disabling the OC for a few days. SFC wont tell me what errors, they just say there is corruption.

techgeek · Mar 7, 2016

Are you running sfc from an elevated (run as administrator) command prompt? Does it say that it's fixing it?

You could try also running it from Safe Mode.

Can you give us a screenshot of the verbose of chkdsk as well?

ModMonster · Mar 7, 2016

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.

techgeek · Mar 7, 2016

What version of Windows are you running? What media type did you use to install Windows from?

ModMonster · Mar 7, 2016

Its the latest version of Windows 10. I installed it from the Install Media from Microsoft.com via USB.

techgeek · Mar 7, 2016

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.

ModMonster · Mar 8, 2016

I'm recreating the USB drive now, but what exactly am I supposed to do? Reinstall windows? Please give me clear instructions on what I really have to do.

techgeek · Mar 8, 2016

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.

ModMonster · Mar 8, 2016

I tried your way, but I got the same errors. I also tried this :http://www.easytechguides.com/sfc-unable-to-fix-corrupt-files.html, but it failed on step 14-15. Any more ideas?

techgeek · Mar 8, 2016

How does it fail on step 14-15, any error messages?

ModMonster · Mar 8, 2016

It says Error 1726 The Remote Procedure call has failed.

techgeek · Mar 8, 2016

Do you have Afterburner and RTSS running? If so, close them and try again.

ModMonster · Mar 8, 2016

They are not opened.

techgeek · Mar 8, 2016

So neither of those are in the System Tray? In your search, type services.msc and run it. Check and make sure these two services are listed:

Remote Procedure Call (RPC) set to Automatic
Remote Procedure Call (RPC) Locator set to Manual

ModMonster · Mar 9, 2016

No, and I already tried all of that. Its starting to look like I'll have to do a system refresh. I even figured out to make DISM mount the USB 's files for scanning, but that didn't even work.

techgeek · Mar 9, 2016

I think something must be locking one or more of your system files. Run msconfig and select Safe Mode with Networking from the Boot tab. Once logged in in Safe Mode try dism again from an elevated command prompt.

ModMonster · Mar 9, 2016

Ok, I'll try that in a hour or so. Also I think you should know if I click on sounds in the tray, nothing happens.

techgeek · Mar 9, 2016

ModMonster :

You mean the volume icon?

ModMonster · Mar 9, 2016

Yeah, I also just booted into network safemode , same results

techgeek · Mar 9, 2016

I've run out of ideas on how to correct this without a System Refresh. A system refresh is going to cause you to have to re-install all your software and drivers.

Maybe someone else has some ideas.

techgeek · Mar 9, 2016

Just thought of something elementary, have you tried System Restore? Hopefully you have a restore point prior to all these issues.

ModMonster · Mar 9, 2016

No, I don't have a restore. I want one, but I dont' Windows 10 supports it does it?

ModMonster · Mar 9, 2016

WIndows 10 Blue screen WHEA_UNCORRECTABLE_ERROR

Reputable

Splendid

Reputable

Splendid

Reputable

Splendid

Reputable

Splendid

Reputable

Splendid

Reputable

Splendid

Reputable

Splendid

Reputable

Splendid

Reputable

Splendid

Reputable

Splendid

Reputable

Splendid

Splendid

Reputable

Reputable

Share this page