CLOCK WATCHDOG TIMEOUT

[basco55]

Hi All

I have new build pc which crashes, freezes randomly or every time i try to run " msdt.exe -id DeviceDiagnostic ". stop code is CLOCK WATCHDOG TIMEOUT. I have tried many fixes and windows repair tools to no avail. 20 years ago my pc knowledge was above amateur but now i have fallen behind so much this issue is beyond me, please help.

pc info :

Processor 12th Gen Intel(R) Core(TM) i5-12500, 3000 Mhz, 6 Core(s), 12 Logical Processor(s)

BaseBoard Product MAG B660M MORTAR WIFI DDR4 (MS-7D42)

BIOS Mode UEFI

System Type x64-based PC

ssd 500 GB

DDR4 RAM 32GB

Windows 11 Pro.



dump file info:

Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\063022-4218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff804`2ba00000 PsLoadedModuleList = 0xfffff804`2c6296b0
Debug session time: Thu Jun 30 05:42:52.235 2022 (UTC - 7:00)
System Uptime: 0 days 0:00:04.888
Loading Kernel Symbols
...............................................................
..............................................
Loading User Symbols
Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`2be15590 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc089`5b45f370=000000000000004c
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: ffffaf043d5c2a50, String that identifies the problem.
Arg2: ffffffffc0000428, Error Code.
Arg3: ffffaf0439cffcf0
Arg4: 0000000000000000

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

ETW minidump data unavailable

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2265

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2399

Key : Analysis.Init.CPU.mSec
Value: 202

Key : Analysis.Init.Elapsed.mSec
Value: 3032

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

Key : Bugcheck.Code.DumpHeader
Value: 0xc000021a

Key : Bugcheck.Code.Register
Value: 0x4c

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: 063022-4218-01.dmp

ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x

EXCEPTION_CODE_STR: c000021a

EXCEPTION_PARAMETER1: ffffaf043d5c2a50

EXCEPTION_PARAMETER2: ffffffffc0000428

EXCEPTION_PARAMETER3: ffffaf0439cffcf0

EXCEPTION_PARAMETER4: 0

BUGCHECK_CODE: c000021a

BUGCHECK_P1: ffffaf043d5c2a50

BUGCHECK_P2: ffffffffc0000428

BUGCHECK_P3: ffffaf0439cffcf0

BUGCHECK_P4: 0

PROCESS_NAME: smss.exe

ADDITIONAL_DEBUG_TEXT: Verification of a KnownDLL failed.

IMAGE_NAME: ntkrnlmp.exe

MODULE_NAME: nt

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffc089`5b45f368 fffff804`2c46831f : 00000000`0000004c 00000000`c000021a ffffc089`5b52a318 ffff8684`d89c7190 : nt!KeBugCheckEx
ffffc089`5b45f370 fffff804`2c459344 : 00000000`00000000 ffffc089`5b45f430 ffffffff`800002b0 00000000`00000000 : nt!PopGracefulShutdown+0x2af
ffffc089`5b45f3b0 fffff804`2c44f82c : 00000000`00000001 ffffaf04`00000006 00000000`00000000 00000000`00000005 : nt!PopTransitionSystemPowerStateEx+0x12e5c
ffffc089`5b45f470 fffff804`2be27b75 : fffff804`2ba10a78 fffff804`2bcff249 00000000`00000000 fffff804`29924c80 : nt!NtSetSystemPowerState+0x4c
ffffc089`5b45f640 fffff804`2be19de0 : fffff804`2c2c9c20 00000000`00000014 ffffffff`ffffff00 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
ffffc089`5b45f7d8 fffff804`2c2c9c20 : 00000000`00000014 ffffffff`ffffff00 00000000`00000000 fffff804`2c622fe0 : nt!KiServiceLinkage
ffffc089`5b45f7e0 fffff804`2c1e7be0 : ffffde80`2769f180 00000000`00000080 ffff8684`d857d040 fffff804`2bd1d679 : nt!PopIssueActionRequest+0xe1c78
ffffc089`5b45f880 fffff804`2bc467a9 : 00000000`00000001 00000000`00000000 ffffffff`ffffffff fffff804`2c733680 : nt!PopPolicyWorkerAction+0x80
ffffc089`5b45f900 fffff804`2bd1d04f : ffff8684`00000001 ffff8684`d857d040 fffff804`2c622f40 ffff8684`00000000 : nt!PopPolicyWorkerThread+0xa9
ffffc089`5b45f940 fffff804`2bc478f5 : ffff8684`d857d040 ffffde80`273d0000 ffff8684`d857d040 004fe47f`bd9bbfff : nt!ExpWorkerThread+0x14f
ffffc089`5b45fb30 fffff804`2be19644 : ffffde80`273c1180 ffff8684`d857d040 fffff804`2bc478a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffc089`5b45fb80 00000000`00000000 : ffffc089`5b460000 ffffc089`5b459000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nt!PopTransitionSystemPowerStateEx+12e5c

IMAGE_VERSION: 10.0.22000.318

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 12e5c

FAILURE_BUCKET_ID: 0xc000021a_SmpInitializeKnownDlls_c0000428_BAD_DLL_difxapi.dll_nt!PopTransitionSystemPowerStateEx

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {299089e9-f138-4840-956f-7abf42a0d528}

Followup: MachineOwner
---------

 

[Sir_George]

Check the website information at the link provided below.

How to Fix the Clock Watchdog Timeout Error in Windows

Running into the Clock Watchdog Timeout Error in Windows? Here's how you can fix it once and for all.

www.makeuseof.com

 

[basco55]

Check the website information at the link provided below.

How to Fix the Clock Watchdog Timeout Error in Windows

Running into the Clock Watchdog Timeout Error in Windows? Here's how you can fix it once and for all.

www.makeuseof.com

I have followed all steps on the link and it did not helped.
I ended up formating both hard drives and installed all drivers one by one to see which one caused the problem and this also did not worked out.
After spending hours online to find the solution i found two posts which said it may be the issue with cd/dvd device sata port. Apparently some dvd readers dont like certain sata ports. So all i have done was switched dvd device to different sata port and this has solved the problem.