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

[brosenz]

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:

 

[brosenz]

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. 2-3 times a day the crash, at least.

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

 

[zerospace-net]

This may sound like a stupid question, but have you installed (successfully) all updates (firmware, drivers, windows)? These errors used to happen frequently on the Surface Book, but that was when the firmware was still very unstable around this time last year.