Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD "Driver power state failure" caused by: ntoskrnl.exe

30 Jun 2012   #11
writhziden

Windows 7 Home Premium 64 Bit
 
 

Verifier Enabled Crash:
Your Verifier Enabled crash blames your VMware Virtualization Driver; this is likely a false positive and due to you running the software at the time.

Disable Verifier before proceeding with the next steps.

BugCheck 0x51:
STOP 0x00000051: REGISTRY_ERROR:
Quote   Quote: Originally Posted by usasma
Usual causes: Hardware failure, File system corruption, Security issues
  • If you are overclocking any hardware, please stop.

  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk).
    For any drives that do not give the message:
    Windows has checked the file system and found no problems
    run disk check again as above. In other words, if it says:
    Windows has made corrections to the file system
    after running the disk check, run the disk check again.

  • Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
    SeaTools for Windows

    SeaTools for DOS
  • If you have an SSD, make sure the following are up to date:
    • SSD firmware
    • BIOS Version
    • Chipset Drivers
    • Hard disk controller drivers/SATA drivers
    • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

  • Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.

  • Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.

  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
    warning   Warning
    Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

    For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
    Once these steps have been followed, it is safe to remove and replace components within your computer.



My System SpecsSystem Spec
.
02 Jul 2012   #12
L84DNR

Windows 7 Pro 64bit
 
 

Thank you for the reply. Okay, I have stepped through and done the following

No BSODs thus far...

I have kicked my bluetooth USB device to the curb.

Also now since the last post, obviously sisabled verifier.exe - hopefully this was a false positive.

1. I don't believe I am allowing over-clocking (ASUS Set Ai Overclock Tuner: Auto vs. Manual or XMP)

2. Ran Diskcheck

first time:

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Windows has made corrections to the file system.

second time:

Free space verification is complete.
Windows has checked the file system and found no problems.

3. Updated drivers for SSD and associated drivers

Ran Intel SSD driver update utility - was already updated
Ran intel driver update utility - was already updated (SATA is intel)


4. Ran windows check for corruption

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violation


5. Ran Malwarebytes and Free SuperAntiSpyware.
found a few things, I took the reccomendations

Still need to run the Memtest86+ but ran one on-board test in the past so hoping my ram is good.

Will keep using and hopefully no BSOD

Thanks for the decoding and the detailed reply.
Jay
My System SpecsSystem Spec
02 Jul 2012   #13
writhziden

Windows 7 Home Premium 64 Bit
 
 

You're welcome. Glad to see the system has been responding well to treatment.

Let us know in a few days how things are going. Best wishes!
My System SpecsSystem Spec
.

03 Jul 2012   #14
L84DNR

Windows 7 Pro 64bit
 
 

I let Memtest86+ run overnight. This morning is said there were errors after 3 passes (attached some pictures of my screen)

Based on the procedure on this page, it looks like I need to step through testing the sticks individually.... Ugh.
RAM - Test with Memtest86+

interesting, I couldn't find a way in my ASUS BIOS to test the ram during POST or any utilities in the BIOS to check it.

So far no crashes in the OS or while running VMs. I'm being very careful to back-up my VMs in the meantime
My System SpecsSystem Spec
03 Jul 2012   #15
writhziden

Windows 7 Home Premium 64 Bit
 
 

Definitely appears you have faulty RAM. You should test each module individually, as you said. Let us know the results.

Good idea to keep things backed up. I back up at least once a week myself.
My System SpecsSystem Spec
08 Jul 2012   #16
L84DNR

Windows 7 Pro 64bit
 
 

Have not had time to step through the RAM testing individually but so far system has been stable running 5 VMs since this last post.... I know it's probably only a matter of time but just having the other issues resolved allows me to keep working and do backups as I go... Once again, a big thanks! I'm a week out from vacation so everything is busy right now... once I return and things settle down I'll see about replacing that stick.
My System SpecsSystem Spec
09 Jul 2012   #17
writhziden

Windows 7 Home Premium 64 Bit
 
 

That's alright. No rush. We will be here as you find time to go through the steps. Glad things are running better.
My System SpecsSystem Spec
Reply

 BSOD "Driver power state failure" caused by: ntoskrnl.exe




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD - ntoskrnl.exe "driver power state failure" at shutdown
I'm getting a BSOD pretty much every time I shutdown the PC. Has only just started happening in the last couple of weeks. DRIVER_POWER_STATE_FAILURE caused by driver: ntoskrnl.exe I've attached the SFDiagnostic here - thanks.
BSOD Help and Support
BSOD after sleep or hibernation - "Driver Power State Failure"
Hello, I left my computer on and open this morning before I left for class. When I returned, I had a BSOD, which specified "Driver Power State Failure" (I did not copy down any numbers, as I probably should have). I did a forced shut down (held the power button) and then restarted it, where it...
BSOD Help and Support
BSOD random, "Driver Power State Failure"
New windows 7 install on one of my home built workstations. I have an appearantly random BSOD. It sometimes runs for days, sometimes hours. I may have multiple issues (I have not been around to see it). Usually I start folding at home (stanford project) and leave it when I am not using the terminal...
BSOD Help and Support
Frequent BSOD "Driver Power State Failure," No pattern that I see
My Alienware M17x suffers daily, random BSODs, I think most are Driver Power State Failures. These persist when I re-install my NVIDIA drivers (I even tried using Driver Fusion to get a clean install), but they do seem more frequent with the recent beta drivers. Maybe it's my Intel display...
BSOD Help and Support
BSOD when going sleep mode "DRIVER POWER STATE FAILURE"
Hi, i keep having this issue. Anyone knows how to solve? My minidump is https://skydrive.live.com/#cid=392FCBBA17F5ACA1&id=392FCBBA17F5ACA1%21187
BSOD Help and Support
BSOD with "usbhub.sys" and "driver power state failure"
I have been getting the BSOD since a few weeks and found out by trial and error that a USB-hub is causing the problem. Whenever I disconnect the hub before I shut off the computer I do not get the blue screen. Yesterday I also got a BSOD that mentioned driver power state failure. After I had...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:39.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App