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: Driver_Power_State_Failure BSOD. Please Help


07 Sep 2010   #1

Windows 7 Professional 64 bit
 
 
Driver_Power_State_Failure BSOD. Please Help

Hi All,

Hoping you can help me w/ my BSOD. I get a Driver_Power_State_Failure in windows 7. Here are the attachments from the FAQ posted on the top of the forum.

This is a Windows 7 Professional 64 bit install on a new system. Below are the specs

Core i5 760 @ 2.8 Ghz
Asus P7P55D-e Pro
4 gb (2X2gb) G. Skill Ripjaw DDR3-1600 (currently running @ 1333)
EVGA SC GTX 460 1GB
Corsair H50 Cpu cooler
Antec Neo Eco 520 PSU
Antec P180 case
2X WD Caviar Blue 640 GB (Raid 0)
D-Link DWA-556 PCIe N Adapter
LG Multi DVD writer
Sony BD-ROM BDU-X10s

I've had the crash several times now, and I'm not sure where it's coming from. Any help would be greatly appreciated.

Thanks!

Anthony

My System SpecsSystem Spec
.

08 Sep 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by thatguyant View Post
Hi All,

Hoping you can help me w/ my BSOD. I get a Driver_Power_State_Failure in windows 7. Here are the attachments from the FAQ posted on the top of the forum.

This is a Windows 7 Professional 64 bit install on a new system. Below are the specs

Core i5 760 @ 2.8 Ghz
Asus P7P55D-e Pro
4 gb (2X2gb) G. Skill Ripjaw DDR3-1600 (currently running @ 1333)
EVGA SC GTX 460 1GB
Corsair H50 Cpu cooler
Antec Neo Eco 520 PSU
Antec P180 case
2X WD Caviar Blue 640 GB (Raid 0)
D-Link DWA-556 PCIe N Adapter
LG Multi DVD writer
Sony BD-ROM BDU-X10s

I've had the crash several times now, and I'm not sure where it's coming from. Any help would be greatly appreciated.

Thanks!

Anthony

Anthony



These were caused by your nusb3xhc.sys which is NEC USB 3.0 Host Controller driver.

Things you can do

1- re-install update that driver.

2-update the other old drivers.
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

3-run a system file
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

Ken




Analysis
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\082810-17971-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`0309de50
Debug session time: Sat Aug 28 03:36:34.150 2010 (GMT-4)
System Uptime: 0 days 0:00:14.617
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Unable to load image \SystemRoot\system32\DRIVERS\nusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3xhc.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880047e4169, fffff880033bcdc8, fffff880033bc630}

Probably caused by : nusb3xhc.sys ( nusb3xhc+19169 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880047e4169, The address that the exception occurred at
Arg3: fffff880033bcdc8, Exception Record Address
Arg4: fffff880033bc630, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nusb3xhc+19169
fffff880`047e4169 488b4810        mov     rcx,qword ptr [rax+10h]

EXCEPTION_RECORD:  fffff880033bcdc8 -- (.exr 0xfffff880033bcdc8)
ExceptionAddress: fffff880047e4169 (nusb3xhc+0x0000000000019169)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000069
Attempt to read from address 0000000000000069

CONTEXT:  fffff880033bc630 -- (.cxr 0xfffff880033bc630)
rax=0000000000000059 rbx=fffffa800739ad70 rcx=fffffa8006790680
rdx=fffffa80059d5910 rsi=fffffa80059d5910 rdi=fffffa8006790680
rip=fffff880047e4169 rsp=fffff880033bd000 rbp=fffffa8007351700
 r8=fffffa800739ad70  r9=fffffa800739ad70 r10=fffffa8006790680
r11=0000000000000001 r12=0000000000000000 r13=fffff880033bd800
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nusb3xhc+0x19169:
fffff880`047e4169 488b4810        mov     rcx,qword ptr [rax+10h] ds:002b:00000000`00000069=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000069

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031080e0
 0000000000000069 

