Windows 10: WATCHDOG CLOCK TIMEOUT/ Not Able to Boot Into WIndows

Hi, I have an Acer Aspire V3-772G. Here is the link for the specs: https://www.acer.com/ac/en/US/content/support-product/4732?b=1&pn=NX.M74AA.011.


One day all the sudden it froze, so I just held the power button down to restart it. After doing so I was not able to get past the lock screen and it would just freeze. It got to the point where it would not boot past the Acer logo and the spinning circle. I tried everything from the startup menu to fix it, including safe mode and startup repair. I would also get a BSOD with the error WATCHDOG CLOCK TIMEOUT. I have now backed up all the data from the HDD so I could make a clean install of Windows 10 using a USB stick. I am able to get past the installation of windows, but once it finishes, it gets stuck on a blue screen that says "just a moment" and freezes. I have also still gotten the same BSOD. I have also tried booting into safe mode and the problem still persists including the BSOD . The furthest I have gotten is to what seems a setup screen and says "Hi, Im Cortana...", and then froze. Once I also got to a lockscreen, with a username "defaultuser 1", tried to unlock it since it had a password for some reason and froze as well.


I have not messed with the BIOS so I dont think its overclocked and I am currently on BIOS V1.15 The lastest available. I also tried disconnecting the touchpad, CD disk tray and the WLAN card. The screen also seems to glitch including boxes popping up randomly.


I have also provided the Memory Dump. I have a minidump file as well but I am not able to open it.



Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [D:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS Personal19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff802`5e000000 PsLoadedModuleList = 0xfffff802`5ec2a250Debug session time: Sat Dec 7 02:56:06.322 2019 UTC - 4:00System Uptime: 0 days 0:00:31.007Loading Kernel Symbols.......................................................................................................................................................................Loading User SymbolsLoading unloaded module list........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff802`5e3dda20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`64278c90=00000000000001010: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************CLOCK_WATCHDOG_TIMEOUT 101An expected clock interrupt was not received on a secondary processor in anMP system within the allocated interval. This indicates that the specifiedprocessor is hung and not processing interrupts.Arguments:Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.Arg2: 0000000000000000, 0.Arg3: ffffda01f9580180, The PRCB address of the hung processor.Arg4: 0000000000000006, The index of the hung processor.Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 11 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-TB3KTS0 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 19 Key : Analysis.Memory.CommitPeak.Mb Value: 61 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 101BUGCHECK_P1: 18BUGCHECK_P2: 0BUGCHECK_P3: ffffda01f9580180BUGCHECK_P4: 6FAULTING_PROCESSOR: 6PROCESS_NAME: dwm.exeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1STACK_TEXT: fffff802`64278c88 fffff802`5e459362 : 00000000`00000101 00000000`00000018 00000000`00000000 ffffda01`f9580180 : nt!KeBugCheckExfffff802`64278c90 fffff802`5e2cef5d : 00000000`00000000 fffff802`5ad01180 00000000`00000246 00000000`000007c0 : nt!KeAccumulateTicks+0x18bee2fffff802`64278cf0 fffff802`5e2c8651 : 00000000`00000600 00000000`0000049e fffff802`5ad01180 00000000`00000001 : nt!KiUpdateRunTime+0x5dfffff802`64278d40 fffff802`5e2ca4eb : 00000000`00000000 ffffc48f`aba29600 fffff802`5ec31900 00000000`00000000 : nt!KiUpdateTime+0x4a1fffff802`64278e80 fffff802`5e2c7722 : ffffc48f`aba295a0 ffffc48f`aba29620 ffffc48f`aba29620 00000000`00000000 : nt!KeClockInterruptNotify+0x2bbfffff802`64278f30 fffff802`5e208705 : 00000000`12923165 fffff802`5ecf3820 fffff802`5ecf38d0 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2fffff802`64278f60 fffff802`5e3df4ca : ffffc48f`aba29620 fffff802`5ecf3820 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5fffff802`64278fb0 fffff802`5e3dfa37 : 00000000`2d69b37c fffff802`5ad04088 ffffc48f`aba296d1 ffe247d5`d14bb804 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfaffffc48f`aba295a0 fffff802`5e2c5130 : 00000000`00000000 ffffffff`ffffffff 00000000`00000002 ffffa085`d8616460 : nt!KiInterruptDispatchNoLockNoEtw+0x37ffffc48f`aba29730 fffff802`5e2c1482 : 00000000`00000001 00000000`00000000 ffffc98b`dfa18b00 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x2a0ffffc48f`aba297c0 fffff802`5e283b5e : fffff000`06fb5e30 80000002`53ca1821 00000000`00000000 00000000`00000004 : nt!MiFlushTbList+0x82ffffc48f`aba297f0 fffff802`5e285774 : ffffc98b`dd6e5b00 ffffc98b`dd6e5b00 ffffc48f`aba29a39 00000000`00001000 : nt!MmSetAddressRangeModifiedEx+0x2aeffffc48f`aba29950 fffff802`5e280c64 : ffffc98b`df88fcd0 00000000`00000000 00000000`00000001 ffffc48f`aba29ae8 : nt!CcFlushCachePriv+0x374ffffc48f`aba29a90 fffff802`5e233f25 : ffffc98b`e1d39850 fffff802`5e280a00 ffffc98b`dd6a9901 ffffc98b`00000000 : nt!CcWriteBehindInternal+0x1f4ffffc48f`aba29b70 fffff802`5e346715 : ffffc98b`dfa3f4c0 00000000`00000080 ffffc98b`dd6b7040 000fa425`bd9bbfff : nt!ExpWorkerThread+0x105ffffc48f`aba29c10 fffff802`5e3e5078 : ffffda01`f93e9180 ffffc98b`dfa3f4c0 fffff802`5e3466c0 00000000`00000000 : nt!PspSystemThreadStartup+0x55ffffc48f`aba29c60 00000000`00000000 : ffffc48f`aba2a000 ffffc48f`aba24000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: nt!KeAccumulateTicks+18bee2MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 18bee2FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicksOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64

:)

 

Clock Watchdog timeout after clean windows 10 install

Hi Robert,

We would like to ask a few questions in order for us to properly address your issue with the Clock Watchdog timeout.

• What is the make and model of your computer?
• Have tried updating all the drivers of your computer?

For more information regarding Clock Watchdog, check this article.

Looking forward to your response.

 

Clock watchdog timeout

No this time I got the “Clock Watchdog Timeout” again. Are you thinking that my processor is failing? When installing win 10 my hardrive was refered to volumes only and had no attached drive letters. Must do another hard boot.

ps thanks for the help

 

clock watchdog timeout

You may give that a try. But before you consider that, you may also try performing another troubleshooting steps provided by ZigZag3143
in this article.

Feel free to let us know if the troubleshooting steps makes any difference.