Computer repeatedly BSODing with WHEA_Uncorrectable_Error

Question

I ran IPDT but it passed on everything. Computer typically bluescreens multiple times an hour. Dump link -> https://drive.google.com/file/d/1-u--hBZqX7NwsypOTldDBbAT6O3B4RlS/view?usp=sharing

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: ffffba06bb924028, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, 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: 2390

Key  : Analysis.Elapsed.mSec
Value: 4817

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x124

Key  : Bugcheck.Code.TargetModel
Value: 0x124

Key  : Failure.Bucket
Value: 0x124\_0\_GenuineIntel\_PROCESSOR\_\_UNKNOWN\_IMAGE\_GenuineIntel.sys

Key  : Failure.Hash
Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Key  : WER.OS.Branch
Value: ni\_release\_svc\_prod3

Key  : WER.OS.Version
Value: 10.0.22621.2506

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffba06bb924028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

FILE_IN_CAB: 041224-12828-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffdd8025cbc8e8 fffff80421cffa6b : 0000000000000124 0000000000000000 ffffba06bb924028 00000000be000000 : nt!KeBugCheckEx ffffdd8025cbc8f0 fffff804230710c0 : 0000000000000000 ffffdd8025cbc9c9 ffffba06bb924028 ffffba06b87472d0 : nt!HalBugCheckSystem+0xeb ffffdd8025cbc930 fffff80421e0ef8f : 0000000000000000 ffffdd8025cbc9c9 ffffba06bb924028 85c033fa75c085c0 : PSHED!PshedBugCheckSystem+0x10 ffffdd8025cbc960 fffff80421d0149a : ffffba06bb91a070 ffffba06bb91a070 ffffba06b8747320 fffff80421b7effe : nt!WheaReportHwError+0x38f ffffdd8025cbca30 fffff80421d018f0 : 0000000000000001 ffffba0600000003 ffffdb03dfe41000 ffffdb03dfe48000 : nt!HalpMcaReportError+0xb2 ffffdd8025cbcba0 fffff80421d01784 : ffffba06b7f66f50 ffc06b4800000001 0000000000000000 832c24440000000c : nt!HalpMceHandlerCore+0x138 ffffdd8025cbcc00 fffff80421d01a29 : 0000000000000014 0000000000000001 0000000000000000 f883c03314770841 : nt!HalpMceHandler+0xe0 ffffdd8025cbcc40 fffff80421d00be2 : 0000000000000000 0000000000000000 ffffdd8025cbced0 24848b0000008c24 : nt!HalpMceHandlerWithRendezvous+0xc9 ffffdd8025cbcc70 fffff80421d0339b : ffffba06b7f66f50 84894860c0834868 848b480000008024 408b480000008024 : nt!HalpHandleMachineCheck+0x62 ffffdd8025cbcca0 fffff80421d69999 : 44894802c0834848 00a024848b484824 7348244439480000 6b4800000002b82f : nt!HalHandleMcheck+0x3b ffffdd8025cbccd0 fffff80421c2a8be : 24548b4800c96b48 7cc13b0a0cbf0f48 b4eb00000529e905 000000d024848b48 : nt!KiHandleMcheck+0x9 ffffdd8025cbcd00 fffff80421c2a4d3 : 0000000000000010 0000000000000000 0000000000000000 ffffdd8025cbced0 : nt!KxMcheckAbort+0x7e ffffdd8025cbce40 fffff8045ef2156f : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x2d3 ffffdb03dfe474c8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : intelppm!MWaitIdle+0x1f

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.22621.2506

BUILDLAB_STR: ni_release_svc_prod3

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

Answer 1

Hi,

My name is Igor, it's a pleasure for me to help others and I'll try to help you.

This bugcheck indicates that a fatal hardware error has occurred. See details at https://docs.microsoft.com/en-us/windows-hardwa...

Unfortunately hardware errors mostly cannot be diagnosed using dump files.

Please clean PC and power supply unit from dust. Update BIOS.

Run Windows memory diagnostic tool and switch it to extended mode when it starts.

Check system journal (Event Viewer) for possible errors at these moments, especially Kernel-Power 41 (63) errors. DistributedCOM errors should be ignored.

And please repair system files by

DISM.exe /Online /Cleanup-Image /RestoreHealth

command from Windows Terminal (admin) environment.

Tell the result.