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

L84DNR · 27 Jun 2012

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 · 28 Jun 2012

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

Tews · 28 Jun 2012

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=j...Zwa8sz_NoRT-lw

writhziden · 28 Jun 2012

Problematic Software:

Code:

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 Good and Free system security combination. 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.

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

Alternatively:

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

3rd Party Drivers:

Code:

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)
btwaudio.sys Fri Aug 20 13:16:14 2010 (4C6ED47E)
AsIO.sys Mon Aug 23 19:53:02 2010 (4C7325FE)
btwavdt.sys Tue Sep 7 18:18:36 2010 (4C86D65C)
btwrchid.sys Tue Sep 7 18:19:49 2010 (4C86D6A5)
IntcDAud.sys Fri Oct 15 02:28:17 2010 (4CB810A1)
btwl2cap.sys Fri Dec 10 14:56:16 2010 (4D02A200)
btwampfl.sys Fri Dec 10 14:57:30 2010 (4D02A24A)
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
  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 System Restore 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 · 28 Jun 2012

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 · 28 Jun 2012

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 · 28 Jun 2012

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 · 28 Jun 2012

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

writhziden · 28 Jun 2012

You're welcome.

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

L84DNR · 30 Jun 2012

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

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

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