BSOD Problem in Vista

V

VaRz

Adept
Sep 23, 2007
440
10
31
36
www.devilsreign.net
Whenever i leave a download at the night and i come to check it in the morning i get an error saying "Windows has recovered from an unexpected shutdown"

Here is what it showed....

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 00000003
BCP2: 85C15B70
BCP3: 85DFD380
BCP4: 8540C2D0
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini061508-01.dmp
C:\Users\Varun\AppData\Local\Temp\WER-162272-0.sysdata.xml
C:\Users\Varun\AppData\Local\Temp\WERF4E8.tmp.version.txt

Help!!!!
 
The Sorcerer

The Sorcerer

Skilled
Jun 16, 2007
2,051
156
152
38
hardwarebbq.com
Its always best to keep windows, drivers and bios updated. If you get any other BSOD screen, note down the error code which start with "0x000000..."!

Just in case, google and download HD tune and run an error scan on your HDs to rule out any possibility of bad sections.
 
S

shroff87

Disciple
May 11, 2009
131
0
0
36
I'm no BSOD expert but i had similar BSOD problems .. turned out that the intel inf drivers were causing instability (not on my sig rig) .. just used system restore. Try it .. may work if this has just started occuring.
 
tommy_vercetti

tommy_vercetti

Skilled
Apr 20, 2006
1,423
334
177
46
Mumbai/Bangalore
www.boricha.org
*******************************************************************************
* *
* 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: 85c15b70, Physical Device Object of the stack
Arg3: 85dfd380, Functional Device Object of the stack
Arg4: 8540c2d0, The blocked IRP

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

ReadVirtual: 826828aa not properly sign extended

Could not read faulting driver name

DRVPOWERSTATE_SUBCODE: 3

DEVICE_OBJECT: 85dfd380

DRIVER_OBJECT: 86f16b30

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x9F

PROCESS_NAME: Ã

LAST_CONTROL_TRANSFER: from 81a4569f to 81ae38af

STACK_TEXT:
81b0bacc 81a4569f 0000009f 00000003 85c15b70 nt!FsRtlCreateSectionForDataScan+0x24f
81b0bb28 81a454b3 81b0bb94 81b0bc50 86f49c01 nt!MiGetInPageSupportBlock+0x1f
81b0bb68 81aae622 81b244e0 00000000 2c35fa41 nt!MiResolveMappedFileFault+0x5ca
81b0bc88 81aae1e2 81b0bcd0 871f7e02 81b0bcd8 nt!KiAttachProcess+0x2b4
81b0bce8 81aadda5 00000000 00000000 000d775b nt!KeSetProcess+0x242
81b0bd50 81aadbbd 00000000 0000000e 00000000 nt!KdpStub+0x70
81b0bd54 00000000 0000000e 00000000 00000000 nt!IopRemoveLockedDeviceNode+0x17f1
STACK_COMMAND: kb

FOLLOWUP_IP:
nt!FsRtlCreateSectionForDataScan+24f
81ae38af 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!FsRtlCreateSectionForDataScan+24f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 496ec23c

FAILURE_BUCKET_ID: 0x9F_nt!FsRtlCreateSectionForDataScan+24f

BUCKET_ID: 0x9F_nt!FsRtlCreateSectionForDataScan+24f

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* 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: 85c15b70, Physical Device Object of the stack
Arg3: 85dfd380, Functional Device Object of the stack
Arg4: 8540c2d0, The blocked IRP

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

ReadVirtual: 826828aa not properly sign extended

Could not read faulting driver name

DRVPOWERSTATE_SUBCODE: 3

DEVICE_OBJECT: 85dfd380

DRIVER_OBJECT: 86f16b30

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x9F

PROCESS_NAME: Ã

LAST_CONTROL_TRANSFER: from 81a4569f to 81ae38af

STACK_TEXT:
81b0bacc 81a4569f 0000009f 00000003 85c15b70 nt!FsRtlCreateSectionForDataScan+0x24f
81b0bb28 81a454b3 81b0bb94 81b0bc50 86f49c01 nt!MiGetInPageSupportBlock+0x1f
81b0bb68 81aae622 81b244e0 00000000 2c35fa41 nt!MiResolveMappedFileFault+0x5ca
81b0bc88 81aae1e2 81b0bcd0 871f7e02 81b0bcd8 nt!KiAttachProcess+0x2b4
81b0bce8 81aadda5 00000000 00000000 000d775b nt!KeSetProcess+0x242
81b0bd50 81aadbbd 00000000 0000000e 00000000 nt!KdpStub+0x70
81b0bd54 00000000 0000000e 00000000 00000000 nt!IopRemoveLockedDeviceNode+0x17f1
STACK_COMMAND: kb

FOLLOWUP_IP:
nt!FsRtlCreateSectionForDataScan+24f
81ae38af 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!FsRtlCreateSectionForDataScan+24f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 496ec23c

FAILURE_BUCKET_ID: 0x9F_nt!FsRtlCreateSectionForDataScan+24f

BUCKET_ID: 0x9F_nt!FsRtlCreateSectionForDataScan+24f

Followup: MachineOwner
 
K

KingKrool

Skilled
Mar 16, 2005
3,556
71
136
I don't think you can blame this on the Intel drivers just yet - the dump doesn't have the necessary information ("Could not read faulting driver name").

Overview of memory dump file options for Windows Vista, Windows Server 2008, Windows Server 2003, Windows XP, and Windows 2000 describes how to get a kernel dump (not just a minidump). Once you get a kernel dump, analyze it using windbg. There are many sources of information on that; one is on TE: http://www.techenclave.com/guides-and-tutorials/solving-mysteries-of-crashing-windows-119344.html
 
Top Bottom