WHEA UNCORRECTABLE ERROR - BSOD

Question

WHEA UNCORRECTABLE ERROR - BSOD

Anonymous

Constant BSOD screen from a week

I attach the dmp file:

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: ffff9d036159d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f6100780, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000060010, Low order 32-bits of the MCi_STATUS value.

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

fffff807316283b8: Unable to get Flags value from nt!KdVersionBlock
fffff807316283b8: Unable to get Flags value from nt!KdVersionBlock
fffff807316283b8: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4718

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 36104

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1

    Key  : WHEA.MCiStatus.Code
    Value: 0xf610078000060010

    Key  : WHEA.MCiStatus.McaError
    Value: 0x0010

    Key  : WHEA.MCiStatus.ModelError
    Value: 0x0006

    Key  : WHEA.MCiStatus.Reserved
    Value: 0x00100780

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9d036159d028

BUGCHECK_P3: f6100780

BUGCHECK_P4: 60010

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  2

PROCESS_NAME:  dwm.exe

STACK_TEXT:  
ffff8d00`3f7ccad8 fffff807`311a4178     : 00000000`00000124 00000000`00000000 ffff9d03`6159d028 00000000`f6100780 : nt!KeBugCheckEx
ffff8d00`3f7ccae0 fffff807`32981920     : ffff9d03`5a7e4e70 00000000`00000000 ffff9d03`6159d028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
ffff8d00`3f7ccb20 fffff807`31540052     : ffff9d03`5a7e4e70 ffff8d00`3f7ccba9 00000000`00000000 ffff9d03`6159d028 : PSHED!PshedBugCheckSystem+0x10
ffff8d00`3f7ccb50 fffff807`311a5ad6     : ffff8d00`3f7ccc70 00000000`00000001 ffff9d03`5a7e4ec0 ffff9d03`5a7e4e70 : nt!WheaReportHwError+0x382
ffff8d00`3f7ccc10 fffff807`311a5f6a     : 00000000`00000010 ffff9d03`5a7e4ec0 ffff8d00`3f7ccdc8 ffff8d00`3f7cd010 : hal!HalpMcaReportError+0x72
ffff8d00`3f7ccd70 fffff807`311a5e44     : ffff9d03`5a6b69a0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
ffff8d00`3f7ccdc0 fffff807`311a60b0     : 00000000`00000006 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
ffff8d00`3f7cce00 fffff807`311a5158     : 00000000`00000000 ffff8d00`3f7cd090 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffff8d00`3f7cce30 fffff807`311a6337     : ffff9d03`5a6b69a0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffff8d00`3f7cce60 fffff807`314a42d0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffff8d00`3f7cce90 fffff807`313d2afa     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
ffff8d00`3f7ccec0 fffff807`313d27af     : 00000000`00000000 00000000`00000000 00000293`4bed5950 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff8d00`3f7cd000 00007ffc`94e1881c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f
000000dd`7ae7d400 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`94e1881c

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_BANK0_MSCOD0006_MCACOD0010_PCC_UC_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {42c21059-a8a3-ac4c-c29f-5d0f8ab0967b}

Followup:     MachineOwner.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

5 answers

Answer 1

Hi Cristian,

I'm Independent Advisor not Microsoft employee or support person. I have deep enough Windows knowledge and you may trust me. It's a pleasure for me to help others and I'll do all my best to help you.

This bug check is typically related to physical hardware failures. It can be heat related, defective hardware, memory or even a processor that is beginning to fail or has failed. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory is not defective. It is less likely, but possible that a driver is causing the hardware to fail with this bug check.

Repair system files by

DISM.exe /Online /Cleanup-Image /RestoreHealth

command from Windows PowerShell (administrator) environment.

Update or at least reinstall graphic driver.

Answer 2

Anonymous

Remove your RAM, clean the RAM contacts with alcohol and blow out the RAM slots using compressed air. Replace the RAM one stick at a time, boot and check stability before powering down, replacing another RAM stick and repeating.

0 comments

Answer 3

Hi Igor, thank you for your reply.

I've assembled this pc almost one year ago and these crashes started to happen from a week ago.

I've already done twice a clean install of Windows 10 and it continue to crash almost every day while browsing using netflix or during gaming.

I've done stress test with Prime95 for about one hour with stable temperature around 70 C and the Memtest for about an hour and it doesn't show me a single error.

The cpu is not overcloked, same as the ram. The XMP profile is not active.

I've noticed that in the dmp file the PROCESS_NAME: dwm.exe and it shows MODULE_NAME: GenuineIntel .

It could be something related to the CPU or the module GenuineIntel has nothing to do with that?

For the Graphics card, i've already update the drivers from Nvidia.

Thank you.

Answer 4

Thank you Igor for you reply.

After updating to the last versione of Windows 10, the blue screen came back, with some difference on the log.

Here the last dmp log:

*******************************************************************************

* *

* 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: ffffb18dece3c028, Address of the WHEA_ERROR_RECORD structure.

Arg3: 00000000f611b840, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000000060010, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

fffff8003d40f330: Unable to get Flags value from nt!KdVersionBlock

*************************************************************************

*** ***

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