driver_power_state_failure asus zenbook windows 8.1


I have a asus zenbook ux32a with windows 8.1. The computer won't shut down or hibernate correctly. Additionaly, Windows don't react for about 3 minutes after start-up, only then it's possible to use the computer again.

I keep getting the driver_power_state_error. In the minidump it says that it is cause by driver ntoskrnl.exe. 

The minidump files:

The device manager says that there is a problem with usb-if xhci USB Host Controller. However, I have problems updating the driver.

How do I fix it?

Thanks in advance


Fantastic, thank you!

BugCheck 9F, {4, 12c, ffffe00000fb3880, ffffd000201ff860}

1st parameter = 0x4.

Let's take a look at the call stack:

2: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd000`201ff828 fffff800`177d457e nt!KeBugCheckEx
01 ffffd000`201ff830 fffff800`1797a6ca nt!PnpBugcheckPowerTimeout+0x6a
02 ffffd000`201ff890 fffff800`176b1f64 nt!PopBuildDeviceNotifyListWatchdog+0x16
03 ffffd000`201ff8c0 fffff800`176b2478 nt!KiProcessExpiredTimerList+0x1d8
04 ffffd000`201ff9a0 fffff800`1770e478 nt!KiExpireTimerTable+0x218
05 ffffd000`201ffa40 fffff800`1765eabc nt!KiTimerExpiration+0x148
06 ffffd000`201ffaf0 fffff800`177557ea nt!KiRetireDpcList+0x19c
07 ffffd000`201ffc60 00000000`00000000 nt!KiIdleLoop+0x5a

Not really much info, just a few PnP routines that call into the bugcheck eventually. No driver in the stack, etc.

Let's run !locks to see what's going on:

2: kd> !locks
KD: Scanning for held locks..

Resource @ nt!IopDeviceTreeLock (0xfffff800178d3260)    Shared 1 owning threads
     Threads: ffffe00000fb3880-01<*>
KD: Scanning for held locks.

Resource @ nt!PiEngineLock (0xfffff800178d3360)    Exclusively owned
    Contention Count = 15
    NumberOfExclusiveWaiters = 2
     Threads: ffffe00000fb3880-01<*>
     Threads Waiting On Exclusive Access:
              ffffe00000b98880       ffffe00000fb2880       

KD: Scanning for held locks.......

Resource @ 0xffffe000076cc6d0    Exclusively owned
    Contention Count = 1
    NumberOfExclusiveWaiters = 1
     Threads: ffffe0000745a880-01<*>
     Threads Waiting On Exclusive Access:

Let's take the address in the 'Threads' field and run !thread:

2: kd> !thread ffffe0000745a880
THREAD ffffe0000745a880  Cid 0eb4.0ec8  Teb: 00007ff68359a000 Win32Thread: fffff901407a4010 WAIT: (Executive) KernelMode Non-Alertable
    ffffd00036bbcd88  NotificationEvent
IRP List:
    ffffe00006bdf6e0: (0006,01f0) Flags: 00060000  Mdl: 00000000
    ffffe000051faaa0: (0006,03a0) Flags: 00000884  Mdl: 00000000
