Share via

Driver Power State Failure (Windows 8.1 Pro 64-bit)

Anonymous
2014-01-14T15:07:29+00:00

My computer has crash 3 times this week, two of those today. I get a blue screen and an error message of "Driver Power State Failure".

https://www.dropbox.com/s/a2o1btmboh8jmut/122713-11484-01.dmp

https://www.dropbox.com/s/sljr94irb8ab1oi/011414-29187-01.dmp

Here are the two files I found in my minidump folder. Any help would be greatly appreciated.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

7 answers

Sort by: Most helpful
  1. Anonymous
    2015-01-28T18:49:10+00:00

    Any update on this? Did that fix it? What was your solution?

    Start you own thread, with the link to the dump files included, and someone will be happy to help you.

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2015-01-28T18:14:46+00:00

    Any update on this? Did that fix it? What was your solution?

    0 comments No comments
  3. Anonymous
    2014-01-15T22:55:59+00:00

    My pleasure, I look forward to your update.

    Regards,

    Patrick

    0 comments No comments
  4. Anonymous
    2014-01-15T13:54:54+00:00

    Thanks for the reply. I set up the Driver Verifier, but after a restart and a few hours of usage there have been no crashes yet. I guess time will tell.

    0 comments No comments
  5. Anonymous
    2014-01-14T23:13:46+00:00

    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.*If we run an !irp on the 4th parameter of the bug check (blocked IRP address), we get the following:

    >[ 16, 2]   0 e1 ffffe00000f02610 00000000 fffff80000808ff0-ffffe00001406cb0 Success Error Cancel pending          Unable to load image \SystemRoot\System32\drivers*ataport.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for ataport.SYS*** ERROR: Module load completed but symbols could not be loaded for ataport.SYS \Driver*atapi*   CLASSPNP!ClasspPowerUpCompletion*

    ^^

    atapi.sys = ATAPI IDE Miniport Driver

    ataport.sys = ATAPI Driver Extension

    Both system drivers, not the true cause and being faulted by something else. Please go ahead and enable Driver Verifier to see what driver(s) are causing corruption:

    Driver Verifier:

    What is Driver Verifier?

    Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

    Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

    Before enabling Driver Verifier, it is recommended to create a System Restore Point:

    Vista - START | type rstrui - create a restore point

    Windows 7 - START | type create | select "Create a Restore Point"

    Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

    How to enable Driver Verifier:

    Start > type "verifier" without the quotes > Select the following options -

    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    • Special Pool
    • Pool Tracking
    • Force IRQL Checking
    • Deadlock Detection
    • Security Checks (Windows 7 & 8)
    • DDI compliance checking (Windows 8)
    • Miscellaneous Checks
    1. Select  - "Select driver names from a list"
    2. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    3. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
    4. Click on Finish.
    5. Restart.

    Important information regarding Driver Verifier:

    • If Driver Verifier finds a violation, the system will BSOD.
    • After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

    If this happens, do not panic, do the following:

    • Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    • Once in Safe Mode - Start > Search > type "cmd" without the quotes.
    • To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

    ・    Restart and boot into normal Windows.

    If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

    • Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    • Once in Safe Mode - Start > type "system restore" without the quotes.
    • Choose the restore point you created earlier.

    How long should I keep Driver Verifier enabled for?

    It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

    My system BSOD'd, where can I find the crash dumps?

    They will be located in %systemroot%\Minidump

    Any other questions can most likely be answered by this article:

    http://support.microsoft.com/kb/244617

    Regards,

    Patrick

    0 comments No comments