System Interrupts chewing 10%, 20%, 30% of your CPU is one of those problems that looks unfixable — you can’t end the “process,” there’s no app to uninstall, and generic advice just says “update drivers” and wishes you luck. But it’s very fixable once you know the playbook: in most cases it’s one USB device, one driver, or one power setting, and the fixes below find it in minutes rather than hours.

This is the quick-fix companion to the full diagnostic walkthrough. If you want the deep isolation methodology — Device Manager interrogation, LatencyMon ISR correlation, hardware health forensics — read troubleshooting System Interrupts high CPU . If you want it fixed now, work this list top to bottom; the first two fixes resolve the majority of cases.

Why this happens

  • Bad USB device: The single most common cause — dying drives, flaky hubs, damaged cables generating interrupt storms.
  • Outdated USB/network/storage driver: Inefficient interrupt handlers multiplying per-interrupt cost.
  • USB selective suspend conflicts: Power management fighting with devices that don’t suspend cleanly.
  • Failing hard drive/SSD: Retry loops on bad blocks presenting as interrupt load.
  • Network adapter issues: Faulty NIC hardware or drivers firing excessive interrupts.
  • Docking station problems: Dock firmware bugs or marginal connections multiplying interrupts.
  • BIOS/firmware bugs: Platform-level interrupt routing issues fixed by BIOS updates.
  • Overheating: Thermal management interrupts from components running too hot.

How to fix it

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

Fix 1: Unplug all USB devices (2-minute test)

Do this first — it resolves most cases immediately.

  1. Unplug everything USB: external drives, hubs, docks, printers, wireless mouse/keyboard dongles (use the laptop’s built-in keyboard/trackpad temporarily), phone cables, everything.
  2. Watch Task Manager’s System Interrupts for 60-90 seconds. Dropped to 1-2%? A USB device was the cause — continue to step 3. Unchanged? Leave everything unplugged and move to Fix 2 (you’ve still simplified the system).
  3. Plug devices back one at a time, waiting a full minute between each. When interrupts spike, you’ve found the offender.
  4. Fix the offender: try a different port and cable first; check for firmware updates from the device maker; flash drives and SD cards causing this are usually dying — copy their data off now.
  5. If a dock is the trigger, test with the laptop undocked for a full day before blaming the dock permanently — and check the dock maker’s site for firmware updates, which fix interrupt bugs regularly.

Fix 2: Update USB, chipset, and network drivers

When USB stripping didn’t fully resolve it.

  1. Open Device Manager > Universal Serial Bus controllers — right-click each USB Root Hub and Host Controller > Update driver > Search automatically. Then do the same under Network adapters for Wi-Fi and Ethernet.
  2. Better: get the validated drivers from your laptop maker’s support page — Dell , HP, Lenovo — especially the chipset driver package, which governs USB controllers and interrupt routing.
  3. Intel network users: the Driver & Support Assistant delivers the latest validated wireless drivers, a frequent interrupt-improver.
  4. Restart fully after driver updates (shutdown /r /t 0 — not a Fast Startup shutdown) and re-measure at idle for several minutes.
  5. If interrupts rose after a driver update, roll that specific driver back (Device Manager > device > Driver tab > Roll Back Driver) — newer isn’t always better for interrupt handling.

Fix 3: Disable USB selective suspend and tune power

Power management vs. interrupt handling is a classic conflict.

  1. Open Control Panel > Power Options > Change plan settings > Change advanced power settings > USB settings > USB selective suspend setting > set to Disabled for both battery and plugged-in.
  2. In Device Manager, for each USB Root Hub > Properties > Power Management tab, uncheck Allow the computer to turn off this device to save power — do this for hubs, not for the devices themselves.
  3. Set PCI Express > Link State Power Management to Off in the same advanced power settings — aggressive link power saving generates management interrupts on some platforms.
  4. Set Power mode to Best performance (Settings > System > Power & battery) as a test — full details in the power plan guide .
  5. Re-measure: if interrupts collapse, you’ve found a power-management trigger. You can re-enable settings selectively later, but many users just leave selective suspend off — its power savings are negligible on modern hardware.

Fix 4: Check the disk (the silent interrupt generator)

