Windows 10: BSOD WHEA Uncorrectable Error when running games.

Discus and support BSOD WHEA Uncorrectable Error when running games. in Windows 10 BSOD Crashes and Debugging to solve the problem; Whoops, missed that link the first time. Giving it another go I'm restarting and I now have the proper verifier settings in there. Discussion in 'Windows 10 BSOD Crashes and Debugging' started by zbook, Apr 5, 2018.

  1. CHeinz Win User

    BSOD WHEA Uncorrectable Error when running games.


    Whoops, missed that link the first time. Giving it another go I'm restarting and I now have the proper verifier settings in there.
     
    CHeinz, Apr 24, 2018
    #16
  2. CHeinz Win User

    So it finally crashed again after several hours of running two different games, then when I walked away and left it basically on desktop without running any intensive programs it crashed. I'm trying to run the dump file through the log collector, but now the log collector doesn't seem to work, when I open it it looks like a red error message paragraph is flashing at the top too quickly to read, then the window closes itself even when I run as administrator. I'm also not totally certain what the verifier is doing in the background or how to collect any information from it.

    EDIT: Figured out log collector and am attaching newest dump file.
     
    CHeinz, Apr 24, 2018
    #17
  3. zbook New Member
    The bugcheck on the BSOD mini dump was WHEA 0x124
    There was no memory dump.

    Code: Common Platform Error Record @ ffffc506708fe8f8-------------------------------------------------------------------------------Record Id : 01d3dc337f26bfbaSeverity : Fatal (1)Length : 928Creator : MicrosoftNotify Type : Machine Check ExceptionTimestamp : 4/25/2018 1:19:55 (UTC)Flags : 0x00000002 PreviousError===============================================================================Section 0 : Processor Generic-------------------------------------------------------------------------------Descriptor @ ffffc506708fe978Section @ ffffc506708fea50Offset : 344Length : 192Flags : 0x00000001 PrimarySeverity : FatalProc. Type : x86/x64Instr. Set : x64Error Type : BUS errorOperation : GenericFlags : 0x00Level : 3CPU Version : 0x0000000000600f20Processor ID : 0x0000000000000000===============================================================================Section 1 : x86/x64 Processor Specific-------------------------------------------------------------------------------Descriptor @ ffffc506708fe9c0Section @ ffffc506708feb10Offset : 536Length : 128Flags : 0x00000000Severity : FatalLocal APIC Id : 0x0000000000000000CPU 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 00Proc. Info 0 @ ffffc506708feb10===============================================================================Section 2 : x86/x64 MCA-------------------------------------------------------------------------------Descriptor @ ffffc506708fea08Section @ ffffc506708feb90Offset : 664Length : 264Flags : 0x00000000Severity : FatalError : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4) Status : 0xf600000000070f0f Address : 0x00000000d0009d40 Misc. : 0x0000000000000000[/quote] The logs had displayed another bug check.

    How many active tests are there now at one time with Windows driver verifier?
     
    zbook, Apr 24, 2018
    #18
  4. CHeinz Win User

    BSOD WHEA Uncorrectable Error when running games.

    There are 3 active tests on every non-windows driver, just like in the link. Are there more tests I need to add in?
     
    CHeinz, Apr 24, 2018
    #19
  5. zbook New Member
    Yes
    View the Microsoft link.
    On this link there are approximately 19 tests.
    So always maintain the 3 tests and increase 3 - 4 tests every 2 hours so that you eventually use all of the tests to test all of the non-Microsoft drivers. If you have problems you can remove some tests but make sure you maintain the initial 3 tests and rotate the rest of tests if necessary. The goal is to have all of the non-Microsoft drivers tested with all 19 tests. The more that you can use at any one time the better.
     
    zbook, Apr 24, 2018
    #20
  6. CHeinz Win User
    Ok I've added a few more tests and made sure it's running with the elevated command prompt. So now when I crash it will give additional information in the dump file if it detects a problem with one of the drivers? There's nothing else I need to manually do myself with it?
     
    CHeinz, Apr 24, 2018
    #21
  7. zbook New Member
    If you can run all 19 tests at the same time and produce more BSOD that is the best option. You must be able to turn off the tool with each BSOD. As more BSOD dump files debugged there will be more information about the misbehaving drivers or malfunctioning hardware.
     
    zbook, Apr 24, 2018
    #22
  8. CHeinz Win User

    BSOD WHEA Uncorrectable Error when running games.

    With every test running on the driver verifier, I was given two different BSODs. First, I was given:

    Stop code: DRIVER VERIFIER DETECTED VIOLATION
    What failed: AvidMBox.sys

    I already knew that this is my audio interface for pro tools, so I removed it and the security dongle from their respective usb slots in the back, then I was given another one that now said:

    Stop code: DRIVER VERIFIER DETECTED VIOLATION
    What failed: GM312Fltr.sys

    A quick google search led me to believe that was probably my gaming mouse, so I unplugged that and finally was able to boot windows, as the verifier /reset and /bootmode commands did not work as they're meant to and I couldn't disable the verifier, so I just kept removing the supposed problem devices.

    Right now I'm using a spare mouse that doesn't seem to crash it while I disable the tests for the moment and I included the newest dump file after these errors, thought curiously it said "0kb" next to this dmp file so I hope it has additional info and isn't just empty. I have however had a hard time getting it to crash organically since yesterday, as it no longer seems to crash after a brief time running games or other intensive software.
     
    CHeinz, Apr 24, 2018
    #23
  9. zbook New Member
    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:[/quote]
    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[/quote]
     
    zbook, Apr 24, 2018
    #24
  10. CHeinz Win User
    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.
     
    CHeinz, Apr 25, 2018
    #25
  11. zbook New Member
    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![/quote] 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.
     
    zbook, Apr 25, 2018
    #26
  12. CHeinz Win User
    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.
     
    CHeinz, Apr 26, 2018
    #27