FOLLOWUP_IP: 
nusb3xhc+19169
fffff880`047e4169 488b4810        mov     rcx,qword ptr [rax+10h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff8a001ecbd00 to fffff880047e4169

STACK_TEXT:  
fffff880`033bd000 fffff8a0`01ecbd00 : fffff800`02ed2d26 fffff880`00000001 00000000`00000000 ffff0000`07457d9e : nusb3xhc+0x19169
fffff880`033bd008 fffff800`02ed2d26 : fffff880`00000001 00000000`00000000 ffff0000`07457d9e fffff800`0304ae00 : 0xfffff8a0`01ecbd00
fffff880`033bd010 00000000`00000000 : 00000000`00000000 fffff880`033bd800 fffffa80`059d5910 fffff880`047e25c3 : nt!IopfCompleteRequest+0x3a6


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nusb3xhc+19169

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nusb3xhc

IMAGE_NAME:  nusb3xhc.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ae5b004

STACK_COMMAND:  .cxr 0xfffff880033bc630 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nusb3xhc+19169

BUCKET_ID:  X64_0x7E_nusb3xhc+19169

Followup: MachineOwner
---------
Old drivers need to be updated.
Code:
jswpslwfx.sys        fffff880`041f3000    fffff880`04200000    0x0000d000    0x481664dd    4/28/2008 19:59:25                        
iaStorV.sys        fffff880`01086000    fffff880`011a4000    0x0011e000    0x49dcd76d    4/8/2009 12:57:17                        
spldr.sys        fffff880`01885000    fffff880`0188d000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
lirsgt.sys        fffff880`062c0000    fffff880`062cd000    0x0000d000    0x4a100bf1    5/17/2009 09:06:57                        
atksgt.sys        fffff880`06271000    fffff880`062c0000    0x0004f000    0x4a1012e2    5/17/2009 09:36:34                        
amdxata.sys        fffff880`01297000    fffff880`012a2000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
Rt64win7.sys        fffff880`04c00000    fffff880`04c39000    0x00039000    0x4a16bc2e    5/22/2009 10:52:30                        
iaStor.sys        fffff880`012d1000    fffff880`013ed000    0x0011c000    0x4a287aa4    6/4/2009 21:53:40                        
dump_iaStor.sys        fffff880`02e8e000    fffff880`02faa000    0x0011c000    0x4a287aa4    6/4/2009 21:53:40                        
ccHPx64.sys        fffff880`04510000    fffff880`045a3000    0x00093000    0x4a3c1f27    6/19/2009 19:28:39                        
SymIMv.sys        fffff880`041d2000    fffff880`041dd000    0x0000b000    0x4a400fbc    6/22/2009 19:11:56                        
SRTSP64.SYS        fffff880`06751000    fffff880`067cf000    0x0007e000    0x4a4041c1    6/22/2009 22:45:21                        
SRTSPX64.SYS        fffff880`042bc000    fffff880`042d0000    0x00014000    0x4a40425a    6/22/2009 22:47:54                        
SYMEFA64.SYS        fffff880`01000000    fffff880`01067000    0x00067000    0x4a414ea7    6/23/2009 17:52:39                        
athrx.sys        fffff880`04c6d000    fffff880`04ddc000    0x0016f000    0x4a41752d    6/23/2009 20:37:01                        
SYMEVENT64x86.SYS        fffff880`0406c000    fffff880`040a2000    0x00036000    0x4a428a40    6/24/2009 16:19:12                        
AsUpIO.sys        fffff880`04457000    fffff880`0445d000    0x00006000    0x4a515fb2    7/5/2009 22:21:38                        
SYMTDI.SYS        fffff880`04020000    fffff880`0406c000    0x0004c000    0x4a5296c0    7/6/2009 20:28:48                        
SYMFW.SYS        fffff880`040b2000    fffff880`040d4000    0x00022000    0x4a5296e2    7/6/2009 20:29:22                        
SYMNDISV.SYS        fffff880`040a2000    fffff880`040b2000    0x00010000    0x4a5297d6    7/6/2009 20:33:26
My System SpecsSystem Spec
08 Sep 2010   #3

Windows 7 x64, Windows XP SP3, Fedora
 
 

Hi,

AiCharger.sys -ASUS's specialised charging software is blamed for the majority of your BSODs. As I can think of no reason why you would need to use it (as the devices still charge normally via. USB without it) uninstall it for now.

Also, it may pay to get rid of Norton sometime in the near future (or when your subscription expires) as we have seen it causing BSODs before.
Quote:
Download the Norton Removal Tool (NRT); save to desktop. Boot into SAFEMODE - NO Networking. Tap F8 key during boot-up. Then go to desktop, RIGHT-click on the NRT icon and select Run as Administrator.

When complete - re-boot.

