
Solved!
Go to SolutionMemory Dump W10 Precision 3420
I have a user with a Precision 3420, fully Windows updated and Dell driver updated, who, is getting a rash of Blue Screens lately. No changes in hardware or software. The error message was WHEA_UNCORRECTABLE ERROR (124).
In the past I would do Windows and driver updates and that solved it. Not this time. Here is the BugCheck analysis:
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`37a00000 PsLoadedModuleList = 0xfffff804`3862a2d0
Debug session time: Mon Feb 28 15:21:31.308 2022 (UTC - 5:00)
System Uptime: 0 days 0:01:47.959
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`00497018). Type ".hh dbgerr001" for details
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`37df7610 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffda00`33746910=0000000000000124
7: 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: ffffc48f1c71b028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4249
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 5596
Key : Analysis.Init.CPU.mSec
Value: 1186
Key : Analysis.Init.Elapsed.mSec
Value: 10763
Key : Analysis.Memory.CommitPeak.Mb
Value: 95
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffc48f1c71b028
BUGCHECK_P3: b2000000
BUGCHECK_P4: 10005
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: AdAppMgrSvc.exe
STACK_TEXT:
ffffda00`33746908 fffff804`37eb442a : 00000000`00000124 00000000`00000000 ffffc48f`1c71b028 00000000`b2000000 : nt!KeBugCheckEx
ffffda00`33746910 fffff804`36f715b0 : 00000000`00000000 ffffc48f`1c71b028 ffffc48f`03ceea30 ffffc48f`1c71b028 : nt!HalBugCheckSystem+0xca
ffffda00`33746950 fffff804`37fb636e : 00000000`00000000 ffffda00`337469f9 ffffc48f`1c71b028 ffffc48f`03ceea30 : PSHED!PshedBugCheckSystem+0x10
ffffda00`33746980 fffff804`37eb5d51 : ffffc48f`1c710be0 ffffc48f`1c710be0 ffffc48f`03ceea80 ffffc48f`03ceea30 : nt!WheaReportHwError+0x46e
ffffda00`33746a60 fffff804`37eb60c3 : 00000000`00000007 ffffc48f`03ceea80 ffffc48f`03ceea30 00000000`00000007 : nt!HalpMcaReportError+0xb1
ffffda00`33746bd0 fffff804`37eb5fa0 : ffffc48f`03ac00b8 f6fd2fe8`00000001 00000000`00000000 0020ba00`03871f84 : nt!HalpMceHandlerCore+0xef
ffffda00`33746c20 fffff804`37eb61f1 : 00000000`00000008 00000000`00000001 00000000`00000000 0386db84`0fc08548 : nt!HalpMceHandler+0xe0
ffffda00`33746c60 fffff804`37eb545b : 00000000`00000000 00000000`00000000 ffffda00`33746ef0 8b492847`8d491868 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffda00`33746c90 fffff804`37eb7ca5 : ffffc48f`03ac00b8 184f8d4d`10478d49 ce8b4820`24448948 000e23e8`08428d4c : nt!HalpHandleMachineCheck+0x5f
ffffda00`33746cc0 fffff804`37f0d659 : fffd70e9`02518d41 048b4a38`468b49ff 25bbffff`feefe9d0 48484f8b`48c00002 : nt!HalHandleMcheck+0x35
ffffda00`33746cf0 fffff804`37e066fa : ed854d00`0386ed85 23e9ffff`fde1840f c0000225`bb000387 ccccccff`fffda5e9 : nt!KiHandleMcheck+0x9
ffffda00`33746d20 fffff804`37e063b7 : 00000000`00000000 00000000`00000000 00000000`03f82d92 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffda00`33746e60 00000000`741d82e8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
00000000`006fd21c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x741d82e8
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_MAE_INTERNAL_PARITY_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7e2584db-2def-9a86-cc7c-1fcc158fa39a}
Followup: MachineOwner
---------
7: 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: ffffc48f1c71b028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2796
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2781
Key : Analysis.Init.CPU.mSec
Value: 5453
Key : Analysis.Init.Elapsed.mSec
Value: 170527
Key : Analysis.Memory.CommitPeak.Mb
Value: 98
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffc48f1c71b028
BUGCHECK_P3: b2000000
BUGCHECK_P4: 10005
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: AdAppMgrSvc.exe
STACK_TEXT:
ffffda00`33746908 fffff804`37eb442a : 00000000`00000124 00000000`00000000 ffffc48f`1c71b028 00000000`b2000000 : nt!KeBugCheckEx
ffffda00`33746910 fffff804`36f715b0 : 00000000`00000000 ffffc48f`1c71b028 ffffc48f`03ceea30 ffffc48f`1c71b028 : nt!HalBugCheckSystem+0xca
ffffda00`33746950 fffff804`37fb636e : 00000000`00000000 ffffda00`337469f9 ffffc48f`1c71b028 ffffc48f`03ceea30 : PSHED!PshedBugCheckSystem+0x10
ffffda00`33746980 fffff804`37eb5d51 : ffffc48f`1c710be0 ffffc48f`1c710be0 ffffc48f`03ceea80 ffffc48f`03ceea30 : nt!WheaReportHwError+0x46e
ffffda00`33746a60 fffff804`37eb60c3 : 00000000`00000007 ffffc48f`03ceea80 ffffc48f`03ceea30 00000000`00000007 : nt!HalpMcaReportError+0xb1
ffffda00`33746bd0 fffff804`37eb5fa0 : ffffc48f`03ac00b8 f6fd2fe8`00000001 00000000`00000000 0020ba00`03871f84 : nt!HalpMceHandlerCore+0xef
ffffda00`33746c20 fffff804`37eb61f1 : 00000000`00000008 00000000`00000001 00000000`00000000 0386db84`0fc08548 : nt!HalpMceHandler+0xe0
ffffda00`33746c60 fffff804`37eb545b : 00000000`00000000 00000000`00000000 ffffda00`33746ef0 8b492847`8d491868 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffda00`33746c90 fffff804`37eb7ca5 : ffffc48f`03ac00b8 184f8d4d`10478d49 ce8b4820`24448948 000e23e8`08428d4c : nt!HalpHandleMachineCheck+0x5f
ffffda00`33746cc0 fffff804`37f0d659 : fffd70e9`02518d41 048b4a38`468b49ff 25bbffff`feefe9d0 48484f8b`48c00002 : nt!HalHandleMcheck+0x35
ffffda00`33746cf0 fffff804`37e066fa : ed854d00`0386ed85 23e9ffff`fde1840f c0000225`bb000387 ccccccff`fffda5e9 : nt!KiHandleMcheck+0x9
ffffda00`33746d20 fffff804`37e063b7 : 00000000`00000000 00000000`00000000 00000000`03f82d92 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffda00`33746e60 00000000`741d82e8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
00000000`006fd21c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x741d82e8
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_MAE_INTERNAL_PARITY_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7e2584db-2def-9a86-cc7c-1fcc158fa39a}
Followup: MachineOwner
---------
ANy help is greatly appreciated
Responses (0)
Solutions (0)
