Windows 10: Random MACHINE_CHECK_EXCEPTION (9c) Occurrences

What I've done so far:
-Checked every possible component for failure.
CPU, RAM, Video Card. Ran various stress tests, no errors occurred.
-Reinstalled Windows 10 twice.
Once I left the updater to download all the recommended rivers
The second time I downloaded the recommended Vendor drivers.
Tried using the desktop with and without the Asus drivers, similarly did that with the Intel drivers.
After a period of stability (10 days or so), the BSODs returned. Google Chrome usually causes those errors to appear more frequently than other browsers.
-Updated the BIOS.
-Event Viewer doesn't have any related errors. around the time the crash happened

The specs are in my profile.

Attachment 157346

:)

 

BSOD - MACHINE_CHECK_EXCEPTION (9c)

Hello everyone,

I've been having troubles lately with my computer crashing randomly and inconsistently. I've done a full research and also done the following steps to see if this got fixed, but had no luck with it.

- I checked the mini dump file to try to pinpoint the problem and this is what I found. It seems to be related to error 9C which I also found useful information from this forum

BSOD: Stop 0x0000009C

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, ffffe68036845820, 0, 0}

Probably caused by : intelppm.sys ( intelppm!MWaitIdle+18 )

Followup: MachineOwner

- I ran !analyze -v to further check the issue and this is the result:

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

* *

* Bugcheck Analysis *

* *

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

MACHINE_CHECK_EXCEPTION (9c)

A fatal Machine Check Exception has occurred.

KeBugCheckEx parameters;

x86 Processors

If the processor has ONLY MCE feature available (For example Intel

Pentium), the parameters are:

1 - Low 32 bits of P5_MC_TYPE MSR

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of P5_MC_ADDR MSR

4 - Low 32 bits of P5_MC_ADDR MSR

If the processor also has MCA feature available (For example Intel

Pentium Pro), the parameters are:

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

IA64 Processors

1 - Bugcheck Type

1 - MCA_ASSERT

2 - MCA_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing MCA.

3 - MCA_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.

4 - MCA_FATAL

FW reported a fatal MCA.

5 - MCA_NONFATAL

SAL reported a recoverable MCA and we don't support currently

support recovery or SAL generated an MCA and then couldn't

produce an error record.

0xB - INIT_ASSERT

0xC - INIT_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing INIT event.

0xD - INIT_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.

0xE - INIT_FATAL

Not used.

2 - Address of log

3 - Size of log

4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO

AMD64 Processors

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

Arguments:

Arg1: 0000000000000000

Arg2: ffffe68036845820

Arg3: 0000000000000000

Arg4: 0000000000000000

Debugging Details:

------------------

BUGCHECK_STR: 0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff803b86c7b9d to fffff803b7f71580

STACK_TEXT:

ffffe680`368457e8 fffff803`b86c7b9d : 00000000`0000009c 00000000`00000000 ffffe680`36845820 00000000`00000000 : nt!KeBugCheckEx

ffffe680`368457f0 fffff803`b86c7fe7 : 00000000`00000004 ffffe680`36845af0 00000000`00000000 00000000`00000004 : hal!HalpMcaReportError+0xf5

ffffe680`36845940 fffff803`b86c8120 : ffffc30b`420c87f0 ffffe680`36845b70 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x12b

ffffe680`36845970 fffff803`b7f7b6bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40

ffffe680`368459a0 fffff803`b7f7b42c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b

ffffe680`36845ae0 fffff803`2ed71388 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1ac

ffffe680`36c5b858 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18

STACK_COMMAND: kb

FOLLOWUP_IP:

intelppm!MWaitIdle+18

fffff803`2ed71388 c3 ret

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: intelppm!MWaitIdle+18

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.15063.413

BUCKET_ID_FUNC_OFFSET: 18

FAILURE_BUCKET_ID: 0x9C_GenuineIntel_intelppm!MWaitIdle

BUCKET_ID: 0x9C_GenuineIntel_intelppm!MWaitIdle

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9c_genuineintel_intelppm!mwaitidle

FAILURE_ID_HASH: {b437bf01-d2c2-2e2f-fa19-a64dea7afbde}

Followup: MachineOwner

---------

I've also tried to google why the specific driver is failing but had no luck with it. Any help would be highly appreciated .

PS: I would also like to add that I followed/tried all of these steps and none of them fixed the problem.

"

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Download Speccy | Find your computer specs, free!

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - 3 Easy Ways to Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *9C or *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite, AI Charger software, etc. If you have something like this software-wise, remove it ASAP (which I see you do have Asus
software installed).

"

 

BSOD - MACHINE_CHECK_EXCEPTION (9c)

Hello Ernie,

I downloaded the "Intel Driver & Support Assistance" software to check all drivers on my PC as suggested, but it is informing me that all the drivers are up to date. Is there anything else that I can do to properly check on this ? All other dump files are
showing the same error each time it crashes.

 

Rule 4
No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc) - it is forum policy that no help shall be given to people who knowingly steal software or services.

One of the main reasons for this is that the act of pirating the software will inevitably change the working of the software and make investigation and repair impossible. Please install a legitimate copy of the software and if you are still experiencing the issue we will be please to assist - No further assistance will be provided until we are satisfied that the software is genuine.

Theres a tool which is used to bypass the activation of microsoft products. If you are sure you did not use a tool like this, maybe a friend or store tech did it without your knowledge.