Jump to content

BSOD on resume from hibernate


Recommended Posts

Posted

Hi, I've been having issues resuming from Hibernate in Vista SP2. Sometimes I get a BSOD: Driver_power_state_failure. Mostly the screen just stays black perpetually. I've attached the latest minidump. Any help is much appreciated!

Mini101809_01.zip


Posted

There was a bug filed for this particular USB crash on Vista RTM and SP1, and it was fixed in Windows 7 (I know because I tested the test patch for this during beta). However, Vista SP2 doesn't add an updated binary for this file, so this may not have actually been fixed on Vista. Normally !analyze -v in these cases isn't sufficient, but in this case it is:

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: 86970028, Physical Device Object of the stack
Arg3: 86c1f028, Functional Device Object of the stack
Arg4: 860e8008, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: 860e8008

DEVICE_OBJECT: 86970028

DRIVER_OBJECT: 866ba9a0

IMAGE_NAME: usbuhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47919050

MODULE_NAME: usbuhci

FAULTING_MODULE: 87ff2000 usbuhci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 8206d3ab to 82109b0d

STACK_TEXT:
82131acc 8206d3ab 0000009f 00000003 86970028 nt!KeBugCheckEx+0x1e
82131b28 8206cfc8 82131b94 82131c50 8214a401 nt!PopCheckIrpWatchdog+0x1ad
82131b68 820e62eb 8214a4e0 00000000 484a0a50 nt!PopCheckForIdleness+0x343
82131c88 820e5eab 82131cd0 8c6fab02 82131cd8 nt!KiTimerListExpire+0x367
82131ce8 820e6615 00000000 00000000 003f6dff nt!KiTimerExpiration+0x22a
82131d50 820e487d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
82131d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49

STACK_COMMAND: kb


// You are running Vista SP2...:
0: kd> lmvm nt
start end module name
8203c000 823f5000 nt
Loaded symbol image file: ntkrpamp.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Tue Aug 04 05:26:11 2009 (4A77FEB3)
CheckSum: 00370777
ImageSize: 003B9000
File version: 6.0.6002.18082
Product version: 6.0.6002.18082
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 6.0.6002.18082
FileVersion: 6.0.6002.18082 (vistasp2_gdr.090803-2339)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

//...but your usb device driver is from Vista SP1!:
0: kd> lmvm usbuhci
start end module name
87ff2000 87ffd000 usbuhci
Loaded symbol image file: usbuhci.sys
Image path: \SystemRoot\system32\DRIVERS\usbuhci.sys
Image name: usbuhci.sys
Timestamp: Sat Jan 19 00:53:20 2008 (47919050)
CheckSum: 0000AF6F
ImageSize: 0000B000
File version: 6.0.6001.18000
Product version: 6.0.6001.18000
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: USBUHCI.sys
OriginalFilename: USBUHCI.sys
ProductVersion: 6.0.6001.18000
FileVersion: 6.0.6001.18000 (longhorn_rtm.080118-1840)
FileDescription: UHCI USB Miniport Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.

I'm not sure how this is possible, because there are a bunch of drivers SP2 doesn't update, but I can reproduce this and can confirm most of the usb* binaries don't get updated by SP2. I would consider contacting Microsoft on this (you should be able to open a free case, considering this is indeed a known bug) and see if there's something specific that can be done to get this fixed on Vista SP2. I know for certain it was fixed for Win7, but I don't know for certain it was actually fixed properly on Vista SP2, and in fact it does seem it was not (considering the binary where this occurs wasn't updated).

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...