Windows 10: MACHINE_CHECK_EXCEPTION 9c

Discus and support MACHINE_CHECK_EXCEPTION 9c in Windows 10 BSOD Crashes and Debugging to solve the problem; Why this? No ctrl+v answers please, I can use google too, nothing is overclocked, the drivers, memory and processor have been checked Microsoft R... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by bobsmith3333333333, Aug 6, 2020.

  1. MACHINE_CHECK_EXCEPTION 9c


    Why this? No ctrl+v answers please, I can use google too, nothing is overclocked, the drivers, memory and processor have been checked



    Microsoft R Windows Debugger Version 10.0.19041.1 AMD64
    Copyright c Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\user\Documents\New folder\080620-32718-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 19041 MP 6 procs Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff806`33a00000 PsLoadedModuleList = 0xfffff806`3462a310
    Debug session time: Thu Aug 6 23:11:37.168 2020 UTC - 4:00
    System Uptime: 1 days 0:04:22.067
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................................
    Loading User Symbols
    Loading unloaded module list
    ..............
    For analysis of this file, run !analyze -v
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * 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 If Param 1 is < 0x80000000
    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
    AMD64 Processors If Param 1 is > 0x80000000
    1 - Failure Type
    VALUES:
    0x80000001: Spurious MCE
    2 - Address of MCA_EXCEPTION structure
    0x80000002: Rendezvous failure
    2 - Address of MCA_EXCEPTION structure
    END_VALUES
    Arguments:
    Arg1: 0000000080000001
    Arg2: fffff80637697b30
    Arg3: 0000000000000000
    Arg4: 0000000000000000

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.Sec
    Value: 1

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

    Key : Analysis.DebugData
    Value: CreateObject

    Key : Analysis.DebugModel
    Value: CreateObject

    Key : Analysis.Elapsed.Sec
    Value: 1

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

    Key : Analysis.System
    Value: CreateObject


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump

    BUGCHECK_CODE: 9c

    BUGCHECK_P1: 80000001

    BUGCHECK_P2: fffff80637697b30

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    BLACKBOXBSD: 1 !blackboxbsd


    BLACKBOXNTFS: 1 !blackboxntfs


    BLACKBOXPNP: 1 !blackboxpnp


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: javaw.exe

    BAD_STACK_POINTER: fffff80637697ae8

    STACK_TEXT:
    fffff806`37697ae8 fffff806`33ec1719 : 00000000`0000009c 00000000`80000001 fffff806`37697b30 00000000`00000000 : nt!KeBugCheckEx
    fffff806`37697af0 fffff806`33ec1b74 : 00000000`00000006 fffff806`37697e70 00000000`00000000 00000000`00000006 : nt!HalpMcaReportError+0x149
    fffff806`37697c60 fffff806`33ec0d8b : 00000000`00000000 00000000`80000001 fffff806`37697ef0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0x11c
    fffff806`37697c90 fffff806`33ec35d5 : ffffce88`d02e6990 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f
    fffff806`37697cc0 fffff806`33f18d59 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
    fffff806`37697cf0 fffff806`33decbba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
    fffff806`37697d20 fffff806`33dec877 : 00000000`00000000 00000000`00000000 00000000`ee481b50 00000000`00000000 : nt!KxMcheckAbort+0x7a
    fffff806`37697e60 00000000`03521323 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
    00000000`1f82e4b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3521323


    SYMBOL_NAME: nt!HalpMcaReportError+149

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    IMAGE_VERSION: 10.0.19041.388

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 149

    FAILURE_BUCKET_ID: 0x9C_SPURIOUS_GenuineIntel_STACKPTR_ERROR_nt!HalpMcaReportError

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {16dc0b79-ffca-6bb9-61b6-e2cd4a0f3ed7}

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

    0: kd> !blackboxpnp
    PnpActivityId : {00000000-0000-0000-0000-000000000000}
    PnpActivityTime : 132412424892292363
    PnpEventInformation: 3
    PnpEventInProgress : 0
    PnpProblemCode : 24
    PnpVetoType : 0
    DeviceId : SWD\MMDEVAPI\{0.0.0.00000000}.{db7eaec7-b580-4db3-9d4c-e29fe1f922f6}
    VetoString :

    0: kd> !blackboxntfs

    NTFS Blackbox Data

    0 Slow I/O Timeout Records Found
    0 Oplock Break Timeout Records Found
    0: kd> !blackboxbsd
    Version: 168
    Product type: 1

    Auto advanced boot: FALSE
    Advanced boot menu timeout: 30
    Last boot succeeded: TRUE
    Last boot shutdown: FALSE
    Sleep in progrees: FALSE

    Power button timestamp: 0
    System running: TRUE
    Connected standby in progress: FALSE
    User shutdown in progress: FALSE
    System shutdown in progress: FALSE
    Sleep in progress: 0
    Connected standby scenario instance id: 0
    Connected standby entry reason: 0
    Connected standby exit reason: 0
    System sleep transitions to on: 3
    Last reference time: 0x1d66c62f07c3543
    Last reference time checksum: 0x7c3852b6
    Last update boot id: 84

    Boot attempt count: 1
    Last boot checkpoint: TRUE
    Checksum: 0x38
    Last boot id: 84
    Last successful shutdown boot id: 82
    Last reported abnormal shutdown boot id: 83

    Error info boot id: 0
    Error info repeat count: 0
    Error info other error count: 0
    Error info code: 0
    Error info other error count: 0

    Power button last press time: 0
    Power button cumulative press count: 0
    Power button last press boot id: 0
    Power button last power watchdog stage: 0
    Power button watchdog armed: FALSE
    Power button shutdown in progress: FALSE
    Power button last release time: 0
    Power button cumulative release count: 0
    Power button last release boot id: 0
    Power button error count: 0
    Power button current connected standby phase: 0
    Power button transition latest checkpoint id: 0
    Power button transition latest checkpoint type: 0
    Power button transition latest checkpoint sequence number: 0


    :)
     
    bobsmith3333333333, Aug 6, 2020
    #1

  2. 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 MACHINE_CHECK_EXCEPTION 9c :).

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

    "
     
    Edwin.Edwards, Aug 6, 2020
    #2
  3. ghost101 Win User
    Directx 9c games

    Ive been trying to compile a list of games which require or can use 9c features but my list is pretty limited. HDR using a 9b path dont count. So that rules out the hl2 series/stalker etc.

    So far i have

    Rainbow Six: Vegas
    Colin Mcrae: DiRT
    Splinter Cell: Double Agent
    Spiderman 3
    MOH: Airborne
    Kane and Lynch Dead men
    Gears of War
    Company of Heroes
    Call of Juarez
    Flight Simulator X
    Farcry
    Hellgate London
    Crysis
    Oblivion
    CoH

    Also, games with directx 10 capability, we will assume require 9c since theres no way to tell.

    Thanks for any help.
     
    ghost101, Aug 6, 2020
    #3
  4. MACHINE_CHECK_EXCEPTION 9c

    MACHINE_CHECK_EXCEPTION (9c)

    Nothing's overclocked, drivers are up to date, ram and cpu have been tested, no faults.

    Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\user\Documents\New folder\080420-25609-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP (6 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Machine Name:

    Kernel base = 0xfffff807`07600000 PsLoadedModuleList = 0xfffff807`0822a310

    Debug session time: Tue Aug 4 20:47:43.956 2020 (UTC - 4:00)

    System Uptime: 0 days 21:33:55.623

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ............................................

    Loading User Symbols

    Loading unloaded module list

    ...........

    For analysis of this file, run !analyze -v

    1: kd> !analyze -v

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

    * *

    * 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 (If Param 1 is < 0x80000000)

    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

    AMD64 Processors (If Param 1 is > 0x80000000)

    1 - Failure Type

    VALUES:

    0x80000001: Spurious MCE

    2 - Address of MCA_EXCEPTION structure

    0x80000002: Rendezvous failure

    2 - Address of MCA_EXCEPTION structure

    END_VALUES

    Arguments:

    Arg1: 0000000080000001

    Arg2: ffffe6002b5dcb30

    Arg3: 0000000000000000

    Arg4: 0000000000000000

    Debugging Details:

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

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.Sec

    Value: 1

    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-PI35CFS

    Key : Analysis.DebugData

    Value: CreateObject

    Key : Analysis.DebugModel

    Value: CreateObject

    Key : Analysis.Elapsed.Sec

    Value: 1

    Key : Analysis.Memory.CommitPeak.Mb

    Value: 78

    Key : Analysis.System

    Value: CreateObject

    DUMP_FILE_ATTRIBUTES: 0x8

    Kernel Generated Triage Dump

    BUGCHECK_CODE: 9c

    BUGCHECK_P1: 80000001

    BUGCHECK_P2: ffffe6002b5dcb30

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)

    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: GameBarFTServe

    BAD_STACK_POINTER: ffffe6002b5dcae8

    STACK_TEXT:

    ffffe600`2b5dcae8 fffff807`07ac1719 : 00000000`0000009c 00000000`80000001 ffffe600`2b5dcb30 00000000`00000000 : nt!KeBugCheckEx

    ffffe600`2b5dcaf0 fffff807`07ac1b74 : 00000000`00000006 ffffe600`2b5dce70 00000000`00000000 00000000`00000006 : nt!HalpMcaReportError+0x149

    ffffe600`2b5dcc60 fffff807`07ac0d8b : 00000000`00000000 00000000`80000001 ffffe600`2b5dcef0 cccccccc`cc00134f : nt!HalpMceHandlerWithRendezvous+0x11c

    ffffe600`2b5dcc90 fffff807`07ac35d5 : ffffd208`bb4e4a48 f88b49f0`598d48f6 8b116e8d`41f28b48 6f7533b1`0f4cf0c5 : nt!HalpHandleMachineCheck+0x5f

    ffffe600`2b5dccc0 fffff807`07b18d59 : 7533b10f`4cf00000 b20d1fe8`cb8b4860 8b482475`fe3b48ff 8b48ffaf`c472e8ce : nt!HalHandleMcheck+0x35

    ffffe600`2b5dccf0 fffff807`079ecbba : 5e5f5e41`20c48348 0001609f`8d48ccc3 b10f4cf0`c58b4800 dde8cb8b`480a7533 : nt!KiHandleMcheck+0x9

    ffffe600`2b5dcd20 fffff807`079ec877 : 00000000`00000000 00000000`00000000 00007ff8`7cba60de 00000000`00000000 : nt!KxMcheckAbort+0x7a

    ffffe600`2b5dce60 00007ff8`a2a7393c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277

    000000c0`e3bab5f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`a2a7393c

    SYMBOL_NAME: nt!HalpMcaReportError+149

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    IMAGE_VERSION: 10.0.19041.388

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 149

    FAILURE_BUCKET_ID: 0x9C_SPURIOUS_GenuineIntel_STACKPTR_ERROR_nt!HalpMcaReportError

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {16dc0b79-ffca-6bb9-61b6-e2cd4a0f3ed7}

    Followup: MachineOwner

    ---------

    1: kd> !blackboxbsd

    Version: 168

    Product type: 1

    Auto advanced boot: FALSE

    Advanced boot menu timeout: 30

    Last boot succeeded: TRUE

    Last boot shutdown: FALSE

    Sleep in progrees: FALSE

    Power button timestamp: 0

    System running: TRUE

    Connected standby in progress: FALSE

    User shutdown in progress: FALSE

    System shutdown in progress: FALSE

    Sleep in progress: 0

    Connected standby scenario instance id: 0

    Connected standby entry reason: 0

    Connected standby exit reason: 0

    System sleep transitions to on: 1

    Last reference time: 0x1d66ac1a9e1054b

    Last reference time checksum: 0xc8168e2f

    Last update boot id: 77

    Boot attempt count: 1

    Last boot checkpoint: TRUE

    Checksum: 0x28

    Last boot id: 77

    Last successful shutdown boot id: 71

    Last reported abnormal shutdown boot id: 76

    Error info boot id: 0

    Error info repeat count: 0

    Error info other error count: 0

    Error info code: 0

    Error info other error count: 0

    Power button last press time: 0

    Power button cumulative press count: 0

    Power button last press boot id: 0

    Power button last power watchdog stage: 0

    Power button watchdog armed: FALSE

    Power button shutdown in progress: FALSE

    Power button last release time: 0

    Power button cumulative release count: 0

    Power button last release boot id: 0

    Power button error count: 0

    Power button current connected standby phase: 0

    Power button transition latest checkpoint id: 0

    Power button transition latest checkpoint type: 0

    Power button transition latest checkpoint sequence number: 0
     
    bobsmith3333333333, Aug 6, 2020
    #4
Thema:

MACHINE_CHECK_EXCEPTION 9c

Loading...
  1. MACHINE_CHECK_EXCEPTION 9c - Similar Threads - MACHINE_CHECK_EXCEPTION

  2. MACHINE_CHECK_EXCEPTION How to fix

    in Windows 10 Gaming
    MACHINE_CHECK_EXCEPTION How to fix: https://1drv.ms/u/s!Aj_bCrW1fRl9ga4o7hnIi0HT4irYYw?e=1beF7a https://answers.microsoft.com/en-us/windows/forum/all/machinecheckexception-how-to-fix/b988a13b-a191-4f14-b30e-cf9378b954ee
  3. MACHINE_CHECK_EXCEPTION How to fix

    in Windows 10 BSOD Crashes and Debugging
    MACHINE_CHECK_EXCEPTION How to fix: https://1drv.ms/u/s!Aj_bCrW1fRl9ga4o7hnIi0HT4irYYw?e=1beF7a https://answers.microsoft.com/en-us/windows/forum/all/machinecheckexception-how-to-fix/b988a13b-a191-4f14-b30e-cf9378b954ee
  4. MACHINE_CHECK_EXCEPTION How to fix

    in Windows 10 Software and Apps
    MACHINE_CHECK_EXCEPTION How to fix: https://1drv.ms/u/s!Aj_bCrW1fRl9ga4o7hnIi0HT4irYYw?e=1beF7a https://answers.microsoft.com/en-us/windows/forum/all/machinecheckexception-how-to-fix/b988a13b-a191-4f14-b30e-cf9378b954ee
  5. [WINDOWS 11] Bsod - machine_check_exception

    in Windows 10 Gaming
    [WINDOWS 11] Bsod - machine_check_exception: Hi,I'm using windows 11 pro x64, and today i got bsod after a complete freezei can't find minidump, i waited 1 hour for microsoft to save data, but didn't loaded above 0% on bsod screen with stop code: MACHINE_CHECK_EXCEPTION. I was using microsoft edge with 14 tabs, steam,...
  6. [WINDOWS 11] Bsod - machine_check_exception

    in Windows 10 Software and Apps
    [WINDOWS 11] Bsod - machine_check_exception: Hi,I'm using windows 11 pro x64, and today i got bsod after a complete freezei can't find minidump, i waited 1 hour for microsoft to save data, but didn't loaded above 0% on bsod screen with stop code: MACHINE_CHECK_EXCEPTION. I was using microsoft edge with 14 tabs, steam,...
  7. Blue Screen error: MACHINE_CHECK_EXCEPTION

    in Windows 10 Gaming
    Blue Screen error: MACHINE_CHECK_EXCEPTION: Hi,I have the above issue on my laptop.I cannot restart the laptop but I did access some options.On this screen I was offered access to command prompt, roll back of updates amongst others.However, to do this its asks me to log in.When I do this it states the password is...
  8. Blue Screen error: MACHINE_CHECK_EXCEPTION

    in Windows 10 Software and Apps
    Blue Screen error: MACHINE_CHECK_EXCEPTION: Hi,I have the above issue on my laptop.I cannot restart the laptop but I did access some options.On this screen I was offered access to command prompt, roll back of updates amongst others.However, to do this its asks me to log in.When I do this it states the password is...
  9. Blue Screen error: MACHINE_CHECK_EXCEPTION

    in Windows 10 BSOD Crashes and Debugging
    Blue Screen error: MACHINE_CHECK_EXCEPTION: Hi,I have the above issue on my laptop.I cannot restart the laptop but I did access some options.On this screen I was offered access to command prompt, roll back of updates amongst others.However, to do this its asks me to log in.When I do this it states the password is...
  10. bluescreen clock_watchdog_timeout & machine_check_exception

    in Windows 10 Software and Apps
    bluescreen clock_watchdog_timeout & machine_check_exception: Hello there. I have been facing a problem with a blue screen for a long time now, and I can't seem to solve it. The blue screen appears on average once every three days. But sometimes, after one blue screen, several others appear in a row. It's unlikely to be a Windows...