WHEA Uncorrectable Error - Mini dump file

Question

Hi there, I recently upgrade my MoBo and CPU but my system keeps crashing. After installing the new hardware system crashed as soon as i signed in then I updated all drivers and the crashing stopped. But today again system start crashing again,my big guess is the CPU is faulty. I downloaded an app from the store and collected some data drom the mini dump files which reports what happened but I'm not sure how to interpret them. I'll paste the report, if someone can help me reading it I'd appreciate it. Many Thanks.

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

*                                                                             *

*                        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: ffffd006bb6c7028, Address of the nt!_WHEA_ERROR_RECORD structure.

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

Arg4: 0000000000200135, 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: 2500

    Key : Analysis.DebugAnalysisManager

    Value: Create

    Key : Analysis.Elapsed.mSec

    Value: 10352

    Key : Analysis.Init.CPU.mSec

    Value: 405

    Key : Analysis.Init.Elapsed.mSec

    Value: 76958

    Key : Analysis.Memory.CommitPeak.Mb

    Value: 81

    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: 112321-5109-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd006bb6c7028

BUGCHECK_P3: be000000

BUGCHECK_P4: 200135

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Corsair.Service.CpuIdRemote64.exe

STACK_TEXT:

ffffab81182ff908 fffff8075d0b453a     : 0000000000000124 0000000000000000 ffffd006bb6c7028 00000000be000000 : nt!KeBugCheckEx

ffffab81182ff910 fffff807595915b0     : 0000000000000000 ffffd006bb6c7028 ffffd006b42e1020 ffffd006bb6c7028 : nt!HalBugCheckSystem+0xca

ffffab81182ff950 fffff8075d1b61de     : 0000000000000000 ffffab81182ff9f9 ffffd006bb6c7028 ffffd006b42e1020 : PSHED!PshedBugCheckSystem+0x10

ffffab81182ff980 fffff8075d0b5e61     : ffffd006bb947900 ffffd006bb947900 ffffd006b42e1070 ffffd006b42e1020 : nt!WheaReportHwError+0x46e

ffffab81182ffa60 fffff8075d0b61d3     : 0000000000000007 ffffd006b42e1070 ffffd006b42e1020 0000000000000007 : nt!HalpMcaReportError+0xb1

ffffab81182ffbd0 fffff8075d0b60b0     : ffffd006b3cefec8 8b48000000000001 0000000000000000 3300000080858948 : nt!HalpMceHandlerCore+0xef

ffffab81182ffc20 fffff8075d0b6301     : 0000000000000010 0000000000000001 0000000000000000 24448948000f003f : nt!HalpMceHandler+0xe0

ffffab81182ffc60 fffff8075d0b556b     : 0000000000000000 0000000000000000 ffffab81182ffef0 4830244c8b48014e : nt!HalpMceHandlerWithRendezvous+0xc9

ffffab81182ffc90 fffff8075d0b7db5     : ffffd006b3cefec8 d88bff99c2c2e820 00000129880fc085 48000000b8878b4c : nt!HalpHandleMachineCheck+0x5f

ffffab81182ffcc0 fffff8075d10d4c9     : 0107880fc085d88b 0000c0878b4c0000 0003d2a8158d4800 d49ee830244c8b48 : nt!HalHandleMcheck+0x35

ffffab81182ffcf0 fffff8075d0063fa     : d376158d48000001 e830244c8b480003 c085d88bff95d47c 8b4c000000c3880f : nt!KiHandleMcheck+0x9

ffffab81182ffd20 fffff8075d0060b7     : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x7a

ffffab81182ffe60 00007ff9a3d97ecc     : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277

000000b2811fcb00 0000000000000000     : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff9`a3d97ecc

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

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup:     MachineOwner

Answer

Was it really compatible with the MOBO?

I'd suggest doing a Prime95 test to check for issues: https://www.tenforums.com/tutorials/16474-prime95-stress-test-your-cpu.html

NOTE: If the device overheats during the stress test, immediately stop the stressing to avoid hardware damage.

@@@@@@@@@@@@@@@@@@@@

If the proc is fully compatible with the MOBO, please try to set your power mode to Performance mode, as users here reported that it worked for them: https://www.sysnative.com/forums/threads/0x124-caused-by-genuineintel-workarounds-dont-let-cpu-mhz-drop-disable-intelppm-disable-speedstep-change-power-plan-settings-remove-under-clock.32907/

Also update your Windows.

Answer

No overclocking at all. Everything running as usual. Idk this CPU gave bad vibes when i got it. It has a dint at the top and it was kind greasy, ive always bought my items new from Amazon and never bought from Newegg so I'm returning it.

Answer

Are you overclocking your proc?

Answer

Thanks for your answer. As I said this mobo is brand new and cpu is a "refurbished" item from Newegg. I applied the correct amount of thermal paste and download all drivers. System was crashing at the beginning then stabilized for couple of days and now crashing again.

Been running system on safe mode and CPU temp are below 40 C.

Answer

The cause is listed as GenuineIntel.sys and it seems to ME like the processor is causing the issues.

While using the device, please check if it's overheating too much, if it does, apply thermal paste on top of the processor properly and make sure the MOBO doesn't have any dust.

If not done already, go to the MOBO manufacturer's official site and download the latest and recommend chipset driver(s) compatible with your device, and install it / them. Also download the latest firmware file and update your firmware.

Share via

WHEA Uncorrectable Error - Mini dump file

7 answers