W
Wyatt_15
Manufacture Lenovo Extreme Gen 3
OS Windows 10 Pro
OS Version 10.0.19042 N/A Build 19042
Hotfix(s): 11 Hotfix(s) Installed.
[01]: KB4580419
[02]: KB4534170
[03]: KB4537759
[04]: KB4542335
[05]: KB4545706
[06]: KB4557968
[07]: KB4562830
[08]: KB4577266
[09]: KB4580325
[10]: KB4586864
[11]: KB4586781
I am having a hell of a time figuring out what is causing the crash, I was able to find Event ID 1001 Bugcheck that correlates with the time of the crashes. The crashes seem to happen when waking up from a sleep.
I've tried with no success
- Changing power settings
- In BIO disable Intel Speed Step, checked Lenovo software for power saving settings and set to maximum
- Ran Windows Update and check Lenovo for driver updates as well as using there software updating tool
- Allowed system to sleep and wakeup unplugged from docking station to eliminate usb devices with only power adapter (167Watt)
I do have dump files, but I don't read Aramaic
, I tried using WinDbg here was the output of the latest. Help would be much appreciated.
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`209f5210 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffd0b`2cac7a00=000000000000014f
3: 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: ffff948c821c80b0, Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT).
Arg4: fffffd0b2cac7a50, 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: 11000
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on ITADMIN02-PC
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 22879
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 14f
BUGCHECK_P1: 4
BUGCHECK_P2: 1
BUGCHECK_P3: ffff948c821c80b0
BUGCHECK_P4: fffffd0b2cac7a50
IMAGE_NAME: dam.sys
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffd0b`2cac79f8 fffff807`2425dccd : 00000000`0000014f 00000000`00000004 00000000`00000001 ffff948c`821c80b0 : nt!KeBugCheckEx
fffffd0b`2cac7a00 fffff807`209034b5 : ffffca8b`5d85c040 ffffca8b`48098920 ffffca8b`48098920 ffffca8b`00000000 : pdc!PdcpNotificationWatchdog+0x19d
fffffd0b`2cac7a70 fffff807`208a29a5 : ffffca8b`5d85c040 00000000`00000080 ffffca8b`480d2240 6d6f6420`2c736c6f : nt!ExpWorkerThread+0x105
fffffd0b`2cac7b10 fffff807`209fc868 : ffffb680`17f54180 ffffca8b`5d85c040 fffff807`208a2950 2f3a7370`74746822 : nt!PspSystemThreadStartup+0x55
fffffd0b`2cac7b60 00000000`00000000 : fffffd0b`2cac8000 fffffd0b`2cac1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
MODULE_NAME: dam
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
IMAGE_VERSION: 10.0.19041.1030
FAILURE_ID_HASH: {71a660da-efa0-43ad-07ec-33220699ba4c}
Followup: MachineOwner
---------
Continue reading...
OS Windows 10 Pro
OS Version 10.0.19042 N/A Build 19042
Hotfix(s): 11 Hotfix(s) Installed.
[01]: KB4580419
[02]: KB4534170
[03]: KB4537759
[04]: KB4542335
[05]: KB4545706
[06]: KB4557968
[07]: KB4562830
[08]: KB4577266
[09]: KB4580325
[10]: KB4586864
[11]: KB4586781
I am having a hell of a time figuring out what is causing the crash, I was able to find Event ID 1001 Bugcheck that correlates with the time of the crashes. The crashes seem to happen when waking up from a sleep.
I've tried with no success
- Changing power settings
- In BIO disable Intel Speed Step, checked Lenovo software for power saving settings and set to maximum
- Ran Windows Update and check Lenovo for driver updates as well as using there software updating tool
- Allowed system to sleep and wakeup unplugged from docking station to eliminate usb devices with only power adapter (167Watt)
I do have dump files, but I don't read Aramaic
, I tried using WinDbg here was the output of the latest. Help would be much appreciated.For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`209f5210 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffd0b`2cac7a00=000000000000014f
3: 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: ffff948c821c80b0, Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT).
Arg4: fffffd0b2cac7a50, 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: 11000
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on ITADMIN02-PC
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 22879
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 14f
BUGCHECK_P1: 4
BUGCHECK_P2: 1
BUGCHECK_P3: ffff948c821c80b0
BUGCHECK_P4: fffffd0b2cac7a50
IMAGE_NAME: dam.sys
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffd0b`2cac79f8 fffff807`2425dccd : 00000000`0000014f 00000000`00000004 00000000`00000001 ffff948c`821c80b0 : nt!KeBugCheckEx
fffffd0b`2cac7a00 fffff807`209034b5 : ffffca8b`5d85c040 ffffca8b`48098920 ffffca8b`48098920 ffffca8b`00000000 : pdc!PdcpNotificationWatchdog+0x19d
fffffd0b`2cac7a70 fffff807`208a29a5 : ffffca8b`5d85c040 00000000`00000080 ffffca8b`480d2240 6d6f6420`2c736c6f : nt!ExpWorkerThread+0x105
fffffd0b`2cac7b10 fffff807`209fc868 : ffffb680`17f54180 ffffca8b`5d85c040 fffff807`208a2950 2f3a7370`74746822 : nt!PspSystemThreadStartup+0x55
fffffd0b`2cac7b60 00000000`00000000 : fffffd0b`2cac8000 fffffd0b`2cac1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
MODULE_NAME: dam
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
IMAGE_VERSION: 10.0.19041.1030
FAILURE_ID_HASH: {71a660da-efa0-43ad-07ec-33220699ba4c}
Followup: MachineOwner
---------
Continue reading...