Hi,
I ran windbg and analyzed one .dmp file.
Below is the result of the analysis of the debugger. Bug check analysis is pointing issue towards hardware. Need help to understand the issue, if it is a hardware issue, then which is the hardware. I did ran memtestx86, sfc scannow and chkdsk but
found no issues after running them.
-----------------------------------------------------------------------------------------------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80088ad8f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80088ad8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`033af6f0 fffff800`036ddc59 : fffffa80`088ad8d0 fffffa80`05a73b60 00000000`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`033afc10 fffff800`035bdfa7 : fffffa80`088ad8d0 fffff800`036382b8 fffffa80`05a73b60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`033afc40 fffff800`035255c5 : fffff800`03699ac0 00000000`00000001 fffffa80`088f1860 fffffa80`05a73b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`033afc80 fffff800`034a5021 : fffff880`014fce00 fffff800`035255a0 fffffa80`05a73b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`033afcb0 fffff800`0373732e : 00000000`00000000 fffffa80`05a73b60 00000000`00000080 fffffa80`05a5c5f0 : nt!ExpWorkerThread+0x111
fffff880`033afd40 fffff800`0348c666 : fffff880`031d5180 fffffa80`05a73b60 fffff880`031dffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033afd80 00000000`00000000 : fffff880`033b0000 fffff880`033aa000 fffff880`033af6a0 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
Followup: MachineOwner
---------
3: kd> lmvm hardware
start end module name
Mini Kernel Dump does not contain unloaded driver list