Windows 10: Please Help: BSOD (MACHINE_CHECK_EXCEPTION (9c)

*******************************************************************************
* *
* 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: ffffab01f3ca0d20
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.17763.503 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffab01f3ca0d20

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x9C_GenuineIntel

CPU_COUNT: 8

CPU_MHZ: d0d

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 1a

CPU_STEPPING: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: ME

ANALYSIS_SESSION_TIME: 05-22-2019 21:38:19.0182

ANALYSIS_VERSION: 10.0.18362.1 x86fre

BAD_STACK_POINTER: ffffab01f3ca0ce8

LAST_CONTROL_TRANSFER: from fffff8063b2c1f4f to fffff8063a9beef0

STACK_TEXT:
ffffab01`f3ca0ce8 fffff806`3b2c1f4f : 00000000`0000009c 00000000`00000000 ffffab01`f3ca0d20 00000000`00000000 : nt!KeBugCheckEx
ffffab01`f3ca0cf0 fffff806`3b2c23c1 : 00000000`00000008 ffffab01`f3ca1050 00000000`00000000 00000000`00000008 : hal!HalpMcaReportError+0x113
ffffab01`f3ca0e40 fffff806`3b2c15dc : 00000000`00000000 ffffab01`f3ca10d0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x131
ffffab01`f3ca0e70 fffff806`3b2c2607 : ffff8084`1409f6b0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffffab01`f3ca0ea0 fffff806`3aa971b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffffab01`f3ca0ed0 fffff806`3a9cd87a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
ffffab01`f3ca0f00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7a


THREAD_SHA1_HASH_MOD_FUNC: 1846948e522468ba82f2e885638405883bf2094b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 952edff0ade2d9727cab0ddd605a52059843acc3

THREAD_SHA1_HASH_MOD: b6bbaa1564c589ceedf361754e46684469a6106a

FOLLOWUP_IP:
nt!KiHandleMcheck+10
fffff806`3aa971b0 0fb705b3712b00 movzx eax,word ptr [nt!KiSpeculationFeatures+0x2 (fffff806`3ad4e36a)]

FAULT_INSTR_CODE: b305b70f

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: nt!KiHandleMcheck+10

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 6105701f

IMAGE_VERSION: 10.0.17763.503

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 10

FAILURE_BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KiHandleMcheck

BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KiHandleMcheck

PRIMARY_PROBLEM_CLASS: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KiHandleMcheck

TARGET_TIME: 2019-05-22T04:40:25.000Z

OSBUILD: 17763

OSSERVICEPACK: 503

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2021-07-31 11:45:35

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17763.503

ANALYSIS_SESSION_ELAPSED_TIME: 2641

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9c_genuineintel_stackptr_error_nt!kihandlemcheck

FAILURE_ID_HASH: {f10d6786-a78f-4993-4f62-7de145ea1ce2}

Followup: MachineOwner
---------

:)

 

MACHINE_CHECK_EXCEPTION BSODS error

Hi Danicela,

Thank you for posting in Microsoft Community. I understand that you are getting the error MACHINE_CHECK_EXCEPTION BSODS be rest assured, we are happy to help you.

Appreciate you for trying to fix the issue by yourself.

There area lot of CPU functions that are disabled in safe mode ( You may use your favorite search engine and perform a search). Let's follow the steps below and try resolving the issue.

First run the hardware and device troubleshooter and check.

• 
  Type troubleshooting in the search bar.
  
• 
  Click view all in the left panel.
  
• 
  Select ‘Hardware and devices' and follow the on-screen instructions.
  

I suggest you to contact your manufacturer and update the BIOS. Machine Check Exception is related to the BIOS. After BIOS is updated, it should be fine.

Hope this post helps. Get back to us for further queries. We are happy to help!

 

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

"

 

MACHINE_CHECK_EXCEPTION bsod

well i recently built my friend a computer with the following specs

Athlon II x2 250(3ghz),
g.skill 4gb 2x2gb ddr2 1066,
Biostar TA790GX XE AM2+/AM3
OCZ modxstrem Pro 600w

now we put it together no problem, it boots up fine every time. The problem we're having is that i insert the windows vista installation disc and it starts to load but every single time it gets to the end of the loading bar there's bout 2 sec where the screen is blackish n then a BSOD stating this

MACHINE_CHECK_EXCEPTION

now i googled this real quick as i have to go to work and what i found out is that this is usually due to a hardware issue. But wouldn't there be other side affects? i have to go to work but any comments will be greatly appreciated. be back at 9.