S
ShadeAeternum
Hi there,
Since a few days now I encounter a BSOD of a Machine_Check_Exception.
On Wed 17/07/2019 19:01:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071719-8343-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpMcaReportError+0x11D)
Bugcheck code: 0x9C (0x0, 0xFFFFF80471A84B30, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 17/07/2019 13:02:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071719-8515-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpMcaReportError+0x11D)
Bugcheck code: 0x9C (0x0, 0xFFFFF80236684B30, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 16/07/2019 09:34:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071619-8125-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpMcaReportError+0x11D)
Bugcheck code: 0x9C (0x0, 0xFFFFF8043FE84B30, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
I've already tried many solutions that I've read gere and there.
Memory Diagnostic : No failure. Still the issue.
Replace RAM sticks and GPU Card. Still the issue.
Check the CPU with Intel Processor Diagnostic Tool (All test passed). Still the issue.
Try previous GPU Drivers. Still the same issue.
--------------------------------------------------
I've also tried to enable verifier.exe as suggested in a post I saw on the web. Ended up with a different crash after the reboot. (Happened many times).
On Wed 17/07/2019 20:46:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071719-17390-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!ObReferenceObjectByHandle_wrapper+0x198)
Bugcheck code: 0xC4 (0xF6, 0x5B4, 0xFFFF9C0C0A82A080, 0xFFFFF8044FBD16C5)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Extension du vérificateur de pilotes
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION
On Wed 17/07/2019 20:46:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!ObReferenceObjectByHandle_wrapper+0x198)
Bugcheck code: 0xC4 (0xF6, 0x5B4, 0xFFFF9C0C0A82A080, 0xFFFFF8044FBD16C5)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Extension du vérificateur de pilotes
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION
On Wed 17/07/2019 20:38:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071719-16921-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!ObReferenceObjectByHandle_wrapper+0x198)
Bugcheck code: 0xC4 (0xF6, 0x618, 0xFFFFBC87526DA080, 0xFFFFF801312416C5)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Extension du vérificateur de pilotes
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION
So I disabled (delete exisiting settings) it to avoid further BSOD (which isn't the actual cause I'm dealing with when not activated).
-------------------------------------
Also today I've downloaded Windbg to analyze furthermore the problem. (Not the verifier one but the hal.dll).
Those are the results:
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\minidump\071619-8125-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 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff804`3c000000 PsLoadedModuleList = 0xfffff804`3c4432f0
Debug session time: Tue Jul 16 11:34:14.166 2019 (UTC + 2:00)
System Uptime: 0 days 2:41:48.910
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
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: fffff8043fe84b30
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: 18362.1.amd64fre.19h1_release.190318-1202
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: fffff8043fe84b30
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BUGCHECK_STR: 0x9C_GenuineIntel
CPU_COUNT: 8
CPU_MHZ: e10
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: DESKTOP-5D315HN
ANALYSIS_SESSION_TIME: 07-18-2019 11:46:52.0549
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
BAD_STACK_POINTER: fffff8043fe84af8
LAST_CONTROL_TRANSFER: from fffff8043cafb1f1 to fffff8043c1bc900
STACK_TEXT:
fffff804`3fe84af8 fffff804`3cafb1f1 : 00000000`0000009c 00000000`00000000 fffff804`3fe84b30 00000000`00000000 : nt!KeBugCheckEx
fffff804`3fe84b00 fffff804`3cafb77d : 00000000`00000008 fffff804`3fe84e70 00000000`00000000 00000000`00000000 : hal!HalpMcaReportError+0x11d
fffff804`3fe84c60 fffff804`3cafa7c8 : 00000000`00000000 fffff804`3fe84ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x131
fffff804`3fe84c90 fffff804`3cafb9a7 : ffffd488`748d9b30 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
fffff804`3fe84cc0 fffff804`3c2a1e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
fffff804`3fe84cf0 fffff804`3c1cb8ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
fffff804`3fe84d20 fffff804`3c1cb571 : fffff804`00000000 fffff804`3c1cb4ae fffff804`383a1180 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff804`3fe84e60 fffff804`52c1138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x271
fffff804`3fe686a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f
THREAD_SHA1_HASH_MOD_FUNC: 7c5c59ad39e6527cb43445b5353a8a9ae211ef69
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 508569533680281e900705b003e24f391a869693
THREAD_SHA1_HASH_MOD: 017fb57dd2c8bb08a42a859207056f83b9fd79be
FOLLOWUP_IP:
intelppm!MWaitIdle+1f
fffff804`52c1138f 4585c9 test r9d,r9d
FAULT_INSTR_CODE: 75c98545
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: intelppm!MWaitIdle+1f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.18362.1083
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1f
FAILURE_BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle
BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle
PRIMARY_PROBLEM_CLASS: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle
TARGET_TIME: 2019-07-16T09:34:14.000Z
OSBUILD: 18362
OSSERVICEPACK: 239
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: 1972-02-02 09:33:06
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 7942
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9c_genuineintel_stackptr_error_intelppm!mwaitidle
FAILURE_ID_HASH: {d82f1232-e6fd-ac41-d01e-ddeec73b684b}
Followup: MachineOwner
---------
I'm not qualified to say I can understand properly the problem, but it seems to point out the CPU, even though IPDT see the test passed.
Also, the problem is happening at random and I'm not doing something specific. (Most of the time I'm only surfing on web or even AFK.
There was also a 0x124 Problem the July 12th 2019, although when I wanted to see it again it was deleted . I suspect disk cleanup to be the fault of this. Although this error didn't occured again. (Not sure if those are related though.) So for this one I can't provide any info and sorry about that.
Could I please ask your assistance?
Best regards.
Edit: Additional info:
Here's a full list of I/O and components of the computer:
Continue reading...
Since a few days now I encounter a BSOD of a Machine_Check_Exception.
On Wed 17/07/2019 19:01:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071719-8343-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpMcaReportError+0x11D)
Bugcheck code: 0x9C (0x0, 0xFFFFF80471A84B30, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 17/07/2019 13:02:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071719-8515-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpMcaReportError+0x11D)
Bugcheck code: 0x9C (0x0, 0xFFFFF80236684B30, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 16/07/2019 09:34:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071619-8125-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpMcaReportError+0x11D)
Bugcheck code: 0x9C (0x0, 0xFFFFF8043FE84B30, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
I've already tried many solutions that I've read gere and there.
Memory Diagnostic : No failure. Still the issue.
Replace RAM sticks and GPU Card. Still the issue.
Check the CPU with Intel Processor Diagnostic Tool (All test passed). Still the issue.
Try previous GPU Drivers. Still the same issue.
--------------------------------------------------
I've also tried to enable verifier.exe as suggested in a post I saw on the web. Ended up with a different crash after the reboot. (Happened many times).
On Wed 17/07/2019 20:46:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071719-17390-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!ObReferenceObjectByHandle_wrapper+0x198)
Bugcheck code: 0xC4 (0xF6, 0x5B4, 0xFFFF9C0C0A82A080, 0xFFFFF8044FBD16C5)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Extension du vérificateur de pilotes
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION
On Wed 17/07/2019 20:46:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!ObReferenceObjectByHandle_wrapper+0x198)
Bugcheck code: 0xC4 (0xF6, 0x5B4, 0xFFFF9C0C0A82A080, 0xFFFFF8044FBD16C5)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Extension du vérificateur de pilotes
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION
On Wed 17/07/2019 20:38:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071719-16921-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!ObReferenceObjectByHandle_wrapper+0x198)
Bugcheck code: 0xC4 (0xF6, 0x618, 0xFFFFBC87526DA080, 0xFFFFF801312416C5)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Extension du vérificateur de pilotes
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION
So I disabled (delete exisiting settings) it to avoid further BSOD (which isn't the actual cause I'm dealing with when not activated).
-------------------------------------
Also today I've downloaded Windbg to analyze furthermore the problem. (Not the verifier one but the hal.dll).
Those are the results:
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\minidump\071619-8125-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 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff804`3c000000 PsLoadedModuleList = 0xfffff804`3c4432f0
Debug session time: Tue Jul 16 11:34:14.166 2019 (UTC + 2:00)
System Uptime: 0 days 2:41:48.910
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
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: fffff8043fe84b30
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: 18362.1.amd64fre.19h1_release.190318-1202
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: fffff8043fe84b30
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BUGCHECK_STR: 0x9C_GenuineIntel
CPU_COUNT: 8
CPU_MHZ: e10
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: DESKTOP-5D315HN
ANALYSIS_SESSION_TIME: 07-18-2019 11:46:52.0549
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
BAD_STACK_POINTER: fffff8043fe84af8
LAST_CONTROL_TRANSFER: from fffff8043cafb1f1 to fffff8043c1bc900
STACK_TEXT:
fffff804`3fe84af8 fffff804`3cafb1f1 : 00000000`0000009c 00000000`00000000 fffff804`3fe84b30 00000000`00000000 : nt!KeBugCheckEx
fffff804`3fe84b00 fffff804`3cafb77d : 00000000`00000008 fffff804`3fe84e70 00000000`00000000 00000000`00000000 : hal!HalpMcaReportError+0x11d
fffff804`3fe84c60 fffff804`3cafa7c8 : 00000000`00000000 fffff804`3fe84ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x131
fffff804`3fe84c90 fffff804`3cafb9a7 : ffffd488`748d9b30 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
fffff804`3fe84cc0 fffff804`3c2a1e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
fffff804`3fe84cf0 fffff804`3c1cb8ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
fffff804`3fe84d20 fffff804`3c1cb571 : fffff804`00000000 fffff804`3c1cb4ae fffff804`383a1180 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff804`3fe84e60 fffff804`52c1138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x271
fffff804`3fe686a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f
THREAD_SHA1_HASH_MOD_FUNC: 7c5c59ad39e6527cb43445b5353a8a9ae211ef69
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 508569533680281e900705b003e24f391a869693
THREAD_SHA1_HASH_MOD: 017fb57dd2c8bb08a42a859207056f83b9fd79be
FOLLOWUP_IP:
intelppm!MWaitIdle+1f
fffff804`52c1138f 4585c9 test r9d,r9d
FAULT_INSTR_CODE: 75c98545
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: intelppm!MWaitIdle+1f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.18362.1083
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1f
FAILURE_BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle
BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle
PRIMARY_PROBLEM_CLASS: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle
TARGET_TIME: 2019-07-16T09:34:14.000Z
OSBUILD: 18362
OSSERVICEPACK: 239
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: 1972-02-02 09:33:06
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 7942
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9c_genuineintel_stackptr_error_intelppm!mwaitidle
FAILURE_ID_HASH: {d82f1232-e6fd-ac41-d01e-ddeec73b684b}
Followup: MachineOwner
---------
I'm not qualified to say I can understand properly the problem, but it seems to point out the CPU, even though IPDT see the test passed.
Also, the problem is happening at random and I'm not doing something specific. (Most of the time I'm only surfing on web or even AFK.
There was also a 0x124 Problem the July 12th 2019, although when I wanted to see it again it was deleted . I suspect disk cleanup to be the fault of this. Although this error didn't occured again. (Not sure if those are related though.) So for this one I can't provide any info and sorry about that.
Could I please ask your assistance?
Best regards.
Edit: Additional info:
Here's a full list of I/O and components of the computer:
| Operating System | Windows 10 (X64) 1903 System install date: 7/7/2019 |
| Processor | Intel Core i7 9700K clocked at 3.60 GHz Processor frequency measure (core0): 4.70 GHz Number of cores: 8 physical, 8 logical Processor socket: Socket 1151 LGA CPU Temperature (core 0): 32 °C |
| Motherboard | Micro-Star International Co., Ltd. MPG Z390 GAMING EDGE AC (MS-7B17) 2.0 Serial number (motherboard): J216060934 SKU Number: Default string Bios version: A.50 Date: 3/26/2019 |
| Chipset | Northbridge : Intel Coffee Lake Revision ID: 0D Southbridge : Intel Z390 Revision ID: 10 |
| Memory | 32 GB total memory type DDR4 to 1.07 GHz Memory timing: 15.0 clocks-15 clocks-15 clocks-36 clocks-2 TT Memory chip Corsair of 16 GB Maximum frequency: 1.07 GHz Max bandwidth: DDR4-2132 Memory chip Corsair of 16 GB Maximum frequency: 1.07 GHz Max bandwidth: DDR4-2132 |
| Graphics card | NVIDIA GeForce RTX 2070 DirectX version installed: 11.0 Core clock: 300 MHz Memory clock: 405 MHz |
| Harddrive | SSD KINGSTONSV300S37A240G of 223.57 GB SATA III Firmware: 603ABBF0 SATA version: SATA Rev 2.6 Serial number: 50026B7758042783 SSD WDCWDS100T2B0A-00SM50 of 931.51 GB SATA III Firmware: X61190WD SATA version: SATA Rev 2.6 Serial number: 183276804573 Harddrive WDCWD1002FAEX-00Z3A0 of 931.51 GB SATA III Firmware: 05.01D05 SATA version: SATA Rev 2.6 Serial number: WD-WMATR1014348 |
| Network | Intel Corporation Ethernet Connection (7) I219-V Adapter type: ethernet Microsoft Wi-Fi Direct Virtual Adapter Adapter type: IEEE 802.11 wireless Microsoft Wi-Fi Direct Virtual Adapter #2 Adapter type: IEEE 802.11 wireless Intel Corporation Wireless-AC 9560 [Jefferson Peak] Adapter type: IEEE 802.11 wireless Bluetooth Device (Personal Area Network) Adapter type: ethernet Software Loopback Interface 1 Adapter type: Loopback |
| Multimedia cards | Intel Corporation Cannon Lake PCH cAVS NVIDIA Corporation TU106 High Definition Audio Controller |
| Keyboard | Logitech, Inc. G105 Gaming Keyboard (Gaming Keyboard G105) Holtek Semiconductor, Inc. USB Gaming Mouse |
| Mouse | Holtek Semiconductor, Inc. USB Gaming Mouse |
| Screen(s) | KG251Q Maximum resolution: 1920 x 1080 Screen size: 24.3" (54 cm x 30 cm) Manufacture date: 7/1/2018 Aspect ratio: 16:9 Video input type: DisplayPort Digital Signal |
| USB peripheral | Micro Star International Supported USB version: 1.10 Logitech, Inc. G105 Gaming Keyboard (Gaming Keyboard G105) Supported USB version: 1.10 Razer USA, Ltd Razer Kraken 7.1 Supported USB version: 2.0 Holtek Semiconductor, Inc. USB Gaming Mouse Supported USB version: 2.0 Intel Corp. Supported USB version: 2.0 |
Continue reading...