Hi All 
I was hoping you could assist me with interpreting a minidump analyis from Windbg.
I am pretty sure the processor is to blame. The reason for this suspicion is because I have two computers running Q6600s. One is for music production (Windows XP) the other for gaming (Windows Vista).
I was experiencing crashing (though not BSODs) when using music applications on my production machine. After much testing and swapping of components, I ended up swapping the CPUs on the two machines. The crashing on the production machine then stopped but now I am getting BSODs when playing games on my gaming machine.
As you can probably quite easily diagnose, process of elimination would dictate the CPU is to blame. I was just hoping to double check this however and as such please see the following minidump analysis:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 84b47030, Physical Device Object of the stack
Arg3: 85a39380, Functional Device Object of the stack
Arg4: 845c9008, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: 845c9008
DEVICE_OBJECT: 85a39380
DRIVER_OBJECT: 85a199f0
IMAGE_NAME: Rtlh86.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45190cfb
MODULE_NAME: Rtlh86
FAULTING_MODULE: 8c0b0000 Rtlh86
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 81c37b6c to 81cd1163
STACK_TEXT:
81cf9acc 81c37b6c 0000009f 00000003 84b47030 nt!KeBugCheckEx+0x1e
81cf9b28 81c376bc 81cf9b94 81cf9c50 81d12401 nt!PopCheckIrpWatchdog+0x1ad
81cf9b68 81cbad00 81d124e0 00000000 9b36a76b nt!PopCheckForIdleness+0x343
81cf9c88 81cba936 81cf9cd0 81cbbb02 81cf9cd8 nt!KiTimerListExpire+0x367
81cf9ce8 81cba483 00000000 00000000 0004c438 nt!KiTimerExpiration+0x2a0
81cf9d50 81cb8f9d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
81cf9d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_IMAGE_Rtlh86.sys
BUCKET_ID: 0x9F_IMAGE_Rtlh86.sys
Followup: MachineOwner
---------
********************************************************************************************************
I have quite a few examples of the above and they all vary slightly. Some say the game executable name as the process, others like the above simply say 'System'.
"INTEL_CPU_MICROCODE_ZERO" was another small hint towards the CPU
Any ideas?
Many thanks in advance,
Jake Almond
I was hoping you could assist me with interpreting a minidump analyis from Windbg.
I am pretty sure the processor is to blame. The reason for this suspicion is because I have two computers running Q6600s. One is for music production (Windows XP) the other for gaming (Windows Vista).
I was experiencing crashing (though not BSODs) when using music applications on my production machine. After much testing and swapping of components, I ended up swapping the CPUs on the two machines. The crashing on the production machine then stopped but now I am getting BSODs when playing games on my gaming machine.
As you can probably quite easily diagnose, process of elimination would dictate the CPU is to blame. I was just hoping to double check this however and as such please see the following minidump analysis:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 84b47030, Physical Device Object of the stack
Arg3: 85a39380, Functional Device Object of the stack
Arg4: 845c9008, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: 845c9008
DEVICE_OBJECT: 85a39380
DRIVER_OBJECT: 85a199f0
IMAGE_NAME: Rtlh86.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45190cfb
MODULE_NAME: Rtlh86
FAULTING_MODULE: 8c0b0000 Rtlh86
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 81c37b6c to 81cd1163
STACK_TEXT:
81cf9acc 81c37b6c 0000009f 00000003 84b47030 nt!KeBugCheckEx+0x1e
81cf9b28 81c376bc 81cf9b94 81cf9c50 81d12401 nt!PopCheckIrpWatchdog+0x1ad
81cf9b68 81cbad00 81d124e0 00000000 9b36a76b nt!PopCheckForIdleness+0x343
81cf9c88 81cba936 81cf9cd0 81cbbb02 81cf9cd8 nt!KiTimerListExpire+0x367
81cf9ce8 81cba483 00000000 00000000 0004c438 nt!KiTimerExpiration+0x2a0
81cf9d50 81cb8f9d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
81cf9d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_IMAGE_Rtlh86.sys
BUCKET_ID: 0x9F_IMAGE_Rtlh86.sys
Followup: MachineOwner
---------
********************************************************************************************************
I have quite a few examples of the above and they all vary slightly. Some say the game executable name as the process, others like the above simply say 'System'.
"INTEL_CPU_MICROCODE_ZERO" was another small hint towards the CPU
Any ideas?
Many thanks in advance,
Jake Almond
