PDC_WATCHDOG_TIMEOUT (14f)
A system component failed to respond within the allocated time period, preventing the system from exiting connected standby.
Connected standby is a low-power state (implemented in Windows 8, also in 8.1) that features extremely low power consumption while maintaining a
constant internet connection. Here is how to trigger connected standby:
- Press the system power button.
- Close the lid or tablet cover, or close the tablet into an attached dock.
- Select Sleep from the Power button on the Settings charm
I've
never seen this bug check on anything other than Windows tablets. I had an email a few months ago that had the same issue, and it turned out to be a network software conflict. It was a Surface Pro 3. Interestingly enough...
Code:
1: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=2446]
BiosMajorRelease = 0
BiosMinorRelease = 9
FirmwareMajorRelease = 4
FirmwareMinorRelease = 2
BiosVendor = DellInc.
BiosVersion = A09
BiosReleaseDate = 09/19/2014
SystemManufacturer = DellInc.
SystemProductName = Venue 8 Pro 5830
You have a Windows tablet as well.
Code:
1: kd> k
ChildEBP RetAddr
c5411cc0 856ba84d nt!KeBugCheckEx
c5411ce8 8192b980 pdc!PdcpNotificationWatchdog+0x93
c5411d70 8191c800 nt!ExpWorkerThread+0x244
c5411db0 81970601 nt!PspSystemThreadStartup+0x58
c5411dbc 00000000 nt!KiThreadStartup+0x15
Despite being a kernel-dump, our call stack is pretty naked for lack of a better word. We can see we're starting a thread which turns out to be a worker thread, and then we call into
pdc!PdcpResiliencyWatchdog+0xa6. This implies we failed to complete the resiliency phase in the allotted time period (however long). Usually when you see resiliency phase issues on a device regarding anything in terms of waking from an inactive state (sleep, hibernate, etc), the first thing to look at is network. For example, the D0 IRP for the required network device may not have completed in time due to a 3rd party conflict, etc.
We can further confirm we're likely dealing with a network issue by taking a look at our bucket_id:
Code:
FAILURE_BUCKET_ID: 0x14F_WCM_pdc!PdcpNotificationWatchdog
WCM is the Windows Connection Manager, which enables the creation and configuration of connection manager software.
As this is a tablet, I imagine you're most likely using Wi-Fi 100% of the time as your way of connecting to the internet? If a Wi-Fi connection is available, the system will wait for the Wi-Fi device only, regardless of whether a mobile broadband (MBB) connection is available. With this said, I took a look at what loaded modules we had to see if any antivirus was installed, firewall, etc. I was essentially looking for anything (kernel mode driver) that could have accidentally interfered with the network upon wake, regardless of its actual job.
As with most Windows tablet devices, it was mostly just DLLs and mandatory system files,
except:
Code:
1: kd> lmvm pcdsrvc
start end module name
c35c2000 c35c5e80 pcdsrvc (deferred)
Image path: \??\c:\program files\my dell\pcdsrvc.pkms
Image name: pcdsrvc.pkms
Timestamp: Mon May 09 20:20:45 2011 (4DC884DD)
CheckSum: 00014A51
ImageSize: 00003E80
File version: 6.2.2.0
Product version: 0.0.0.0
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: PC-Doctor, Inc.
InternalName: PCDSRVC
OriginalFilename: pcdsrvc
ProductVersion: 0.0.0.0
FileVersion: 6.2.2.0
FileDescription: Kernel Driver
LegalCopyright: Copyright PC-Doctor© 2002-2010
Looks like the kernel mode driver for Dell's Support Center software for hardware diagnostics. It's
really old, and probably the culprit if anything. Check to see if you can update this software, and if not, I'd honestly just uninstall it.
