Windows 10: PDC_WATCHDOG_TIMEOUT 14f When Waking From Sleep.

I have tried numerous solutions from reinstalling Windows, using exclusively OEM Nvidia drivers, and installing the reference GPU drivers directly from Nvidia. This is a Zenbook Pro 14 UX6404VV model and I always have problems when trying to wake from sleep. Sometimes it just remains at a black screen when I open the lid, then restarts. Other times, it just reboots randomly while the lid is still closed. I am at a wits end. I will include the bug report down below. Someone please help me!************* Preparing the environment for Debugger Extensions Gallery repositories ************** Ext

:)

 

BugCheck PDC_WATCHDOG_TIMEOUT (14f) - PdcpMonitorOnWatchdogWorker

I'm having this issue as well with Surface Pro 4. I was hoping the April 2016 software and firmware updates would rectify the problem but it did not.

After getting three or four crashes in a matter of hours one day, I've disabled the sleep while plugged in and have not encountered the problem since.

*********************************************************

* *

* 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: 0000000000000000, Client ID of the hung component.

Arg2: 0000000000000100, Win32k did not complete a monitor-on request in a timely manner.

Arg3: 0000000000000000, The most recent POWER_MONITOR_REQUEST_REASON value for this request.

Arg4: 000000004f4d524d, A value indicating the internal path taken to initiate the request.

 

BugCheck PDC_WATCHDOG_TIMEOUT (14f) - PdcpMonitorOnWatchdogWorker

Has anyone found a solution to this problem?

I am also just encountering the exact same problem on my Surface Pro 2017 and Surface Book 2 (both on 1709) and not on docks. When the devices are on idle/sleep mode, the device will restart or blue screen with pdc.sys as the faulting driver, and 0x14F_DAM_IMAGE_dam.sys
as the faulting bucket id. This is occurring multiple times a day.

I have gone through updating all drivers/firmware, and re-imaging with same results.

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: fffff8021bffbe78, Pointer to the resiliency client (pdc!_PDC_RESILIENCY_CLIENT).

Arg4: ffffc60b2ec3fa60, Pointer to a pdc!PDC_14F_TRIAGE structure.

 

BugCheck PDC_WATCHDOG_TIMEOUT (14f) - PdcpMonitorOnWatchdogWorker

Same here: Surface Book i7, 16GB.

I have two monitors connected via DP to the Surface dock. I have two very annoying issues, that might be related.

External monitors do not always wake up from standby. It is either one or both having the problem. It sometimes helps to turn off an on the respective monitor(s) or the remove and reconnect the docking cable. Sometimes only a rebooot works.

The other issue is the mentioned BSOD caused by pdc.sys:

PDC_WATCHDOG_TIMEOUT (14f)

A system component failed to respond within the allocated time period,

preventing the system from exiting connected standby.

Arguments:

Arg1: 0000000000000000, Client ID of the hung component.

Arg2: 0000000000000100, Win32k did not complete a monitor-on request in a timely manner.

Arg3: 0000000000000000, The most recent POWER_MONITOR_REQUEST_REASON value for this request.

Arg4: 0000000050434c45, A value indicating the internal path taken to initiate the request.

This issue is a real show stopper and needs to be addressed quickly. Is there at least a reasonable workaround until a fix arrives?