Solved Driver power state failure

Hagrinas

New Member
Messages
2
Computer was recently updated to Windows 8. When laptop lid is closed and opened, BSOD instead of sleep. I need to know which driver is causing it. "grab all" results attached. Thanks.
 

My Computer

System One

  • OS
    Windows 8
Welcome to Eight Forums,

Looks like a mixture of drivers from Acronis and Total Mounter seems to be the cause of the BSOD.
I would uninstall both these programs and their drivers and see if the sleep mode BSOD is eliminated.


Do you have a SSD and is the firmware for it up to date? Check for one, it may bring stability.
Code:
********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 9F, {3, fffffa8005c49050, fffff8033d53c7e0, fffffa8009021010}


*** WARNING: Unable to verify timestamp for KSPrt64.sys
*** ERROR: Module load completed but symbols could not be loaded for KSPrt64.sys
Probably caused by : KSPrt64.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: fffffa8005c49050, Physical Device Object of the stack
Arg3: fffff8033d53c7e0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8009021010, The blocked IRP


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




DRVPOWERSTATE_SUBCODE:  3


IMAGE_NAME:  KSPrt64.sys


DEBUG_FLR_IMAGE_TIMESTAMP:  4e56d23b


MODULE_NAME: KSPrt64


FAULTING_MODULE: fffff880017a2000 KSPrt64


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  0x9F


PROCESS_NAME:  System


CURRENT_IRQL:  2


TAG_NOT_DEFINED_c000000f:  FFFFF8033D542FB0


STACK_TEXT:  
fffff803`3d53c7a8 fffff803`3ba15f6e : 00000000`0000009f 00000000`00000003 fffffa80`05c49050 fffff803`3d53c7e0 : nt!KeBugCheckEx
fffff803`3d53c7b0 fffff803`3ba15fa1 : fffffa80`090979a0 fffffa80`08e83e80 fffff803`3d53c939 fffff803`3b92c786 : nt!PopIrpWatchdogBugcheck+0xe2
fffff803`3d53c810 fffff803`3b92d8e4 : fffffa80`08e83e80 fffffa80`09000b00 fffff803`3d53cb18 fffff803`3bb7c180 : nt!PopIrpWatchdog+0x32
fffff803`3d53c860 fffff803`3b92dfd5 : 00000000`00000000 00000000`0000313b 00000000`00140001 00000000`000000c7 : nt!KiProcessExpiredTimerList+0x214
fffff803`3d53c9a0 fffff803`3b92de88 : fffff803`3bb7c180 fffff803`3bb7ef80 00000000`00000007 00000000`00078eaf : nt!KiExpireTimerTable+0xa9
fffff803`3d53ca40 fffff803`3b9282d6 : fffffa80`00000000 00001fa0`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff803`3d53caf0 fffff803`3b92c67a : fffff803`3bb7c180 fffff803`3bb7c180 00000000`00183de0 fffff803`3bbd6880 : nt!KiRetireDpcList+0x1f6
fffff803`3d53cc60 00000000`00000000 : fffff803`3d53d000 fffff803`3d537000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a




STACK_COMMAND:  kb


FOLLOWUP_NAME:  MachineOwner


FAILURE_BUCKET_ID:  0x9F_3_disk_IMAGE_KSPrt64.sys


BUCKET_ID:  0x9F_3_disk_IMAGE_KSPrt64.sys


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


0: kd> !irp fffffa8009021010
Irp is active with 4 stacks 2 is current (= 0xfffffa8009021128)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    


			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8007013740 00000000 fffff88000fd1e40-00000000 Success Error Cancel pending
	      Unable to load image \SystemRoot\system32\DRIVERS\fltsrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fltsrv.sys
*** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys
 \Driver\disk	partmgr!PmPowerCompletion
			Args: 00015600 00000001 00000004 00000003
 [ 16, 2]   0 e1 fffffa8007014b10 00000000 fffff8033b9a132c-fffffa8005d2c010 Success Error Cancel pending
	       \Driver\partmgr	nt!PopRequestCompletion
			Args: 00015600 00000001 00000004 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8005d2c010    


			Args: 00000000 00000000 00000000 00000000
Perform a System File Check:
http://www.eightforums.com/tutorials/3047-sfc-scannow-command-run-windows-8-a.html

Reduce items at Start Up:
http://www.eightforums.com/tutorials/5180-startup-items-manage-windows-8-a.html
 

My Computer

System One

  • OS
    Windows 7 Home Premium 64 Bit
    Computer type
    PC/Desktop
Total Mounter is the problem. I have it mostly fixed. Trying to remove it resulted in a different BSOD ("Page fault in nonpaged area") and I tried removing the offending devices in Device Manager and then doing the uninstall. Then the uninstall worked. The problem didn't go away, though, and I found that the two devices were again listed in Device manager. Removing them allowed sleep to work, but they reappeared so I disabled them. Now things seem to work, but I'd rather remove them completely.

I was able to erase KSPrt64.sys and want to know if removing its keys from the registry (once my full backup finishes) is what I need to get rid of it.


 

My Computer

System One

  • OS
    Windows 8
Thanks for letting us know.

Post if you still need help.
 

My Computer

System One

  • OS
    Windows 7 Home Premium 64 Bit
    Computer type
    PC/Desktop
Back
Top