BSOD anlysis help WHEA_UNCORRECTABLE_ERROR

Question

Microsoft (R) Windows Debugger Version 10.0.22000.194 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.

Dump completed successfully, progress percentage: 100

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff80611800000 PsLoadedModuleList = 0xfffff80612429bc0
Debug session time: Sat Feb 12 03:20:27.433 2022 (UTC + 8:00)
System Uptime: 0 days 0:04:59.675
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000a7`cc412018). Type ".hh dbgerr001" for details
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
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: ffff908ada2ab028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000014, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 5296

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 16632

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

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

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

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

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff908ada2ab028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 14

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: MsMpEng.exe

STACK_TEXT:
ffffde01979888f8 fffff80611d0171b : 0000000000000124 0000000000000000 ffff908ada2ab028 00000000b2000000 : nt!KeBugCheckEx
ffffde0197988900 fffff8060f3210c0 : 0000000000000000 ffffde01979889d9 ffff908ada2ab028 ffff908ada2ab028 : nt!HalBugCheckSystem+0xeb
ffffde0197988940 fffff80611e3fa03 : 0000000000000000 ffffde01979889d9 ffff908ada2ab028 ffff908ad6329540 : PSHED!PshedBugCheckSystem+0x10
ffffde0197988970 fffff80611d0310d : ffff908ada238070 ffff908ada238070 ffff908ad6329590 bfebfbff7ffafbbf : nt!WheaReportHwError+0x393
ffffde0197988a40 fffff80611d03558 : 0000000000000003 ffff908a00000003 ffffb38fabb29000 0000000000000003 : nt!HalpMcaReportError+0xb1
ffffde0197988ba0 fffff80611d033ec : ffff908ad6327eb0 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandlerCore+0x138
ffffde0197988c00 fffff80611d03691 : 0000000000000008 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandler+0xe0
ffffde0197988c40 fffff80611d02856 : 0000000000000000 0000000000000000 ffffde0197988ed0 0000000000000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffde0197988c70 fffff80611d0520b : ffff908ad6327eb0 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHandleMachineCheck+0x62
ffffde0197988ca0 fffff80611d657f9 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalHandleMcheck+0x3b
ffffde0197988cd0 fffff80611c25dfe : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x9
ffffde0197988d00 fffff80611c25a28 : 0000000000000010 0000000000000000 ffff908ae1d78e10 0000000000000000 : nt!KxMcheckAbort+0x7e
ffffde0197988e40 fffff80611b30504 : ffff908ada61fac0 0000000000000000 ffff908ada61fac0 0000000000000000 : nt!KiMcheckAbort+0x2a8
ffffb38fabb2ed10 fffff80611b303c9 : ffff908ae1d78e10 ffffa308a66da060 0000000000000001 fffff80611b34cc7 : nt!ExpAcquireResourceSharedLite+0x84
ffffb38fabb2edc0 fffff80611f5848f : ffffa308a139d700 0000000000000001 0000000000000000 ffff908ad8dc9a30 : nt!ExAcquireResourceSharedLite+0x39
ffffb38fabb2ee00 fffff806205110d8 : ffff908ad8d8bad0 ffffb38f00000000 ffff908ae7f020d0 fffff80611b2ee05 : nt!SeQueryInformationToken+0x9f
ffffb38fabb2ef20 fffff806205202da : ffffb38fabb2f0d0 ffff908ae7f3ba88 0000000000000001 0000000000000030 : bindflt!BfGetMappingContexts+0xc8
ffffb38fabb2efd0 fffff8060f357034 : 0000000000000000 ffff908ae7f3b900 ffff908ae7f3ba88 ffffb38fabb2f200 : bindflt!BfPreCreate+0x17a
ffffb38fabb2f160 fffff8060f356ae6 : ffffb38fabb2f300 fffff8060f358800 0000000000000000 fffff80611f74600 : FLTMGR!FltpPerformPreCallbacksWorker+0x374
ffffb38fabb2f270 fffff8060f38d960 : ffffb38fabb30000 ffffb38fabb29000 ffff908ad8d8bad0 fffff80611f53319 : FLTMGR!FltpPassThroughInternal+0xc6
ffffb38fabb2f2c0 fffff80611b03115 : ffff908ae9ba1600 ffff908ad8d89630 0000000000000000 0000000000000000 : FLTMGR!FltpCreate+0x300
ffffb38fabb2f370 fffff80611f54007 : ffff908ad8d89630 ffff908ad8d89630 ffffb38fabb2f670 ffff908a00000040 : nt!IofCallDriver+0x55
ffffb38fabb2f3b0 fffff80611f733c1 : ffffb38fabb2f5b0 ffffa3089f83dc00 0000000000000000 ffffa3089f83dbd0 : nt!IopParseDevice+0x897
ffffb38fabb2f570 fffff80611f723c1 : 0000000000000000 ffffb38fabb2f7a0 0000000000000040 ffff908ad6357c40 : nt!ObpLookupObjectName+0xac1
ffffb38fabb2f710 fffff80611f0648f : ffff908a00000000 0000000000000001 ffff908ae771caa0 000000a7ce2ff058 : nt!ObOpenObjectByNameEx+0x1f1
ffffb38fabb2f840 fffff80611f06069 : 000000a7ce2ff018 000000a7ce2feec8 000000a7ce2ff058 000000a7ce2ff020 : nt!IopCreateFile+0x40f
ffffb38fabb2f8e0 fffff80611c28775 : 00000290fbfc1180 0000000000000000 000000a7ce2ff4d0 0000000000000000 : nt!NtCreateFile+0x79
ffffb38fabb2f970 00007ffa5e1441f4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000a7ce2fef98 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`5e1441f4

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_TLB_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a69b051d-c02e-962a-395d-451af6277742}

Followup: MachineOwner

---

Answer 1

WHEA 124 BSOD are almost always caused by malfunctioning hardware.

Sometimes the malfunctioning hardware can be identified by running software which stress tests the hardware.

Other times the stress testing may fail to identify the malfunctioning hardware.

For desktops swap testing can be performed.

For laptops servicing by a local computer store is typically required.

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 2

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 3

Hello

The Error whea_uncorrectable_error (124) on genuineintel.sys undoubtedly is produced by a hardware issue. The most common causes are: BIOS misconfiguration (generally related to voltage), BIOS version (some chipset/motherboard issues are fixed in later versions), overclocking software or performance profile applications, or in worse case scenario a faulty processor.

Since you haven't posted any previous actions, frequency of the BSOD, or any troubleshooting done, my suggested approach would be the next:

• Update your BIOS firmware
• Install any pending Windows Update
• Save your current BIOS settings profile, and load a default profile (usually named "Optimized default settings")
• Uninstall or disable any software that controls the voltage or frequency for the processor or RAM (or set a "balanced" plan on it)
• Run stress tests with one of the multiple CPU testing application that you can find online, for example CPUZ or Prime95

Hope this helps with your query,

---

--If the reply is helpful, please Upvote and Accept as answer--