Random 9F Driver Power State Failure BSOD

[dpm5049]

Hello,

I'm getting random driver power state failure (9f) BSODs without any discernible trigger event as far as application. I used the sevenforum tool to collect the information. You guys have been very helpful in the past and hopefully can help with this issue too.

Thanks.

 

[Arc]

Hello dpm5049.

You need to update your realtek driver, as advised here, too.

fffff880`06247000 fffff880`062cc000   Rt64win7   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
 [COLOR=Red]   Image name: Rt64win7.sys
    Timestamp:        Fri Jun 10 12:03:15 2011[/COLOR] (4DF1BAAB)
    CheckSum:         0008B67F
    ImageSize:        00085000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

All the recent dumps I have checked are identically same, and vague.

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800513e050, fffff80001c5a518, fffffa80040cda50}

Probably caused by : sbp2port.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: fffffa800513e050, Physical Device Object of the stack
Arg3: fffff80001c5a518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa80040cda50, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  sbp2port.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79299

MODULE_NAME: sbp2port

FAULTING_MODULE: fffff88001aee000 sbp2port

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80001C60FB0

STACK_TEXT:  
fffff800`01c5a4c8 fffff800`01f026d2 : 00000000`0000009f 00000000`00000003 fffffa80`0513e050 fffff800`01c5a518 : nt!KeBugCheckEx
fffff800`01c5a4d0 fffff800`01ea2c3c : fffff800`01c5a600 fffff800`01c5a600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33ac0
fffff800`01c5a570 fffff800`01ea2ad6 : fffff800`0203ff20 00000000`000a0648 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`01c5a5e0 fffff800`01ea29be : 00000017`dcbf3c89 fffff800`01c5ac58 00000000`000a0648 fffff800`0200db88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`01c5ac30 fffff800`01ea27a7 : 00000007`f32e44c1 00000007`000a0648 00000007`f32e449e 00000000`00000048 : nt!KiTimerExpiration+0x1be
fffff800`01c5acd0 fffff800`01e8fcca : fffff800`0200ae80 fffff800`02018cc0 00000000`00000000 fffff880`00dc74c0 : nt!KiRetireDpcList+0x277
fffff800`01c5ad80 00000000`00000000 : fffff800`01c5b000 fffff800`01c55000 fffff800`01c5ad40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_disk_IMAGE_sbp2port.sys

BUCKET_ID:  X64_0x9F_3_disk_IMAGE_sbp2port.sys

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

0: kd> !irp fffffa80040cda50
Irp is active with 4 stacks 2 is current (= 0xfffffa80040cdb68)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [ 16, 0]   0  0 fffffa800513e050 00000000 fffff88001bc4d30-fffffa80051485a0    
           \Driver\sbp2port    CLASSPNP!ClasspPowerUpCompletion
            Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 fffffa8005148060 00000000 fffff88000fa9f50-00000000 Success Error Cancel pending
           \Driver\Disk    partmgr!PmPowerCompletion
            Args: 00021100 00000001 00000001 00000002
 [ 16, 2]   0 e1 fffffa8005148b90 00000000 00000000-00000000    pending
           \Driver\partmgr
            Args: 00021100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8006c0ff90    

            Args: 00000000 00000000 00000000 00000000
0: kd> !devobj fffffa8005148b90
Device object (fffffa8005148b90) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa8005148b60
 \Driver\partmgr DriverObject fffffa8003d36bd0
Current Irp 00000000 RefCount 0 Type 00000007 Flags 00002010
DevExt fffffa8005148ce0 DevObjExt fffffa8005148f90 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa8005148060 \Driver\Disk
Device queue is not busy.
0: kd> !devobj fffffa8005148060
Device object (fffffa8005148060) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa8005148030
 \Driver\Disk DriverObject fffffa8004242920
Current Irp 00000000 RefCount 0 Type 00000007 Flags 01002050
Vpb fffffa8004f41220 DevExt fffffa80051481b0 DevObjExt fffffa8005148858 Dope fffffa8004efd220 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) fffffa8005148b90 \Driver\partmgr
AttachedTo (Lower) fffffa800513e050 \Driver\sbp2port
Device queue is not busy.

Moreover, there are some STORPORT.sys errors present in the dumps. THose port errors might occur due to some malware. Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

If it comes clean, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.