Driver Power State Failure BSOD

Neons97 · 31 Dec 2013

Hi,

My laptop goes to BSOD what seems like several times a week and drives drives me nuts. We've had the laptop exactly two years now and it seems to be getting worse and more frequent. I've tried a completely fresh/clean install of Windows 7 64-bit, but no luck.

The problem happens about 70-80% of the time when the computer has gone to sleep and we're trying to wake it up using any button on the keyboard or the power button (doesn't matter which one). Less often, it will completely freeze up while we're browsing the internet (Chrome...we can switch between windows/desktop and scroll the cursor for a minute or so before the BSOD comes up).

The BSOD error comes up as: "Driver Power State Failure". Attached is the ZIP file as instructed.

Any help would be greatly appreciated.

Thanks,
Jeremy

Arc · 31 Dec 2013

Hi Neons97.

You need to update Fresco Logic xHCI (USB3) Controller FL1000 Series driver. No feasible update is available in ASUSTeK Computer Inc. -Support- Drivers and Download N53SV. So try the
Fresco Logic FL-1000/1009 USB 3.0 Controllers from Station-Drivers - Fresco Logic (drivers).

Also turn off USB selective suspend.
USB Selective Suspend - Turn On or Off

BTW, your RAM seems to be of odd volume.

Code:

Installed Physical Memory (RAM)    14.0 GB

Publish a Speccy snapshot : Speccy - Publish Snapshot of your System Specs .

Let us know the results.
__________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800fced060, fffff80000b9c3d8, fffffa80153e7010}

Probably caused by : usbhub.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800fced060, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa80153e7010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa800f257700

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5227239a

MODULE_NAME: usbhub

FAULTING_MODULE: fffff88004670000 usbhub

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c388 fffff800`02efd8d2 : 00000000`0000009f 00000000`00000003 fffffa80`0fced060 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02e9885c : fffff800`00b9c4f0 fffff800`00b9c4f0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`02e986f6 : fffff800`0303df80 00000000`025f3974 00000000`00000000 fffff880`0f47300e : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02e985de : 000005a5`6dc3c014 fffff800`00b9cb18 00000000`025f3974 fffff800`0300c108 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02e983c7 : 00000135`d6426cc3 00000135`025f3974 00000135`d6426c57 00000000`00000074 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02e858ca : fffff800`03008e80 fffff800`03016cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_usbhub.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_usbhub.sys

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

Neons97 · 31 Dec 2013

Hi Arc,

Thanks for the quick response! Amazing what a bit of google search can do. I'll post a response in a few days/weeks to check back on if the driver update and disabling selective USB Suspend solves my problems.

For the RAM, the computer actually came stock with 6GB, and I added 8GB (only upgrade done to the laptop). Therefore the 14GB. Should I be adjusting this? Should I take out the 2GB stick to make it 12GB? Would 14GB be causing any issues other than being a non-normal set-up?

Thanks,
Jeremy

Here's my speccy link: http://speccy.piriform.com/results/d...RxMVkrE4FR8YAQ

Arc · 31 Dec 2013

OK let us know how things go.

Neons97 · 05 Jan 2014

Hi Arc,

Unfortunately I am still getting my BSOD with "Driver State Power Failure". Lasted 5 days before a BSOD. I've attached the latest dump files.

Arc · 06 Jan 2014

The same bugcheck code, but the device object and the driver object are different. This time the BSOD is occurred due to the graphics driver.

Code:

0: kd> !irp fffffa8014851e10
Irp is active with 4 stacks 3 is current (= 0xfffffa8014851f70)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 fffffa800e0bfa10 00000000 fffff8800596b98c-fffffa8013a492e0    
           \Driver\pci    nvlddmkm
            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800ebe8480 00000000 fffff80002ebd710-fffffa8013569d90 Success Error Cancel pending
           \Driver\nvlddmkm    nt!IopUnloadSafeCompletion
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800c6c7ce0    

            Args: 00000000 00000000 00000000 00000000
0: kd> !devobj fffffa800ebe8480
Device object (fffffa800ebe8480) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa800ebe8450
 \Driver\nvlddmkm DriverObject fffffa800e875060
Current Irp 00000000 RefCount 0 Type 00000023 Flags 00002004
DevExt fffffa800ebe85d0 DevObjExt fffffa800ebe8f88 
ExtensionFlags (0x00000800) 
 Unknown flags 0x00000800
AttachedTo (Lower) fffffa800e1a31d0 \Driver\ACPI
Device queue is not busy.

It is a side effect of ACPI. ACPI is itself complicated, and it becomes much more complicated when it is controlled by any third party driver.

Code:

asmmap64    ASMMAP64    \??\c:\program files (x86)\asus\atk package\atkgfnex\asmmap64.sys    Kernel Driver    Yes    Auto    Running    OK    Normal    No    Yes

I'd recommend you to Clean Up Factory Bloatware, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

** A clean install is not always enough to solve all issues relating to display transitions during gaming (same stop code, 0x9F). In that situation the best way is to use the laptop as a desktop .... on the dedicated GPU only; by disabling the integrated Intel GPU.

Neons97 · 06 Jan 2014

Hi ARC,

I have already clean-installed a factory OEM Windows 7 64 bit Home Premium (from digital river). Only using drivers from the ASUS support site where available and going to the manufacturers site if not on Asus site.

I needed to load the Asus ATK driver package to get some of my hotkeys to work. But if uninstalling them will solve my problem, I would trade that for the convenience of the hot keys. Do you think removing Asus ATK will work?

Last resort is going to dedicated graphics card as that eats up my battery life, makes the unit very warm on the lap and turns on the fan pretty loud.

Thanks,
Jeremy

Arc · 07 Jan 2014

Hi Neons97.

It is not 100% possible to say that removing ATK will work with a certainty, but that is very necessary here. Because, the BSODs are caused by ACPI, and ATK controls ACPI as an external source.

It is not possible to say with certainty that removing ATK will be the final solution, because of the nature of switchable graphics. BSODs may occur anytime during graphics swing. Whether ATK is present there or not.

But, ATK maximizes the chance.