Windows 11’s Task Manager shows System Interrupts eating 10, 20, or 30 percent of your CPU, and like a ghost it cannot be ended, uninstalled, or reasoned with. This phantom reading is the CPU time spent answering hardware interrupts — and when it is high, some device is shouting at your processor far too often.

Windows 11 adds its own wrinkles: the 24H2 upgrade’s driver swaps, modern USB4/Thunderbolt controllers, and Wi-Fi 6E drivers all appear in recent interrupt-storm reports. The good news is that the diagnostic method has not changed — interrupts are countable, drivers are nameable, and the evidence leads you straight to the fix. This guide is the complete Windows 11 diagnostic path. For brand-specific angles, see System Interrupts on Acer laptops and on Lenovo systems ; for Windows 10, System Interrupts on Windows 10 .

Why this happens

  • Driver regressions from the 24H2 upgrade: Feature-update driver swaps installing versions with interrupt-handling bugs.

  • USB4/Thunderbolt controller issues: Modern high-speed controllers with firmware bugs generating interrupt storms.

  • Wi-Fi 6/6E driver bugs: New wireless drivers with broken interrupt moderation flooding the CPU during traffic.

  • Faulty USB peripherals: The eternal champion: one bad device or cable dominating interrupt traffic.

  • Storage errors: NVMe/SATA error handling generating constant interrupt load on struggling drives.

  • Audio driver DPC latency: Bad audio drivers deferring work that surfaces near System Interrupts with crackling audio.

  • BIOS interrupt routing bugs: Firmware misassigning interrupts, exposed or introduced by OS upgrades.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Run the USB isolation test

Five minutes, no tools, catches the most common external cause.

  1. Disconnect ALL USB devices including hubs, docks, and dongles; watch System Interrupts for 5 minutes.
  2. If it drops, reconnect one device at a time with 2-minute observation windows.
  3. Pay special attention to Thunderbolt/USB4 docks — their firmware updates (from the dock vendor) fix interrupt bugs regularly.
  4. Test suspect devices on another PC to separate device faults from port faults.
  5. Replace the guilty device or cable; update dock firmware where applicable.

Fix 2: Name the driver with LatencyMon

For internal causes, evidence beats intuition. Ten minutes of monitoring produces a ranked list of suspects that no amount of forum-searching can match.

  1. Run LatencyMon elevated for 10 minutes during the high-interrupt period.
  2. Sort Drivers by DPC count and ISR count; record the top offenders’ .sys names.
  3. On Windows 11 24H2, watch for network (Wi-Fi 6E vendor drivers), USB4 (thunderbolt-related .sys), and audio drivers.
  4. For precision work, capture with Windows Performance Recorder and analyze DPC/ISR by module in Windows Performance Analyzer.
  5. The named driver is your target for the next fix.

Fix 3: Fix the named driver

Update, roll back, or reconfigure — guided by timing.

  1. If the driver’s date matches the 24H2 upgrade: try Device Manager > Roll Back Driver first.
  2. Otherwise update: chip vendor sites (Intel, Realtek, MediaTek for Wi-Fi; dock vendors for Thunderbolt) usually beat Windows Update’s versions.
  3. For network adapters, toggle Interrupt Moderation in Advanced properties and test both states.
  4. For audio crackle + interrupts: update the audio driver or test with a lower sample rate in Sound settings.
  5. Verify each change with a fresh 10-minute LatencyMon run — keep what measurably helps.

Fix 4: Update BIOS and chipset drivers

Firmware is a first-class suspect on Windows 11, especially post-24H2. When the OS upgrade re-enumerates hardware against buggy firmware tables, interrupt routing is one of the first things to go wrong — and a BIOS update is often the only fix that reaches that layer.

  1. Check BIOS version (msinfo32) vs the latest on your laptop maker’s support site; read changelogs for interrupt/stability mentions.
  2. Install the newest chipset driver package as well — it coordinates OS-firmware interrupt handling.
  3. Flash on AC power, uninterrupted; load optimized defaults afterward.
  4. If ACPI.sys topped LatencyMon, this fix is your highest-probability move.
  5. Re-measure; firmware interrupt-routing fixes are usually immediate and dramatic.

