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

[L84DNR]

Hi Folks,

I really hope you can help me, I followed the instructions to create the attachement.

What I know so far is that this machine has BSOD'd several times...The last 2 times a ultilty called BlueScreenViewer.exe says it's due to "Driver power state failure" caused by: ntoskrnl.exe

I checked event viewer for the time mentioned 6/17/2012 11:29:02 pm and it says there is system error "source:Bug Check" at that exact time

For anti-virus I have MS Security Essentials. For Spyware, I have Spybot S&D.
I use with Workstation 7 as a study too so it has hosed my VMs which is very disappointing. I would really like to root cause this to continue with confidence...

I know you hear this all the time...but... please help! I don't mind collecting info and checking into things, I am just out of my element a little here.

I looked throug the results of the permon report and it seems clean for the most part.

Thanks in advance,

Jay

 

[L84DNR]

Is there anything else I can do to help action this post? Thanks

 

[Tews]

First of all, Ntoskrnl.exe is a core Windows file, and is not the root problem for your BSOD problem. You will need to enable driver verifier to find out which driver(s) are the culprit. Follow these instructions, and upload any new .dmp files for analysis..

http://www.google.com/url?sa=t&rct=...2UoAlsZDXwzxlOuhQ&sig2=5SAwR-R4Zwa8sz_NoRT-lw

 

[writhziden]

Problematic Software:

Start Menu\Programs\ASUS\AI Suite II	Public:Start Menu\Programs\ASUS\AI Suite II	Public
Start Menu\Programs\ASUS\PC Diagnostics	Public:Start Menu\Programs\ASUS\PC Diagnostics	Public
Start Menu\Programs\Spybot - Search & Destroy	Public:Start Menu\Programs\Spybot - Search & Destroy	Public

• Spybot Search and Destroy is not the best malware/spyware utility. Take a look at http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 for better options.
  
  
• Recommend removing your ASUS utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability. They are also not needed for the system to function properly and may reduce system resources.

Crashes point to a BlueTooh device. Probably should re-install your Broadcom BlueTooth devices; see below.

To fully re-install a driver, use the following steps.

1. First, download the latest driver. Then do the next steps.
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer only if Windows asks you to.
11. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. First, download the latest driver. Then do the next steps.
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Find the device you are trying to uninstall by expanding the appropriate set of devices
8. Right click the device
9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
11. Restart your computer only if Windows asks you to.
12. Install the latest driver for the device.

3rd Party Drivers:

VMNET.SYS Mon Aug 10 06:04:50 2009 (4A800CE2)
vmnetadapter.sys Mon Aug 10 06:04:53 2009 (4A800CE5)
vmnetbridge.sys Mon Aug 10 06:05:58 2009 (4A800D26)
amdxata.sys Fri Mar 19 10:18:18 2010 (4BA3A3CA)
AsUpIO.sys Mon Aug 2 20:47:59 2010 (4C57835F)
vstor2-ws60.sys Thu Aug 19 14:28:39 2010 (4C6D93F7)
[B][COLOR="Red"]btwaudio.sys Fri Aug 20 13:16:14 2010 (4C6ED47E)[/COLOR][/B]
AsIO.sys Mon Aug 23 19:53:02 2010 (4C7325FE)
[B][COLOR="red"]btwavdt.sys Tue Sep 7 18:18:36 2010 (4C86D65C)
btwrchid.sys Tue Sep 7 18:19:49 2010 (4C86D6A5)[/COLOR][/B]
IntcDAud.sys Fri Oct 15 02:28:17 2010 (4CB810A1)
[B][COLOR="red"]btwl2cap.sys Fri Dec 10 14:56:16 2010 (4D02A200)
btwampfl.sys Fri Dec 10 14:57:30 2010 (4D02A24A)[/COLOR][/B]
CipcCdp.sys Fri Jan 21 07:29:59 2011 (4D399867)
vstor2-mntapi10-shared.sys Tue Jul 12 10:35:21 2011 (4E1C77C9)
asmtxhci.sys Wed Nov 2 21:00:22 2011 (4EB203C6)
asmthub3.sys Wed Nov 2 21:00:32 2011 (4EB203D0)
HECIx64.sys Wed Nov 9 17:52:25 2011 (4EBB2049)
tap0901.sys Thu Nov 24 11:50:27 2011 (4ECE91F3)
Rt64win7.sys Fri Feb 3 06:00:02 2012 (4F2BDA52)
MpFilter.sys Fri Mar 9 04:05:26 2012 (4F59E3F6)
igdkmd64.sys Mon Mar 19 17:31:54 2012 (4F67C1EA)
VMparport.sys Sat Jun 9 18:08:14 2012 (4FD3E56E)
vmci.sys Sat Jun 9 18:10:40 2012 (4FD3E600)
hcmon.sys Sat Jun 9 18:42:44 2012 (4FD3ED84)
vmnetuserif.sys Sat Jun 9 18:57:59 2012 (4FD3F117)
VMkbd.sys Sat Jun 9 19:33:53 2012 (4FD3F981)
vmx86.sys Sat Jun 9 20:22:32 2012 (4FD404E8)

