BSOD - DRIVER_POWER_STATE_FAILURE

I have had two blue screens with the error message Driver Power State Failure. The failure appears to occur in ntoskrnl.exe+7cc40. The first time happened when the computer was in sleep mode (or at least idle, I'm not sure because I was not at the computer at the time) and the second was when I was using it. Here is some information that might help:

111111-26660-01.dmp 11/11/2011 6:31:54 PM DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000`00000003 fffffa80`0b895cd0 fffff800`00ba2748 fffffa80`0b37cc60 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\111111-26660-01.dmp 4 15 7601 838,688

Thank you for any help you can give me!
16 answers Last reply
More about bsod driver_power_state_failure
  1. Download and install the most recent graphics driver for your hardware.
  2. which graphics card u have ?

    read this
  3. I updated my graphics driver after the first incident, but it did not resolve the problem. My card is the Radeon 5850. Should I upload my minidump?
  4. Yeah ok. Sure.
  5. Mini dump shows a driver IRP blocking problem.

    Don't know which one causing it thou.

    I will try in elevated command prompt with "sfc /scannow"

    Then update all the driver.

    There are some drivers that is especially old in your computer:

    secdrv.SYS
    UsbFltr.sys
    spldr.sys
    intelppm.sys
    msisadrv.sys
    pcw.sys
    Null.SYS
    Fs_Rec.sys
    atapi.sys
    Msfs.SYS
    Npfs.SYS
    PCIIDEX.SYS
    pciide.sys
    kbdclass.sys
    mouclass.sys
    WMILIB.SYS
    WDFLDR.SYS
    CLFS.SYS
    disk.sys
    nsiproxy.sys
    dump_dumpfve.sys
    Wdf01000.sys
    mup.sys
    luafv.sys
    BATTC.SYS
    compbatt.sys
    wmiacpi.sys
    HidBatt.sys
    mssmbios.sys
    fileinfo.sys
    blbdrive.sys
    discache.sys
    watchdog.sys
    Dxapi.sys
    vga.sys
    VIDEOPRT.SYS
    monitor.sys
    Beep.SYS
    Dot4.sys
    swenum.sys
    ksthunk.sys
    dot4usb.sys
    mouhid.sys
    crashdmp.sys
    vdrvroot.sys
    HIDPARSE.SYS
    portcls.sys
    BthEnum.sys
    bthmodem.sys
    rfcomm.sys
    bthpan.sys
    mpsdrv.sys
    lltdio.sys
    rspndr.sys
    netbios.sys
    wfplwf.sys
    ndistapi.sys
    asyncmac.sys
    raspppoe.sys
    AgileVpn.sys
    rassstp.sys
    RDPCDD.sys
    rdpencdd.sys
    rdprefmp.sys
    usbscan.sys
    usbprint.sys
    peauth.sys
    drmk.sys
    PSHED.dll
    xusb21.sys

    Google for them and see what driver they are associated and try to get a newer driver. Sorry that the list is so long. These are the driver that haven't been updated since or prior to 2009.
  6. Thanks! I ran sfc and there were no errors. I'll google the drivers and get back to you.
  7. http://msdn.microsoft.com/en-us/library/ff559329(v=VS.85).aspx

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


    Points to drivers.

    The fact that the first parameter is 0x03 is worrying, as these should all be caught in development of the driver...Any driver [in particular, GPU driver] upgrades prior to this error first occuring?
  8. I recently did a fresh install of Windows, and this did not occur before that reinstallation. One thing that may be of importance is that my system has issues where it will freeze from time to time, which is why I did the reinstallation. I made a separate article for that a while back, you can see it here
    http://www.tomshardware.com/forum/298379-30-computer-freezing-possibly-motherboard-issue
  9. Could be SRT driver not working well with your hardware. Unfortunately there is no newer driver for SRT. Can you just run the computer on SSD without SRT?
  10. The computer froze when SRT was off, so I don't believe it's that.
  11. Eeek, total system lockups are never good; I had a mobo that did that for a while [790i series, which was FAMOUS for hard-locking]. Usually points to the mobo, if it gets to the point where Windows is unable to BSOD...[seriously, you have to TRY to be able to pull that off...:D]

    Might want to RMA the mobo if possible, if for no other reason to rule that out.
  12. I would think it's the mobo, except I've run Memtest multiple times with no problems.
  13. Another concern about the mobo is that when I installed my Hyper 212+ cooler, the nuts seemed to tear up the paint a bit on the PCB. Would this cause problems and/or void my motherboard warranty? I used this cooler on other mobos and not had this problem...
  14. rjkucia said:
    I would think it's the mobo, except I've run Memtest multiple times with no problems.


    In the case of my old 790i, the hard-locks were due to a northbridge that needed a significant boost in voltage [1.3V from 1.1V], overvolting the RAM significantly, setting RAM timings to the more conservative 2T, and syncing the RAM/FSB to 1:1. Never ONCE did I have a failure in memtest during any of this; its was a low-level mobo thing.

    The main issue with hard-locks is they tend to be very low level, and near impossible to replicate on demand for testing.
  15. With this setup, however, there's no FSB or northbridge, as it's all in the CPU. And it's certainly very difficult to test; every time I think it's fixed, it turns out it isn't. The motherboard is the only other thing I can think of.
Ask a new question

Read More

Drivers Blue Screen Power Error Message Computers Windows 7