Windows 10: BSOD WHEA Uncorrectable Error when running games.

If you have a second computer or if you can use this computer for a period of time as only a "vanilla type" clean install then you can test the hardware without any confounding factors.

These are steps to check the hardware before moving to testing as a vanilla type clean install.

1) Make sure that there is no over clocking while troubleshooting.
2) Sometimes there are problems in the bios that produce bsod.
The BIOS: Version/Date American Megatrends Inc. 2101, 12/2/2014 SMBIOS Version 2.5
3) Please check to see if this is the most up to date version.
4) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.
5) To ensure that there are no improper bios settings please reset the bios.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

6) When testing for WHEA hardware errors we need to systematically check CPU, GPU, RAM and drive.

Once the bios is reset and there is no overclocking:

7) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

8) Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU Windows 10 Tutorials
24a) Record the maximum temperature and post the maximum temperature into the thread
24b) Record test duration and post the uninterrupted test duration into the thread
24c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
24d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 Windows 10 Tutorials

9) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 12 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM Windows 10 Tutorials

10) Run HD Tune (free edition)
HD Tune website
Post images into the thread for test results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 Windows 10 Tutorials

11) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Windows 10 Tutorials
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
a) Record the maximum temperature and post the maximum temperature into the thread.
b) Record the test duration and post the uninterrupted test duration into the thread.
c) Aim for testing 1 hour.
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 Windows 10 Tutorials

12) All of these test should be done with the bios reset and no over clocking.

13) For each of the above tests please record maximum temperatures.

14) And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

15) Open administrative command prompt and type or copy and paste: chkdsk /x /f /r
C:\Windows\system32>chkdsk /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

Run the command on all drives using the syntax: chkdsk /x /f /r C: or chkdsk /x /f /r D: changing the drive letter to the applicable drive.
This may take many hours to run so plan to run it overnight.

16) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials

 

Essentially, a few days ago my computer started crashing after variable lengths of time after running games, which is unusual as nothing had changed between when it started and prior to this development, as everything has been running fine for about two years. This thread I have on Tom's Hardware has all pertinent information thus far and it would be easier to understand the issue through this: BSOD Crashing when running games. - Windows 10 - Toms Hardware
Any assistance in further diagnosing specifically what is causing this issue would be greatly appreciated!

:)

 

Whea uncorrectible error help.

I have a problem with my computer. My computer gets the blue screen error whea uncorrectible error when I play most of my steam games. What I think is that it is the directx but that is my best guest. I have a windows 10 custom gaming computer.

 

Getting WHEA_UNCORRECTABLE_ERROR while installing VMware or Virtual Box.

Hi Siva,

How to fix whea uncorrectable error

https://support.microsoft.com/en-us...845cfc1d6/how-to-fix-whea-uncorrectable-error

Thank you.

 

See posting instructions.
Run the beta log collector (extract > open) > zip > post into the thread

Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Windows 10 Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)
https://www.tenforums.com/profile.php?do=extra

 

I've attached the log collector info, mysteriously the minidump folder is now empty even though I still have the first log after I reinstalled windows 10 a couple days ago here: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. and I even ran a game to make it crash just now in the attempt of having it create a new dump file but it didn't seem to. System specs are updated, a curious note as a reply I got on Tom's Hardware, apparently one of the times I crashed the computer only managed to load one driver which was for my iLok dongle for the Pro Tools 12 software, however that crash was kind of unusual as I can usually have my computer running for well over 24 hours as long as I don't run any games (not sure about other processor intensive programs, such as pro tools as I haven't ran it for an extended period so far).

 

The posted zip was empty.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
6) After the above steps re-run the beta log collector using the text and images in this link (post #5)
DM Log tool problem Solved - Windows 10 Forums
(extract > open)
Windows 10 Help Forums

7) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

8) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

 

