Multiple Blue Screens

Question

Hello. I just build a new pc few weeks ago. Did every Windows 10 update, software updates, etc, yet, i have multiple BSOD's, while playing some games, and message on screen always is ''CLOCK_WATCHDOG_TIMEOUT''. So far in 2 weeks time, over 10-15 blue screens, always with ''Clock Watchdog Timeout'' error.

I'm not using any kind of cpu/gpu overclocks, except Intel's native turbo mode on Balanced/High Performance, and XMP to get my ram to correct speeds.

Tried various stress tests/benchmarks, no crashes at all. Intel's processor diagnostic tool, same. Everything passed without any error(s). Memory test, both Window's and Memtest, no errors. My CPU is an Intel 11900F, brand new, not even 2 months old.

WinDbg:

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

* *

* Bugcheck Analysis *

* *

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

CLOCK_WATCHDOG_TIMEOUT (101)

An expected clock interrupt was not received on a secondary processor in an

MP system within the allocated interval. This indicates that the specified

processor is hung and not processing interrupts.

Arguments:

Arg1: 000000000000000c, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: ffffb1016c1c1180, The PRCB address of the hung processor.

Arg4: 0000000000000007, The index of the hung processor.

Debugging Details:

------------------

KEY_VALUES_STRING: 1

*Key  : Analysis.CPU.mSec* 

*Value: 1514* 

*Key  : Analysis.DebugAnalysisProvider.CPP* 

*Value: Create: 8007007e on DESKTOP-5BQA5S0* 

*Key  : Analysis.DebugData* 

*Value: CreateObject* 

*Key  : Analysis.DebugModel* 

*Value: CreateObject* 

*Key  : Analysis.Elapsed.mSec* 

*Value: 1470* 

*Key  : Analysis.Init.CPU.mSec* 

*Value: 890* 

*Key  : Analysis.Init.Elapsed.mSec* 

*Value: 29024* 

*Key  : Analysis.Memory.CommitPeak.Mb* 

*Value: 132* 

*Key  : Analysis.System* 

*Value: CreateObject* 

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump

BUGCHECK_CODE: 101

BUGCHECK_P1: c

BUGCHECK_P2: 0

BUGCHECK_P3: ffffb1016c1c1180

BUGCHECK_P4: 7

FAULTING_PROCESSOR: 7

FAULTING_THREAD: ffffd6885a4870c0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffe80408b7efa0 fffff8073fc13110 : ffffb10100000009 0000000000000200 0000000000000000 0000000000000000 : nt!KiSwapContext+0x76

ffffe80408b7f0e0 fffff8073fc1263f : 0000000000000002 0000000000000009 ffffe80408b7f2a0 0000000000000000 : nt!KiSwapThread+0x500

ffffe80408b7f190 fffff8073fc11ee3 : ffffe80400000000 fffff80700000000 0000000000000000 ffffd6885a487200 : nt!KiCommitThreadWait+0x14f

ffffe80408b7f230 fffff80740008291 : 0000000000000000 0000000000000000 0000000000000001 ffffd688548a5900 : nt!KeWaitForSingleObject+0x233

ffffe80408b7f320 fffff8074000831a : ffffd6885a4870c0 0000000000000000 0000000000000000 ffffd688548a59e0 : nt!ObWaitForSingleObject+0xb1

ffffe80408b7f380 fffff8073fe0caf5 : 0000000048580cc0 0000000000000000 0000000000000000 0000000000000000 : nt!NtWaitForSingleObject+0x6a

ffffe80408b7f3c0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25

STACK_COMMAND: .thread 0xffffd6885a4870c0 ; kb

SYMBOL_NAME: nt!KiSwapContext+76

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.2311

BUCKET_ID_FUNC_OFFSET: 76

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_nt!KiSwapContext

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {bc34b25d-64f9-4279-f3ff-b1c57dd37e2c}

Followup: MachineOwner

Tried Driver Verifier, and 3 times found a "HIDCLASS.Sys" driver violation in all of the 3 crashes. In past blue screens, was again same Clock Watchdog Timeout, but it was "FAULTING_PROCESSOR: 6 or 5". Now it's 7. Is that mean somehow, CPU it's faulty? Can anyone please take a look at my minidumps and provide any kind of help? Here's my OD link with compressed folder of 3 minidumps, main dump, and msinfo32/dxdiag files.

Thanks in advance.

Minidumps

Answer 1

Hi MindDoser1,

Thanks for sharing the minidump files.

The minidump files indicate HIDCLASS.SYS as a cause of the crash which is Human Interface Devices like keyboards, mice and game controllers.

May I know which devices are connected to the computer?

To troubleshoot this issue, kindly disconnect all the external devices (if possible use another mouse and keyboard) and try the following steps:

1-Go to Settings > Update and Security > Check for updates > Install all pending updates.

2-Right-click on Start > Expand Universal Serial Bus Controller > Right click on the USB Root Hub and click on Uninstall > Check the box 'Delete the driver software for this device' > Uninstall > Restart your computer and see if your computer would be stable or not.

3-Use System File Checker:

https://support.microsoft.com/en-us/windows/usi...

Please let me know if you need further assistance and keep me posted.

Regards,

Answer 2

Hi and thanks for reaching out. Weird.I just downloaded it to check, and it contains everything inside compressed folder.

Re uploaded to google drive this time:

https://drive.google.com/file/d/1zj5PnGeyJrEiUgvoM_4an3MY8zdxSCJb/view?usp=share_link

Answer 3

Hi MindDoser1,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

I am afraid that there is no minidump available in the provided link. Would you please double check it?

Thank you

Answer 4

You update bios & drivers from the mobo makers support site, and the vid card maker if a seperate card