PDC_WATCHDOG_TIMEOUT (14f)

U

User42

Member
Joined
Jun 15, 2021
Posts
7
Hi All,
I wonder if anyone can help me with the next steps to find the cause of the below please? I suspect this is something to do with Modern Standy (S0) but any help would be much appreciated.




Kernel Bitmap Dump File: Full address space is available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`1de00000 PsLoadedModuleList = 0xfffff800`1ea2a1b0
Debug session time: Wed Jun 9 18:43:41.499 2021 (UTC + 1:00)
System Uptime: 1 days 5:06:09.892
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................................................
Loading User Symbols

Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
4: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000001, A notification client failed to respond.
Arg3: ffffac000918bc60, Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT).
Arg4: fffffa03581c7a50, Pointer to a pdc!PDC_14F_TRIAGE structure.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on LN-PF1FNLY2

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 2

Key : Analysis.Memory.CommitPeak.Mb
Value: 74

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 14f

BUGCHECK_P1: 4

BUGCHECK_P2: 1

BUGCHECK_P3: ffffac000918bc60

BUGCHECK_P4: fffffa03581c7a50

IMAGE_NAME: dam.sys

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
fffffa03`581c79f8 fffff800`2085dccd : 00000000`0000014f 00000000`00000004 00000000`00000001 ffffac00`0918bc60 : nt!KeBugCheckEx
fffffa03`581c7a00 fffff800`1e141225 : ffffbf07`8ccb5480 ffffbf07`1be8dcf0 ffffbf07`1be8dcf0 ffffbf07`00000000 : pdc!PdcpNotificationWatchdog+0x19d
fffffa03`581c7a70 fffff800`1e0f53b5 : ffffbf07`8ccb5480 00000000`00000080 ffffbf07`1bebe080 00000000`00000000 : nt!ExpWorkerThread+0x105
fffffa03`581c7b10 fffff800`1e1fe348 : ffffd081`9a7d2180 ffffbf07`8ccb5480 fffff800`1e0f5360 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffa03`581c7b60 00000000`00000000 : fffffa03`581c8000 fffffa03`581c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


MODULE_NAME: dam

IMAGE_VERSION:

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x14F_DAM_IMAGE_dam.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {71a660da-efa0-43ad-07ec-33220699ba4c}

Followup: MachineOwner
---------
 
Could you please also provide a Kernel memory dump? It should be in the following directory:

Code: 
%systemroot%\MEMORY.DMP

Please ensure that you zip it and then upload it to a file sharing site such as Dropbox or Google Drive. It will too large to attach to a forum post.
 
Typically this is caused by some form of driver issue, usually the driver hasn't been written to properly handle a power transition request.

Rich (BB code): 
4: kd> !poaction
PopAction: fffff8001ea23200
  State..........: 0 - Idle
  Updates........: 0 
  Action.........: None
  Lightest State.: Unspecified
  Flags..........: 10000003 QueryApps|UIAllowed
  Irp minor......: ??
  System State...: Unspecified
  Hiber Context..: 0000000000000000

Allocated power irps (PopIrpList - fffff8001ea23970)
  IRP: ffffbf07547eba60 (wait-wake/S0), PDO: ffffbf07242ef8f0
  IRP: ffffbf0724edca40 (wait-wake/S0), PDO: ffffbf071f611060
  IRP: ffffbf0756775a70 (wait-wake/S0), PDO: ffffbf071f67e060
  IRP: ffffbf07565f4a40 (wait-wake/S0), PDO: ffffbf071f681060
  IRP: ffffbf07252f0010 (wait-wake/S0), PDO: ffffbf071f67c060
  IRP: ffffbf0751c915e0 (wait-wake/S1), PDO: ffffbf071f641630
  IRP: ffffbf0789696aa0 (wait-wake/S3), PDO: ffffbf0722736d00
  IRP: ffffbf07764a3aa0 (wait-wake/S3), PDO: ffffbf072273cd00
  IRP: ffffbf07518b87e0 (wait-wake/S0), PDO: ffffbf0722850d00
  IRP: ffffbf0785351aa0 (wait-wake/S0), PDO: ffffbf071f5f5360

Irp worker threads (PopIrpThreadList - fffff8001ea20960)
  THREAD: ffffbf071becb040 (static)
  THREAD: ffffbf071beca040 (static)
  THREAD: ffffbf0791502080 (dynamic)
  THREAD: ffffbf075765c040 (dynamic)
  THREAD: ffffbf078906a040 (dynamic)
  THREAD: ffffbf0789d0a040 (dynamic)
  THREAD: ffffbf078d59c040 (dynamic)
  THREAD: ffffbf078de77080 (dynamic)

Broadcast in progress: FALSE
Is Directed DRIPS Transition: FALSE

No Device State present

I've had a look at a few which are in the low-powered state and they appear to be related to your Intel Audio system. I would suggest checking for an update using the Intel Driver Support Assistant.

Rich (BB code): 
4: kd> lmvm IntcAudioBus
Browse full module list
start             end                 module name
fffff800`2c2d0000 fffff800`2c310000   IntcAudioBus   (no symbols)           
    Loaded symbol image file: IntcAudioBus.sys
    Image path: \SystemRoot\System32\drivers\IntcAudioBus.sys
    Image name: IntcAudioBus.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Apr 30 13:50:38 2019 (5CC8449E)
    CheckSum:         000448BA
    ImageSize:        00040000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
 
x BlueRobot said:
Typically this is caused by some form of driver issue, usually the driver hasn't been written to properly handle a power transition request.

Rich (BB code): 
4: kd> !poaction
PopAction: fffff8001ea23200
  State..........: 0 - Idle
  Updates........: 0
  Action.........: None
  Lightest State.: Unspecified
  Flags..........: 10000003 QueryApps|UIAllowed
  Irp minor......: ??
  System State...: Unspecified
  Hiber Context..: 0000000000000000

Allocated power irps (PopIrpList - fffff8001ea23970)
  IRP: ffffbf07547eba60 (wait-wake/S0), PDO: ffffbf07242ef8f0
  IRP: ffffbf0724edca40 (wait-wake/S0), PDO: ffffbf071f611060
  IRP: ffffbf0756775a70 (wait-wake/S0), PDO: ffffbf071f67e060
  IRP: ffffbf07565f4a40 (wait-wake/S0), PDO: ffffbf071f681060
  IRP: ffffbf07252f0010 (wait-wake/S0), PDO: ffffbf071f67c060
  IRP: ffffbf0751c915e0 (wait-wake/S1), PDO: ffffbf071f641630
  IRP: ffffbf0789696aa0 (wait-wake/S3), PDO: ffffbf0722736d00
  IRP: ffffbf07764a3aa0 (wait-wake/S3), PDO: ffffbf072273cd00
  IRP: ffffbf07518b87e0 (wait-wake/S0), PDO: ffffbf0722850d00
  IRP: ffffbf0785351aa0 (wait-wake/S0), PDO: ffffbf071f5f5360

Irp worker threads (PopIrpThreadList - fffff8001ea20960)
  THREAD: ffffbf071becb040 (static)
  THREAD: ffffbf071beca040 (static)
  THREAD: ffffbf0791502080 (dynamic)
  THREAD: ffffbf075765c040 (dynamic)
  THREAD: ffffbf078906a040 (dynamic)
  THREAD: ffffbf0789d0a040 (dynamic)
  THREAD: ffffbf078d59c040 (dynamic)
  THREAD: ffffbf078de77080 (dynamic)

Broadcast in progress: FALSE
Is Directed DRIPS Transition: FALSE

No Device State present

I've had a look at a few which are in the low-powered state and they appear to be related to your Intel Audio system. I would suggest checking for an update using the Intel Driver Support Assistant.

Rich (BB code): 
4: kd> lmvm IntcAudioBus
Browse full module list
start             end                 module name
fffff800`2c2d0000 fffff800`2c310000   IntcAudioBus   (no symbols)          
    Loaded symbol image file: IntcAudioBus.sys
    Image path: \SystemRoot\System32\drivers\IntcAudioBus.sys
    Image name: IntcAudioBus.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Apr 30 13:50:38 2019 (5CC8449E)
    CheckSum:         000448BA
    ImageSize:        00040000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
Click to expand...
It seems that is part of the Realtek audio driver package, seems that component has not had an update from Lenovo since 2018! I will check and see what Intel has as you suggested, seems odd that it is trying to make S1,S3 calls on a S0 device, Modern Standby and drivers seem to be bad bedfellows!

Thanks for your help, really useful to see how you got to this conclusion, I will go through the tutorials and try and improve my skills with this stuff :)
 
User42 said:
It seems that is part of the Realtek audio driver package, seems that component has not had an update from Lenovo since 2018! I will check and see what Intel has as you suggested, seems odd that it is trying to make S1,S3 calls on a S0 device, Modern Standby and drivers seem to be bad bedfellows!
Click to expand...
I'll update that also then. And Modern Standby is pretty buggy to be honest, there is little documentation on it so it developers are doing guess work to an extent.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top