i got a machine check exception

[YanZhang_390]

would this be a memory or cpu issue?


[COLOR=rgba(30, 30, 30, 1)]*******************************************************************************
* *
* 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: ffff8280c1d54b10
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2421

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2501

Key : Analysis.Init.CPU.mSec
Value: 593

Key : Analysis.Init.Elapsed.mSec
Value: 25835

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

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: ffff8280c1d54b10

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxbsd[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXNTFS: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxntfs[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXPNP: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxpnp[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXWINLOGON: 1

PROCESS_NAME: chrome.exe

BAD_STACK_POINTER: ffff8280c1d54ac8

STACK_TEXT:
ffff8280`c1d54ac8 fffff801`354b5629 : 00000000`0000009c 00000000`80000001 ffff8280`c1d54b10 00000000`00000000 : nt!KeBugCheckEx
ffff8280`c1d54ad0 fffff801`354b5a84 : 00000000`00000008 ffff8280`c1d54e50 00000000`00000000 00000000`00000008 : nt!HalpMcaReportError+0x149
ffff8280`c1d54c40 fffff801`354b4c9b : 00000000`00000000 00000000`80000001 ffff8280`c1d54ed0 000000ae`e9000000 : nt!HalpMceHandlerWithRendezvous+0x11c
ffff8280`c1d54c70 fffff801`354b74e5 : ffffb485`8f4dce90 5a8d4900`00002db8 8dd9f702`89416602 48d233c3`8b4cd478 : nt!HalpHandleMachineCheck+0x5f
ffff8280`c1d54ca0 fffff801`3550cc89 : d9708d44`00000057 c7ff48c6`460f4166 c9850389`66c20366 fb3b49de`8b480874 : nt!HalHandleMcheck+0x35
ffff8280`c1d54cd0 fffff801`35404efa : 00b70f41`3e894466 01894166`09b70f41 08894166`02e98349 72c13b4d`02c08349 : nt!KiHandleMcheck+0x9
ffff8280`c1d54d00 fffff801`35404bb7 : 00000000`00000000 fffff801`35404aec 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff8280`c1d54e40 fffff801`35359071 : 00000000`00000000 ffffec86`4dc078d0 ffffec86`4dc072f0 00000000`00000000 : nt!KiMcheckAbort+0x277
ffffec86`4dc072e0 fffff801`353356fe : ffffb485`a28af080 ffffec86`4dc07391 00000000`00000004 00000000`00000006 : nt!KeFlushProcessWriteBuffers+0xb5
ffffec86`4dc07320 fffff801`35336a22 : ffffb485`00000000 ffffb485`a28af000 ffffb485`adf47006 ffffb485`a28af080 : nt!KeSetPriorityAndQuantumProcess+0x122
ffffec86`4dc073f0 fffff801`356f3bfc : ffffffff`ffffff06 00000000`00000000 000000e0`00000000 ffffb485`00000000 : nt!PspSetProcessPriorityByClass+0x4a
ffffec86`4dc07430 fffff801`356f3c97 : 00000000`00000100 ffffec86`4dc07a80 00000000`00000000 ffff9f04`2890ed80 : nt!PspSetProcessForegroundBackgroundRequest+0x7c
ffffec86`4dc07480 fffff801`3569a82d : 00000000`00000100 ffffec86`4dc07a80 00000000`00001a0c ffffb485`a28af080 : nt!PsSetProcessPriorityByClass+0x17
ffffec86`4dc074b0 fffff801`354077b5 : ffffb485`a3edb0c0 ffffb485`b36955e0 00000000`00000000 00000000`00000000 : nt!NtSetInformationProcess+0x61d
ffffec86`4dc07a00 00007ffe`061ccf94 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000e0`a01ff078 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`061ccf94


SYMBOL_NAME: nt!HalpMcaReportError+149

MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]nt

[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 149

FAILURE_BUCKET_ID: 0x9C_SPURIOUS_GenuineIntel_STACKPTR_ERROR_nt!HalpMcaReportError

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner[/COLOR]

Continue reading...