This stop code (0x00000101) means an expected clock interrupt never arrived from a secondary processor core within the time allowed: one core of the CPU stopped answering while the others kept working. The PC often freezes solid for a while before the blue screen appears. In practice this is an overclocking and firmware error first, a cooling error second, and a dying processor a distant third.
DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Kernel scheduler fixes arrive through Windows Update.If the error persists at stock settings on a current BIOS with healthy temperatures and passing memory, test with one RAM stick and one core-heavy workload at a time. A processor that still drops interrupts in that state, ideally confirmed by swapping in a known-good CPU or board, is failing hardware. That outcome is rare; exhaust the firmware and settings steps first.
Does CLOCK_WATCHDOG_TIMEOUT mean my CPU is broken? Almost never, on its own. Unstable overclocks, aging BIOS microcode, and overheating cause the overwhelming majority. A CPU becomes the suspect only after defaults, current firmware, good cooling, and clean memory tests all fail to stop it.
Why does the PC freeze before the blue screen shows? Windows waits for the missing core, hoping it recovers, before declaring the watchdog timeout. During that wait the system is partially hung, mouse frozen, sound looping, because a core that other work depends on has stopped. The freeze is a symptom of the same stall the blue screen then reports.