Solved BSOD instead of sleep/hibernate

[sanchises]

Hi,

Since a while, I'm unable to sleep my computer. Instead of sleeping, the screen goes black with the computer apparently still working (I can lock and unlock my computer 'blindly', and hear the lock/unlock sounds). After a while though, the system will then crash with a BSOD: DRIVER_POWER_STATE_FAILURE

Attached is the zip file with the dumps etc,

Note to admins:this tool does not actually put the zip file on the desktop (which is D:\Desktop in my case) but simply in C:\Users\[username]\Desktop. Could potentially be confusing...

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800432e050, fffff80000b9c3d8, fffffa800a0931d0}

*** WARNING: Unable to verify timestamp for KSPrt64.sys
*** ERROR: Module load completed but symbols could not be loaded for KSPrt64.sys
Probably caused by :[COLOR="Red"][B] KSPrt64.sys[/B][/COLOR]

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.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800432e050, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800a0931d0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  KSPrt64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e56d23b

MODULE_NAME: KSPrt64

FAULTING_MODULE: fffff880010fc000 KSPrt64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

DPC_STACK_BASE:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c388 fffff800`039018d2 : 00000000`0000009f 00000000`00000003 fffffa80`0432e050 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`0389c85c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`0389c6f6 : fffffa80`07ed0380 fffffa80`07ed0380 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`0389c5de : 0000000b`89824de9 fffff800`00b9cb18 00000000`0004d8c4 fffff800`03a10b08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`0389c3c7 : 00000002`3f061dc2 00000002`0004d8c4 00000002`3f061dff 00000000`000000c4 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`038898ca : fffff800`03a0ce80 fffff800`03a1acc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  [COLOR="red"][B]X64_0x9F_3_POWER_DOWN_cdrom_IMAGE_KSPrt64.sys[/B][/COLOR]

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_cdrom_IMAGE_KSPrt64.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_cdrom_image_ksprt64.sys

FAILURE_ID_HASH:  {9256b14b-8e2e-0f96-dcd9-a08493409b2f}

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

0: kd> !irp fffffa800a0931d0
Irp is active with 4 stacks 3 is current (= 0xfffffa800a093330)
 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
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8006064e10 00000000 00000000-00000000    pending
	       [B][COLOR="red"]\Driver\cdrom[/COLOR][/B]
			Args: 00015400 00000001 00000004 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8003f7e560    

			Args: 00000000 00000000 00000000 00000000

0: kd> lmvm ksprt64
start             end                 module name
fffff880`010fc000 fffff880`01122000   KSPrt64  T (no symbols)           
    Loaded symbol image file: KSPrt64.sys
    Image path: KSPrt64.sys
    Image name: [B][COLOR="red"]KSPrt64.sys[/COLOR][/B]
    Timestamp:        [B][COLOR="red"]Fri Aug 26 08:22:43 2011[/COLOR][/B] (4E56D23B)
    CheckSum:         0002ED85
    ImageSize:        00026000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Check for updates for for your virtual dvd/cd device below:
KernSafe iSCSI initiator, Virtual CD/DVD-RW Emulator, Virtual Encryption Disk and Virtual CD/DVD-ROM Emulator All-in-One free software.

 

[sanchises]

This was caused by KernSafe TotalMounter. My advice: do not download this software.

 

[Golden]

This was caused by KernSafe TotalMounter. My advice: do not download this software.

Thats correct - thats what the .dmp files identified :sarc: