BSOD DRIVER_POWER_STATE_FAILURE (9f)

I have been getting the BSOD for the past 3 years (since I got the laptop from DELL). This is my work Laptop and it is annoying like hell now.

Any time my laptop tries to come out of sleep it locks up then a BSOD follows...

I have managed to track the problem using WinDbg to the following:

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80066de040, The thread currently holding on to the Pnp lock.
Arg4: fffff800047ec3d0, nt!TRIAGE_9F_PNP on Win7 and higher

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

Implicit thread is now fffffa80`066de040

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: fffffa80066de040

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

LAST_CONTROL_TRANSFER: from fffff80002ebc5f2 to fffff80002ec9a8a

STACK_TEXT:
fffff880`03708210 fffff800`02ebc5f2 : 00000000`00f80010 fffffa80`066de040 fffffa80`0a6ba110 fffff800`0000000d : nt!KiSwapContext+0x7a
fffff880`03708350 fffff800`02ecd99f : fffffa80`0a6ba110 fffff800`02edb771 00000000`00000000 fffffa80`0c47ebf0 : nt!KiCommitThreadWait+0x1d2
fffff880`037083e0 fffff880`04e0baca : fffffa80`0a6ba100 fffff880`00000000 ffffffff`c0000000 00000000`a0000000 : nt!KeWaitForSingleObject+0x19f
fffff880`03708480 fffff880`04e0f8dd : fffffa80`0c47eb10 00000000`00000000 00000000`00000000 fffff880`03708530 : storport!StorWaitForSingleObject+0x1a
fffff880`037084c0 fffff880`04e5968f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : storport!RaUnitWaitForRemoveLock+0x2d
fffff880`037084f0 fffff880`04e5a383 : fffffa80`0a6ba110 00000000`00000001 fffffa80`09855ab0 fffff880`04e20110 : storport!RaUnitSurpriseRemovalIrp+0x2f
fffff880`03708520 fffff880`04e5abaa : fffffa80`0a45f610 fffff880`04e20110 fffffa80`0c47e9c0 fffffa80`0a6ba110 : storport!RaUnitPnpIrp+0x193
fffff880`03708580 fffff880`019ed6b7 : fffffa80`0a45f610 00000000`c00000bb fffffa80`0a6ba228 fffff800`02e6aefd : storport!RaDriverPnpIrp+0x8a
fffff880`037085c0 fffffa80`0a45f610 : 00000000`c00000bb fffffa80`0a6ba228 fffff800`02e6aefd fffffa80`0a6ba110 : stdcfltn+0x16b7
fffff880`037085c8 00000000`c00000bb : fffffa80`0a6ba228 fffff800`02e6aefd fffffa80`0a6ba110 fffffa80`09855aa0 : 0xfffffa80`0a45f610
fffff880`037085d0 fffffa80`0a6ba228 : fffff800`02e6aefd fffffa80`0a6ba110 fffffa80`09855aa0 fffffa80`09855a01 : 0xc00000bb
fffff880`037085d8 fffff800`02e6aefd : fffffa80`0a6ba110 fffffa80`09855aa0 fffffa80`09855a01 fffffa80`0c3f91b0 : 0xfffffa80`0a6ba228
fffff880`037085e0 fffff880`014a6ae5 : 00000000`00000001 00000000`c00000bb fffff880`014a1110 fffffa80`0a6ba110 : nt!IoGetDriverObjectExtension+0x3d
fffff880`03708610 fffff800`031ea219 : fffffa80`0c3f91b0 fffffa80`09855ac8 fffffa80`0a6ba270 fffffa80`06902240 : CLASSPNP! ?? ::NNGAKEGL::`string'+0x1783
fffff880`037086a0 fffff880`00fe26d3 : fffffa80`0a6ba110 fffffa80`09f64c18 fffffa80`06902200 fffffa80`0c47e900 : nt!IoForwardIrpSynchronously+0x75
fffff880`03708700 fffff880`00fe42c4 : fffffa80`0a6ba110 fffffa80`0a6ba2b8 00000000`00000000 fffffa80`09f64a40 : partmgr!PmSurpriseRemoval+0xa3
fffff880`03708740 fffff800`03132571 : fffffa80`09f64a40 fffff880`03708848 00000000`c00000bb fffffa80`0a6ba110 : partmgr!PmPnp+0xb4
fffff880`03708790 fffff800`032b33a1 : fffffa80`0c47e9c0 00000000`00000000 fffffa80`0a3163e0 fffff800`02ffae80 : nt!IopSynchronousCall+0xe1
fffff880`03708800 fffff800`032add78 : fffff880`037089c0 fffffa80`0c47e9c0 00000000`0000030a 00000000`00000308 : nt!IopRemoveDevice+0x101
fffff880`037088c0 fffff800`032b2ee7 : fffffa80`0a3163e0 00000000`00000000 00000000`00000003 00000000`00000070 : nt!PnpSurpriseRemoveLockedDeviceNode+0x128
fffff880`03708900 fffff800`032b3000 : 00000000`00000000 fffff8a0`0fbe5d00 fffff8a0`137dc130 fffff880`03708a58 : nt!PnpDeleteLockedDeviceNode+0x37
fffff880`03708930 fffff800`0334397f : 00000000`00000002 00000000`00000000 fffffa80`0a3163e0 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`037089a0 fffff800`0334453c : fffff880`03708b78 00000000`00000000 fffff8a0`05f0e500 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0x6cf
fffff880`03708ae0 fffff800`0322d73e : 00000000`00000000 fffffa80`0c17a6a0 fffff8a0`0fbe5da0 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`03708b10 fffff800`02ed0261 : fffff800`031313d8 fffff8a0`0fbe5da0 fffff800`0306c2d8 fffffa80`066de040 : nt! ?? ::NNGAKEGL::`string'+0x54d9b
fffff880`03708b70 fffff800`0316273a : 00000000`00000000 fffffa80`066de040 00000000`00000080 fffffa80`066514a0 : nt!ExpWorkerThread+0x111
fffff880`03708c00 fffff800`02eb78e6 : fffff880`033e4180 fffffa80`066de040 fffff880`033eefc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03708c40 00000000`00000000 : fffff880`03709000 fffff880`03703000 fffff880`037076d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .thread 0xfffffa80066de040 ; kb

FOLLOWUP_IP:
stdcfltn+16b7
fffff880`019ed6b7 ?? ???

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: stdcfltn+16b7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: stdcfltn

