Surface Crash when Sleeping due to DRIVER_POWER_STATE

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.

Edited by Joey.Jo-Jo.Junior.Shabadoo 3 hours 34 minutes ago

May 26th, 2015 11:47pm

JJJ

This was related to Network SurfaceGigabitEthernetAdapter 8.14.0704.2014 msu30x64w8.sys I would remove the current driver completely and install the newest driver available

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


Loading Dump File [C:\Users\zigza\Desktop\052715-12515-01.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 = 0xfffff802`ce08d000 PsLoadedModuleList = 0xfffff802`ce366850
Debug session time: Tue May 26 20:56:08.764 2015 (UTC - 4:00)
System Uptime: 0 days 2:20:22.923
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, 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:
------------------


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: ffffe0013035b830

BUGCHECK_P3: ffffd00116773960

BUGCHECK_P4: ffffe0012f126010

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5507a0c0

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff800f8f61000 UsbHub3

CPU_COUNT: 4

CPU_MHZ: 8f7

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  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:  
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

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
---------

3: kd> !irp ffffe0012f126010
Irp is active with 20 stacks 19 is current (= 0xffffe0012f1265f0)
 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 ffffe0012efc8050 00000000 fffff802ce1ac1cc-ffffe0013075ed50 Success Error Cancel pending
	      *** 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 00000004 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe0013075ed50    

			Args: 00000000 00000000 00000000 00000000

Irp Extension present at 0xffffe0012f126680:

	Activity ID: {00000000-0000-0000-0000-000000000000}
3: kd> !devobj ffffe0013035b830
Device object (ffffe0013035b830) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
Unable to load image \SystemRoot\system32\DRIVERS\ctxusbm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ctxusbm.sys
*** ERROR: Module load completed but symbols could not be loaded for ctxusbm.sys
 \Driver\USBHUB3 DriverObject ffffe001303826a0
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00003044
DevExt ffffe0013076b9c0 DevObjExt ffffe0013035b9a8 DevNode ffffe00130754d30 
ExtensionFlags (0000000000)  
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffe0012efc8050 \Driver\msu30x64w8
Device queue is not busy.
3: kd> !devstack ffffe0013035b830
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffe0012efc8050  \Driver\msu30x64w8 ffffe0012efc81a0  InfoMask field not found for _OBJECT_HEADER at ffffe0012efc8020

> ffffe0013035b830  \Driver\USBHUB3    ffffe0013076b9c0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffe00130754d30 :
  DeviceInst is "USB\VID_045E&PID_07C6\000001000000"
  ServiceName is "msu30x64w8"

Free Windows Admin Tool Kit Click here and download it now

May 27th, 2015 12:15am

appreciate your prompt reply.

I am currently running the newest version of that driver on our devices. I did try previously to roll back to the older driver but this issue still occurred and since have gobe back to the newer driver.

I will remove and reinstall the driver and see if it helps the situation.

Thanks

May 27th, 2015 2:06am

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