Windows 10: Random but frequent BSOD - whea_uncorrectable_error

I’m getting a lots of BSOD with whea_uncorrectable_error and I have tried lots of thing/suggestions from googleing…. Before this happened it all worked perfectly fine for a month and all of the sudden it began. It have never been overclocked only RAM have been set for XMP standard.

So here is my information and the behavior of my system

Setup:

• ASUS Maximus VIII Ranger Z170 (1+ month old)
• Intel i7-6700K (Stock speed) (1+ month old)
• Noctua NH-D15 (1+ month old)
• Corsair Vengeance LPX DDR4 2666MHz 2 x 8GB (1+ month old)
• Samsung 850 pro 128 GB (2 years old)
• Cooler Master Silent Pro 1000W (3 years old)

What I have tried hardware wise:

• Removed all unnecessary connections such as extra front USB and AUDIO connection
• Removed all other drives than the OS drive
• Switched RAM sockets placing and tried only one at a time (with each one)
• Moved jumper back and forth
• Reset BIOS settings
• Installed OS on different drive
• Changed to use different keyboard/mouse
• Firmware updated both SSD and BIOS
• Unplugged internet cable
• XMP left on and off

What I have tried OS wise:

• Windows 10 version 1607 anniversary update (newest and fully updated windows 10)
• Windows 10 version 1607 anniversary update (without updating)
• Windows 10 version 1511 (to determine of some updates between 1511 and 1607 were the issue)
• Windows 7 service 1 (fully updated)
• Windows 7 service 1 (not updated) – Pretty stable (1 BSOD total)
• Booting into safemode seems to remove the issue aswell

What I have tried software/testing wise (all tests passed):

• Run memtest86
• Intel Diagnostic Tool
• CMD chkdsk
• CMD sfc /scannow
• Windows memory dia tool
• Prime95 for hours’ multiple times (temp really isn’t an issue max 70c but mostly around 60c)
• DRIVER VERIFIER
• Furmark
• PCMark 7 – tried all free benchmarks (on sable win 7)
• HDTune
• CrystalInfo
• Intel Driver Update Utility
• Uninstalled most drivers and installed all newest drives from ASUS website (only drivers)

BSOD “whea_uncorrectable_error” happens with no visible pattern, but her is what I have seen:

• BSOD happens regular 3-15 min from boot time
• BSOD can happen before login (at login screen)
• BSOD happens both if left totally untouched or if used
• BSOD seems to be delayed by prime95 (my thought is that prime95 takes all the CPU power/priority from other threads, so the software issue or whatever can’t be executed)
• A prime95 test of 1 hour happened without BSOD, 7 min after prime95 end a BSOD happened
• Nothing specific seems to trigger the issue
• Windows 7 service 1 without updates - doesn’t seem to be triggered or just not as easily (The only 1 BSOD happened shortly after inserting ASUS driver cd(might be random) on a fresh WIN 7 install, for 2 days it ran without BSOD)

I have tried online dmp file analysis and can see mostly:

• Machine Check Exception
• 0x124_GenuineIntel
• WIN8_DRIVER_FAULT or WIN7_DRIVER_FAULT

I hope somebody can help me, I don’t know what else to do, it could be a hardware issue with the newer parts and I could send it for RMA, but to me it seems as a software issue when prime95 can delay it and there mostly isn’t any issue with windows 7 service 1 without any updates.

I have made a ZIP with a dmp files in different folder for each OS test along with the required DM log zip.

UPDATE: I did another prime95 test of 3 hours which again delayed the BSOD, 15 min after I ended prime95 I got a BSOD. So it seems to delay it.

:)

 

Random but frequent BSOD - whea_uncorrectable_error

Thanks for the reply!

The troubleshoot didn’t come with any new suggestions that I haven’t already tried. Remove new hardware (already tried) or and update windows (already tried).

BIOS and Chipset have already been updated as well.



I have already tried uninstalling all driver and then install the provided from ASUS’ website and then restart, but didn’t fix it.

I tried removing all bloatware (from windows such as candy crush). And I tried remove pretty much all drivers from Device Manager, until I couldn’t use USB devices any more, but windows automatically installed some driver even though internet was disconnected
after restart.

The above didn’t fix the issue unfortunately.

Furthermore, I did another prime95 test of 3 hours which again delayed the BSOD, 15 min after I ended prime95 I got a BSOD. So it seems to delay it.

 

Random but frequent BSOD - whea_uncorrectable_error

Hi Mikkel,

Thank you for responding.

As most of the troubleshooting steps couldn't resolve the issue,
I suggest you to download Windows 10 ISO file, create an installation media from other working computer to perform Startup Repair of the computer that you are unable to boot.

Using ISO file to perform Startup Repair will allow the device to boot the system to Windows Recovery Environment and tries to repair the device.

Step 1:
I suggest you to try Startup Repairing the Windows and check if it helps.

Download the Windows 10 ISO and create a Media Creation tool and then perform Startup Repair.

Refer to the following link: Installing Windows 10 using the media creation tool

