cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
gmstk
Paper Tape
Posts: 2
Registered: ‎03-17-2015
Location: Greece
Views: 9,927
Message 1 of 3

Driver power state failure caused by usbhub3.sys

Hello, I am a prowd owner of a Y50-70 that I bought for live music performance using an external Audio Interface (M-Audio Fast Track Pro) and a MIDI Keyboard (Roland Fantom - X). 

After my live session when I try to shut down my Laptop, it takes around 10 minutes to display a BSOD stating a Driver Power State Failure. It collects data and then restarts with no problem. After the restart I shut down the machine with no problems at all.

This problem persists only when I use my External Audio Interface with Ableton Live 9 (the digital audio workstation I use). 

When I use the laptop for other purposes like Internet, Office or Gaming there is no problem at all at shutting down afterwards.

I am sharing my latest DMP file after the last crash.

 

Thanking you in advance

 

https://drive.google.com/file/d/0B2cGbbfYbjIaN3hmTV9vQUJLbmc/view?usp=sharing

 

Social Support Agent
Social Support Agent
Posts: 5,822
Registered: ‎02-11-2012
Location: PH
Views: 9,899
Message 2 of 3

Re: Driver power state failure caused by usbhub3.sys

hi gmstk,

 

Welcome to the Forums.

 

That BSOD is indeed comming from the M-Audio Fast Track Pro when connected to the USB 3.0 port see spoiler).

 

Spoiler

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\XXX\Desktop\031815-20500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff802`a327a000 PsLoadedModuleList = 0xfffff802`a3553250
Debug session time: Wed Mar 18 21:04:56.255 2015 (UTC + 8:00)
System Uptime: 0 days 1:02:09.045
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 12c, ffffe000f3643040, fffff802a4f09980}

*** WARNING: Unable to verify timestamp for MAudioFastTrackPro.sys
*** ERROR: Module load completed but symbols could not be loaded for MAudioFastTrackPro.sys
Implicit thread is now ffffe000`f3643040
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : UsbHub3.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe000f3643040, The thread currently holding on to the Pnp lock.
Arg4: fffff802a4f09980, nt!TRIAGE_9F_PNP on Win7 and higher

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

Implicit thread is now ffffe000`f3643040

DRVPOWERSTATE_SUBCODE: 4

IMAGE_NAME: UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5434e8a2

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff80115a94000 UsbHub3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
ffffd000`22d0f290 fffff802`a33144fe : ffffd001`9eff1180 ffffe000`f3643040 00000000`fffffffe 00000000`fffffffe : nt!KiSwapContext+0x76
ffffd000`22d0f3d0 fffff802`a3313f79 : ffffd000`00000100 ffffd000`22d0f4d8 00000000`00000000 00001f80`0108f6b0 : nt!KiSwapThread+0x14e
ffffd000`22d0f470 fffff802`a32e6340 : 00000000`00000000 00000000`00000000 00000000`00000040 00000000`6964534b : nt!KiCommitThreadWait+0x129
ffffd000`22d0f4f0 fffff801`1761f31d : ffffe000`f7fbef60 fffff802`00000000 fffff801`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x2c0
ffffd000`22d0f580 ffffe000`f7fbef60 : fffff802`00000000 fffff801`00000000 00000000`00000000 ffffd001`9eff1180 : MAudioFastTrackPro+0x1231d
ffffd000`22d0f588 fffff802`00000000 : fffff801`00000000 00000000`00000000 ffffd001`9eff1180 ffffe000`efb22060 : 0xffffe000`f7fbef60
ffffd000`22d0f590 fffff801`00000000 : 00000000`00000000 ffffd001`9eff1180 ffffe000`efb22060 ffffe000`ef275100 : 0xfffff802`00000000
ffffd000`22d0f598 00000000`00000000 : ffffd001`9eff1180 ffffe000`efb22060 ffffe000`ef275100 fffff801`1761d1ca : 0xfffff801`00000000


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.3.9600.17396

FAILURE_BUCKET_ID: 0x9F_4_MAudioFastTrackPro_IMAGE_UsbHub3.sys

BUCKET_ID: 0x9F_4_MAudioFastTrackPro_IMAGE_UsbHub3.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_4_maudiofasttrackpro_image_usbhub3.sys

FAILURE_ID_HASH: {dc2ec278-9ad1-c082-5674-38174718fda5}

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

0: kd> lmvm UsbHub3
start end module name
fffff801`15a94000 fffff801`15b0c000 UsbHub3 (pdb symbols) c:\symbols\usbhub3.pdb\D0B0758E7B1D41B2AEC1E9ED5F1991632\usbhub3.pdb
Loaded symbol image file: UsbHub3.sys
Mapped memory image file: c:\symbols\UsbHub3.sys\5434E8A278000\UsbHub3.sys
Image path: \SystemRoot\System32\drivers\UsbHub3.sys
Image name: UsbHub3.sys
Timestamp: Wed Oct 08 15:32:50 2014 (5434E8A2)
CheckSum: 00075E4E
ImageSize: 00078000
File version: 6.3.9600.17396
Product version: 6.3.9600.17396
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: usbhub3.sys
OriginalFilename: usbhub3.sys
ProductVersion: 6.3.9600.17396
FileVersion: 6.3.9600.17396 (winblue_r4.141007-2030)
FileDescription: USB3 HUB Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.

The BSOD happens when the the USB 3.0 driver failed to complete a power IRP within a specific time. During shutdown, the OS terminates all running processes and safely removes all devices connected to the PC.

 

Things that you can try:

1. Instead of using the USB 3.0 port, try the USB 2.0 port and observe if you still get the BSOD.

2. Open the Device Manager and uncheck the "Allow the computer to turn off this device to save power" on all of the USB Hub / USB Root Hubs. When finished, disable also the USB suspend settings in the power options.

    - Sample image

    - Sample image

 

3. Run and install all Windows Updates to get the latest patch and bug fixes for the OS.

 

 

Let me know how it goes.

 

Regards



Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.

Follow us @LenovoSupport on Facebook and Twitter!

gmstk
Paper Tape
Posts: 2
Registered: ‎03-17-2015
Location: Greece
Views: 9,879
Message 3 of 3

Re: Driver power state failure caused by usbhub3.sys

Thank you very much for your reply. I also thought about plugging the audio interface to the usb 2.0 port but the problem still persists. In fact the crash log I shared with you came from the connection with the usb 2.0 port (sorry I didn't mention in my first post). Your second solution actually did the trick. Again, thank you very much, I appreciate it

Check out current deals!


Shop current deals

Top Kudoed Authors