Windows 7 BSOD during Sleep/hibernation

[mslinux235]

Hi,

I get BSOD "Driver power state failure" when i try to resume from sleep mode, sometimes i can resume without any problems after the system has been in sleep for hours. I am attaching all the dump files in the minidump folder.

This is the report for the latest bsod , using Nirsoft Blue screen viewer -

[Dump File : 052811-13260-01.dmp
Crash Time : 5/28/2011 1:24:41 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`048bca10
Parameter 3 : fffff800`0404c748
Parameter 4 : fffffa80`03f7e5a0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7fd00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052811-13260-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 833,136
==================================================

System Info - i3 540
MSI H55-p33 ( onboard Graphics)
4gb corsair Ram ( I checked the Ram using windows diagnostic tool)
Corsair CX400 PSU

OS - Windows 7 Pro x64 / Xp pro x86 dual boot , Only Using Win7 ( Bsod Happens in Win7 )

I have updated Video, Lan , Audio drivers to latest versions but still getting Bsod.Link Removed

 

[mslinux235]

Bump......

 

[Saltgrass]

Even though I am not very good at finding problems, I would try if you could attach a .zip of the dump file.

 

[mslinux235]

I already attached all the dump files in the first post , at the end of the 1st post there is a link for "new folder.rar" it has all the dump files.

 

[Captain Jack]

Hi there,

Seems like the crash is caused by your Network driver i.e. Rt64win7.sys, So I would recommend to download a new copy from Internet then disconnect from internet then remove the drivers and install the new versions in.

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: fffffa80048bca10, Physical Device Object of the stack
Arg3: fffff8000404c748, Functional Device Object of the stack
Arg4: fffffa8003f7e5a0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8003f7e5a0

DEVICE_OBJECT: fffffa8005024050

DRIVER_OBJECT: fffffa800509ea70

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d5b92fd

MODULE_NAME: Rt64win7

FAULTING_MODULE: fffff88003f8b000 Rt64win7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b3e9c2 to fffff80002ad1d00

STACK_TEXT:  
fffff800`0404c6f8 fffff800`02b3e9c2 : 00000000`0000009f 00000000`00000003 fffffa80`048bca10 fffff800`0404c748 : nt!KeBugCheckEx
fffff800`0404c700 fffff800`02add652 : fffff800`0404c830 fffff800`0404c830 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`0404c7a0 fffff800`02add4f6 : fffff800`02c79f00 00000000`00176fe7 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`0404c810 fffff800`02add3de : 00000037`ca167d26 fffff800`0404ce88 00000000`00176fe7 fffff800`02c48f68 : nt!KiProcessExpiredTimerList+0xc6
fffff800`0404ce60 fffff800`02add1c7 : fffff800`02c44ec1 fffff800`00176fe7 fffffa80`048ee050 00000000`000000e7 : nt!KiTimerExpiration+0x1be
fffff800`0404cf00 fffff800`02ad4765 : 00000000`00000000 fffffa80`04193770 00000000`00000000 fffff880`044f4588 : nt!KiRetireDpcList+0x277
fffff800`0404cfb0 fffff800`02ad457c : fffff800`02a39460 fffff880`0816c400 fffff800`02a39460 fffff800`00000000 : nt!KyRetireDpcList+0x5
fffff880`0816c350 fffff800`02b1d8dc : 00000000`00000000 fffffa80`04193770 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
fffff880`0816c380 fffff800`02ad9838 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0xcc
fffff880`0816c510 fffff880`014bf992 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`053b4c00 : nt!KeWaitForSingleObject+0x228
fffff880`0816c5b0 fffff880`053b4c8e : fffff880`01517101 fffffa80`052d31a0 fffff880`014fc110 fffff880`01517101 : ndis!NdisWaitEvent+0x32
fffff880`0816c5f0 fffff880`01517101 : fffffa80`052d31a0 fffff880`014fc110 fffff880`01517101 fffffa80`052d31a0 : avfwim+0x6c8e
fffff880`0816c5f8 fffffa80`052d31a0 : fffff880`014fc110 fffff880`01517101 fffffa80`052d31a0 fffff880`0156ad2d : ndis!_security_cookie+0x1
fffff880`0816c600 fffff880`014fc10f : fffff880`01517101 fffffa80`052d31a0 fffff880`0156ad2d 00000000`00000000 : 0xfffffa80`052d31a0
fffff880`0816c608 00000000`00000000 : fffffa80`04a02870 00000000`00000000 fffff880`01517110 00000000`00000000 : ndis!ndisFreeReceiveQueue+0x11f


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys

BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys

 

[mslinux235]

Thanks a lot for looking into this Captain Jack , i had updated the realtek Lan drivers twice before and have the latest driver installed but was still getting the BSOD , now that i know which driver is causing the BSOD it will easier to fix this.