BSOD, Mini Dump File Help

August 7, 2011 at 05:14:53
Specs: Windows Vista
I randomly get the BSOD on my laptop while I am working on it. I have turned sleep off and the problem continues.

I looked at the mini dump file and am not seeing anything that points to a specific item as being the problem. Can anybody please help me?


See More: BSOD, Mini Dump File Help

Report •

#1
August 7, 2011 at 10:42:12
If it is creating a dump log then there should be some info of the cause. See also event logs.

If it did work OK at one time then decide which way to start. Either hardware or software. Personally I reload the OS back to OEM state. If fails then use hardware diags.

1/3 of highway deaths are caused by drunks. The rest are by people who can't drive any better than a drunk.


Report •

#2
August 7, 2011 at 22:13:25
The mini dump file says

BugCheck 9F, {3, fffffa80070fe060, fffffa800710b940, fffff9801a4d2cf0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner


When I click the analyze link it spits out

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80070fe060, Physical Device Object of the stack
Arg3: fffffa800710b940, Functional Device Object of the stack
Arg4: fffff9801a4d2cf0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: fffff9801a4d2cf0

DEVICE_OBJECT: 0000000000000000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`0373f9f8 fffff800`01ebc79d : 00000000`0000009f 00000000`00000003 fffffa80`070fe060 fffffa80`0710b940 : nt!KeBugCheckEx
fffff800`0373fa00 fffff800`01e653fd : fffff800`0373faf0 00000000`00000000 00000000`00000001 fffff800`01fabf01 : nt! ?? ::FNODOBFM::`string'+0x17cec
fffff800`0373fa70 fffff800`01e64818 : fffff800`0373fcd0 00000000`00000002 fffff800`0373fcc8 00000000`00000010 : nt!KiTimerListExpire+0x30d
fffff800`0373fca0 fffff800`01e64faf : 000040eb`c06c76e6 00000000`00000000 fffffa80`00000010 fffff800`01f7da80 : nt!KiTimerExpiration+0x1d8
fffff800`0373fd10 fffff800`01e658d2 : fffff800`01f7a680 fffff800`01f7a680 00000000`00000000 fffff800`01f7fb80 : nt!KiRetireDpcList+0x1df
fffff800`0373fd80 fffff800`02032860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`0373fdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4


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_0x9F_VRF_3_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_0x9F_VRF_3_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner


Report •
Related Solutions


Ask Question