Solved BSOD When playing games, using chrome, and light weight programs.


Rhaged

Member
Local time
4:00 AM
Posts
9
OS
Windows 11
I originally was getting random bsod's on win10, but after mucking about with event viewer, reading mem dumps, uninstalling programs, rolling back drivers, running chksdk, sfc, dism, disabled any overclocking, tried with cpu boost off, driver verifier, redid cpu paste lowered temp by 5 'C =D (haven't done cards). I have not tried reseating, or swapping parts as I have very little parts to swap. This has been going on for around a year? The list goes on, so I got frustrated and switched to win11 got basic stuff installed and it has been fine for a whole week. I have never had a bsod while using my computer during work, it is always after later at night.

These bsod's are very very random, I can go weeks before I get one, or get 3 in the same week. Doing the same thing all the time so unsure of what causes it infrequency.



Was playing a game and everything was running great until it bsod. This most recent mem dump looks pretty close to the one I would some times get on win10. The error is not always the same. And a few times it has failed to capture the dump, which is quite aggravating. WHEA_UNCORRECTABLE_ERROR seems to be a common theme, thou I have seen some that where point towards a driver issue related to my on board raid.


Sadly any tests that require a very lengthy amount of time (4h+) will only be able to preformed on the weekend.
 
Windows Build/Version
21H2 / 22000.978

Attachments

  • RHAGED-(2022-09-18_21-26-11).zip
    623.3 KB · Views: 1

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, 369
    Motherboard
    Z370-A PRO (MS-7B48)
    Memory
    F4-2666C19-8GNT x4
    Graphics Card(s)
    NVIDIA GeForce GTX 1050 Ti / AMD Radeon R7 240

tomdsr

Fighting Cancer :(
Member
VIP
Local time
3:00 AM
Posts
118
Location
Little Island Near Seattle
OS
Windows 11
Code:
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffa88fb8914028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000c0010001, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1531

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2760

    Key  : Analysis.Init.CPU.mSec
    Value: 406

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3099

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 79

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa88fb8914028

BUGCHECK_P3: b2000000

BUGCHECK_P4: c0010001

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  TradingView.exe

STACK_TEXT:  
ffff8001`812c78f8 fffff806`3270187b     : 00000000`00000124 00000000`00000000 ffffa88f`b8914028 00000000`b2000000 : nt!KeBugCheckEx
ffff8001`812c7900 fffff806`2e5810c0     : 00000000`00000000 ffff8001`812c79d9 ffffa88f`b8914028 ffffa88f`b8914028 : nt!HalBugCheckSystem+0xeb
ffff8001`812c7940 fffff806`3283f683     : 00000000`00000000 ffff8001`812c79d9 ffffa88f`b8914028 ffffa88f`b7ef6e70 : PSHED!PshedBugCheckSystem+0x10
ffff8001`812c7970 fffff806`3270326d     : ffffa88f`bf0584c0 ffffa88f`bf0584c0 ffffa88f`b7ef6ec0 bfebfbff`0000017a : nt!WheaReportHwError+0x393
ffff8001`812c7a40 fffff806`327036b8     : 00000001`00000003 ffffa88f`b7ef6e70 ffffa88f`b80c9980 00000001`00000003 : nt!HalpMcaReportError+0xb1
ffff8001`812c7ba0 fffff806`3270354c     : ffffa88f`b80c9980 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0x138
ffff8001`812c7c00 fffff806`327037f1     : 00000000`00000006 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffff8001`812c7c40 fffff806`327029b6     : 00000000`00000000 00000000`00000000 ffff8001`812c7ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff8001`812c7c70 fffff806`3270536b     : ffffa88f`b7d37410 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x62
ffff8001`812c7ca0 fffff806`327653e9     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffff8001`812c7cd0 fffff806`3262a9fe     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffff8001`812c7d00 fffff806`3262a628     : 00000000`00000000 00000000`00000000 7fffffff`ffffffff 00000000`00000000 : nt!KxMcheckAbort+0x7e
ffff8001`812c7e40 00007ff7`f17aeaa0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
0000007c`c19ff278 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff7`f17aeaa0


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_HYPERV_HYPERVISOR_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9eed9242-750a-f4e7-39db-cfbaa8fa0bd4}

Followup:     MachineOwner
---------

3: kd> !errrec ffffa88fb8914028
===============================================================================
Common Platform Error Record @ ffffa88fb8914028
-------------------------------------------------------------------------------
Record Id     : 01d8c80c00e0f5ac
Severity      : Fatal (1)
Length        : 1067
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 9/19/2022 2:38:09 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa88fb89140a8
Section       @ ffffa88fb89141c8
Offset        : 416
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
No valid data fields are present.

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffa88fb89140f0
Section       @ ffffa88fb8914288
Offset        : 608
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_XPF_PROCESSOR_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_XPF_PROCESSOR_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
No valid data fields are present.

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffa88fb8914138
Section       @ ffffa88fb8914308
Offset        : 736
Length        : 292
Flags         : 0x00000000
Severity      : Fatal

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_XPF_MCA_SECTION                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_XPF_MCA_SECTION                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_XPF_MCA_SECTION                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_XPF_MCA_SECTION                     ***
***                                                                   ***
*************************************************************************
Error         : Unknown (Proc 0 Bank 0)
  Status      : 0x0000000000000000

===============================================================================
Section 3     : {c34832a1-02c3-4c52-a9f1-9f1d5d7723fc}
-------------------------------------------------------------------------------
Descriptor    @ ffffa88fb8914180
Section       @ ffffa88fb891442c
Offset        : 1028
Length        : 39
Flags         : 0x00000000
Severity      : Informational
WHEA_UNCORRECTABLE_ERROR means you have a hardware failure. As you can see from the dmp file, your processor is having a problem.
Stress test your cpu
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self Built
    CPU
    Ryzen 5 3600
    Motherboard
    ASUS Prime X570-P
    Memory
    32gb DDR4 - 3200Mhz
    Graphics Card(s)
    EVGA 2060 Super KO 6GB PCIE 3.0
    Sound Card
    Realtek S1200A
    Monitor(s) Displays
    1. LG 34UM68-P 34-Inch 21:9 UltraWide IPS 2. ONN 24-Inch LCD
    Screen Resolution
    1. 2560 x 1080 2. 1920 x 1080 (side by side 4480 x 1080)
    Hard Drives
    Samsung 860 EVO 1TB SATA III SSD (OS)
    WD BLUE 2TB SATA III (DATA)
    WD BLUE 2TB SATA III (DATA)
    WD BLUE 1TB SATA III (DATA)
    PSU
    Thermaltake Toughpower PF1 750W
    Case
    Coolermaster HAF XB EVO
    Cooling
    Corsair 240mm AIO + 4x 120mm case fans
    Keyboard
    Standard Logitech
    Mouse
    Logitech M535
    Internet Speed
    Gigabit (Cable)
    Browser
    Firefox, Chrome, Edge
    Antivirus
    Defender

Rhaged

Member
Thread Starter
Local time
4:00 AM
Posts
9
OS
Windows 11
This was most likely too short of a test but ran smallest FFT for 45 min as I need to work in a bit. Aside from HW monitor not saving any logs and windows search being unusable. Everything seemed alright, max temps was 75 on all 6 cores. I will be able to do more in 7 hours, once done work.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, 369
    Motherboard
    Z370-A PRO (MS-7B48)
    Memory
    F4-2666C19-8GNT x4
    Graphics Card(s)
    NVIDIA GeForce GTX 1050 Ti / AMD Radeon R7 240

Rhaged

Member
Thread Starter
Local time
4:00 AM
Posts
9
OS
Windows 11
Coming up on 2 and half hours on running prime95, everything running pretty much normal. Temps are going between 65 - 76, mostly at 70 thou. Glad I had redone my thermal paste last week as that dropped my idle temp by 5, and in use by 10. I'd be getting worried watching it go up to 85.

Here's a HWM log
 

Attachments

  • HWMonitor.txt
    38.7 KB · Views: 1

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, 369
    Motherboard
    Z370-A PRO (MS-7B48)
    Memory
    F4-2666C19-8GNT x4
    Graphics Card(s)
    NVIDIA GeForce GTX 1050 Ti / AMD Radeon R7 240

Rhaged

Member
Thread Starter
Local time
4:00 AM
Posts
9
OS
Windows 11
Alright, 16 hours of prime95 along with 8 hours of OCCT, heck I even ran furmak after on primary gfx, for a bit. So what now run it for 32 hours??? These have been the most befalling BSOD I have ever delt with, their random and as I said in the first post not always the same. I only have one dump from win10 which was for irql_not_less_or_equal. If I remember correctly the previous dump to that was related to IaStorV which is an Intel raid controller.

I added the dump for irql_not_less_or_equal

 

Attachments

  • RHAGED-(2022-09-18_21-26-11).zip
    623.3 KB · Views: 0

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, 369
    Motherboard
    Z370-A PRO (MS-7B48)
    Memory
    F4-2666C19-8GNT x4
    Graphics Card(s)
    NVIDIA GeForce GTX 1050 Ti / AMD Radeon R7 240

Rhaged

Member
Thread Starter
Local time
4:00 AM
Posts
9
OS
Windows 11
Finally!!!! Got a new BSOD for DRIVER_IRQL_NOT_LESS_OR_EQUAL. Seen this one before I have tried using older drivers for the card but never seem to have done anything. Thou I don't ever recall that bucket ID.

Was just playing Oxygen not included, has YouTube going and a bunch of chrome tabs, this is sorta what I have running during a crash. And no it's not the game cause I have it happen without it open.

How strange was just in device manager after the last BSOD and one of my drivers is messed up. Don't know if it's related to the current crash but seems to an intel chipset driver. Well if that's bugging out might it explain the initial crash for WHEA_UNCORRECTABLE_ERROR? I swear it was there yesterday. I'll see about getting that sorted, HWID if curious PCI\VEN_8086&DEV_1911&SUBSYS_7B481462&REV_00
 

Attachments

  • RHAGED-(2022-09-25_21-34-53).zip
    730.4 KB · Views: 1

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, 369
    Motherboard
    Z370-A PRO (MS-7B48)
    Memory
    F4-2666C19-8GNT x4
    Graphics Card(s)
    NVIDIA GeForce GTX 1050 Ti / AMD Radeon R7 240

Rhaged

Member
Thread Starter
Local time
4:00 AM
Posts
9
OS
Windows 11
Alright on sept 26th had one more bsod didn't post it, as no one had even viewed the last 3 posts. But after that I re-flashed my bios was 2 version behind, reseated all components and cleaned contacts, switched from raid to ahci. And since then I have had zero problems, the original idea to stress test was a dead end as I have done more since then. I do not know which of the three things potentially has resolved my issue, but this is the longest stretch with out a bsod in a while. As everything else has remained the same.

Still unsure why that one driver vanished. The reason for switching from raid to ahci was had previous issues with raid, from bsod to high disk usage while idle. Windows wasn't very happy about the switch after I fumbled a cmd and messed up bcdedit.

So unless some one else has any idea of how to diagnose a multi bsod error problem be my guest. Cause I've seen everything from whea, to irql, ones related to raid storeai (I think), and crashes that fail to write a dump.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, 369
    Motherboard
    Z370-A PRO (MS-7B48)
    Memory
    F4-2666C19-8GNT x4
    Graphics Card(s)
    NVIDIA GeForce GTX 1050 Ti / AMD Radeon R7 240

Latest Support Threads

Top Bottom