VMNET.SYS
vmnetadapter.sys
vmnetbridge.sys
amdxata.sys
AsUpIO.sys
vstor2-ws60.sys
btwaudio.sys - Broadcom Bluetooth Audio Device
AsIO.sys
btwavdt.sys - Broadcom Bluetooth AVDT Service
btwrchid.sys - Bluetooth Remote Control HID Minidriver
IntcDAud.sys
btwl2cap.sys - Broadcom Bluetooth L2CAP Service
btwampfl.sys - Broadcom bluetooth driver
CipcCdp.sys
vstor2-mntapi10-shared.sys
asmtxhci.sys
asmthub3.sys
HECIx64.sys
tap0901.sys
Rt64win7.sys
MpFilter.sys
igdkmd64.sys
VMparport.sys
vmci.sys
hcmon.sys
vmnetuserif.sys
VMkbd.sys
vmx86.sys


If the above do not yield more stability, please follow the instructions provided by Tews and run Verifier. Use the following steps to run Verifier:

• a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 218736
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

 

[L84DNR]

Excellent.. thanks

I enabled driver verifier and will uninstall the ASUS and S&D - thanks!
Will also update the driver on the bluetooth device.
I promise I will report back in a week or so... if I don't have a crash by then I think I'm good - fingers crosseD!

 

[L84DNR]

While attempting to uninstall ASUS and starting a VM in Workstation 7 (VMware), I observed a crash.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: c4
BCP1: 00000000000000F6
BCP2: 0000000000000308
BCP3: FFFFFA800DB7E630
BCP4: FFFFF88005A0C2D5
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\062812-11668-01.dmp
C:\Users\jkuhne\AppData\Local\Temp\WER-41449-0.sysdata.xml

Attached is the latest mini-dump.


This time I had driver verifier.exe enabled.

Note - ASUS and S&D no removed yet.

Thanks,
Jay

 

[writhziden]

That is why you were supposed to do the previous steps prior to running Verifier. Verifier stresses system drivers, so you cannot uninstall software or drivers cleanly with it running; it will cause a crash. Please disable Verifier prior to doing the software and driver steps. Then, if you still have crashes after uninstalling the software and re-installing/updating the BlueTooth drivers, enable Verifier again.

 

[L84DNR]

Yes, ok thanks. I did now and just moving onto dealing with the bluetooth driver now.
Thanks again! I really appreciate your help

 

[writhziden]

You're welcome.

Glad to help. Let us know how things go with those changes.

 

[L84DNR]

2 More crashes..

Hello again,

I experienced two more crashes. Since last time I have done the following as reccomended.

- Removed all ASUS software mentioned (and rebooted)
- Removed Spybot S&D
- Uninstalled and re-installed the Broadcom Bluetooth device

According to windows I am running the latest version of the Boradcom driver. The Broadcom website does not list a better driver. I don't have a DriverBoost subscription (nor do I believe they would resolve). I'm going to kick this bluetooth USB device to the curb.

However, in the meantime, I experienced a crash while doing nothing in particular. I then enabled driver verifier.exe as directed and experienced a second crash while trying to boot a VM in VMware workstation.

Could I ask one more time, for a decode of these dump files? I want to be sure it is still the Broadcom device and not something else now,

If so, it's going in the trash as I have another higher rated bluetooth USB adapater in the mail already.

Thanks again so much!
Jay

 

[writhziden]

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:

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 http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html (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 http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html 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 http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html 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 http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 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

  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. :warn: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.

 

[L84DNR]

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

 

[writhziden]

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!

 

[L84DNR]

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.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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

 

[writhziden]

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.

 

[L84DNR]

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.

 

[writhziden]

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