BSOD MACHINE_CHECK_EXCEPTION

Zoram 96 Reputation points
2021-05-01T20:20:41.31+00:00

The computer is just a few months old, and it gets a BSOD once every few days. It nearly always happens at night.
The error is sometimes MACHINE_CHECK_EXCEPTION, sometimes WHEA_UNCORRECTABLE_ERROR.

I ran memtest86, Intel Processor Diagnostics, Prime95, OCCT - none of them have any issues.

I replaced my PSU with an old one that I know is working fine, but it didn't help.

There is no overclocking, and no graphics card.

I have minidumps, but unsure how to attach to this question.

Specs: Windows 10 Pro, i7-9700K, B365M DS3H (motherboard).

Here is a summary of the error, copied from WinDbg:

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.

Debugging Details:

KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2858
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 19064
Key : Analysis.Init.CPU.mSec
Value: 312
Key : Analysis.Init.Elapsed.mSec
Value: 4779
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
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

BUGCHECK_CODE: 9c
BUGCHECK_P1: 80000001
BUGCHECK_P2: ffffaa000b7e6b30
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
BAD_STACK_POINTER: ffffaa000b7e6ae8

STACK_TEXT:
ffffaa000b7e6ae8 fffff8067a0b5619 : 000000000000009c 0000000080000001 ffffaa000b7e6b30 0000000000000000 : nt!KeBugCheckEx
ffffaa000b7e6af0 fffff8067a0b5a74 : 0000000000000008 ffffaa000b7e6e70 0000000000000000 0000000000000008 : nt!HalpMcaReportError+0x149
ffffaa000b7e6c60 fffff8067a0b4c8b : 0000000000000000 0000000080000001 ffffaa000b7e6ef0 ef3bfb6496659275 : nt!HalpMceHandlerWithRendezvous+0x11c
ffffaa000b7e6c90 fffff8067a0b74d5 : ffffbf8cd76cad40 03c21cac60a5675d e0f07086da81f8bf ee39f3308ccae531 : nt!HalpHandleMachineCheck+0x5f
ffffaa000b7e6cc0 fffff8067a10cc79 : ba05590ece0d35e7 bc4d5ff848e84b99 5bfcae3278a45edb 7c05fe3c150bdc2d : nt!HalHandleMcheck+0x35
ffffaa000b7e6cf0 fffff8067a004efa : 96096e3a3d39a983 045bfe8409ffbc15 52b9211e5e39b337 a3a5e88898213369 : nt!KiHandleMcheck+0x9
ffffaa000b7e6d20 fffff8067a004bb7 : 0000000000000000 fffff8067a004aec 0000000000000002 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffaa000b7e6e60 fffff8068880138f : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
ffffa28c9f63f5b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : intelppm!MWaitIdle+0x1f

SYMBOL_NAME: intelppm!MWaitIdle+1f
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
IMAGE_VERSION: 10.0.19041.1134
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1f
FAILURE_BUCKET_ID: 0x9C_SPURIOUS_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {1e3f83d3-dcec-5c94-4c1c-54ecb2a7abc1}

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,697 questions
Accepted answer
  1. Zoram 96 Reputation points
    2021-05-13T18:58:50.41+00:00

    Since it only happened at night, it made sense that the issue happened when the CPU entered some deep sleep state (C-state).
    I disabled the C-states in the BIOS, and haven't had any BSOD since (for 7 days).

    What I wonder is, do these C-state crashes mean that the CPU is faulty, or the motherboard, or something else?

    I will enable the C-states one by one, waiting a week after each, to see which one it was that was causing the issue.

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. S.Sengupta 15,511 Reputation points MVP
    2021-05-02T00:26:26.737+00:00

    You will find attachment button [ the clip image in toolbar above> click on it > select either Upload or Drop the minidump file from computer.

  2. Jenny Feng 14,081 Reputation points
    2021-05-03T07:48:40.513+00:00

    @Zoram
    Hi,
    MACHINE_CHECK_EXCEPTION is pretty much always a hardware issue. Often CPU, but sometimes RAM, cache or even defective PSU.
    This is another MACHINE_CHECK _EXCEPTION STOP Error, this points to a hardware defect.
    https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x124---whea-uncorrectable-error
    In view of the greater possibility of hardware errors, I think you should consult the manufacturer
    Please understand due to security policy and from our professional level, we do not provide dump/log analysis. In addition, if this problem is more urgent for you I still recommend that you open a case to Microsoft for further professional help.
    https://support.microsoft.com/en-us/help/4341255/support-for-business

    Hope above information can help you.

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  3. Docs 15,146 Reputation points
    2021-05-04T06:44:04.64+00:00

    For bugchecks 9C and WHEA 124 you can perform hardware stress tests using software to potentially find the malfunctioning hardware.
    (you ran commonly used tests)
    (additional common tests are available for drive and GPU)

    These tests do not directly test the motherboard.

    If the tests, when properly performed, did not display the malfunctioning hardware then options are:

    a) swap testing

    b) contacting the component manufacturer or vendor for Return Merchandise Authorization (RMA)

    0 comments