Windows crashes on power button pressed

Question

Windows crashes on power button pressed

Anonymous

Hello,

I have a problem with sleep mode on my Lenovo Yoga C940 14" laptop. Instead of successfully putting the computer to sleep, it seems to return to the active state after I close the lid or try to switch to sleep mode. If I press the power button where I have set the hibernate mode, the system crashes. It's strange because when I test both sleep and hibernate mode using the icons in the start menu, both modes work perfectly fine.

Here is some information about my configuration:

Laptop: Lenovo Yoga C940 14"

Operating System: Windows 11

Connected USB-C HUB: VAVA 9-in-1 USB-C Hub

Standby (S0 Low Power Idle) Network Connected and Hibernate

Sleep modes not available on my system: Standby (S1), Standby (S2), Standby (S3), Hybrid Sleep, Fast Startup

I am aware that Modern Standby (S0 Low Power Idle) is a newer and more energy efficient sleep mode that replaces older sleep modes such as S3. However, I am having trouble with this mode and would like to learn more about possible solutions to this problem.

So far, I have taken the following steps:

I have checked the power settings in Windows.

I have tried resetting the power settings using the powercfg command.

I checked the BIOS/UEFI settings, but found no options related to sleep mode except for USB power in sleep mode. I saw a message in the event viewer saying that the device could not be put into sleep mode.

I changed the USB3 settings to not switch to sleep mode, probably since the faulting module has changed.

I disabled sleep mode, disabled power to USB ports in sleep mode in UEFI, disabled fast start.

I ran a battery diagnostic with a tool from Lenovo.

I see related event in the log with ID 196:

USB device draining system power when system is idle.

USB Device: VID: 0xC76 PID: 0x153F REV: 0x100

Removal action failed: QueryRemovalInitiated

OR

USB Device: VID: 0x58F PID: 0x8468 REV: 0x100

Removal action failed: SkippedAsPersistentIoObserved

OR

USB Device: VID: 0x58F PID: 0x8468 REV: 0x100

Removal action failed: SkippedAsRecentIoObservered

In summary, the PDC_WATCHDOG_TIMEOUT bugcheck (0x14F) is related to the Power Dependency Coordinator (PDC) watchdog timer expiring. This occurs when certain system components do not respond within the allotted time frame. There are multiple parameters that can help you identify the underlying issue.

Debugging the PDC_WATCHDOG_TIMEOUT bugcheck (0x14F) requires a deep understanding of the Windows kernel, power management subsystems, and debugging tools. It is over my experience and competences.

Could you give me any other advice or suggestions on how to solve this sleep mode problem on my Lenovo Yoga C940 laptop? What other diagnostics or steps should I take to ensure that my laptop is working properly in sleep mode?

Thank you in advance for your help and taking the time to answer my query.

Sincerely,

Jiri

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

I am attaching additional data below:

Microsoft Windows [Version 10.0.22621.1413]

C:\Windows\System32>powercfg /availablesleepstates

The following sleep states are available on this system:

Standby (S0 Low Power Idle) Network Connected 

Hibernate

The following sleep states are not available on this system:

Standby (S1) 

    The system firmware does not support this standby state. 

    This standby state is disabled when S0 low power idle is supported. 

Standby (S2) 

    The system firmware does not support this standby state. 

    This standby state is disabled when S0 low power idle is supported. 

Standby (S3) 

    This standby state is disabled when S0 low power idle is supported. 

Hybrid Sleep 

    Standby (S3) is not available. 

Fast Startup 

    This action is disabled in the current system policy.

C:\Windows\System32>powercfg.exe /sleepstudy

Sleep Study report saved to file path C:\Windows\System32\sleepstudy-report.html.

C:\Windows\System32>powercfg /lastwake

Wake History Count - 0

C:\Windows\System32>powercfg /waketimers

There are no active wake timers in the system.

C:\Windows\System32>powercfg /requests

DISPLAY:

None.

SYSTEM:

[DRIVER] USB Audio Device (USB\VID_0C76&PID_153F&MI_00\8&29ec458f&0&0000)

An audio stream is currently in use.

[DRIVER] Legacy Kernel Caller

AWAYMODE:

None.

EXECUTION:

None.

PERFBOOST:

None.

ACTIVELOCKSCREEN:

None.

C:\Windows\System32>powercfg /list

Existing Power Schemes (* Active)

Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Balanced)

Power Scheme GUID: e24aea34-c295-45cd-905a-b7906a0dba46 (Yoga) *

Debug data:

