Random but frequent BSOD - whea_uncorrectable_error

  1. Posts : 5
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor

    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

    • 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)
    • 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

    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.
    Last edited by mikkel1107; 19 Aug 2016 at 02:55.
      My Computer

  2. Posts : 14,903
    Windows 10 Pro

    Hi mikkel1107,

    Welcome to the 10forums :)

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

    1. Run memtest86 - photo
    2. CMD chkdsk - log
    3. CMD sfc /scannow - log
    4. DRIVER VERIFIER - crash?
    5. Furmark - screenshot, GPU-Z with it would be nice
    6. 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 :) 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 :)
    Language - Add, Remove, and Change in Windows 10 - Windows 10 Forums

    Diagnostic Test


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note

    MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

    Make a photo of the result and post it.

    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
    If errors show up and you see them a lot later, no problem, the errors don't affect the test.

    Diagnostics Test


    Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
    Run the long test.
    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.

    Make a photo of the result and post it.

    Run chkdsk
    Disk Check - Windows 7 Help Forums
    Use option TWO with parameter /r
    Upload the chkdsk log 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


    warning   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   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


    Run Furmark to test your GPU. Furmark tutorial

    Note   Note
    Run Furmark for around 30 minutes

    warning   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.
      My Computers

  3. Posts : 5
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor
    Thread Starter

    Thanks, and thanks for your reply! :)

    I thinkt i have changed the language now :)
    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

    Attachment 97010

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

  4. Posts : 14,903
    Windows 10 Pro

    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+.

    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 :/
    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 :)

    Please fill in your system specs
    Please 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:

      My Computers

  5. Posts : 5
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor
    Thread Starter

    Thanks again!

    I'm setting up a memtest86+ right now just to be sure :)

    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 :)

    I have now updated my current system info!
      My Computer

  6. Posts : 14,903
    Windows 10 Pro

    For now we can ignore the SFC issue :)
      My Computers

  7. Posts : 5
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor
    Thread Starter

    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.
      My Computer

  8. Posts : 14,903
    Windows 10 Pro

    I should've read your post better and should've seen that driver verifier instructions aren't necessary.
    So now it looks like a hardware issue to me
    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 :)
    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.
      My Computers

  9. Posts : 5
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor
    Thread Starter

    Turns out to be the CPU :) Off to RMA with that one! :/ Thanks for helping :)
      My Computer

  10. Posts : 14,903
    Windows 10 Pro

    Good to hear you found the cause :)

    You're welcome :)
      My Computers


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:03.
Find Us

Windows 10 Forums