NRT - ftp://ftp.symantec.com/public/englis...moval_Tool.exe

Install MS Security Essentials --> http://www.microsoft.com/Security_Essentials/

Then reset the Windows Firewall to its default settings -
START -> type cmd.exe -> right-click -> run as administrator -> type netsh advfirewall reset press enter
If you still get BSODs after removing both the AiCharger utility and Norton, run Driver Verifier

Regards,
Reventon

BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 15:21:28.182 2010 (GMT+12)
System Uptime: 1 days 10:13:40.275
*** WARNING: Unable to verify timestamp for AiCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys
Probably caused by : AiCharger.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`07245060 fffff800`00b9c518 fffffa80`08a42010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 05:06:29.517 2010 (GMT+12)
System Uptime: 0 days 12:22:25.610
*** WARNING: Unable to verify timestamp for AiCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys
Probably caused by : AiCharger.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`07237060 fffff800`00b9c518 fffffa80`07a91790
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 16:39:13.283 2010 (GMT+12)
System Uptime: 0 days 7:53:54.672
*** WARNING: Unable to verify timestamp for AiCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys
Probably caused by : AiCharger.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0734e060 fffff800`04738518 fffffa80`03ca83e0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 08:44:02.230 2010 (GMT+12)
System Uptime: 0 days 12:46:46.244
*** WARNING: Unable to verify timestamp for AiCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys
Probably caused by : AiCharger.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`074c6060 fffff800`00b9c518 fffffa80`041d5b40
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Aug 28 19:36:34.150 2010 (GMT+12)
System Uptime: 0 days 0:00:14.617
*** WARNING: Unable to verify timestamp for nusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3xhc.sys
Probably caused by : nusb3xhc.sys ( nusb3xhc+19169 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`047e4169 fffff880`033bcdc8 fffff880`033bc630
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Aug 28 19:19:59.242 2010 (GMT+12)
System Uptime: 0 days 0:57:00.335
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+5e5346 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  EVGAPrecision.
Bugcheck code 0000003B
Arguments 00000000`c0000094 fffff880`10691346 fffff880`0948c0a0 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Aug 21 19:55:05.218 2010 (GMT+12)
System Uptime: 0 days 0:00:22.171
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+1a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`0000003d 00000000`00000002 00000000`00000000 fffff800`02ce382a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
My System SpecsSystem Spec
.


08 Sep 2010   #4

Windows 7 Professional 64 bit
 
 

Thanks guys! I will perform the steps tonight when I get home from work. On a side note, what is a recommended anti-virus for Windows 7?
My System SpecsSystem Spec
08 Sep 2010   #5

Windows 7 x64, Windows XP SP3, Fedora
 
 

Microsoft Security Essentials is what I prefer - it's free and works well without slowing your system down.

You can get it here: http://www.microsoft.com/Security_Essentials/
My System SpecsSystem Spec
09 Sep 2010   #6

Windows 7 Professional 64 bit
 
 

Hi ZigZag and Reventon,

Here are the steps I've completed so far:

1. downloaded lated NEC USB 3.0 Host controller driver from Asus website (couldn't find it on the NEC site)
2. Ran System File Check ~ Windows did not find any conflicts
3. I'm in the process of updating drivers, but some are harder to figure out. Also for the first one, it seems like a driver for a d-link wireless usb card, but I don't have one installed. I do however have a d-link pci-e wireless adapter on my desktop. Is it safe to leave the driver as is?

4. Uninstalled AI Charger
5. Uninstalled Norton using the Norton Removal Tool in Safe Mode.
6. Downloaded MS Security Essentials and running scans on the computer now.

So far no crashes for the past 3 hours. I will continue to update if I see anymore crashes, and once I figure out how to update all the drivers.
My System SpecsSystem Spec
Reply

 Driver_Power_State_Failure BSOD. Please Help




Thread Tools



Similar help and support threads for2: Driver_Power_State_Failure BSOD. Please Help
Thread Forum
Bsod driver_power_state_failure BSOD Help and Support
Solved BSOD Driver_Power_State_Failure BSOD Help and Support
BSOD: Driver_Power_State_Failure BSOD Help and Support
Driver_Power_State_Failure BSOD BSOD Help and Support
Bsod - driver_power_state_failure BSOD Help and Support
BSOD - driver_power_state_failure Please Help! BSOD Help and Support
Bsod, driver_power_state_failure 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 08:48 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33