(Refer to the section "Installing Windows 10 using the media creation tool” in the above article for creating the tool).

Step 2: After creating the tool perform Startup Repair.

I would like to inform that, if your Windows 10 is not able to boot or startup, Startup Repair will come into action and try to diagnose and fix the issue. It will scan system files, registry settings, configuration settings and
more and try to fix the problem on its own, automatically.

Perform the Startup Repair:

• 
  When your computer starts, wait for the manufacturer logo to check the option for boot menu, it will usually be
  F12.
  
• 
  The boot menu key might differ with each manufacturer. If you are unable to find the boot menu key, you may refer the user manual.
  
• 
  Restart the computer, when the manufacturer's logo is displayed, keep pressing the
  Boot menu option key to enter the boot menu and change the boot option to
  CD\DVD ROM.
  
• 
  After you boot your computer using Windows 10 DVD, a black screen appears with gray text "Press any key to boot from CD or DVD". Press any key.
  
• 
  Select the correct time and
  Keyboard type.
  
• 
  Click Repair your computer in the lower left corner
  
• 
  Click on Troubleshooting, advanced option and then click
  Startup Repair.
  

Hope it helps. Kindly update the status of the issue, we will be happy to help you.

Thank you.

 

Hi mikkel1107,

Welcome to the 10forums *Smile

I don't assume that you have logs/screenshots/photos of the tests you performed?
To be specific:

• Run memtest86 - photo
• CMD chkdsk - log
• CMD sfc /scannow - log
• DRIVER VERIFIER - crash?
• Furmark - screenshot, GPU-Z with it would be nice
• HDTune - screenshots

Why logs/screenshots/photos? I answer it with the question 'What are the results and what did you do with the results?'
To be annoying, I personally find 'they passed' not good enough. I need details about the tests so I can interpret them and have a better insight in where the possible cause could be.
I'll post my instructions for the tests at the end of this post just in case *Smile please read it carefully.

Please change the system language so those who don't have your native language (like myself) can read the text logs too *Smile
Language - Add, Remove, and Change in Windows 10 - Windows 10 Forums







Diagnostic Test

RAM TEST
*Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums



Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the error scan,
• the health,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc /scannow" (without quotes) and press enter
• When it is finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at %systemroot%\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of SFC and post it.






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.






Diagnostic test

GPU TEST


Run Furmark tutorial



Note Run Furmark for around 30 minutes



Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high
When finished, make a photo/screenshot of Furmark and post it.

In Furmark you can find a tool called 'GPU-Z' (if you want to install GPU-Z is up to you), when GPU-Z is open click on the 'Sensors' tab, on this tab you can monitor

• the frequency of the GPU,
• the GPU memory clock,
• the temperature,
• the power,
• the load on the GPU,
• Etc.

I would like you to make a screenshot of GPU-Z after you have either cancelled Furmark for any reason or Furmark is finished, post this screenshot in your next reply with the result of Furmark.

 

Thanks, and thanks for your reply! *Smile

I thinkt i have changed the language now *Smile
I have linked to a new DM_log collector and a ZIP with logs and images. <- here

Furmark with temps
Attachment 97003

HD tune
Attachment 97004Attachment 97005Attachment 97006


Prime95 (after 20 min)
Attachment 97007

sfc /scannow

Now with a new feedback i didn't get before. Log is added in zip file
I tried "dism /online /cleanup-image /restorehealth" but without luck.

It said: "The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source."
Might be something here? but some also says sfc gives alot of false positives :/
Attachment 97008

Memtest86
Attachment 97010

Driver Verifier - just crashed with same BSOD as usual
Attachment 97011

 

A small issue, MemTest86 & MemTest86+, explains why you were this quickly done.
We request that you run MemTest86+ instead of MemTest86, our experience is that MemTest86+ is basically better in finding problems.
To note, 16GB could take a day to 2 days to reach 8 passes with MemTest86+.

I would say that it depends on your definition of 'false positive' in the case of SFC.
A few weeks ago I saw an issue with Avast & SFC, SFC flagged some files from Avast because the hashes were incorrect according to SFC. These cases have returned more often and it turned out that the hive holding the Avast hashes was holding wrong hashes, because of this SFC reported it as a corrupt one but that wasn't the case. That I would call a false positive.
In the case of your corruption, it is the known opencl.dll causing it. The known situation is where Nvidia replaces it with driver updates, thus replacing the Windows version with a newer version. I don't know if you have Nvidia or not, but the opencl.dll is newer than the one from Windows. I wouldn't call that a 'false positive', it has a different hash because it is different from the one Windows expects what theoretically makes it corrupt. Fortunately it does not have affect on the system *Smile


Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.How to fill in your system specs:

 

Thanks again!

I'm setting up a memtest86+ right now just to be sure *Smile

Haven't done anything about the SFC issue yet, but usually I have a AMD 7970 XFX installed. But I removed it to reduce error handling *Smile

I have now updated my current system info!

 

For now we can ignore the SFC issue *Smile

 

Okay so here is 8 passes in memtest86+
Attachment 97199

I was lucky to try another PSU and could clearly rule that out, same BSOD.

I also tried my SSD with installed Windows 10 (the exact drive and install I use) in one of my friend’s pc which is very near mine spec wise and it didn’t fail. So now it looks like a hardware issue to me….. Maybe the MOBO, the only untestable item left (now when I have ruled out PSU)?

He has: CPU: i7 6700K MOBO: ASUS Z170-PRO

Tried my SSD/Windows 10 after and it still failed into BSOD.

 

I should've read your post better and should've seen that driver verifier instructions aren't necessary.

It is a hardware issue when multiple OS crash (I assume on a clean install without any program installed)

What I would do if I was in your position is test each part of your system in the system of your friend and see what crashes and what not, it is an easy way to rule out parts *Smile
I really mean each, in 70-75 out of 100 times the software (stress) tests do find problems in my experience, but the true best test is using the parts in a different system.

 

Turns out to be the CPU *Smile Off to RMA with that one! :/ Thanks for helping *Smile

 

Good to hear you found the cause *Smile

You're welcome *Smile