Loading Dump File [C:\Windows\Minidump\032623-8656-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 22621 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff80664a00000 PsLoadedModuleList = 0xfffff80665613430

Debug session time: Sun Mar 26 20:33:41.473 2023 (UTC + 2:00)

System Uptime: 3 days 0:25:17.160

Loading Kernel Symbols

...............................................................

................................................................

.....

Loading User Symbols

Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v

1: kd> !analyze -v

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

* *

* 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: ffffe18dd7e382d0, Physical Device Object of the stack

Arg3: ffff8c8260a47158, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

Arg4: ffffe18e01c81010, The blocked IRP

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 2202 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 6486 

Key  : Analysis.Init.CPU.mSec 

Value: 1421 

Key  : Analysis.Init.Elapsed.mSec 

Value: 177539 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 103

FILE_IN_CAB: 032623-8656-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008

Kernel Generated Triage Dump

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe18dd7e382d0

BUGCHECK_P3: ffff8c8260a47158

BUGCHECK_P4: ffffe18e01c81010

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: UsbHub3.sys

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff806f26f0000 UsbHub3

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffff8c8260a47108 fffff80664f71946 : 000000000000009f 0000000000000003 ffffe18dd7e382d0 ffff8c8260a47158 : nt!KeBugCheckEx

ffff8c8260a47110 fffff80664f7181c : 0000000000000002 ffff940019b89180 ffffe18e06fa6810 ffff8c8260a47289 : nt!PopIrpWatchdogBugcheck+0x122

ffff8c8260a47190 fffff80664cbc09b : ffffe18e00000002 0000000000000001 ffff8c8200000000 0000000000000002 : nt!PopIrpWatchdog+0xc

ffff8c8260a471c0 fffff80664cbd816 : 0000000000000000 0000000000000000 0000000000000000 000000000097c1e2 : nt!KiProcessExpiredTimerList+0x1eb

ffff8c8260a472f0 fffff80664e2e1fe : ffff940019b89180 ffff940019b89180 ffffe18dc8641040 ffffe18dce132040 : nt!KiRetireDpcList+0xed6

ffff8c8260a47580 0000000000000000 : ffff8c8260a48000 ffff8c8260a41000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

IMAGE_VERSION: 10.0.22621.1485

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_rtux64w10_IMAGE_UsbHub3.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {07aff34b-0056-8e9b-3bad-55fc873e7886}

Followup: MachineOwner

Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64

Loading Dump File [C:\Windows\Minidump\040223-11640-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 22621 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff80020200000 PsLoadedModuleList = 0xfffff80020e13430

Debug session time: Sun Apr 2 12:48:00.790 2023 (UTC + 2:00)

System Uptime: 6 days 1:43:14.770

Loading Kernel Symbols

...............................................................

................................................................

.....

Loading User Symbols

Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v

1: kd> IMAGE_NAME: UsbHub3.sys

    ^ Syntax error in 'IMAGE\_NAME:  UsbHub3.sys'

1: kd> MODULE_NAME: UsbHub3

Couldn't resolve error at 'ODULE_NAME: UsbHub3'

1: kd> analyze -v

Couldn't resolve error at 'nalyze -v'

1: 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: ffffa28c4f81df00, Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT).

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

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 4812 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 19101 

Key  : Analysis.Init.CPU.mSec 

Value: 749 

Key  : Analysis.Init.Elapsed.mSec 

Value: 46065 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 99

FILE_IN_CAB: 040223-11640-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008

Kernel Generated Triage Dump

BUGCHECK_CODE: 14f

BUGCHECK_P1: 4

BUGCHECK_P2: 1

BUGCHECK_P3: ffffa28c4f81df00

BUGCHECK_P4: fffffa80d09c7320

IMAGE_NAME: dam.sys

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

fffffa80d09c72c8 fffff800243aeeef : 000000000000014f 0000000000000004 0000000000000001 ffffa28c4f81df00 : nt!KeBugCheckEx

fffffa80d09c72d0 fffff80020418985 : ffffd78f7e2d3040 ffffd78f6d5daa20 ffffd78f00000000 ffffd78f00000000 : pdc!PdcpNotificationWatchdog+0x15f

fffffa80d09c7340 fffff8002040f5b7 : ffffd78f7e2d3040 0000000000000ded ffffd78f7e2d3040 fffff80020418830 : nt!ExpWorkerThread+0x155

fffffa80d09c7530 fffff8002062e364 : ffffe781618be180 ffffd78f7e2d3040 fffff8002040f560 0000000000000000 : nt!PspSystemThreadStartup+0x57

fffffa80d09c7580 0000000000000000 : fffffa80d09c8000 fffffa80d09c1000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

MODULE_NAME: dam

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x14F_DAM_IMAGE_dam.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.22621.1485

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

Followup: MachineOwner

Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64

Loading Dump File [C:\Windows\Minidump\040323-7671-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 22621 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff80414600000 PsLoadedModuleList = 0xfffff80415213430

Debug session time: Mon Apr 3 09:09:33.100 2023 (UTC + 2:00)

System Uptime: 0 days 20:20:34.788

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: ffffe684e31ee650, Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT).

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

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 2874 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 10786 

Key  : Analysis.Init.CPU.mSec 

Value: 577 

Key  : Analysis.Init.Elapsed.mSec 

Value: 25858 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 99

FILE_IN_CAB: 040323-7671-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008

Kernel Generated Triage Dump

BUGCHECK_CODE: 14f

BUGCHECK_P1: 4

BUGCHECK_P2: 1

BUGCHECK_P3: ffffe684e31ee650

BUGCHECK_P4: ffffe406660d2320

IMAGE_NAME: dam.sys

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffe406660d22c8 fffff804198ceeef : 000000000000014f 0000000000000004 0000000000000001 ffffe684e31ee650 : nt!KeBugCheckEx

ffffe406660d22d0 fffff80414818985 : ffffbb098febb040 ffffbb0979237c50 ffffbb0900000000 fffff80400000000 : pdc!PdcpNotificationWatchdog+0x15f

ffffe406660d2340 fffff8041480f5b7 : ffffbb098febb040 0000000000001544 ffffbb098febb040 fffff80414818830 : nt!ExpWorkerThread+0x155

ffffe406660d2530 fffff80414a2e364 : ffff990080d40180 ffffbb098febb040 fffff8041480f560 0000000000000246 : nt!PspSystemThreadStartup+0x57

ffffe406660d2580 0000000000000000 : ffffe406660d3000 ffffe406660cc000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

MODULE_NAME: dam

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x14F_DAM_IMAGE_dam.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.22621.1485

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

Followup: MachineOwner

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

Complete diagnostic data are available for download for 7 day from:
https://upload.nolog.cz/download/3b735e6e2dd06367/#qSWSWDDBTJZI7oXJgXv0uA

Relevant info at: https://bsodtutorials.wordpress.com/2019/12/15/debugging-stop-0x14f-pdc\_watchdog\_timeout/

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

5 answers

Answer 1

Hello colegues,

thank you for your advices.

Yes, the events are different because sometimes the crash happened spontaneously and sometimes when the power button was pressed. I am some time running without any another crash. Actually I cannot say, what was the solution and if it is really solved. I will see later.

But I'll ask in general, is there any guidance for configuring the power mode of modern laptops? Are there any power management modes, is there an option to let or not let the device power down, is there an option to set sleep mode with or without networking. I believe there was a big problem if there was a speaker connected to the external usb hub that was charging. I would need to get a better understanding of this so I could routinely set it up on different configurations. There are too many possibilities to test by trial and error :-)

Feel free to point me to a link if there is relevant documentation.

Best regards,

Jiri

Answer 2

Igor Leyko 111K Independent Advisor

Jiri,

different dumps point to different modules, including Windows components. This likely means hardware problems unfortunately. However, you may try to disconnect all USB devices and see if this helps.

0 comments

Answer 3

It looks like it has to to with UsbHub3 which is probably the collection of ports on the computer or its case. It could be the external hub if you have one. They're all hubs.

You can obviously try disabling all of that one in Device Manager if you have another still capable of using the mouse and keyboard and the problem should go away.

It could also in theory be something plugged into that UsbHub3 or the BIOS.

It could also be in theory something else conflicting and interacting poorly with it.

Personally, I would avoid saying its hardware and needs to be sent in for repair unless a different OS with a different driver also had a problem with those ports. People are often too hasty that way before actually narrowing down enough.

But, if the ports are working fine outside of this then its probably not a hardware issue. Drivers have to shutdown the hardware for suspend and power off and in rare cases they don't do it well lol. There's probably just some difference in Windows doing it verses the user manually doing it. Since they're technically two different things then its possible for programmers to mess it up in some way.

PDC_WATCHDOG_TIMEOUT however, could indeed very well be software as well. It doesn't strictly mean hardware failure.

Hope the best :)

Answer 4

Anonymous

Hello Igor.

why do you think so?

Are you sure that problem is not in external USB hub?

Jiri

0 comments

Answer 5

Igor Leyko 111K Independent Advisor

Hi Jiri,

My name is Igor, it's a pleasure for me to help others and I'll do all my best to help you.

I'm sorry but seems it is needed to check the laptop in Lenovo service center.

0 comments

Share via

Windows crashes on power button pressed

5 answers