Microsoft Windows [Version 10.0.16299.371](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.371[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 973824 file records processed.File verification completed. 36704 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 20374 reparse records processed. 1103534 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 20374 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 64856 data files processed.CHKDSK is verifying Usn Journal... 36364592 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 487821311 KB total disk space. 188977168 KB in 358194 files. 239588 KB in 64857 indexes. 0 KB in bad sectors. 1107211 KB in use by the system. 65536 KB occupied by the log file. 297497344 KB available on disk. 4096 bytes in each allocation unit. 121955327 total allocation units on disk. 74374336 allocation units available on disk.C:\WINDOWS\system32>


I don't have CCleaner but this should be everything.

 

Oops can't see how to delete post

 

Hi CHeinz ,

Welcome to the Ten Forums BSOD forum.

The logs on the computer start on 4/19/2017.
There were no mini or memory dump files to debug.

For startup and recovery system failure un-check automatically restart.
Then reboot.
With automatically restart un-checked you will see a BSOD window.
The BSOD window should display : ( with a bugcheck.
Sometimes it may display the misbehaving driver in the form *.sys.
If you see the misbehaving driver please record it and post it into the thread.
There is a counter which rises to 100%.
Please make sure that you allow this counter to rise to 100% before rebooting so that there is sufficient time to create the dump files.

Windows driver verifier is a tool that is used to create BSOD.
The BSOD are then troubleshooted to find misbehaving drivers or malfunctioning hardware.
The tool will repetitively produce BSOD until all misbehaving drivers are fixed or until the tool is turned off.

Backup important files to another drive or to the cloud.
Make a backup image using Macrium.
Place the backup image onto another drive or into the cloud.
Make a brand new restore point.

Use the information in this link for the Windows driver verifier test settings.
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Use the information in this link for the methods to turn off or recover from using the tool:
Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials

The Windows driver verifier tool will be used for 48 hours.
After the last BSOD it will be used for an additional 36 hours of typical computer use.
When using the tool the computer may become sluggish and the boots may become slow.
If there are significant problems the test settings can be modified.

Once the tool is started the methods to turn off the tool or recover from using the tool are performed using the Windows advanced troubleshooting menu.
Review the above link so that you are comfortable with the safe mode with command prompt command:
verifier /reset
Also become familiar with the command prompt verifier /bootmode resetonbootfail
The 3rd option is system restore and this often leads to a loss of the BSOD file so only use this method if the other methods do not work to turn off the tool.

After each BSOD post a new beta zip into the thread.
The tool that we use to debug BSOD crashes enables us to provided deeper debugging than other software.
After each BSOD you can run Whocrashed to see if it finds the misbehaving driver > update the driver > restart windows driver verifier to find the next misbehaving driver.

Open file explorer > this PC > C: > in the right upper corner search for C:\Windows\memory.dmp > zip > post into the thread using a one drive or drop box share link

 

The BSOD screen that pops up upon restart says:
"Stop code: BAD POOL CALLER"
"What Failed: Wdf01000.sys"

I'm now on my laptop at the moment as I'm trying to get out of this infinite loop of BSOD errors upon restarting, I tried the reset commands in safe mode with command prompt but they didn't seem to solve it so I may have to restore. I read that that specific driver is the Kernel Mode Driver Framework Runtime, but I'm not 100% sure what that means and how to go about fixing that.

 

The BSOD mini dump and memory dump files when debugged may indicate the misbehaving driver(s) or malfunctioning hardware.
To turn off Windows driver verifier were you able to open startup options?
1) startup options > click restart > select #6 safe mode with command prompt > type: verifier /reset
2) if the above command fails then open command prompt > Administrator: X:\Windows\System32\cmd.exe > X:\Sources> type:
verifier /bootmode resetonbootfail
3) if the above 2 commands fail then use system restore. Unfortunately system restore often leads to a loss of the BSOD dump files. If you have to do restore you can look for the files and post them. Run the beta log collector after each BSOD.

 

Both of those commands failed to work and I was still stuck in an infinite BSOD loop of rebooting so I had to restore, unfortunately it seems none of the dump files were saved, so I may have to just intentionally run some programs that I know will crash it in order to have something to diagnose. As for the Driver Verifier Manager, what settings should I use when activating that? The standard settings and automatically select unsigned drivers, or is there something else I should be doing with that?

 

The settings for Windows driver verifier can be modified.
Either the number of drivers tested at one time or the number of tests performed.
Turn on Windows driver verifier using the test settings in this link:
Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials

The link from Microsoft had approximately 19 tests running.
The link from Ten Forums has approximately 3 tests running.
If you are able to recover using just 3 tests, the number of tests will be increased so that all drivers are exposed to the same tests over time.

 

When you select drivers from a list > click on the column heading: provider > this should sort all of the drivers > then check all drivers that are not Microsoft drivers.
So you will be testing all drivers with 3 tests.
Again if you are able to recover you will then add tests (3 - 4 at a time) while always maintaining the first 3 tests.