none
BSOD DRIVER_POWER_STATE FAILURE 0x1000009f ntoskrnl.exe

    Question

  • Hi there,

    I get a BSOD every once in a while, but only for a few weeks by now:

    Sometimes while working on the computer it just freezes (not using any certain program), I can't use my mouse/ keyboard, sound stops, waiting a long time sometimes helps, but after 10-15 minutes I usually give up and reset.

    Then rebooting most of the time does not work propperly: The computer waits about 30secs showing my motherboard instructions (BIOS key, boot menu key, ...), then freezes for about 5-10 minutes showing the windows logo and saying something like "windows is starting up" (the black screen with the 4 colored windows logo). Sometimes it doesn't continue from there at all. If it does the computer runs fine (after the 10min boot). Otherwise I reset it again, Windows asks whether I want to start normal or safe mode, normal works.

    Yesterday windows told me while booting that I'd need to do a system restore, did that. Works for now, but I'd like to really solve the problem.

    Checking the last crashes I always have the same BSOD:

    Problemsignatur
    Problemereignisame:    BlueScreen
    Betriebsystemversion:    6.1.7601.2.1.0.256.1
    Gebietsschema-ID:    1031

    Weitere Informationen über das Problem
    BCCode:    1000009f
    BCP1:    0000000000000004
    BCP2:    0000000000000258
    BCP3:    FFFFFA8003CFF040
    BCP4:    FFFFF80000B9C510
    OS Version:    6_1_7601
    Service Pack:    1_0
    Product:    256_1
    Bucket-ID:    X64_0x9F_4_IMAGE_nvstor.sys
    Serverinformationen:    7ef390d9-572b-4571-853a-9a9c91b1c365

    I'm not really into understanding the Minidump, just saw it it the ntoskrnl.exe at ntoskrnl.exe+ 78a8a causing the problem. My Minidump: https://www.dropbox .com/s/1351wa0e47hs4qt/042614-411998-01.dmp (delete the space behind dropbox. Can't upload files...)

    My system:
    AMD Athlon II X2 250 (3.0Ghz)
    Asus M4N68T-M LE V2
    Sapphire/ AMD HD4850
    2x2GB RAM

    anything missing?
    Thanks for your help!


    Monday, April 28, 2014 12:21 PM

