Need urgent BSoD help

O-Okasha — Sat, 12 Feb 2022 10:38:32 GMT

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]

[CODE]The driver \Driver\WudfRd failed to load for the device ROOT\SYSTEM\0001.[/CODE]

[CODE]6062 - Lso was triggered[/CODE]
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]
[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:
------------------

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

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

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

[/CODE]

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.

topic Need urgent BSoD help in Mobile and Desktop Processors

Need urgent BSoD help