Need urgent BSoD help


Oka

New member
Local time
7:03 AM
Posts
3
OS
Windows 11
Hello everyone,

So, I've recently started getting a WHEA_UNCORRECTABLE_ERROR BSoD,
I have run hardware and software diagnostics on every component in my laptop, all pass,
Nothing is overclocked.

Used windows memory diagnostics and Lenovo system diagnostics on RAM, no issues,
Used Intel diagnostic tool and Lenovo system diagnostics on the processor, no issues,

Did the same for almost every component, no issues.

Event logger shows some unusual things, however, I'm not sure if they're related.
Code:
The driver \Driver\WudfRd failed to load for the device PCI\VEN_8086&DEV_9A03&SUBSYS_380C17AA&REV_05\3&11583659&0&20.

Code:
The driver \Driver\WudfRd failed to load for the device ROOT\SYSTEM\0001.

Code:
6062 - Lso was triggered
Plus some DistributedCOM warnings.

I checked out the BDoS minidump file, I also ran !errrec on it, here's the result.
Code:
FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys
Code:
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\021222-11546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff804`58000000 PsLoadedModuleList = 0xfffff804`58c29bc0
Debug session time: Sat Feb 12 11:20:03.566 2022 (UTC + 2:00)
System Uptime: 0 days 0:03:34.186
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`58416220 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff9c01`57a6c920=0000000000000124
10: 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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffac8e90baf028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2608

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 9062

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

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

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

    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


FILE_IN_CAB:  021222-11546-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffac8e90baf028

BUGCHECK_P3: be000000

BUGCHECK_P4: 100110a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Wrath.exe