Fix 5: Audit Thunderbolt/USB4 and display connections

Windows 11’s modern connectivity has modern failure modes.

  1. Update Thunderbolt/USB4 controller drivers and dock firmware from the laptop and dock vendors.
  2. Test with the dock disconnected entirely for a day — docks are disproportionate interrupt-storm sources.
  3. Try different cables (certified Thunderbolt cables matter) and ports.
  4. In Device Manager, check the Thunderbolt controller for warning icons after the 24H2 upgrade.
  5. Disable PCI Express Link State Power Management (Power Options > Advanced) as a test — aggressive link states trigger storms on some controllers.

Fix 6: Check storage and memory health

Hardware error interrupts are the serious underlying cause to rule out.

  1. CrystalDiskInfo for NVMe/SATA health; reallocated sectors or warnings mean error-interrupt load.
  2. Windows Memory Diagnostic extended test for RAM faults.
  3. If disk health is poor, back up immediately — then replace the drive.
  4. Run chkdsk /f to clear file-system-level contributors.
  5. Healthy hardware confirmed? The cause is software — continue.

Fix 7: Stabilize with updates and clean-boot

Catch-all for the stubborn remainder.

  1. Install all pending Windows updates — 24H2’s cumulative updates regularly include interrupt/driver fixes.
  2. Check the Update Catalog for newer driver versions than Windows Update offers.
  3. Clean-boot (msconfig, hide Microsoft services, disable rest) to isolate third-party drivers; re-enable in halves to find offenders.
  4. As a last resort, an in-place upgrade from the Windows 11 download page rebuilds the driver stack.
  5. Document your culprit and fix in the Windows support hub feedback channels — interrupt regressions need reports to get fixed.

Closing

System Interrupts on Windows 11 is the hardware interrupt ledger running red: find the shouting device with the USB test and LatencyMon, fix its driver or firmware, and check the hardware underneath. The 24H2 upgrade made driver swaps the prime suspect — but the method is timeless, and the phantom always has a name once you look. Keep LatencyMon installed after you fix it; the next time a driver update misbehaves, you will name the culprit in minutes instead of suffering for weeks.

Frequently asked questions

What does System Interrupts high CPU mean on Windows 11?
It means your CPU is spending a large share of its time servicing hardware interrupts — the signals devices use to request attention. On Windows 11, healthy idle systems show under 2%; sustained readings above 10% indicate a device or driver generating excessive interrupt traffic. Common Windows 11-specific triggers include drivers replaced during the 24H2 upgrade, USB4/Thunderbolt controller bugs, and Wi-Fi 6E drivers with interrupt-moderation issues. The process is a symptom reporter, not a cause.
How do I find which device is causing high System Interrupts?
Two tools: the USB unplug test (disconnect all USB devices; if interrupts drop, reconnect one by one) and LatencyMon (run elevated 10 minutes, sort Drivers by DPC/ISR count to name the offending .sys file). For deeper analysis, Windows Performance Recorder + Windows Performance Analyzer (from the Windows ADK) shows per-driver ISR/DPC timing. Between the unplug test and LatencyMon, you will identify the culprit in the vast majority of cases without needing the heavier WPA workflow.
Can Windows 11 24H2 cause System Interrupts spikes?
Yes — feature updates are a known trigger. The 24H2 upgrade re-enumerates hardware and replaces drivers, which can install versions with interrupt-handling regressions or misconfigure interrupt affinity on some platforms. If spikes began right after the 24H2 upgrade, prioritize: rolling back recently-changed drivers in Device Manager, updating the BIOS (firmware interrupt routing), and checking Windows Update for the cumulative fixes that typically follow a feature release within weeks.
Is high System Interrupts CPU harmful to my laptop?
Not directly damaging — the CPU is designed to handle interrupts — but the side effects matter: wasted battery, heat, fan noise, and stolen performance that makes everything else slower. More importantly, the underlying cause (failing drive, bad RAM, buggy driver) may be genuinely harmful if ignored. Treat the CPU reading as an early warning: investigate the cause for its own sake, and the interrupt CPU resolves as a byproduct.