Windows 10: Surface Book 2 BSOD - DRIVER_POWER_STATE_FAILURE 9f - Suspect Surface Dock

Discus and support Surface Book 2 BSOD - DRIVER_POWER_STATE_FAILURE 9f - Suspect Surface Dock in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi, I recently purchased a Surface Dock and since then I have started to have DRIVER_POWER_STATE_FAILURE 9f BSODs when the system is idle, I assume... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by MattYUK99, Jan 10, 2020.

  1. MattYUK99 Win User

    Surface Book 2 BSOD - DRIVER_POWER_STATE_FAILURE 9f - Suspect Surface Dock


    Hi,


    I recently purchased a Surface Dock and since then I have started to have DRIVER_POWER_STATE_FAILURE 9f BSODs when the system is idle, I assume when trying to hibernate. The crash dump below suggests that this is related to the dock ethernet drivers.


    The msux64w10 driver version is 10.7.807.2018 and I have tried to update the dock firmware but cannot tell if this has worked as the instructions talk about a flashing light while updating in the Eth port, but there are not LEDs on this dock! Any ideas?




    Microsoft R Windows Debugger Version 10.0.18362.1 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 17763 MP 8 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 17763.1.amd64fre.rs5_release.180914-1434

    Machine Name:

    Kernel base = 0xfffff800`3de02000 PsLoadedModuleList = 0xfffff800`3e21b710

    Debug session time: Fri Jan 10 00:31:17.428 2020 UTC + 0:00

    System Uptime: 0 days 3:48:12.433

    Loading Kernel Symbols

    ......................................Page 2001e354c too large to be in the dump file.

    .........................

    ................................................................

    ................................................................

    ...................................................

    Loading User Symbols



    Loading unloaded module list

    ..........................

    For analysis of this file, run !analyze -v

    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: ffffd503d395b8f0, Physical Device Object of the stack

    Arg3: fffff800408687d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

    Arg4: ffffd503cbe7b010, The blocked IRP



    Debugging Details:

    ------------------



    Implicit thread is now ffffd503`d6527040



    KEY_VALUES_STRING: 1





    PROCESSES_ANALYSIS: 1



    SERVICE_ANALYSIS: 1



    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 401



    BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434



    SYSTEM_MANUFACTURER: Microsoft Corporation



    SYSTEM_PRODUCT_NAME: Surface Book 2



    SYSTEM_SKU: Surface_Book_1832



    SYSTEM_VERSION: D:0B:10K:0F:5C:10P:38



    BIOS_VENDOR: Microsoft Corporation



    BIOS_VERSION: 389.2837.768



    BIOS_DATE: 08/21/2019



    BASEBOARD_MANUFACTURER: Microsoft Corporation



    BASEBOARD_PRODUCT: Surface Book 2



    DUMP_TYPE: 1



    BUGCHECK_P1: 3



    BUGCHECK_P2: ffffd503d395b8f0



    BUGCHECK_P3: fffff800408687d0



    BUGCHECK_P4: ffffd503cbe7b010



    DRVPOWERSTATE_SUBCODE: 3



    FAULTING_THREAD: ffffd503d6527040



    CPU_COUNT: 8



    CPU_MHZ: 840



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 8e



    CPU_STEPPING: a



    CPU_MICROCODE: 6,8e,a,0 F,M,S,R SIG: B4'00000000 cache B4'00000000 init



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXPNP: 1 !blackboxpnp





    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    BUGCHECK_STR: 0x9F



    PROCESS_NAME: System



    CURRENT_IRQL: 2



    ANALYSIS_SESSION_HOST: YAR-CLE-PC03



    ANALYSIS_SESSION_TIME: 01-10-2020 08:17:39.0292



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    LAST_CONTROL_TRANSFER: from fffff8003deaa627 to fffff8003dfbf546



    STACK_TEXT:

    ffffd309`91e7fd60 fffff800`3deaa627 : 00000000`00000000 ffffd503`d6527040 ffffd309`91e80280 ffffd503`cbe80010 : nt!KiSwapContext+0x76

    ffffd309`91e7fea0 fffff800`3deaa199 : ffffd503`c99851a0 ffffd309`91e80280 ffffd309`91e7ff90 fffff800`00000000 : nt!KiSwapThread+0x297

    ffffd309`91e7ff60 fffff800`3dea8f20 : 00000000`00000100 ffffd503`00000000 fffff800`00000000 ffffd309`91e80071 : nt!KiCommitThreadWait+0x549

    ffffd309`91e80000 fffff800`3de63b70 : ffffd309`91e80108 00000000`00000000 fffff800`52f6a400 fffff800`52e2bc00 : nt!KeWaitForSingleObject+0x520

    ffffd309`91e800d0 fffff800`52f9a99c : fffff800`52e06180 00000000`00000001 00000000`00000004 ffffd309`91e80428 : nt!ExWaitForRundownProtectionReleaseCacheAware+0xa0

    ffffd309`91e80140 fffff800`52e3707a : ffffd503`d5e25100 fffff800`00000003 ffffd503`c67e8660 ffffd503`c67e8660 : tcpip!FlpWaitForMiniportToReturnTransmittedPackets+0x14

    ffffd309`91e80170 fffff800`52e062b4 : 00000000`00000000 fffff800`51d508e0 00000000`7377444e 00000000`00000008 : tcpip!FlpUninitializePacketProviderInterface+0x52

    ffffd309`91e801b0 fffff800`52e0618e : ffffd503`d6dee280 00000000`00000008 ffffd503`bce138e0 ffffd309`91e80420 : tcpip!FlPnpEvent+0x108

    ffffd309`91e80250 fffff800`51d72119 : ffffd503`d5e251e0 fffff800`51d66e04 ffffffff`5f114500 00000000`00000002 : tcpip!Fl48PnpEvent+0xe

    ffffd309`91e80280 fffff800`51d71dba : 00000000`00000008 ffffd503`d6dee280 ffffd503`bce138e0 ffffd503`d6dee280 : ndis!ndisInvokeNetPnPEvent+0x49

    ffffd309`91e802c0 fffff800`51dbe47a : 00000000`c00000bb ffffd309`91e80420 ffffd503`bce138e0 ffffd503`cbe87c70 : ndis!ndisDeliverNetPnPEventSynchronously+0x9e

    ffffd309`91e80320 fffff800`51d6e8fd : ffffd309`91e80570 ffffd309`91e805e9 ffffd309`91e80570 ffffd503`c99851a0 : ndis!ndisPnPNotifyBinding+0xde

    ffffd309`91e80500 fffff800`51d6a15c : ffffd503`d6dee280 fffff800`51d7066b ffff8f0f`b6f03de0 ffffd309`91e805f9 : ndis!ndisPnPNotifyBindingUnlocked+0x35

    ffffd309`91e80550 fffff800`51d6a08e : ffffd309`91e806c0 ffff8f0f`b6f04780 00000000`00000000 ffffd503`00000000 : ndis!ndisPauseProtocolInner+0x68

    ffffd309`91e80650 fffff800`51d6fe42 : 00000000`00000000 ffffd309`91e80790 00000000`00000001 ffffd503`c99865b8 : ndis!ndisPauseProtocol+0x66

    ffffd309`91e80690 fffff800`51d6fc73 : ffffd503`c99865b8 ffffd503`c99865b8 ffffd503`c9986630 ffffd503`c99851a0 : ndis!Ndis::BindEngine::Iterate+0x13e

    ffffd309`91e80800 fffff800`51d724ed : ffffd503`c99865b8 ffffd503`cbe7b000 00000000`00000000 ffffd309`91e80880 : ndis!Ndis::BindEngine::UpdateBindings+0x7b

    ffffd309`91e80830 fffff800`51d6f9d0 : ffffd503`c99865b8 00000000`00000000 ffffd503`c99865b8 fffff800`51d703d7 : ndis!Ndis::BindEngine:Surface Book 2 BSOD - DRIVER_POWER_STATE_FAILURE 9f - Suspect Surface Dock :DispatchPendingWork+0x75

    ffffd309`91e80860 fffff800`51cdfffb : ffffd503`c99851a0 ffffd503`cbe7b020 ffffd503`c99865b8 00000000`00000003 : ndis!Ndis::BindEngine::ApplyBindChanges+0x54

    ffffd309`91e808b0 fffff800`51ce0355 : 00000000`00000800 ffffd503`cbe7b010 ffffd503`c99851a0 ffffd503`c99851a0 : ndis!ndisPrepForLowPower+0x20993

    ffffd309`91e80980 fffff800`51d67bda : 00000000`00000000 ffffd503`cbe7b010 ffffd503`cbe7b680 ffffd503`d6b2e490 : ndis!ndisSetDevicePower+0x20919

    ffffd309`91e809f0 fffff800`51cd3c01 : ffffd503`cbe7b010 ffffd503`d395b8f0 ffffd503`cbe7b680 ffffd503`cbe7b010 : ndis!ndisSetPower+0x5e

    ffffd309`91e80a30 fffff800`3df70016 : ffffd503`d6527040 ffffd309`91e80ae0 ffffd503`cbe7b010 ffffd503`cbe7a100 : ndis!ndisPowerDispatch+0xa1

    ffffd309`91e80a60 fffff800`3de5a9c5 : ffffffff`fa0a1f00 fffff800`3df6fdf0 ffffd503`c616b770 00000000`00000000 : nt!PopIrpWorker+0x226

    ffffd309`91e80b10 fffff800`3dfbfdfc : ffffbc82`003cf180 ffffd503`d6527040 fffff800`3de5a970 00000000`00000000 : nt!PspSystemThreadStartup+0x55

    ffffd309`91e80b60 00000000`00000000 : ffffd309`91e81000 ffffd309`91e7a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c





    STACK_COMMAND: .thread 0xffffd503d6527040 ; kb



    THREAD_SHA1_HASH_MOD_FUNC: 0d4afe61821f4ce125981cea28a3b288745a5608



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 30cc7d81059d4ad4e1455b8febfd23d1f7c7b2df



    THREAD_SHA1_HASH_MOD: 3ff2f9e2eba41bc3c3b5337f3bb249eb0e2b33c1



    FOLLOWUP_IP:

    tcpip!FlpWaitForMiniportToReturnTransmittedPackets+14

    fffff800`52f9a99c 4883c428 add rsp,28h



    FAULT_INSTR_CODE: 28c48348



    SYMBOL_STACK_INDEX: 5



    SYMBOL_NAME: tcpip!FlpWaitForMiniportToReturnTransmittedPackets+14



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: tcpip



    IMAGE_NAME: tcpip.sys



    DEBUG_FLR_IMAGE_TIMESTAMP: 257daf83



    BUCKET_ID_FUNC_OFFSET: 14



    FAILURE_BUCKET_ID: 0x9F_3_tcpip!FlpWaitForMiniportToReturnTransmittedPackets



    BUCKET_ID: 0x9F_3_tcpip!FlpWaitForMiniportToReturnTransmittedPackets



    PRIMARY_PROBLEM_CLASS: 0x9F_3_tcpip!FlpWaitForMiniportToReturnTransmittedPackets



    TARGET_TIME: 2020-01-10T00:31:17.000Z



    OSBUILD: 17763



    OSSERVICEPACK: 0



    SERVICEPACK_NUMBER: 0



    OS_REVISION: 0



    SUITE_MASK: 272



    PRODUCT_TYPE: 1



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



    OS_LOCALE:



    USER_LCID: 0



    OSBUILD_TIMESTAMP: unknown_date



    BUILDDATESTAMP_STR: 180914-1434



    BUILDLAB_STR: rs5_release



    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434



    ANALYSIS_SESSION_ELAPSED_TIME: 5a9c



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x9f_3_tcpip!flpwaitforminiporttoreturntransmittedpackets



    FAILURE_ID_HASH: {56e2c87f-3e61-a984-a054-31675410c461}



    Followup: MachineOwner

    ---------



    0: kd> !devstack ffffd503d395b8f0

    !DevObj !DrvObj !DevExt ObjectName

    ffffd503c9985050 \Driver\msux64w10 ffffd503c99851a0 NDMP20

    > ffffd503d395b8f0 Page 20018d3b7 too large to be in the dump file.

    \Driver\USBHUB3 ffffd503d5eb27f0 USBPDO-6

    !DevNode ffffd503d89dc9a0 :

    DeviceInst is "USB\VID_045E&PID_07C6\000001000000"

    ServiceName is "msux64w10"

    :)
     
    MattYUK99, Jan 10, 2020
    #1
  2. Brink Win User

    New Version of Surface Dock Updater Available


    Source: New Version of Surface Dock Updater Available Surface
     
    Brink, Jan 10, 2020
    #2
  3. BSOD during connected standby on Surface Book 2: DRIVER_POWER_STATE_FAILURE

    Hi,

    I'm getting BSOD on my Surface Book 2 - Core i7 16GB 1TB several times a days when it gets in to connected standby.

    Here's the output from WinDBG:

     
    N Deslandes, Jan 10, 2020
    #3
  4. waldo21 Win User

    Surface Book 2 BSOD - DRIVER_POWER_STATE_FAILURE 9f - Suspect Surface Dock

    2nd monitor with surface book and dock does not play nice

    1. The new Microsoft surface dock.

    2. No, it has always behaved that way with the surface book and surface dock.

    3. Using the default display drivers that came with the surface book. - windows update does not show any alternatives.
     
    waldo21, Jan 10, 2020
    #4
