Driver power state failure

[sqwob]

I've had this issue with windows 7, 8 and now 8.1 and i'm slowly getting tired of it.

Whenever i wake my pc up, it crashes about 10 minutes into use with the error "Driver power state failure" & it writes a minidump (see attachment for sample)

Currently this is a clean install with only custom ATI drivers installed for my graphics card. I did install software already (lightroom/office/..) but generally i'm only running firefox when it happens.

The minidump mentions iscsi, i do use this occasionally (my nas isn't always on so it can't always find the iscsi target on the server)

all help towards a solution is very much appreciated!

Kind regards
Rik

Some error details

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000040961e0, Physical Device Object of the stack
Arg3: fffff8002a7a8aa0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe00003989180, The blocked IRP
DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: msiscsi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5215f78c

MODULE_NAME: msiscsi

FAULTING_MODULE: fffff80006960000 msiscsi

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`2a7a8a68 fffff800`28fff8d2 : 00000000`0000009f 00000000`00000003 ffffe000`040961e0 fffff800`2a7a8aa0 : nt!KeBugCheckEx
fffff800`2a7a8a70 fffff800`28fff7f2 : ffffe000`06322160 fffff780`00000014 ffffe000`063221a0 fffff800`28e89dbc : nt!PopIrpWatchdogBugcheck+0xde
fffff800`2a7a8ad0 fffff800`28e886e2 : 00000000`00000000 fffff800`2a7a8c20 ffffe000`06322198 ffffe000`00000002 : nt!PopIrpWatchdog+0x32
fffff800`2a7a8b20 fffff800`28f58bea : fffff800`290f6180 fffff800`290f6180 fffff800`2914ea80 ffffe000`06ead880 : nt!KiRetireDpcList+0x6b2
fffff800`2a7a8da0 00000000`00000000 : fffff800`2a7a9000 fffff800`2a7a3000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

More in the dump file...

 

[sqwob]

now with the minidump, i'm now using the SD diag tool to add more details.

 

[koolkat77]

Hello and welcome to the forum.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!

e1y60x64.sys Wed Feb 16 02:21:13 2011 (4D5AE039)
Intel(R) 82567LM Gigabit Network Connection
http://www.carrona.org/drivers/driver.php?id=e1y60x64.sys

ASACPI.sys Fri Nov 2 07:54:34 2012 (509327DA)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys

If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: How To Clear CMOS (Reset BIOS). Uninstall any overclocking tool as these can also be a reason of blue screens.

CPUID:        "Intel(R) Core(TM) i7 CPU         975  @ 3.33GHz" 
MaxSpeed:     3330 
CurrentSpeed: 3338

Test your hard drive: Hard Drive Diagnostic Procedure

********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 9F, {3, ffffe000040961e0, fffff8002a7a8aa0, ffffe00003989180}


Probably caused by : msiscsi.sys


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


0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000040961e0, Physical Device Object of the stack
Arg3: fffff8002a7a8aa0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe00003989180, The blocked IRP


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




DRVPOWERSTATE_SUBCODE:  3


IMAGE_NAME:  msiscsi.sys


DEBUG_FLR_IMAGE_TIMESTAMP:  5215f78c


MODULE_NAME: msiscsi


FAULTING_MODULE: fffff80006960000 msiscsi


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  0x9F


PROCESS_NAME:  System


CURRENT_IRQL:  2


TAG_NOT_DEFINED_c000000f:  FFFFF8002A7AFFB0


STACK_TEXT:  
fffff800`2a7a8a68 fffff800`28fff8d2 : 00000000`0000009f 00000000`00000003 ffffe000`040961e0 fffff800`2a7a8aa0 : nt!KeBugCheckEx
fffff800`2a7a8a70 fffff800`28fff7f2 : ffffe000`06322160 fffff780`00000014 ffffe000`063221a0 fffff800`28e89dbc : nt!PopIrpWatchdogBugcheck+0xde
fffff800`2a7a8ad0 fffff800`28e886e2 : 00000000`00000000 fffff800`2a7a8c20 ffffe000`06322198 ffffe000`00000002 : nt!PopIrpWatchdog+0x32
fffff800`2a7a8b20 fffff800`28f58bea : fffff800`290f6180 fffff800`290f6180 fffff800`2914ea80 ffffe000`06ead880 : nt!KiRetireDpcList+0x6b2
fffff800`2a7a8da0 00000000`00000000 : fffff800`2a7a9000 fffff800`2a7a3000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a




STACK_COMMAND:  kb


FOLLOWUP_NAME:  MachineOwner


FAILURE_BUCKET_ID:  0x9F_3_disk_IMAGE_msiscsi.sys


BUCKET_ID:  0x9F_3_disk_IMAGE_msiscsi.sys


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


0: kd> !irp ffffe00003989180
Irp is active with 4 stacks 2 is current (= 0xffffe00003989298)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [ 16, 0]   0  0 ffffe000040961e0 00000000 fffff8000103fff0-ffffe000053325a0    
           \Driver\iScsiPrt    CLASSPNP!ClasspPowerUpCompletion
            Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 ffffe00005332060 00000000 fffff800005b6c08-00000000 Success Error Cancel pending
           \Driver\disk    partmgr!PmPowerCompletion
            Args: 00051100 00000001 00000001 00000002
 [ 16, 2]   0 e1 ffffe000059bdb20 00000000 fffff80028f1d0e0-ffffe00006322160 Success Error Cancel pending
           \Driver\partmgr    nt!PopRequestCompletion
            Args: 00051100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe00006322160    


            Args: 00000000 00000000 00000000 00000000