BSOD WHEA Uncorrectable Error when running games.

zbook · 25 Apr 2018

The latest mini dump collected by the log collector was dated 4/24/2018 20:20.
Whenever there is a BSOD please run the beta log collector so that there are dump files for debugging.
There was only 1 BSOD mini dump file collected with the latest beta log collector and it displayed bugcheck WHEA 0x124.

These drivers were not in any of the dump files submitted:
AvidMBox.sys
GM312Fltr.sys

Open file explorer > this PC > C: > in the right upper corner search for:

a) C:\Windows\minidump
4/25/2018 12:03 PM 0 042518-26375-01.dmp
4/25/2018 11:59 AM 0 042518-48500-01.dmp

b) C:\Windows\memory.dmp > zip > post one driver or drop box share link
Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 04/25/2018 12:03:52
Size on disk: 649 MB

All files prior to April 24 have disappeared.
Which method was used on the operating system?
How many windows driver verifier tests were you able to run simultaneously and use the startup repair: safe mode with command prompt typing verifier /reset?
If possible the tests that allow and don't allow the command to work can be identified by increasing/decreasing the number of tests? Then you could use the tests that work with the command.

Code:

4/25/2018 1:30 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 124
P2: 0
P3: ffffc506708fe8f8
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\042418-81421-01.dmp
\\?\C:\WINDOWS\TEMP\WER-111828-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7188.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7199.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER71AA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_55a2ef8c9967637c449be5abd9ba69dcac93537c_00000000_cab_10a49b33

Analysis symbol: 
Rechecking for solution: 0
Report Id: c0be6a49-2d0a-4548-a614-2817ebdec684
Report Status: 2049
Hashed bucket:4/25/2018 1:23 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 124
P2: 0
P3: ffffc506708fe8f8
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\042418-81421-01.dmp
\\?\C:\WINDOWS\TEMP\WER-111828-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7188.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7199.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER71AA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_55a2ef8c9967637c449be5abd9ba69dcac93537c_00000000_031371b6

Analysis symbol: 
Rechecking for solution: 0
Report Id: c0be6a49-2d0a-4548-a614-2817ebdec684
Report Status: 4
Hashed bucket:
4/24/2018 9:49 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c2
P2: 9b
P3: 200
P4: c0
P5: fffff808bd9d68bd
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\042418-26609-01.dmp
\\?\C:\WINDOWS\TEMP\WER-43281-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER23C1.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_5fe32184df2fd48df7ade568c45d5d8cbeecfc8_00000000_cab_046649bd

Analysis symbol: 
Rechecking for solution: 0
Report Id: e3a4d1eb-c06f-4fcd-a39f-2d58e9440902
Report Status: 2049
Hashed bucket:

Code:

Common Platform Error Record @ ffffc506708fe8f8-------------------------------------------------------------------------------
Record Id     : 01d3dc337f26bfba
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/25/2018 1:19:55 (UTC)
Flags         : 0x00000002 PreviousError


===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffc506708fe978
Section       @ ffffc506708fea50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal


Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000000


===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffc506708fe9c0
Section       @ ffffc506708feb10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal


Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00


Proc. Info 0  @ ffffc506708feb10


===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffc506708fea08
Section       @ ffffc506708feb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal


Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xf600000000070f0f
  Address     : 0x00000000d0009d40
  Misc.       : 0x0000000000000000

CHeinz · 26 Apr 2018

The mini dump folder only has one dmp file in there from yesterday at 11:59 and it's apparently empty, as it says 0kb and won't let me upload it on onedrive because of that. Oddly enough, I also don't see any sign of a MEMORY.DMP anywhere, even after searching in file explorer under this pc, and navigating manually through the C: drive to windows, there's only one from yesterday that isn't current. The command prompt verifier /reset never worked even when only running three tests, nor did trying any of the different bootmodes to get it to shut off. As it stands however I have yet to experience another crash, which is a little annoying as I know it can still happen and I haven't done anything that would have fixed it yet.

zbook · 26 Apr 2018

The generation of dump files has been inconsistent.
Sometimes there may be memory or mini dumps and other times there can be a crash without dump formation.

Code:

Event[461]:  Log Name: System
  Source: volmgr
  Date: 2018-04-24T20:25:43.401
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: CameronsGayComputer
  Description: 
Crash dump initialization failed!

This problem occurs on many computers.
The aim with windows driver verifier is to create as many dumps as possible so that these dumps can be troubleshooted to find misbehaving drivers or malfunctioning hardware.

If you have backed up files or made a backup image you can perform a clean install. This would fix any operating system or registry problem, allow you to install fresh drivers, and best assess a WHEA 0x124 bugcheck.

At this time you can also try an in place upgrade repair. This should keep all files and applications. Some custom settings may have to be reset. This fixes many operating system problems but often does not fix deeper or registry problems.

Repair Install Windows 10 with an In-place Upgrade Windows 10 Tutorials
Download Windows 10

Clean Install Windows 10 Windows 10 Tutorials

The safe mode with command prompt verifier /reset should work with just 3 tests.
The settings can be modified so that there is only 1 test used. However there must be a BSOD dump for you to see whether the command turns off Windows driver verifier. It is something that you can use trial and error to see which single test can produce a BSOD and whether the command works for a single test.

With WHEA 0x124 we check the major hardware components: CPU, GPU, Drives, RAM.

Please indicate whether you are able to perform a clean install.
There are two methods that can be used after the clean install.

The first method is to install new drivers, reinstall applications, and files.
Then stress test the hardware.

The second method is a "vanilla type" clean install.
This method has fewer confounding factors as drivers, applications and files are not reinstalled.
The drivers in use are only the Windows 10 iso installed drivers.
If there are no BSOD then computer or motherboard manufacturer drivers are installed.

The first method is substantially faster than the second method.

CHeinz · 26 Apr 2018

I've actually already done two clean installs of windows 10 in the past week, as pretty much all of my important data is saved on an external drive, so I think two days ago I reinstalled windows and have only crashed once since then without maxing the driver verifier. It was while just on the desktop too, without any heavy programs running.

Actually I still haven't ever used Memtest so I think I'll try that although I was told whea uncorrectable error is usually not memory based.

zbook · 26 Apr 2018

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)
http://www.hdtune.com/
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