IMAGE_NAME: stdcfltn.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e211411

FAILURE_BUCKET_ID: X64_0x9F_4_stdcfltn+16b7

BUCKET_ID: X64_0x9F_4_stdcfltn+16b7

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x9f_4_stdcfltn+16b7

FAILURE_ID_HASH: {9e57d5f5-6998-ba4d-1c20-b72b382dcf1d}

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

0: kd> lmvm stdcfltn
start end module name
fffff880`019ec000 fffff880`019f5000 stdcfltn T (no symbols)
Loaded symbol image file: stdcfltn.sys
Image path: \SystemRoot\system32\DRIVERS\stdcfltn.sys
Image name: stdcfltn.sys
Timestamp: Sat Jul 16 05:31:13 2011 (4E211411)
CheckSum: 00007FF2
ImageSize: 00009000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Now I don't know what this driver is for nor do I understand what is using this driver. Research states that it is an accelerometer. So if someone could please enlighten me as to what to do with this problem I would be very appreciative.

sorry for the large post but I was hoping to save you guys some time.

Many thanks
Aikikai

Follow Blue Screen of Death (BSOD) Posting Instructions ... attach the data with your reply post.

Apparently your RAID discs are failing to respond within a stipulated time period when the computer is waking up from sleep. Do you really need RAID there for the laptop? Decide it. If not, it would be the best (and the permanent solution) that you break the RAID, set the storage controller mode to AHCI and perform a clean reinstall of windows. The clean reinstall will be a must in that case, because the change in storage controller mode will make windows unable to boot.

If RAID is a must for you (it is not for most of us), update the intel IRST driver, which is too old.

Code:

    Image name: iaStor.sys
    Timestamp:        Thu May 31 02:10:40 2012

Get it form https://downloadcenter.intel.com/ ... or you may try to find an update in Dell's site too.

Also, follow Power Plan Settings - Change .... go upto point 5(B) and set teh time for hard driver to zero or never whichever is applicable there. Dont let the discs to go to sleep.

And, another most important thing is, free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and Apoint.exe.
5. Apply > OK
6. Accept then restart.

Let us know your decision and the resulting situation.
_______________________________________

Code:

BugCheck 9F, {3, fffffa800d341060, fffff80004795748, fffffa800d425bd0}

Probably caused by : msiscsi.sys

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

Code:

 [ 16, 0]   0  0 fffffa800d341060 00000000 fffff880017e1d30-fffffa800d34ccd0    
           \Driver\iScsiPrt    CLASSPNP!ClasspPowerUpCompletion
            Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 fffffa800d34c790 00000000 fffff88000e05f50-00000000 Success Error Cancel pending
           \Driver\Disk    partmgr!PmPowerCompletion
            Args: 00041100 00000001 00000001 00000002
 [ 16, 2]   0 e1 fffffa800dc7f6a0 00000000 00000000-00000000    pending
           \Driver\partmgr
            Args: 00041100 00000001 00000001 00000002

OK, let us know for any further issue. :)