Share via

Driver power state failure after resuming from sleep mode

Anonymous
2014-06-06T00:10:08+00:00

Ever since a Microsoft Windows update last week, about half the time my computer resumes from sleep mode, within 1-2 minutes it will get a BSOD with the "driver power state failure" error and restart, but interestingly I never get the error the moment I wake up the computer. I'm using a Lenovo IdeaPad Y510P with Windows 8 64-bit. I already tried uninstalling the Intel HD 4000 driver, restarting computer, and installing the one on Lenovo's site (as this was suggested on the Lenovo forum as a common fix) but it didn't help.

I used Microsoft's WinDebug tool to collect the BSOD crash dump, which is uploaded here: http://textuploader.com/0fe4

Here is the BlueScreenView log:

==================================================

Dump File         : 060514-96281-01.dmp

Crash Time        : 6/5/2014 7:23:39 PM

Bug Check String  : DRIVER_POWER_STATE_FAILURE

Bug Check Code    : 0x0000009f

Parameter 1       : 00000000`00000003

Parameter 2       : ffffe001`218f88e0

Parameter 3       : ffffd000`bff2b930

Parameter 4       : ffffe001`2561d1c0

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+153fa0

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : ntoskrnl.exe+153fa0

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\WINDOWS\Minidump\060514-96281-01.dmp

Processors Count  : 8

Major Version     : 15

Minor Version     : 9600

Dump File Size    : 1,271,704

Dump File Time    : 6/5/2014 7:26:13 PM

==================================================

Thanks for your help.

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

17 answers

Sort by: Most helpful
  1. Anonymous
    2014-06-06T02:29:54+00:00

    Uninstalled Avira, turned on Windows Defender, and uninstalled DaemonTools Lite now.

    Anything to do next or do I just wait for the next BSOD upon waking from sleep?

    Also from the WinDbg and BluescreenView a "ntoskrnl.exe" seems to be the problem. What exactly is that and do I need to do anything about it?

    0 comments No comments
  2. Anonymous
    2014-06-06T01:50:33+00:00

    You posted text logs of the crash dumps, that's it. I or anyone else can't debug a text document.

    DRIVER_POWER_STATE_FAILURE (9f)

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

    BugCheck 9F, {3, ffffe001218f88e0, ffffd000bff2b930, ffffe0012561d1c0}

    Let's run an !irp on the 4th parameter of the bug check:

    >[ 16, 2]   0  1 ffffe001218f88e0 00000000 00000000-00000000    pending

               \Driver*usbccgp*

                Args: 00041100 00000001 00000001 00000002

     [ 16, 2]   0 e1 ffffe001218b5a60 00000000 fffff802393a52d8-ffffe0011db643e0 Success Error Cancel pending

               \Driver**ksthunk**nt!PopRequestCompletion

    usbccgp.sys is listed as the culprit driver blocking the IRP for too long, however, it's not the true cause as that's a Windows component. Something 3rd party is causing conflicts.

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

    1. Remove and replace Avira with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's very likely causing USB-based/file system conflicts with Malwarebytes PRO:

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

    Windows Defender (how to turn on after removal) - http://www.eightforums.com/tutorials/21962-windows-defender-turn-off-windows-8-a.html

    2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

    Regards,

    Patrick

    0 comments No comments
  3. Anonymous
    2014-06-06T01:24:37+00:00

    Or... you could just be made aware that MANY users report problems with PCs (usually Laptops) coming out-of Sleep modes... generally because one of your many HW devices has a Driver that was poorly coded (not following all of the extensive MS-required Driver 'model'). You 'could' play with Crash Dumps for how many hours you have available to 'waste'...  

     And, just stop using Hibernate and Sleep modes altogether. [Google how-to 'disable' them.] Shutdown your Windows OS each time you are done working, right-after you Defragment your files. And at every Restart, always Update your AntiVirus application 1ST(!), before doing any work.

    ***FYI, Windows 8.1 itself is a well-written and reliable OS (compared to W7 or earlier).

    0 comments No comments
  4. Anonymous
    2014-06-06T01:19:50+00:00

    Well my post already contains both the WinDbg and BluescreenView version of the dump...?

    I'll upload the original dump files then. Here's everything in C:/windows/minidump: https://www.mediafire.com/?i1qdgcmju4tw4al

    0 comments No comments
  5. Anonymous
    2014-06-06T00:20:40+00:00

    Hi,

    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where .DMP files are located, here's how to get to them:

    1. Navigate to the %systemroot%\Minidump folder.

    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

    If you are going to use Onedrive but don't know how to upload to it, please visit the following:

    Upload photos and files to Onedrive.

    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link - Share files and folders and change permissions and view 'Get a link'.

    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.

    If your computer is not generating .DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    4. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    0 comments No comments