I have BSOD problem with my new computer
Spec - I7 920 , Ati 4600 series video card, 8 g ram
Before I had a bsod which was 0X101 and now I have 0X124 hard ware problem
one per day least
i run memtest already no problems with my memory
Here is my Dump file
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007add038, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
4: 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: fffffa8007add038, 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`033776f0 fffff800`02ec8d29 : fffffa80`07add010 fffffa80`06d34040 fffff8a0`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03377c10 fffff800`02da8217 : fffffa80`07add010 fffff800`02e22658 fffffa80`06d34040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03377c40 fffff800`02d0f865 : fffff800`02e843a0 00000000`00000001 fffffa80`07cc5820 fffffa80`06d34040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03377c80 fffff800`02c8fa21 : fffff880`01110e00 fffff800`02d0f840 fffffa80`06d34000 fffff880`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03377cb0 fffff800`02f22cce : 00000000`00000000 fffffa80`06d34040 00000000`00000080 fffffa80`06ca99e0 : nt!ExpWorkerThread+0x111
fffff880`03377d40 fffff800`02c76fe6 : fffff880`03186180 fffffa80`06d34040 fffff880`031910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03377d80 00000000`00000000 : fffff880`03378000 fffff880`03372000 fffff880`03f30540 00000000`00000000 : nt!KxStartSystemThread+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
OLD mind map
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffff88003186180, 7}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003186180, The PRCB address of the hung processor.
Arg4: 0000000000000007, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
STACK_TEXT:
fffff880`06edf478 fffff800`02c33453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03186180 : nt!KeBugCheckEx
fffff880`06edf480 fffff800`02c8dde7 : 00000000`00000000 fffff800`00000007 00000000`000186a0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`06edf510 fffff800`031fb895 : fffff800`03220460 fffff880`06edf6c0 fffff800`03220460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`06edf610 fffff800`02c81c33 : fffff800`02dffe80 00000000`00000001 fffffa80`07c2f780 00000000`00000008 : hal!HalpHpetClockInterrupt+0x8d
fffff880`06edf640 fffff800`02c449ef : fffff800`02c81123 00000000`00000008 fffff800`02dffe80 fffff800`02e0dc40 : nt!KiInterruptDispatchNoLock+0x163
fffff880`06edf7d0 fffff800`02f83568 : 00000000`00000000 fffff880`06edfca0 fffff800`02c15000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x6b
fffff880`06edf840 fffff800`02f841e5 : 00000000`00356190 fffff800`02f8010e 00000000`00000000 fffff800`02c849b9 : nt!ExpQuerySystemInformation+0x1368
fffff880`06edfbe0 fffff800`02c84993 : 00000000`00000000 fffff880`06edfca0 ffffffff`fffe7960 000007fe`f84c0b48 : nt!NtQuerySystemInformation+0x4d
fffff880`06edfc20 00000000`76db00ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03fff138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76db00ba
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
PLZ HELP
Spec - I7 920 , Ati 4600 series video card, 8 g ram
Before I had a bsod which was 0X101 and now I have 0X124 hard ware problem
one per day least
i run memtest already no problems with my memory
Here is my Dump file
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007add038, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
4: 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: fffffa8007add038, 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`033776f0 fffff800`02ec8d29 : fffffa80`07add010 fffffa80`06d34040 fffff8a0`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03377c10 fffff800`02da8217 : fffffa80`07add010 fffff800`02e22658 fffffa80`06d34040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03377c40 fffff800`02d0f865 : fffff800`02e843a0 00000000`00000001 fffffa80`07cc5820 fffffa80`06d34040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03377c80 fffff800`02c8fa21 : fffff880`01110e00 fffff800`02d0f840 fffffa80`06d34000 fffff880`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03377cb0 fffff800`02f22cce : 00000000`00000000 fffffa80`06d34040 00000000`00000080 fffffa80`06ca99e0 : nt!ExpWorkerThread+0x111
fffff880`03377d40 fffff800`02c76fe6 : fffff880`03186180 fffffa80`06d34040 fffff880`031910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03377d80 00000000`00000000 : fffff880`03378000 fffff880`03372000 fffff880`03f30540 00000000`00000000 : nt!KxStartSystemThread+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
OLD mind map
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffff88003186180, 7}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003186180, The PRCB address of the hung processor.
Arg4: 0000000000000007, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
STACK_TEXT:
fffff880`06edf478 fffff800`02c33453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03186180 : nt!KeBugCheckEx
fffff880`06edf480 fffff800`02c8dde7 : 00000000`00000000 fffff800`00000007 00000000`000186a0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`06edf510 fffff800`031fb895 : fffff800`03220460 fffff880`06edf6c0 fffff800`03220460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`06edf610 fffff800`02c81c33 : fffff800`02dffe80 00000000`00000001 fffffa80`07c2f780 00000000`00000008 : hal!HalpHpetClockInterrupt+0x8d
fffff880`06edf640 fffff800`02c449ef : fffff800`02c81123 00000000`00000008 fffff800`02dffe80 fffff800`02e0dc40 : nt!KiInterruptDispatchNoLock+0x163
fffff880`06edf7d0 fffff800`02f83568 : 00000000`00000000 fffff880`06edfca0 fffff800`02c15000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x6b
fffff880`06edf840 fffff800`02f841e5 : 00000000`00356190 fffff800`02f8010e 00000000`00000000 fffff800`02c849b9 : nt!ExpQuerySystemInformation+0x1368
fffff880`06edfbe0 fffff800`02c84993 : 00000000`00000000 fffff880`06edfca0 ffffffff`fffe7960 000007fe`f84c0b48 : nt!NtQuerySystemInformation+0x4d
fffff880`06edfc20 00000000`76db00ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03fff138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76db00ba
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
PLZ HELP