STACK_TEXT:  
ffff9c01`57a6c918 fffff804`5850171b     : 00000000`00000124 00000000`00000000 ffffac8e`90baf028 00000000`be000000 : nt!KeBugCheckEx
ffff9c01`57a6c920 fffff804`561d10c0     : 00000000`00000000 ffff9c01`57a6c9f9 ffffac8e`90baf028 ffffac8e`90baf028 : nt!HalBugCheckSystem+0xeb
ffff9c01`57a6c960 fffff804`5863fa03     : 00000000`00000000 ffff9c01`57a6c9f9 ffffac8e`90baf028 ffffac8e`8f1dfe50 : PSHED!PshedBugCheckSystem+0x10
ffff9c01`57a6c990 fffff804`5850310d     : ffffac8e`94b2aa80 ffffac8e`94b2aa80 ffffac8e`8f1dfea0 bfebfbff`7ffafbbf : nt!WheaReportHwError+0x393
ffff9c01`57a6ca60 fffff804`58503558     : 00000000`0000000a ffffac8e`00000000 00000000`00000000 00000000`0000000a : nt!HalpMcaReportError+0xb1
ffff9c01`57a6cbc0 fffff804`585033ec     : ffffac8e`8ef39580 afafafaf`00000001 00000000`00000000 afafafaf`00000000 : nt!HalpMceHandlerCore+0x138
ffff9c01`57a6cc20 fffff804`58503691     : 00000000`00000010 00000000`00000001 00000000`00000000 afafafaf`afafafaf : nt!HalpMceHandler+0xe0
ffff9c01`57a6cc60 fffff804`58502856     : 00000000`00000000 00000000`00000000 ffff9c01`57a6cef0 afafafaf`afafafaf : nt!HalpMceHandlerWithRendezvous+0xc9
ffff9c01`57a6cc90 fffff804`5850520b     : ffffac8e`8ef39580 afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf : nt!HalpHandleMachineCheck+0x62
ffff9c01`57a6ccc0 fffff804`585657f9     : afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf : nt!HalHandleMcheck+0x3b
ffff9c01`57a6ccf0 fffff804`58425dfe     : afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf : nt!KiHandleMcheck+0x9
ffff9c01`57a6cd20 fffff804`58425a28     : 00000000`00000000 00000000`00000000 00000018`9a12f1b0 00000000`00000000 : nt!KxMcheckAbort+0x7e
ffff9c01`57a6ce60 00007ff9`f4fb2949     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
00000018`9a12f150 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`f4fb2949


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5371cb52-c3d9-558e-47d4-d31c09567ca2}

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

10: kd> !errrec ffffac8e90baf028
===============================================================================
Common Platform Error Record @ ffffac8e90baf028
-------------------------------------------------------------------------------
Record Id     : 01d81ff1382d2d25
Severity      : Fatal (1)
Length        : 1067
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/12/2022 9:20:03 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffac8e90baf0a8
Section       @ ffffac8e90baf1c8
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    @ ffffac8e90baf0f0
Section       @ ffffac8e90baf288
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    @ ffffac8e90baf138
Section       @ ffffac8e90baf308
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    @ ffffac8e90baf180
Section       @ ffffac8e90baf42c
Offset        : 1028
Length        : 39
Flags         : 0x00000000
Severity      : Informational

*** Unknown section format ***

I just got this laptop and I still have 2 years of installments to pay it off, I would genuinely appreciate any help.

Thank you.
 

My Computer

System One

  • OS
    Windows 11

philc43

BSOD Analyst
Member
VIP
Local time
6:03 AM
Posts
83
OS
Windows 10
These hardware related BSODs can be very difficult to diagnose as you have found out. You have done all the right things and all I can do is help you understand what you have found.

1. Diagnostic tests are sometimes useful but in my experience they do not always find a problem when there is one so the best way is usually to swap test components. This is not easy to do unless you have lost of spare parts so I would recommend that you return your system under warranty for repair - if it is out of warranty you may have to try and borrow parts for further testing.

2. The !errrec result is suggesting an unknown error on proc 0 bank 0. This does not necessarily mean the CPU is faulty just that the error is being reported by the CPU. Do you have multiple BSODs that we can look at to build up a picture of all the crashes? Please post the V2 log collector results as requested in the Posting Instructions.
 

My Computers

System One System Two

  • OS
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender
  • Operating System
    Win 11
    Computer type
    Laptop
    Manufacturer/Model
    Microsoft Surface 3
    CPU
    Intel i5 - 10th gen
    Memory
    8GB
    Graphics card(s)
    Intel Iris plus

Oka

New member
Thread Starter
Local time
7:03 AM
Posts
3
OS
Windows 11
These hardware related BSODs can be very difficult to diagnose as you have found out. You have done all the right things and all I can do is help you understand what you have found.

1. Diagnostic tests are sometimes useful but in my experience they do not always find a problem when there is one so the best way is usually to swap test components. This is not easy to do unless you have lost of spare parts so I would recommend that you return your system under warranty for repair - if it is out of warranty you may have to try and borrow parts for further testing.

2. The !errrec result is suggesting an unknown error on proc 0 bank 0. This does not necessarily mean the CPU is faulty just that the error is being reported by the CPU. Do you have multiple BSODs that we can look at to build up a picture of all the crashes? Please post the V2 log collector results as requested in the Posting Instructions.
It's in warranty, however, warranties can get a bit scammy here, so I'm exploring other options since they can force me to pay a hefty sum if the problem isn't 100% hardware. It's a laptop, so I cannot change its parts.

It is worth mentioning that I also got a system threat exception and an IRQL not less or equal, however, 95% of BSoD are WHAE,
The BSoD mostly only occurs 5 minutes after turning on a game or so.

Thank you so much for your help. I appreciate it.

Here's the file you requested.
 

My Computer

System One

  • OS
    Windows 11
Local time
10:33 AM
Posts
5
OS
windows11
One thing you can do is to backup your data, remove all partitions, recreate the partitions, format everything and reinstall the os fresh and run the os as vanilla as possible without installing any drivers except the one gets installed by windows itself. Run the machine for a week or so to make sure it runs perfectly. If this goes well you can ensure that the problem is of some 3rd party driver or software. If you are getting issues in the testing week with vanilla os stage you can probably assume its something hardware related.
 

My Computer

System One

  • OS
    windows11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self Built
    CPU
    AMD Ryzen5 3600
    Motherboard
    Asus tuf gaming x570-plus
    Memory
    2x16 Gb Corsair Vengeance Lpx DDR4 3200MHz
    Graphics Card(s)
    Zotac GTX 1660 super
    Sound Card
    built-in
    Monitor(s) Displays
    Benq GW2780
    Screen Resolution
    1080p
    Hard Drives
    250 GB Silicon power PCIe Gen3x4
    2x 4TB Toshiba HDD
    PSU
    Antec EA750G pro 750 Watt Semi- Modular
    Case
    NZXT H Series H510 Matte Black Tempered Glass ATX
    Cooling
    Deepcool Gammaxx GT RGB
    Keyboard
    Logitech G213 Prodigy
    Mouse
    Logitech G402
    Internet Speed
    100 Mbps
    Browser
    Chrome
    Antivirus
    Comodo Firewall & windows defender ( hardened with DefenderUI)

philc43

BSOD Analyst
Member
VIP
Local time
6:03 AM
Posts
83
OS
Windows 10
It's in warranty, however, warranties can get a bit scammy here, so I'm exploring other options since they can force me to pay a hefty sum if the problem isn't 100% hardware. It's a laptop, so I cannot change its parts.

It is worth mentioning that I also got a system threat exception and an IRQL not less or equal, however, 95% of BSoD are WHAE,
The BSoD mostly only occurs 5 minutes after turning on a game or so.

Thank you so much for your help. I appreciate it.

Here's the file you requested.
Please upload the file - it is missing from your post.
 

My Computers

System One System Two

  • OS
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender
  • Operating System
    Win 11
    Computer type
    Laptop
    Manufacturer/Model
    Microsoft Surface 3
    CPU
    Intel i5 - 10th gen
    Memory
    8GB
    Graphics card(s)
    Intel Iris plus

philc43

BSOD Analyst
Member
VIP
Local time
6:03 AM
Posts
83
OS
Windows 10
The 0x124 WHEA errors are all pointing to the same "unknown error proc 0 bank 0". This is highly suggestive of a CPU failure. I would try and contact the supplier and ask them if they would be prepared to change the CPU under warranty based on the evidence you have found.

I am not sure of the value of more diagnostic testing but you could try running in safemode for a day or two to see if it still crashes - if it does this would rule out any 3rd party driver cause and confirm it is hardware. The problem is that you are limited in what you can do in safemode.

Another test we sometimes recommend for CPUs is Prime95. See Prime95 - Stress Test Your CPU
 

My Computers

System One System Two

  • OS
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender
  • Operating System
    Win 11
    Computer type
    Laptop
    Manufacturer/Model
    Microsoft Surface 3
    CPU
    Intel i5 - 10th gen
    Memory
    8GB
    Graphics card(s)
    Intel Iris plus

tomdsr

Fighting Cancer :(
Member
VIP
Local time
10:03 PM
Posts
110
Location
Little Island Near Seattle
OS
Windows 11
It's in warranty, however, warranties can get a bit scammy here, so I'm exploring other options since they can force me to pay a hefty sum if the problem isn't 100% hardware. It's a laptop, so I cannot change its parts.

It is worth mentioning that I also got a system threat exception and an IRQL not less or equal, however, 95% of BSoD are WHAE,
The BSoD mostly only occurs 5 minutes after turning on a game or so.

Thank you so much for your help. I appreciate it.

Here's the file you requested.
How are warranties scammy? Did you pay by credit card? Who is the vendor/merchant?
 

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

zbook

Well-known member
Power User
VIP
Local time
12:03 AM
Posts
1,122
OS
Windows 10
The logs displayed a brand new Win 11 OS installation with four WHEA 124 and one Bugcheck A.

There were also live kernel events with WHEA and 193.

It's best that you document the problems and contact Lenovo for warranty replacement.

Run the Lenovo Custom diagnostics again overnight with all tests and take pictures to record the tests performed with results.




If you want to perform additional testing you can place the computer into safe mode as philc43 commented.



Another option is to make a free backup image then clean install Windows 10 (not 11).




Install no drivers or applications and monitor the computer for unexpected restarts using reliability monitor.


If there are BSOD this further supports malfunctioning hardware.


If there are no unexpected shutdowns and restarts then add drivers.

If there are no unexpected shutdowns and restarts with Lenovo drivers then add applications.

If there are no unexpected shutdowns and restarts with Windows 10, drivers, and applications then clean install Windows 11 and test again without drivers and applications.

If at anytime there are recurrent BSOD you can reassess.

Make sure that the Windows drive always has > 30 GB of free space.

Software can stress test the hardware but unfortunately there are a significant number of false negatives.

For component testing you can also run OCCT: (run each for 1 hour: CPU, Linpack, Memory, 3D, VRAM, Power)
Prime95 is excellent but unlike Prime95 you're able to step away form the computer.

 

My Computer

System One

  • OS
    Windows 10
    Computer type
    Laptop
    Manufacturer/Model
    HP
    CPU
    Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
    Motherboard
    Product : 190A Version : KBC Version 94.56
    Memory
    16 GB Total: Manufacturer : Samsung MemoryType : DDR3 FormFactor : SODIMM Capacity : 8GB Speed : 1600
    Graphics Card(s)
    NVIDIA Quadro K3100M; Intel(R) HD Graphics 4600
    Sound Card
    IDT High Definition Audio CODEC; PNP Device ID HDAUDIO\FUNC_01&VEN_111D&DEV_76E0
    Hard Drives
    Model Hitachi HTS727575A9E364
    Antivirus
    Microsoft Defender
    Other Info
    Mobile Workstation

zbook

Well-known member
Power User
VIP
Local time
12:03 AM
Posts
1,122
OS
Windows 10
Your thread in Ten Forums was just viewed:

Both operating systems have been tested?

So it is unlikely an operating system problem.

Continue with the Lenovo warranty support.
 

My Computer

System One

  • OS
    Windows 10
    Computer type
    Laptop
    Manufacturer/Model
    HP
    CPU
    Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
    Motherboard
    Product : 190A Version : KBC Version 94.56
    Memory
    16 GB Total: Manufacturer : Samsung MemoryType : DDR3 FormFactor : SODIMM Capacity : 8GB Speed : 1600
    Graphics Card(s)
    NVIDIA Quadro K3100M; Intel(R) HD Graphics 4600
    Sound Card
    IDT High Definition Audio CODEC; PNP Device ID HDAUDIO\FUNC_01&VEN_111D&DEV_76E0
    Hard Drives
    Model Hitachi HTS727575A9E364
    Antivirus
    Microsoft Defender
    Other Info
    Mobile Workstation

x BlueRobot

Active member
Member
Local time
6:03 AM
Posts
102
OS
Windows 11
I personally wouldn't install any other operating systems or run any further tests; this can void your warranty if you aren't careful. The best option is return the machine and request for a full refund. I would not allow them to carry out any testing, they'll usually do this to ensure that the machine goes beyond its warranty period.
 

My Computer

System One

  • OS
    Windows 11
Top Bottom