Impersonation token:  ffffc0000b1d7060 (Level Impersonation)
Owning Process            ffffe000072ed900       Image:         WmiPrvSE.exe
Attached Process          N/A            Image:         N/A
Wait Start TickCount      573138         Ticks: 16601 (0:00:04:19.390)
Context Switch Count      274            IdealProcessor: 1             
UserTime                  00:00:00.015
KernelTime                00:00:00.156
Win32 Start Address 0x00007ffbe050b5c0
Stack Init ffffd00036bbdc90 Current ffffd00036bbc9c0
Base ffffd00036bbe000 Limit ffffd00036bb8000 Call 0
Priority 15 BasePriority 8 UnusualBoost 7 ForegroundBoost 0 IoPriority 2 PagePriority 5
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffd000`36bbca00 fffff800`176a890e : ffffd000`20754180 ffffe000`0745a880 00000000`fffffffe 00000000`fffffffe : nt!KiSwapContext+0x76
ffffd000`36bbcb40 fffff800`176a83a7 : ffffe000`00fe6320 ffffe000`06be4010 ffffe000`06b97c58 fffff800`00ae9825 : nt!KiSwapThread+0x14e
ffffd000`36bbcbe0 fffff800`1763f9a8 : ffffe000`06be4010 ffffe000`0745a9c0 ffffe000`010d74a0 fffff800`00000008 : nt!KiCommitThreadWait+0x127
ffffd000`36bbcc40 fffff800`011781da : ffffd000`36bbcd88 ffffe000`00000000 ffffe000`062fa500 ffffe000`079b2a00 : nt!KeWaitForSingleObject+0x248
ffffd000`36bbcce0 fffff800`011631e8 : ffffe000`03393060 00000000`00000000 ffffe000`062fa500 00000000`000000c0 : CLASSPNP!ClassSendSrbSynchronous+0x22a
ffffd000`36bbcde0 fffff800`011598ba : 00000000`00070024 ffffe000`03393060 ffffe000`06bdf840 ffffd000`36bbcd90 : disk!DiskIoctlIsWritable+0x128
ffffd000`36bbce40 fffff800`01177cec : 00000000`00000000 ffffd000`36bbcf60 ffffe000`06bdf6e0 fffff800`00bab184 : disk!DiskDeviceControl+0xfa
ffffd000`36bbced0 fffff800`00bab19d : ffffe000`076cc010 00000000`00000000 00000000`00000008 ffffffff`ffffffff : CLASSPNP!ClassDeviceControlDispatch+0x2c
ffffd000`36bbcf00 fffff800`01c71fdc : 00000000`00000000 ffffd000`36bbd291 00000000`00000000 00000000`00000001 : fltmgr!FltIsVolumeWritable+0xa1
ffffd000`36bbcf90 fffff800`00b93a27 : 00000000`00000005 00000000`00000000 00000000`00000008 ffffe000`00260cc8 : aswSnx+0x2fdc
ffffd000`36bbd110 fffff800`00b95f4f : ffffe000`07a60ba0 ffffe000`076cc010 ffffd000`36bbd291 ffffe000`076cc010 : fltmgr!FltpDoInstanceSetupNotification+0x87
ffffd000`36bbd170 fffff800`00b94af5 : 00000000`00000000 ffffd000`36bbd338 ffffe000`00000005 00000000`0000000b : fltmgr!FltpInitInstance+0x2db
ffffd000`36bbd200 fffff800`00b962e5 : 00000000`00000000 ffffe000`076cc010 ffffe000`00260c20 00000000`0000001a : fltmgr!FltpCreateInstanceFromName+0x1ad
ffffd000`36bbd2e0 fffff800`00b95276 : ffffe000`00260c20 ffffe000`00260c10 ffffe000`04af1730 ffffe000`0000002e : fltmgr!FltpEnumerateRegistryInstances+0x145
ffffd000`36bbd380 fffff800`00b8c4f4 : ffffe000`076cc010 ffffe000`00000000 ffffe000`00260c20 ffffe000`00fe22a0 : fltmgr!FltpDoFilterNotificationForNewVolume+0x126
ffffd000`36bbd400 fffff800`179b0533 : 00000000`00000000 00000000`000000a5 00000000`00000000 00000000`00000000 : fltmgr!FltpCreate+0x4f3
ffffd000`36bbd4b0 fffff800`179ac0cf : ffffc000`0028b678 ffffc000`0028b678 ffffe000`03393030 ffffe000`03393030 : nt!IopParseDevice+0x7b3
ffffd000`36bbd6b0 fffff800`179a9ad3 : 00000000`00000000 ffffd000`36bbd8a8 ffffe000`00000040 ffffe000`00348dc0 : nt!ObpLookupObjectName+0x6ef
ffffd000`36bbd830 fffff800`179a6ec2 : ffffe000`00000001 ffffe000`07755ba8 000000bf`2acfd1c0 00000000`00000020 : nt!ObOpenObjectByName+0x1e3
ffffd000`36bbd960 fffff800`179a4c94 : 000000bf`2acfd1a8 000000bf`c0100080 000000bf`2acfd200 fffff800`179afd7a : nt!IopCreateFile+0x372
ffffd000`36bbda00 fffff800`1775d4b3 : ffffd000`36bbdb10 00000000`00000000 ffffd000`36bbdaa8 fffff6fb`7da017e0 : nt!NtCreateFile+0x78
ffffd000`36bbda90 00007ffb`e0566aca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ ffffd000`36bbdb00)
000000bf`2acfd078 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`e0566aca

^^ Great, now we actually have some information. We have an IRP list, and a little bit of a more informative stack text. We can see a few file system routines (fltmgr), and then an avast! Virtualization driver call. Very interesting to see avast! in the stack.

Let's go ahead and take a look at the first current IRP within the thread:

2: kd> !devstack ffffe00003393060
  !DevObj   !DrvObj            !DevExt   ObjectName
  ffffe00003393a40  \Driver\partmgr    ffffe00003393b90  
  ffffe00003394890 *** ERROR: Module load completed but symbols could not be loaded for excsd.sys
 \Driver\excsd      ffffe000033949e0  excsd1
> ffffe00003393060  \Driver\disk       ffffe000033931b0  DR1
  ffffe000010d74a0  \Driver\ACPI       ffffe00000fbdc90  
  ffffe00000fe6320 *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
 \Driver\iaStorA    ffffe00000fe6470  0000003b
!DevNode ffffe00000fe9a50 :
  DeviceInst is "SCSI\Disk&Ven_ATA&Prod_SanDisk_SSD_i100\4&5120a8e&0&010000"
  ServiceName is "disk"

Okay, now we are at our culprits.

So, what appears to be happening here is we have a conflict-based scenario caused by three different drivers.

1. Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's very likely causing conflicts:

avast! removal -

Windows Defender (how to turn on after removal) -

2. excsd.sys - ExpressCache, uninstall ASAP. Very problematic software.


2: kd> lmvm iastora
start             end                 module name
fffff800`0081d000 fffff800`00ae8000   iaStorA    (no symbols)           
    Loaded symbol image file: iaStorA.sys
    Image path: \SystemRoot\System32\drivers\iaStorA.sys
    Image name: iaStorA.sys
    Timestamp:        Sat Sep 01 21:01:24 2012

^^ IRST dated from 2012 on your system, and the latest via Asus for your specific model is ~2013. Update ASAP.

It's listed under Windows 8 (no 8.1 yet) 'Others' -



Debugger/Reverse Engineer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Question Info

Last updated February 12, 2018 Views 1,812 Applies to: