Surface Crash when Sleeping due to DRIVER_POWER_STATE_FAILURE (9f)

I have deployed 6 Surface Pro 3 tablets to our business for testing and all but 1 have this issue.

They have been imaged with Windows 8.1 Update Enterprise and have all updates applied to them.

When the device sleeps due to timeout it often crashes with the below error.  Sometimes it is very fast and the user doesn't even notice it has happened, other times it can take quite some time to boot with the surface logo being displayed.

I have tried quite a number of things like turning on or off hibernation, disabling selective suspend on the USB hubs, changing USB and network drivers and disconnecting devices.

The issue seems to be something to do with the dock as it only happens while docked.  We are using the Microsoft surface pro 3 dock. Below is an excerpt from the mini dump and here is a link to the whole mini dump file.

http://1drv.ms/1etIAaA

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe0013035b830, ffffd00116773960, ffffe0012f126010}

Probably caused by : UsbHub3.sys

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

3: 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: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe0013035b830, Physical Device Object of the stack
Arg3: ffffd00116773960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe0012f126010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5507a0c0

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff800f8f61000 UsbHub3

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

DPC_STACK_BASE:  FFFFD0011677AFB0

STACK_TEXT:  
ffffd001`16773928 fffff802`ce295782 : 00000000`0000009f 00000000`00000003 ffffe001`3035b830 ffffd001`16773960 : nt!KeBugCheckEx
ffffd001`16773930 fffff802`ce2956a2 : ffffe001`3075ed50 00000000`00000002 00000000`000007a0 fffff802`ce131391 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`16773990 fffff802`ce1332d8 : 00000000`00000000 ffffd001`16773ae0 00000000`00000001 ffffe001`303d0fe8 : nt!PopIrpWatchdog+0x32
ffffd001`167739e0 fffff802`ce1e17ea : ffffd001`1674a180 ffffd001`1674a180 ffffd001`167562c0 ffffe001`2fa91880 : nt!KiRetireDpcList+0x4f8
ffffd001`16773c60 00000000`00000000 : ffffd001`16774000 ffffd001`1676e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.3.9600.17731

FAILURE_BUCKET_ID:  0x9F_3_msu30x64w8_IMAGE_UsbHub3.sys

BUCKET_ID:  0x9F_3_msu30x64w8_IMAGE_UsbHub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_msu30x64w8_image_usbhub3.sys

FAILURE_ID_HASH:  {bc2f99d4-1d16-ae2a-14da-93e3da4aac3b}

Followup: MachineOwner
Thanks for your help.


May 27th, 2015 3:43am

Have you had any joy resolving this issue? I am also seeing this issue when my surface is docked.

Thanks

Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 4:19pm

If you are still crashing we need the new DMPS to confirm the current situation
June 17th, 2015 4:36pm

Hi, we recently have been experiencing a lot of BSOD within our organisation.

All drivers are up to date.

Please see the latest DMP which is related to the USBHUB3.sys

any help would be appreciated :)

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


Loading Dump File [C:\Users\alvara20\Desktop\061715-12390-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff800`aae73000 PsLoadedModuleList = 0xfffff800`ab14c850
Debug session time: Wed Jun 17 10:33:34.593 2015 (UTC + 9:30)
System Uptime: 0 days 2:10:06.216
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe000032b6a10, fffff800ac940960, ffffe0000aef1830}

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: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000032b6a10, Physical Device Object of the stack
Arg3: fffff800ac940960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe0000aef1830, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  531ae1a4

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff8004803d000 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

DPC_STACK_BASE:  FFFFF800AC947FB0

STACK_TEXT:  
fffff800`ac940928 fffff800`ab07b782 : 00000000`0000009f 00000000`00000003 ffffe000`032b6a10 fffff800`ac940960 : nt!KeBugCheckEx
fffff800`ac940930 fffff800`ab07b6a2 : ffffe000`0af03f00 00000000`00000002 00000000`000007a0 fffff800`aaf17391 : nt!PopIrpWatchdogBugcheck+0xde
fffff800`ac940990 fffff800`aaf192d8 : 00000000`00000000 fffff800`ac940ae0 00000000`00000001 00000000`00000000 : nt!PopIrpWatchdog+0x32
fffff800`ac9409e0 fffff800`aafc77ea : fffff800`ab176180 fffff800`ab176180 fffff800`ab1cfa00 ffffe000`0bc7b880 : nt!KiRetireDpcList+0x4f8
fffff800`ac940c60 00000000`00000000 : fffff800`ac941000 fffff800`ac93b000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.3.9600.17042

FAILURE_BUCKET_ID:  0x9F_3_msu30x64w8_IMAGE_UsbHub3.sys

BUCKET_ID:  0x9F_3_msu30x64w8_IMAGE_UsbHub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_msu30x64w8_image_usbhub3.sys

FAILURE_ID_HASH:  {bc2f99d4-1d16-ae2a-14da-93e3da4aac3b}

Followup: MachineOwner

Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 10:08pm

As usual we need the dumps
June 17th, 2015 10:13pm

https://onedrive.live.com/redir?resid=90713F82C8FFD362!539&authkey=!AGHVC-o16jHU0jo&ithint=file%2cdmp
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 10:22pm

Still the same driver, still the same date on that driver.  I would also remove McAfee as it is often responsible for this type of crash

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


Loading Dump File [C:\Users\zigza\Desktop\061715-12390-01(1).dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff800`aae73000 PsLoadedModuleList = 0xfffff800`ab14c850
Debug session time: Tue Jun 16 21:03:34.593 2015 (UTC - 4:00)
System Uptime: 0 days 2:10:06.216
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
..............
No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe000032b6a10, fffff800ac940960, ffffe0000aef1830}

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: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000032b6a10, Physical Device Object of the stack
Arg3: fffff800ac940960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe0000aef1830, The blocked IRP

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


SYSTEM_SKU:  Surface_Pro_3

SYSTEM_VERSION:  1

BIOS_DATE:  04/07/2015

BASEBOARD_PRODUCT:  Surface Pro 3

BASEBOARD_VERSION:  1

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe000032b6a10

BUGCHECK_P3: fffff800ac940960

BUGCHECK_P4: ffffe0000aef1830

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  531ae1a4

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff8004803d000 UsbHub3

CPU_COUNT: 4

CPU_MHZ: 9be

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 10.0.10075.9 amd64fre

STACK_TEXT:  
fffff800`ac940928 fffff800`ab07b782 : 00000000`0000009f 00000000`00000003 ffffe000`032b6a10 fffff800`ac940960 : nt!KeBugCheckEx
fffff800`ac940930 fffff800`ab07b6a2 : ffffe000`0af03f00 00000000`00000002 00000000`000007a0 fffff800`aaf17391 : nt!PopIrpWatchdogBugcheck+0xde
fffff800`ac940990 fffff800`aaf192d8 : 00000000`00000000 fffff800`ac940ae0 00000000`00000001 00000000`00000000 : nt!PopIrpWatchdog+0x32
fffff800`ac9409e0 fffff800`aafc77ea : fffff800`ab176180 fffff800`ab176180 fffff800`ab1cfa00 ffffe000`0bc7b880 : nt!KiRetireDpcList+0x4f8
fffff800`ac940c60 00000000`00000000 : fffff800`ac941000 fffff800`ac93b000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.3.9600.17042

FAILURE_BUCKET_ID:  0x9F_3_msu30x64w8_IMAGE_UsbHub3.sys

BUCKET_ID:  0x9F_3_msu30x64w8_IMAGE_UsbHub3.sys

PRIMARY_PROBLEM_CLASS:  0x9F_3_msu30x64w8_IMAGE_UsbHub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_msu30x64w8_image_usbhub3.sys

FAILURE_ID_HASH:  {bc2f99d4-1d16-ae2a-14da-93e3da4aac3b}

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

0: kd> !irp ffffe0000aef1830
Irp is active with 20 stacks 19 is current (= 0xffffe0000aef1e10)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe00003494050 00000000 fffff800aaf921cc-ffffe0000af03f00 Success Error Cancel pending
	      Unable to load image \SystemRoot\system32\DRIVERS\msu30x64w8.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for msu30x64w8.sys
*** ERROR: Module load completed but symbols could not be loaded for msu30x64w8.sys
 \Driver\msu30x64w8	nt!PopRequestCompletion
			Args: 00000000 00000001 00000003 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe0000af03f00    

			Args: 00000000 00000000 00000000 00000000

Irp Extension present at 0xffffe0000aef1ea0:

	Activity ID: {00000000-0000-0000-0000-000000000000}
0: kd> !devstack  ffffe000032b6a10
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffe00003494050  \Driver\msu30x64w8 ffffe000034941a0  InfoMask field not found for _OBJECT_HEADER at ffffe00003494020

> ffffe000032b6a10  \Driver\USBHUB3    ffffe0000324de70  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffe000032e4c10 :
  DeviceInst is "USB\VID_045E&PID_07C6\000001000000"
  ServiceName is "msu30x64w8"
0: kd> !devnode  ffffe000032b6a10
DevNode 0xffffe000032b6a10 for PDO 0000000000
  Parent 0xffffe00002ff1e20   Sibling 0x01780003   Child 0xffffe000009eb320   
  InterfaceType 0  Bus Number 0
  InstancePath is ""
  ServiceName is ""
  TargetDeviceNotify List - f 0000000000  b 0x4332494902410024
  State = Unknown State (0x0)
  Previous State = Unknown State (0x10000)
  StateHistory[03] = Unknown State (0x0)
  StateHistory[02] = Unknown State (0xffffe000)
  StateHistory[01] = Unknown State (0x32b6b88)
  StateHistory[00] = Unknown State (0x0)
  StateHistory[19] = Unknown State (0x32b6a10)
  StateHistory[18] = Unknown State (0x0)
  StateHistory[17] = Unknown State (0xd)
  StateHistory[16] = Unknown State (0x0)
  StateHistory[15] = Unknown State (0x1)
  StateHistory[14] = Unknown State (0xffffe000)
  StateHistory[13] = Unknown State (0x32b6b70)
  StateHistory[12] = Unknown State (0xffffe000)
  StateHistory[11] = Unknown State (0x32b6b70)
  StateHistory[10] = Unknown State (0x0)
  StateHistory[09] = Unknown State (0x60001)
  StateHistory[08] = Unknown State (0x22)
  StateHistory[07] = Unknown State (0x0)
  StateHistory[06] = Unknown State (0x0)
  StateHistory[05] = Unknown State (0x0)
  StateHistory[04] = Unknown State (0x0)
  Flags (0000000000)  
  CapabilityFlags (0x00000001)  DeviceD1
June 17th, 2015 11:20pm

Hi All im finally back.

Check out this KB

https://support.microsoft.com/en-us/kb/3051476

This KB has made a massive improvement.  We currently only have 6 devices in the wild.  This seems to have solved the issue for all but one, and that device has only crashed a couple of times since this was applied instead of once or twice a day.

See if it helps.

Free Windows Admin Tool Kit Click here and download it now
June 18th, 2015 2:33am

I'm not sure what driver your suggesting people to use.  As far as I can gather there hasn't been an update to that driver for some time.

I will see if removing Mcafee fixes our last device with the issue.  Although if it dose fix the issue that would be a show stopper for us.

June 18th, 2015 2:38am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics