[SOLVED] BSOD Win 8.1, driver power state failure after awaking from sleep

C

concord72

Member
Joined
Feb 18, 2015
Posts
6
-Win 8.1, recently upgraded from 8
- x64
- Win 8 was the original OS on the laptop
- OEM, came pre-installed
- 1.5 years
- Upgraded to 8.1 about a month ago

- i7 4700MQ
- GT 750M

- Lenovo
- Y410p

-Laptop

I can't access my System Health Report, whenever I try to run perfmon/report in cmd (As administrator), I get an error message saying THE OPERATOR OR ADMINISTRATOR HAS REFUSED THE REQUEST. I can manually view the report in Performance Monitor but I have no idea how to save it from there, there is no option to save the report anyhow.
 
Code: 
2: kd> .bugcheck
Bugcheck code 0000009F
Arguments 00000000`00000003 ffffe001`822538c0 ffffd000`513e3cb0 ffffe001`7b358420

Code: 
2: kd> !irp ffffe0017b358420
Irp is active with 19 stacks 17 is current (= 0xffffe0017b358970)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context

>[ 16, 2]   0  1 ffffe001822538c0 00000000 00000000-00000000    pending
           \Driver\usbccgp
            Args: 00041100 00000001 00000001 00000002
 [ 16, 2]   0 e1 ffffe00181f0d3b0 00000000 fffff80017124efc-ffffe00184686180 Success Error Cancel pending
           \Driver\ksthunk    nt!PopRequestCompletion
            Args: 00041100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe00184686180    

            Args: 00000000 00000000 00000000 00000000

The common class USB driver regarding Windows is certainly not the true cause behind the crash, therefore this is a 3rd party conflict. I have an idea as to what driver is the issue, but enable verifier so we're sure:

Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

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/8.1 - Restore Point - Create in Windows 8

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 (only on Windows 7 & 8/8.1)
- DDI compliance checking (only on Windows 8/8.1)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues.

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- 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 detect it in violation almost straight away, 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.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

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

http://support.microsoft.com/kb/244617
 
Thank you for responding. I posted my problem on 3 other forums and have gotten a few replies, this is everything I have done so far. Another forum told me to run Driver Verifier, so I did. I followed all the steps you listed and enabled it, have not had a BSOD since. I'm not sure if it's still running though, when i go into cmd and type "verifier /query". a new cmd window pops up, a bunch of code comes and a second later the window is gone and all that's left is the original cmd window, waiting for a new command. Is this supposed to happen?

The other forum told me to uninstall Power ISO and Daemon Tools, which I did, and to disable nVidia Streaming Kernel Service within services.msc, which i also did. I should let you know that I have a laptop fan connected via USB and it's always on when I'm using my laptop, could that be causing any issues? And what should I do next, just wait 24 hours for the Driver Verifier to run or is there anything else I should be doing? thank you so much for the help.
 
Is this supposed to happen?
Click to expand...

Yes, it's enabled.

And what should I do next, just wait 24 hours for the Driver Verifier to run or is there anything else I should be doing?
Click to expand...

Keep verifier enabled and just regularly use the system as if it was disabled. Report back in 24 hours if it has crashed.
 
Ok, it has been 24 hours since I started Verifier, no crashes have occured, but my laptop has been running slower than usual, is this normal? Also, how do I turn off verifier? thanks
 
Whenever I wake up from sleep into the login screen, I hear this very short beep sound that wasn't present before. It is very short and not very loud, should I be worried?
 
Hmm, you'd need to check the Lenovo support manual for your model and see what that implies. I wouldn't be worried if there are no symptoms.
 
Please don't post your issue on multiple forums, you end up with different advice being spewed all over, it can get confusing and even conflicting.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top