CLOCK_WATCHDOG_TIMEOUT (stop code 0x00000101) means a CPU core hung — it stopped answering the other cores, and Windows crashed rather than run on a corrupted scheduler. On Asus laptops, especially ROG and TUF gaming models, the story is usually thermals under load, an enthusiastic undervolt, or firmware that needs updating. This guide is tuned for Asus hardware and software.

For the same error on Acer machines, see our Acer-focused guide — the error is identical but the vendor tools differ.

Why this happens

  • CPU overheating under load. Gaming and rendering push Asus laptops to thermal limits.
  • Unstable undervolt. The undervolting community loves Asus laptops — and unstable undervolts cause exactly this.
  • Aggressive Armoury Crate profiles. Manual performance modes can destabilize the CPU.
  • Outdated BIOS. Asus BIOS updates frequently fix CPU stability and microcode issues.
  • Driver deadlock. A driver hanging a core triggers the watchdog.
  • Failing CPU silicon. Degradation over time, especially on heavily-used machines.
  • Bad RAM. Memory errors can present as a hung core.

How to fix it

Work through these in order — verify stability after each.

Fix 1: Check temperatures during the crashing workload

Reproduce the crash conditions and watch the heat.

  1. Install HWiNFO and enable its sensor logging.
  2. Run the workload that crashes (game, render, stress test) for 15-20 minutes.
  3. Watch CPU package temperature: sustained 95°C+ is where cores start hanging on many Asus models.
  4. Check the fan behavior in Armoury Crate — make sure the profile isn’t stuck on Silent with fans barely spinning.
  5. Elevate the laptop, clear the vents with compressed air, and retest.
  6. If temperatures drop and crashes stop, cooling was the cause. A cooling pad helps for sustained gaming sessions.

Fix 2: Reset all undervolts and tuning to stock

The undervolt is guilty until proven innocent.

  1. Open ThrottleStop, Intel XTU, or whatever tuning tool you use, and reset every value to default. Better: close it and prevent it from starting with Windows while testing.
  2. In Armoury Crate, switch to the Balanced or Windows operating mode — avoid Manual mode during diagnosis.
  3. Enter BIOS (F2 or Del) and load optimized defaults (F9, then F10).
  4. Disable XMP/DOCP memory profiles for testing.
  5. Use the laptop for a few days at full stock, including the previously-crashing workload.
  6. If crashes stop, your tuning was unstable. Re-tune conservatively (smaller undervolt steps, longer stress tests) or stay at stock.

Fix 3: Update the Asus BIOS and drivers

Firmware is a frequent fix for core hangs.

  1. Check your BIOS version: Win + R > msinfo32 > BIOS Version/Date.
  2. Look up your exact model on the Asus support site and download the latest BIOS.
  3. Install with the charger connected — never interrupt a BIOS update.
  4. Also install the latest chipset driver from the same page.
  5. After updating, load BIOS defaults again and retest.
  6. For AMD-based Asus laptops, also check AMD’s driver page for chipset updates; for Intel, Intel’s assistant . Prefer Asus-validated versions when close.

Fix 4: Update Armoury Crate and system drivers

Keep Asus’s own software current.

  1. Open the Microsoft Store > Library and update Armoury Crate, MyAsus, and related Asus apps.
  2. In Device Manager, update Processors, System devices, display, network, and storage drivers.
  3. If a specific driver update coincided with the crashes, roll it back instead.
  4. Uninstall any recently added peripheral software (RGB tools, game overlays) and test without it.
  5. Reinstall Asus System Control Interface from the support site if Armoury Crate misbehaves — it’s the driver underneath the app.
  6. Retest the crashing workload for several sessions before concluding.

Fix 5: Test the RAM

Memory faults can masquerade as hung cores.

  1. Press Win + R, type mdsched.exe, and choose Restart now and check for problems.
  2. Check Event Viewer > Windows Logs > System for MemoryDiagnostics-Results.
  3. Run MemTest86 overnight from a bootable USB for a definitive result.
  4. Replace faulty modules with the correct spec for your model.
  5. If your ROG has two slots, test sticks individually to isolate the bad one.
  6. Clean RAM results move suspicion firmly to the CPU/motherboard — continue to Fix 6.

Fix 6: Analyze WHEA logs for the failing core

Let the hardware error records name the culprit.

  1. Open Event Viewer > Windows Logs > System and filter for WHEA-Logger.
  2. Open the processor-error entries and check the Details tab for the APIC ID — the specific core.
  3. If the same core appears in every crash, that core is likely degrading.
  4. As a workaround, some users disable the faulty core affinity for heavy apps via Task Manager (Details > Set affinity) — this is a band-aid, not a fix.
  5. Run Asus’s built-in diagnostics (MyAsus > System Diagnostics) and save the results.
  6. Consistent single-core failures on stock settings with good thermals = CPU degradation. Our machine-check guide covers the closely related hardware fault path.

Fix 7: Repair system files and consider service

Final software sweep before the service decision.

  1. Open an elevated terminal and run: DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow
  2. Restart and retest.
  3. If crashes persist with good temps, stock settings, current BIOS, clean RAM, and repaired system files, the CPU or motherboard is failing.
  4. Back up everything — degrading silicon doesn’t get better.
  5. If under warranty, contact Asus support with your temperature logs, MemTest86 results, and WHEA entries. Documented evidence dramatically speeds up RMA approval.
  6. Microsoft’s hardware-error documentation on support.microsoft.com is useful background if support asks for specific logs.

Closing

On an Asus laptop, CLOCK_WATCHDOG_TIMEOUT is usually the price of pushing hardware hard — heat, an ambitious undervolt, or stale firmware. Reset to stock, cool it properly, update the BIOS, and most cases resolve without spending anything. The WHEA logs are your truth-teller: when they keep naming the same core despite perfect conditions, believe them and get the machine serviced before the degradation spreads.

Frequently asked questions

What does CLOCK_WATCHDOG_TIMEOUT mean?
Stop code 0x00000101: a CPU core stopped responding to interrupts from another core. The core hung — typically from overheating, unstable undervolting/overclocking, a driver deadlock, or degrading silicon.
My Asus ROG crashes with this while gaming. Is that expected?
It’s common but not normal. Gaming pushes thermals and power delivery hardest, so marginal cooling or an aggressive manual undervolt shows up there first. Check temperatures and reset tuning to stock before anything else.
Can Armoury Crate cause this error?
Indirectly — its performance profiles control power limits and fan curves. A stuck profile can let the CPU overheat, or an aggressive manual mode can destabilize it. Try the Balanced profile while diagnosing.
How do I know if my CPU is actually dying?
If temperatures are good, everything runs at stock, drivers and BIOS are current, RAM tests clean, and one specific core still hangs (check WHEA-Logger), the CPU is likely degrading. That’s a warranty/service situation.