Storage retries are interrupt-heavy and invisible in Task Manager’s app list.

  1. Run CrystalDiskInfo (free) — Health Status must be Good. Any Caution/Bad, reallocated sectors, or interface CRC errors = the drive retrying, generating interrupts. Back up immediately.
  2. Open Task Manager > Performance > Disk during high interrupts: Average response time in the hundreds of milliseconds alongside interrupt load confirms storage involvement.
  3. Run chkdsk C: /scan from an elevated prompt to catch file-system issues forcing driver retries.
  4. Check for SSD firmware updates on your laptop maker’s support page — controller firmware bugs cause retry storms that present as interrupt CPU.
  5. If the drive is failing, replace it — this also explains any random freezing you’ve been experiencing alongside the interrupts.

Fix 5: Isolate internal devices quickly

For when external USB and drivers are innocent.

  1. In Device Manager, disable these one at a time with 60-second observation windows: Wi-Fi adapter, Bluetooth, audio device, webcam, fingerprint reader, SD host controller.
  2. Skip anything that would crash you: don’t disable the boot storage controller or your active display adapter.
  3. When interrupts drop after disabling something, update that device’s driver from the maker’s support page; if it’s non-essential (fingerprint reader, for instance), leaving it disabled is a valid permanent fix.
  4. Re-enable everything that tested innocent — don’t leave a trail of disabled devices.
  5. If nothing internal changes the number, the cause is likely the motherboard’s own controllers or firmware — proceed to Fix 6.

Fix 6: Update BIOS and check thermals

The platform-level fixes.

  1. Check BIOS version via msinfo32 against your maker’s support page; update if release notes mention stability, USB, or interrupt fixes — charger plugged in, don’t interrupt the flash.
  2. After updating, Load Optimized Defaults in BIOS — stale custom settings (ASPM tweaks, legacy USB modes) misroute interrupts.
  3. Monitor temperatures with HWiNFO: sustained high temps generate thermal-management interrupts; clean vents and confirm fans work.
  4. Check Event Viewer > Windows Logs > System for WHEA-Logger entries — hardware error reports that name failing components when software fixes have failed.
  5. Still high after all six fixes with healthy hardware? A clean install from the Windows 11 download page is the final software elimination — persistence past that means a motherboard-level fault for warranty service.

Closing

System Interrupts high CPU looks scary and fixes easy: unplug USB (Fix 1), update the controller drivers (Fix 2), calm the power management (Fix 3). Those three end the vast majority of cases in under half an hour. The deeper fixes exist for the stubborn remainder — and for the cases where the interrupts were trying to tell you a drive was dying, in which case catching it now just saved your data.

Frequently asked questions

Why can't I end the System Interrupts process?
Because it isn’t a process — it’s Task Manager’s display name for CPU time spent handling hardware interrupts. There’s nothing to end; the CPU is doing real work answering devices. High readings mean a hardware device is interrupting excessively or its driver handles interrupts slowly. The fix is finding the noisy device or the slow driver, not killing anything in Task Manager.
Will updating drivers fix System Interrupts high CPU?
Sometimes — specifically when the cause is a driver handling interrupts inefficiently rather than a device generating too many. Network, USB controller, and storage drivers are the usual candidates. But if the cause is a failing device (dying USB drive, bad dock, struggling hard disk), no driver update helps; you must remove or replace the hardware. Test by unplugging USB devices first — it’s faster than updating drivers.
How do I know which device is causing high System Interrupts?
Elimination: unplug all USB devices and watch Task Manager — if interrupts drop, reconnect one by one. If not, disable internal devices one at a time in Device Manager (network adapters, audio, Bluetooth, camera) with 60-second waits between. For precision, LatencyMon’s Drivers tab sorted by ISR count names the driver handling the most interrupts. Event Viewer’s System log often names failing hardware directly.
Is 5% System Interrupts CPU something to worry about?
Not really. Up to a few percent is normal background interrupt activity, and brief spikes during heavy disk or network use are expected. Worry when it’s sustained above 10 percent, when it never drops at idle, or when it appeared suddenly alongside another symptom (freezes, stuttering, a device misbehaving). Sudden onset is the key signal — it means something changed, and recent changes are diagnosable.