After my Surface Book entered Sleep Mode it crashed with PDC.SYS being the cause

Discussion in 'Microsoft Surface Book' started by brosenz, Jan 8, 2017.

  1. brosenz

    brosenz New Member

    Joined:
    Apr 19, 2016
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    Surface Book
    My setup is the Surface Book connected to the Surface Dock, external Surface Keyboard, Logitech MX Master mouse with dongle attached to the dock and a 32" UltraSharp Dell Monitor connected to the Dock via mDP (Dock) to DP (Monitor). All Windows Update up to date and sfc /scannow clean with no errors, below is the outcome from the tool WhoCrashed. Please any help will be appreciated, thanks

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

    PDC_WATCHDOG_TIMEOUT (14f)
    A system component failed to respond within the allocated time period,
    preventing the system from exiting connected standby.
    Arguments:
    Arg1: 0000000000000004, Client ID of the hung component.
    Arg2: 0000000000000002, A resiliency client failed to respond.
    Arg3: fffff80b27607a38, Pointer to the resiliency client (pdc!_PDC_RESILIENCY_CLIENT).
    Arg4: ffffa4006dbacae0, Pointer to a pdc!PDC_14F_TRIAGE structure.


    The Stack:

    [​IMG]

    [​IMG]
     
    Last edited: Jan 8, 2017
  2. brosenz

    brosenz New Member

    Joined:
    Apr 19, 2016
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    Surface Book
    I was resuming from sleep and found out another crash, to be honest I am getting super frustrated with this level of instability, I cannot go more than 48 hours without a crash.


    *******************************************************************************
    * *
    * 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: ffff8988821ad610, Physical Device Object of the stack
    Arg3: ffffd900263a68e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffff89889b6b4010, The blocked IRP


    STACK_TEXT:


    nt!KiSwapContext+0x76
    nt!KiSwapThread+0x17c
    nt!KiCommitThreadWait+0x14f
    nt!KeWaitForSingleObject+0x377
    ndis!KWaitEventBase::Wait+0x22
    ndis!Ndis::BindEngine::ApplyBindChanges+0x5f
    ndis!ndisIssueNetEventSetPowerEvent+0x60
    ndis!ndisPrepForLowPower+0x38
    ndis!ndisSetDevicePower+0x204cc
    ndis!ndisSetPower+0x56
    ndis!ndisPowerDispatch+0xa8
    nt!PopIrpWorker+0x1de
    nt!PspSystemThreadStartup+0x41
    nt!KiStartSystemThread+0x16



    On Sun 1/8/2017 11:28:07 AM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\010817-13406-01.dmp
    uptime: 02:27:21
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x9F (0x3, 0xFFFF8988821AD610, 0xFFFFD900263A68E0, 0xFFFF89889B6B4010)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Sun 1/8/2017 11:28:07 AM your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    uptime: 02:27:21
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x9F (0x3, 0xFFFF8988821AD610, 0xFFFFD900263A68E0, 0xFFFF89889B6B4010)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
     
  3. jnjroach

    jnjroach Administrator Staff Member

    Joined:
    Nov 9, 2012
    Messages:
    7,178
    Likes Received:
    1,732
    Trophy Points:
    113
    Location:
    Seattle, WA USA
    My Device:
    Surface Book
    Have you applied all of the Firmware and OS updates?
     
  4. brosenz

    brosenz New Member

    Joined:
    Apr 19, 2016
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    Surface Book
    Everything is up to date, I would say everything was stable until I bought a dock and the external monitor Dell, shortly after all problems started, but it is the Microsoft Dock, it couldn't be any better. 2-3 times a day the crash, at least.
     
    Last edited: Jan 8, 2017
  5. jnjroach

    jnjroach Administrator Staff Member

    Joined:
    Nov 9, 2012
    Messages:
    7,178
    Likes Received:
    1,732
    Trophy Points:
    113
    Location:
    Seattle, WA USA
    My Device:
    Surface Book
    Use the Surface Dock Firmware Update Tool to update the dock:
    https://www.microsoft.com/download/details.aspx?id=46703
     
  6. brosenz

    brosenz New Member

    Joined:
    Apr 19, 2016
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    Surface Book
  7. brosenz

    brosenz New Member

    Joined:
    Apr 19, 2016
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    Surface Book
    Same thing, crash again while in sleep mode, 5 crash in the same day, it is kind of too much.

    On Sun 1/8/2017 6:16:57 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\010817-9921-01.dmp
    uptime: 00:26:41
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x9F (0x3, 0xFFFFD30DBD980120, 0xFFFFE6809C3AE8E0, 0xFFFFD30DB6D81550)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 1/8/2017 6:16:57 PM your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    uptime: 00:26:41
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x9F (0x3, 0xFFFFD30DBD980120, 0xFFFFE6809C3AE8E0, 0xFFFFD30DB6D81550)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 1/8/2017 5:15:01 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\010817-10421-01.dmp
    uptime: 00:45:53
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x9F (0x3, 0xFFFFB181D7F30C70, 0xFFFFF8038357F8E0, 0xFFFFB181EDA53240)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 1/8/2017 4:28:40 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\010817-11281-01.dmp
    uptime: 04:09:24
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x9F (0x3, 0xFFFF858C183D3360, 0xFFFFAB00E252B8E0, 0xFFFF858C1801D010)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 1/8/2017 11:28:07 AM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\010817-13406-01.dmp
    uptime: 02:27:21
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x9F (0x3, 0xFFFF8988821AD610, 0xFFFFD900263A68E0, 0xFFFF89889B6B4010)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 1/8/2017 9:00:12 AM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\010817-11453-01.dmp
    uptime: 21:27:00
    This was probably caused by the following module: pdc.sys (pdc!PdcpResiliencyWatchdog+0x9A)
    Bugcheck code: 0x14F (0x4, 0x2, 0xFFFFF80B27607A38, 0xFFFFA4006DBACAE0)
    Error: CUSTOM_ERROR
    file path: C:\WINDOWS\system32\drivers\pdc.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Power Dependency Coordinator Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
     
  8. ncameron

    ncameron Member

    Joined:
    Apr 4, 2013
    Messages:
    101
    Likes Received:
    12
    Trophy Points:
    18
  9. GreyFox7

    GreyFox7 Super Moderator Staff Member

    Joined:
    Jul 27, 2014
    Messages:
    6,383
    Likes Received:
    1,283
    Trophy Points:
    113
  10. Niterider4

    Niterider4 Active Member

    Joined:
    Oct 29, 2015
    Messages:
    187
    Likes Received:
    55
    Trophy Points:
    28
    My Device:
    Surface Book
    Welcome to the club! My Surface Book has been the most unreliable computer I have ever owned. After a year of crashing repeatedly during sleep, and occasionally during use, I reinstalled Windows completely. That reduced the crashes to about once per week, for maybe four weeks. Now my SB is back to crashing every day or at best every other day. Typically, I use it, close the lid, and when I open the lid again the next day the screen is black although the keys light up. Press the power button for 30 seconds, reboot, and it's fine again until the next spontaneous crash. No error messages except "Windows was not properly shut down" and "The previous system shutdown at ... was unexpected".

    I am very sorry that I ever bought the Surface Book. It has been nothing more than a very expensive exercise in frustration and disappointment for me.

    Since my warranty is about to expire, I am now sending back my SB and getting a replacement. I have absolutely zero confidence that the replacement will be any better than the POS I have now.

    Shame on Microsoft for releasing this buggy, untested, crappy line of computers on the marketplace.
     
  11. ncameron

    ncameron Member

    Joined:
    Apr 4, 2013
    Messages:
    101
    Likes Received:
    12
    Trophy Points:
    18
    Like a complete Windows reset or reinstallation, or buying a new laptop...
     

Share This Page