All replies

  • Hi,

    The attached DMP file is of the DRIVER_POWER_STATE_FAILURE (9f) bug check.

    This bug check indicates that the driver is in an inconsistent or invalid power state.

    BugCheck 1000009F, {4, 258, fffffa8003cff040, fffff80000b9c510}
    

    ^^ 1st parameter = 0x4, which implies that a power IRP has failed to synchronize with the PnP Manager. With this said, we'll need a kernel-dump to properly debug this type of bug check as not information lies within the minidump.

    Kernel-dumps are located at C:\Windows and named MEMORY.DMP. If there is nothing there, you may need to enable generation of them - http://msdn.microsoft.com/en-us/library/windows/hardware/ff540128%28v=vs.85%29.aspx

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Monday, April 28, 2014 5:41 PM
  • Thanks for your fast reply!

    The computer doesn't boot anymore (I gave it a couple tries): Windows startup repair tried to restore, didn't help. Next time the startup repair had no more ideas and gave up with some error...

    I used a linux live system to save the MEMORY.DMP. It's huge :) Almost 300MB for you:

    https://www.dropbox.com/s/r5lo2fg3xep5cpa/MEMORY.DMP

    After that the computer bootet completely fine (no slow Mainboard/ Bootscreen like always during last weeks, no slow windows logo). But I guess nothing is solved so far :)

    Would it help to reinstall Windows? Power Failure sounds like a hardware issue, but does 'driver'powerfailure mean it's a software problem? The installation is quite new. I used a 32bit system for a long time, switched to 64bit a few months ago.

    Hope that helps you. Thanks!

    Friday, May 02, 2014 5:06 PM
  • Thanks very much for the kernel-dump!

    DRIVER_POWER_STATE_FAILURE (9f)

    This bug check indicates that the driver is in an inconsistent or invalid power state.

    0: kd> knL
     # Child-SP          RetAddr           Call Site
    00 fffff800`00b9c4d8 fffff800`02d117e6 nt!KeBugCheckEx
    01 fffff800`00b9c4e0 fffff800`02ec234c nt!PnpBugcheckPowerTimeout+0x76
    02 fffff800`00b9c540 fffff800`02c8a85c nt!PopBuildDeviceNotifyListWatchdog+0x1c
    03 fffff800`00b9c570 fffff800`02c8a6f6 nt!KiProcessTimerDpcTable+0x6c
    04 fffff800`00b9c5e0 fffff800`02c8a5de nt!KiProcessExpiredTimerList+0xc6
    05 fffff800`00b9cc30 fffff800`02c8a3c7 nt!KiTimerExpiration+0x1be
    06 fffff800`00b9ccd0 fffff800`02c778ca nt!KiRetireDpcList+0x277
    07 fffff800`00b9cd80 00000000`00000000 nt!KiIdleLoop+0x5a
    


    Not really much info in the call stack, just a few PnP routines that call into the bugcheck eventually. No driver in the stack, etc.


    0: kd> !locks
    **** DUMP OF ALL RESOURCE OBJECTS ****
    KD: Scanning for held locks..
    
    Resource @ nt!IopDeviceTreeLock (0xfffff80002e83ce0)    Shared 1 owning threads
         Threads: fffffa8003cff040-01<*> 
    KD: Scanning for held locks.
    
    Resource @ nt!PiEngineLock (0xfffff80002e83be0)    Exclusively owned
        Contention Count = 11
        NumberOfExclusiveWaiters = 1
         Threads: fffffa8003cff040-01<*> 
         Threads Waiting On Exclusive Access:
                  fffffa8003cfe660       
    


    0: kd> !thread fffffa8003cff040
    THREAD fffffa8003cff040  Cid 0004.002c  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable
        fffff88002fd21f0  SynchronizationEvent
    Not impersonating
    DeviceMap                 fffff8a0000060c0
    Owning Process            fffffa8003cecb30       Image:         System
    Attached Process          N/A            Image:         N/A
    Wait Start TickCount      5039734        Ticks: 38462 (0:00:10:00.011)
    Context Switch Count      356079         IdealProcessor: 0  NoStackSwap
    UserTime                  00:00:00.000
    KernelTime                00:00:05.896
    Win32 Start Address nt!ExpWorkerThread (0xfffff80002c89150)
    Stack Init fffff88002fd2db0 Current fffff88002fd1f10
    Base fffff88002fd3000 Limit fffff88002fcd000 Call 0
    Priority 15 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`02fd1f50 fffff800`02c755f2 : fffffa80`03cff040 fffffa80`03cff040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
    fffff880`02fd2090 fffff800`02c8699f : fffffa80`07524c80 fffff800`02c64a72 00000000`00000000 fffffa80`04686000 : nt!KiCommitThreadWait+0x1d2
    fffff880`02fd2120 fffff880`010dbf21 : fffffa80`06ea6600 00000000`00000000 fffff880`02fd2600 fffffa80`06ea6600 : nt!KeWaitForSingleObject+0x19f
    fffff880`02fd21c0 fffff880`010ddb41 : 00000000`00000000 fffff880`02fd2620 fffff880`010e9a60 00000000`00000000 : storport!RaSendIrpSynchronous+0x71
    fffff880`02fd2220 fffff880`010e13f1 : 00000000`00000000 fffff880`00000000 fffff880`02fd24c0 fffff880`02fd2628 : storport!RaidBusEnumeratorIssueSynchronousRequest+0x91
    fffff880`02fd2330 fffff880`010e151e : fffffa80`068d2ad0 fffff880`00000000 fffff880`02fd2420 fffff880`02fd24c0 : storport!RaidBusEnumeratorIssueReportLuns+0x71
    fffff880`02fd2380 fffff880`010e789b : 00000000`00000000 fffff6fc`00000000 00000000`00000000 fffff880`02fd24c0 : storport!RaidBusEnumeratorGetLunListFromTarget+0xae
    fffff880`02fd2400 fffff880`010e79e4 : fffff800`02eba540 00000000`00000000 00000000`00000000 00000000`00000000 : storport!RaidBusEnumeratorGetLunList+0x5b
    fffff880`02fd2490 fffff880`010e7ad6 : fffffa80`047a81b0 00000000`00000001 00000000`00000000 fffffa80`047a81b0 : storport!RaidAdapterEnumerateBus+0x94
    fffff880`02fd2600 fffff880`01126812 : 00000000`00000000 fffff880`010ce8f1 fffff880`01126b20 00000000`000000ca : storport!RaidAdapterRescanBus+0x76
    fffff880`02fd2710 fffff880`01126a20 : fffffa80`055de090 00000000`00000000 fffffa80`047a81b0 fffffa80`055de090 : storport!RaidAdapterQueryDeviceRelationsIrp+0xa2
    fffff880`02fd2750 fffff880`01126bb4 : fffffa80`055de090 fffff880`010ec110 fffffa80`047a8060 00000000`00010286 : storport!RaidAdapterPnpIrp+0x150
    fffff880`02fd27b0 fffff800`0303c18e : fffffa80`055de090 fffffa80`0652cdc0 fffffa80`047a8060 fffff880`009ed180 : storport!RaDriverPnpIrp+0x94
    fffff880`02fd27f0 fffff800`0303c4fa : 00000000`00000000 fffffa80`0652cdc0 fffff800`02d7fed0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
    fffff880`02fd2830 fffff800`0303e847 : fffff800`02e839a0 fffffa80`03cb7b10 00000000`00000002 00000000`00000540 : nt!PnpQueryDeviceRelations+0xfa
    fffff880`02fd28f0 fffff800`0306ee3c : fffffa80`03cb7b10 fffffa80`03cb003c fffffa80`03cb7b10 00000000`00000002 : nt!PipEnumerateDevice+0x117
    fffff880`02fd2950 fffff800`0306f448 : fffff800`02e81560 00000000`00000000 00000000`00000001 fffff800`02eeae08 : nt!PipProcessDevNodeTree+0x21c
    fffff880`02fd2bc0 fffff800`02d82827 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
    fffff880`02fd2c10 fffff800`02c89261 : fffff800`02d82500 fffff800`02e25201 fffffa80`03cff000 fffffa80`00000000 : nt!PnpDeviceActionWorker+0x327
    fffff880`02fd2cb0 fffff800`02f1c2ea : 3155082d`4e082847 fffffa80`03cff040 00000000`00000080 fffffa80`03cecb30 : nt!ExpWorkerThread+0x111
    fffff880`02fd2d40 fffff800`02c708e6 : fffff880`009ed180 fffffa80`03cff040 fffff880`009f7f40 396b8f38`688d3667 : nt!PspSystemThreadStartup+0x5a
    fffff880`02fd2d80 00000000`00000000 : fffff880`02fd3000 fffff880`02fcd000 fffff880`02fd29e0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    

     

    There's no IRP list to run !irp on, however, we have a bit more of an informative call stack. We can see various storport.sys (Microsoft Storage Port driver) calls. With that said, it looks like we may have possibly had an I/O request (ultimately an IRP) sent along the Disk, and to the storage driver. Now, the better question is, what did storport.sys do with it? Unfortunately, with no IRP list, I don't know!

    -------------------------

    In the mean time, if you crash again, here's what I can tell you:

    1. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.

    Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:

    C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

    and rename AODDriver2.sys to AODDriver.2old

    and then Restart.

    2. Remove and replace Avira with Microsoft Security Essentials for temporary troubleshooting purposes as it's very likely causing file system conflicts:

    Avira removal - http://www.avira.com/en/support-for-home-knowledgebase-detail/kbid/88

    MSE -http://windows.microsoft.com/en-us/windows/security-essentials-download

    3.

    0: kd> lmvm asacpi
    start             end                 module name
    fffff880`04232000 fffff880`0423a000   ASACPI     (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
        Image name: ASACPI.sys
        Timestamp:        Sun Mar 27 22:30:36 2005

    ASACPI.sys is dated from 2005, Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities. The pre-2009 driver causes many BSOD's. With that said, either update your utilities via Asus' website, or uninstall all of them ASAP. I recommend the latter as Asus' bloatware is generally useless.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Friday, May 02, 2014 7:24 PM
  • There's no IRP list to run !irp on, however, we have a bit more of an informative call stack. We can see various storport.sys (Microsoft Storage Port driver) calls. With that said, it looks like we may have possibly had an I/O request (ultimately an IRP) sent along the Disk, and to the storage driver. Now, the better question is, what did storport.sys do with it? Unfortunately, with no IRP list, I don't know!

    >>Okay. Is there a chance to get this IRP list? The computer boots every once in a while. Using it right now. But had another crash this morning, too

    ----

    1. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.

    Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:

    C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

    and rename AODDriver2.sys to AODDriver.2old

    and then Restart.

    >>AMD Overdrive is installed. Included in the Catalyst Control Center, but I can't uninstall it without uninstalling the CCC (which holds the graphic drivers?). Just rename the AODDriver2.sys?

    I don't have any Asus utilties installed (at least they aren't listed in 'Programs and Features). How do I remove that EasyTune6 thing?

    ----

    2. Remove and replace Avira with Microsoft Security Essentials for temporary troubleshooting purposes as it's very likely causing file system conflicts:

    Avira removal - http://www.avira.com /en/support-for-home-knowledgebase-detail/kbid/88

    MSE -http://windows.microsoft.com /en-us/windows/security-essentials-download

    >>I'll try that.

    ----

    3.

    0: kd> lmvm asacpi
    start             end                 module name
    fffff880`04232000 fffff880`0423a000   ASACPI     (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
        Image name: ASACPI.sys
        Timestamp:        Sun Mar 27 22:30:36 2005

    ASACPI.sys is dated from 2005, Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities. The pre-2009 driver causes many BSOD's. With that said, either update your utilities via Asus' website, or uninstall all of them ASAP. I recommend the latter as Asus' bloatware is generally useless.

    >>Alright. Same here, how to uninstall?

    Thanks for your help!

    edit: quote-fail. How to split? :)

    Saturday, May 03, 2014 9:00 AM
  • 1. Rename it, yes.

    2. Remove and replace.

    3. Remove any and all Asus software, use Revo if you need to and see if anything pops up - http://www.revouninstaller.com/revo_uninstaller_free_download.html

    If not, rename it as well.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Saturday, May 03, 2014 7:36 PM
  • I couldn't find anything named EasyTune6, did the rest. I did not have any crashes within the last time (that's why I didn't answer for a while, sorry) but the computer still needs really long to boot/ doesn't boot at all (I'm always using hibernation). Boot needs a couple minutes or freezes on the boot screen/ on the desktop right after booting.

    To be honest I'm kind of tired of trying to fix here and there without effect. Would a new installation of Windows help?

    Thanks for your help Patrick!

    Sunday, May 18, 2014 5:45 PM
  • Yes, a new install of Windows should help in this situation if the issue is driver/file system related.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Sunday, May 18, 2014 9:37 PM