Thema:

Surface Book 2 BSOD - DRIVER_POWER_STATE_FAILURE 9f - Suspect Surface Dock

Loading...
  1. Surface Book 2 BSOD - DRIVER_POWER_STATE_FAILURE 9f - Suspect Surface Dock - Similar Threads - Surface Book BSOD

  2. Surface Book 3 + Surface Dock 2 Not Recognizing Second Monitor

    in Windows 10 Gaming
    Surface Book 3 + Surface Dock 2 Not Recognizing Second Monitor: My workstation is set up such that I have a Surface Book 3 SB3 connected to a Surface Dock 2 SD2. The SD2 is in turn connected via two USB-C to DVI-D dual link cables to two external monitors. I've noticed an issue that when I connect my SB3 to my SD2, only one of the...
  3. Surface Book 3 + Surface Dock 2 Not Recognizing Second Monitor

    in Windows 10 Software and Apps
    Surface Book 3 + Surface Dock 2 Not Recognizing Second Monitor: My workstation is set up such that I have a Surface Book 3 SB3 connected to a Surface Dock 2 SD2. The SD2 is in turn connected via two USB-C to DVI-D dual link cables to two external monitors. I've noticed an issue that when I connect my SB3 to my SD2, only one of the...
  4. Surface Book 3 + Surface Dock 2 Not Recognizing Second Monitor

    in Windows 10 Drivers and Hardware
    Surface Book 3 + Surface Dock 2 Not Recognizing Second Monitor: My workstation is set up such that I have a Surface Book 3 SB3 connected to a Surface Dock 2 SD2. The SD2 is in turn connected via two USB-C to DVI-D dual link cables to two external monitors. I've noticed an issue that when I connect my SB3 to my SD2, only one of the...
  5. Problems with Surface Book 3 and/or Dock 2

    in Windows 10 Drivers and Hardware
    Problems with Surface Book 3 and/or Dock 2: My NEW Surface Book 3, with the NEW Dock 2, routinely cannot find my external monitor even though it worked for multiple days in a row. It also refuses to use the Nvidia graphics to run the monitor which makes it poorer quality. It is also VERY "laggy" using the Microsoft...
  6. Surface Book 2 on 1903 BSOD - NDIS.SYS - Surface Dock Ethernet

    in Windows 10 Drivers and Hardware
    Surface Book 2 on 1903 BSOD - NDIS.SYS - Surface Dock Ethernet: Hello All, Currently I have 6 Surface Book 2's all with the same issue. The Ethernet Adapter on the Surface Docks will connect and disconnect on repeat, once a second until eventually the SB2 will blue screen. There is roughly 150 Surface book 2's, 200 Surface Laptop 2's...
  7. BSOD (DRIVER_POWER_STATE_FAILURE) upon waking Surface Book 2

    in Windows 10 BSOD Crashes and Debugging
    BSOD (DRIVER_POWER_STATE_FAILURE) upon waking Surface Book 2: My Surface Book 2 (13.5" i7 w/ GTX 1050) on Windows 10 Version 1809 has a roughly 3 in 4 chance to, upon waking up, trigger a DRIVER_POWER_STATE_FAILURE blue screen a couple minutes after waking up. During the couple minutes between waking and crashing, random components of...
  8. Surface Book 2 USB and Docking Problems

    in Windows 10 Drivers and Hardware
    Surface Book 2 USB and Docking Problems: Has anyone encountered this issue? ALWAYS after startup, my Surface Book 2 touchpad freezes for 1-3 seconds several times. After it's done freezing, it gives off the "USB has connected" sound, stops freezing, then does it again and again for about 4-5 times. After it's done...
  9. Surface Book 2 USB and Docking Problems

    in Windows 10 Support
    Surface Book 2 USB and Docking Problems: Has anyone encountered this issue? ALWAYS after startup, my Surface Book 2 touchpad freezes for 1-3 seconds several times. After it's done freezing, it gives off the "USB has connected" sound, stops freezing, then does it again and again for about 4-5 times. After it's done...
  10. BSOD during connected standby on Surface Book 2: DRIVER_POWER_STATE_FAILURE

    in Windows 10 BSOD Crashes and Debugging
    BSOD during connected standby on Surface Book 2: DRIVER_POWER_STATE_FAILURE: Hi, I'm getting BSOD on my Surface Book 2 - Core i7 16GB 1TB several times a days when it gets in to connected standby. Here's the output from WinDBG: 4: kd> !analyze -v ******************************************************************************* *...

Users found this page by searching for:

  1. driver power state falioure surface book.2