Repeated LiveKernelEvent WATCHDOG (0x1A8) – system freezes without BSOD, likely driver timeout

Question

Windows repeatedly logs LiveKernelEvent (WATCHDOG, 0x1A8) without triggering a BSOD.

The issue causes intermittent system hangs and severe UI stuttering.

Live kernel dumps are generated in \Windows\LiveKernelReports\WATCHDOG.

I am experiencing recurring LiveKernelEvent WATCHDOG (0x1A8) events on Windows 11, recorded via Windows Error Reporting, without any BSOD. These events generate kernel dumps in:

\Windows\LiveKernelReports\WATCHDOG

Symptoms are system-wide and intermittent, including:

• Severe UI stuttering and temporary system hangs
• Random audio dropouts, audio distortion, and audio device instability
• Wireless mouse stuttering and delayed input response
• Occasional display-related issues (stutter, brief freezes), especially under multi-monitor usage
• General system instability that accumulates over uptime

The issue appears to be kernel- or driver-level, not application-specific. It affects multiple subsystems simultaneously (graphics, audio, USB/input), suggesting a driver timeout, DPC/ISR latency issue, or power/PCIe management interaction.

Key observations:

• The issue persists across different monitors, including tests with an older 60 Hz Full HD display
• Occurs regardless of HDR being enabled or disabled
• Occurs with both single- and dual-monitor configurations
• Affects both wired and wireless peripherals (wireless mouse input stutter is especially noticeable)
• Audio dropouts occur even when switching between USB audio devices and onboard audio
• Issue is reproducible across different driver versions and after multiple Windows updates

System configuration (summary):

• Windows 11 build 26200.x
• Discrete GPU in use (iGPU disabled/enabled for testing, issue persists)
• High refresh rate monitor configuration used regularly
• All firmware and chipset drivers updated from vendor sources

Troubleshooting already performed:

• Clean driver reinstallation (graphics, audio, chipset)
• Testing with different monitor and refresh rates
• Disabling/enabling iGPU in BIOS
• Power management and performance plan adjustments
• Peripheral isolation tests (different mouse, different USB ports)
• Issue persists after reboots and is not tied to a specific application

Conclusion:

This appears to be a Windows kernel / driver compatibility or scheduling issue rather than faulty hardware or a single third-party application. The recurring WATCHDOG LiveKernelEvent strongly suggests a driver timeout or kernel-level hang affecting multiple subsystems.

Kernel dumps are available and can be analyzed to identify the specific driver or subsystem responsible.

Hardware:

• OS: Windows 11 Pro, version 10.0.26200 (Build 26200)
• CPU: Intel Core Ultra 7 265K (20 cores, 3.90 GHz)
• RAM: 64 GB
• Motherboard: ASUS TUF GAMING Z890-PLUS WIFI
• BIOS: AMI 2401 (12/09/2025), UEFI
• Platform security: Secure Boot, VBS, HVCI enabled
• System type: x64 desktop PC
• Multi-monitor setup, high refresh rate displays in use

Answer 1

Hi Jakub Beháň,

The recurring LiveKernelEvent (WATCHDOG, 0x1A8) without a BSOD typically points to a driver timeout or deferred procedure call (DPC) latency issue affecting multiple subsystems, which matches the stuttering and hangs you’re seeing across graphics, audio, and input devices. Since you’ve already reinstalled drivers and tested hardware isolation, the next step is to analyze the kernel dumps in \Windows\LiveKernelReports\WATCHDOG using WinDbg or the Windows Performance Toolkit. These tools can help identify which driver or subsystem is failing to respond in time.

It’s also worth checking whether PCIe power management or Advanced Power Settings are throttling device responsiveness, disabling “Link State Power Management” and setting the system to High Performance can sometimes reduce WATCHDOG events. Updating to the very latest GPU driver directly from the vendor (rather than Windows Update) is also recommended, as multi‑monitor high refresh rate setups are particularly sensitive to driver scheduling. If the dumps confirm a specific driver, replacing or rolling back that driver version is the most reliable fix.

I hope this guidance helps you move closer to isolating the root cause and stabilizing your system. If you find this answer helpful, please hit “Accept Answer” so I know your concern is resolved.

Jason.