Lenovo E14 System Crash - 04-19-2022
We have few Lenovo E14 Gen2 that suddenly experiencing random system crash after an hour or 2.
The issue started to show up on 04-19-2022. Not sure what is causing it but we are seeking assistance to get it fix as the affected devices are slowly increasing.
The affected devices started at 2 only and it is slowly increasing. We have reviewed the dmp file/s and all of the devices are getting the same dmp output.
Behavior of the issue are all office apps are crashing, during calls the backscreen and lagging occurs.
5: 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: 0000000000000001, Client ID of the hung component.
Arg2: 0000000000000001, A notification client failed to respond.
Arg3: ffffa18de1039380, Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT).
Arg4: ffff8780d196f450, Pointer to a pdc!PDC_14F_TRIAGE structure.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3812
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 31060
Key : Analysis.Init.CPU.mSec
Value: 1703
Key : Analysis.Init.Elapsed.mSec
Value: 130744
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 14f
BUGCHECK_P1: 1
BUGCHECK_P2: 1
BUGCHECK_P3: ffffa18de1039380
BUGCHECK_P4: ffff8780d196f450
IMAGE_NAME: ModernExecServer.dll
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: svchost.exe
STACK_TEXT:
ffff8780`d196f3f8 fffff803`2ae5dccd : 00000000`0000014f 00000000`00000001 00000000`00000001 ffffa18d`e1039380 : nt!KeBugCheckEx
ffff8780`d196f400 fffff803`284b86d5 : ffffe20a`01d85040 ffffe209`d7679010 ffffe209`d7679010 00000000`00000000 : pdc!PdcpNotificationWatchdog+0x19d
ffff8780`d196f470 fffff803`28555a15 : ffffe20a`01d85040 00000000`00000080 ffffe209`d76ad080 001fe4ff`bd9bbfff : nt!ExpWorkerThread+0x105
ffff8780`d196f510 fffff803`285fec78 : ffffb801`8bd95180 ffffe20a`01d85040 fffff803`285559c0 20646574`63657078 : nt!PspSystemThreadStartup+0x55
ffff8780`d196f560 00000000`00000000 : ffff8780`d1970000 ffff8780`d1969000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
MODULE_NAME: ModernExecServer
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x14F_PLM_IMAGE_ModernExecServer.dll
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8007afec-a3d4-8394-2075-d7ee4442d125}
Followup: MachineOwner