Thema:

BSOD WHEA Uncorrectable Error when running games.

Loading...
  1. BSOD WHEA Uncorrectable Error when running games. - Similar Threads - BSOD WHEA Uncorrectable

  2. Whea Uncorrectable Error in games.

    in Windows 10 Gaming
    Whea Uncorrectable Error in games.: Hello,I get a BSOD Whea Uncorrectable Error when playing a games.I've reinstalled the GPU driver with DDU in safemode, repasted the CPU and GPU, SFCScan, Memtest64 and did Heaven Benchmark. but bsod still occurs when I play the game for around 30-60 minutes. Strangely, BSOD...
  3. Whea Uncorrectable Error in games.

    in Windows 10 Software and Apps
    Whea Uncorrectable Error in games.: Hello,I get a BSOD Whea Uncorrectable Error when playing a games.I've reinstalled the GPU driver with DDU in safemode, repasted the CPU and GPU, SFCScan, Memtest64 and did Heaven Benchmark. but bsod still occurs when I play the game for around 30-60 minutes. Strangely, BSOD...
  4. whea uncorrectable error when gaming

    in Windows 10 Gaming
    whea uncorrectable error when gaming: I have a newly built PC that is giving me a blue screen when gaming, it doesn't give me bluescreen in fortnite or rocket league but I get it in warzone and minecraft bedrock. The following errors are associated with a blue screen received with the code reading...
  5. whea uncorrectable error when gaming

    in Windows 10 Software and Apps
    whea uncorrectable error when gaming: I have a newly built PC that is giving me a blue screen when gaming, it doesn't give me bluescreen in fortnite or rocket league but I get it in warzone and minecraft bedrock. The following errors are associated with a blue screen received with the code reading...
  6. Whea Uncorrectable Error in games.

    in Windows 10 Gaming
    Whea Uncorrectable Error in games.: Hello,There is a problem that i have for almost a year. Every time i launch a "heavy" 3d game i get a BSOD Whea Uncorrectable Error. Before i get BSOD game freezes for 1-3 seconds and PC stops responding but not freezing, can push windows Ui buttons, move mouse, when i played...
  7. Whea Uncorrectable Error in games.

    in Windows 10 Software and Apps
    Whea Uncorrectable Error in games.: Hello,There is a problem that i have for almost a year. Every time i launch a "heavy" 3d game i get a BSOD Whea Uncorrectable Error. Before i get BSOD game freezes for 1-3 seconds and PC stops responding but not freezing, can push windows Ui buttons, move mouse, when i played...
  8. Whea Uncorrectable Error in games.

    in Windows 10 BSOD Crashes and Debugging
    Whea Uncorrectable Error in games.: Hello,There is a problem that i have for almost a year. Every time i launch a "heavy" 3d game i get a BSOD Whea Uncorrectable Error. Before i get BSOD game freezes for 1-3 seconds and PC stops responding but not freezing, can push windows Ui buttons, move mouse, when i played...
  9. BSOD Whea Uncorrectable Error during gaming

    in Windows 10 BSOD Crashes and Debugging
    BSOD Whea Uncorrectable Error during gaming: My PC worked totally fine until this past week where I keep on getting BSOD whenever I'm playing games usually after like an hour or so. It didn't matter to what game I was playing, from Stardew Valley to Apex Legends my PC would crash to the blue screen. I made a post on...
  10. WHEA UNCORRECTABLE ERROR BSOD while gaming

    in Windows 10 BSOD Crashes and Debugging
    WHEA UNCORRECTABLE ERROR BSOD while gaming: I've had this problem before happen to me but it somehow was fixed after I was told to uninstall Avast as it was rarely known to be the cause of this problem. But this time I've no clue why it came back, it may actually be a hardware problem this time around but since my...

Users found this page by searching for:

  1. error code 260 roblox language:en