System Interrupts sitting at 10%, 20%, 30% CPU in Task Manager looks alarming — and unlike most high-CPU culprits, you can’t just end the task or uninstall the program. That’s because System Interrupts isn’t a program at all: it’s Task Manager’s label for CPU time spent servicing hardware interrupts, the “hey, pay attention to me” signals from your devices. High readings mean some device or driver is shouting at your CPU nonstop. Your job is to find who’s shouting.

On Lenovo laptops this commonly traces to driver issues — chipset, power management, network, or storage drivers mismatched after a Windows update — though faulty USB devices and failing drives are also classic causes. This guide shows you how to trace the interrupt storm to its source using the right tools (Task Manager won’t cut it; we’ll use LatencyMon-style analysis and Device Manager methodically), then fix the driver or device responsible. For related Lenovo CPU issues, see Defender high CPU on Lenovo and high disk usage on startup on Lenovo .

Why this happens

  • Buggy or mismatched drivers: The #1 cause — a driver spamming interrupts after a Windows update.
  • Failing storage drive: A dying HDD/SSD retrying operations generates interrupt storms.
  • Misbehaving USB device: A faulty peripheral chattering on the USB bus.
  • Network adapter issues: Wi-Fi/Ethernet drivers with interrupt moderation misconfigured.
  • Lenovo power/chipset driver mismatch: Outdated Lenovo system drivers vs. the current OS.
  • BIOS/firmware bugs: Firmware-level interrupt routing problems.
  • Overheating-adjacent throttling: Less direct, but thermal issues can coincide with driver misbehavior.

How to fix it

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

Fix 1: Confirm and characterize the interrupt load

Measure properly first.

  1. Open Task Manager > Processes, show the CPU column, and watch System Interrupts for several minutes at idle — note the sustained percentage, ignoring brief spikes.
  2. Open Resource Monitor > CPU tab — interrupt time appears here too, and you can correlate it with disk/network activity.
  3. For real analysis, download LatencyMon (free) or use Windows Performance Recorder — these show Deferred Procedure Call (DPC) latency by driver, naming the actual offending driver file (e.g., storport.sys, ndis.sys, or a vendor driver).
  4. Note when it’s worst: at idle, during network activity, when a USB device is connected — patterns point at subsystems.
  5. Record your baseline number — you’ll compare against it after each fix.

Fix 2: Update Lenovo chipset and system drivers

The highest-probability fix.

  1. Go to Lenovo’s support site , enter your serial number or model, and download the current chipset, Intel Management Engine, and Lenovo System Interface drivers.
  2. Install them in order: chipset first, then Management Engine, then system interface drivers — rebooting between each.
  3. Update the BIOS/UEFI if a newer version is available — firmware updates frequently fix interrupt routing bugs.
  4. Avoid generic driver-updater tools — get Lenovo-matched drivers for Lenovo hardware.
  5. Re-measure System Interrupts at idle after the updates — chipset driver fixes resolve a large share of these cases.

Fix 3: Hunt the driver with LatencyMon evidence

Let the data name names.

  1. Run LatencyMon for 5–10 minutes during the high-interrupt period and check the Drivers tab sorted by DPC count — the top driver is your prime suspect.
  2. Common offenders: network drivers (ndis.sys with a vendor driver beneath), storage drivers (storport.sys), audio drivers, and USB controller drivers.
  3. Once identified, update that specific driver from the manufacturer’s site (Intel/Realtek for network, etc.) — or from Lenovo’s site for Lenovo-customized versions.
  4. If the newest driver is the problem (started after a driver update), roll it back: Device Manager > device > Properties > Driver > Roll Back Driver.
  5. Re-run LatencyMon after the change — the offending driver’s DPC count should collapse.

Fix 4: Isolate USB and peripheral causes

External devices are easy to test.

  1. Disconnect ALL USB devices (including docks, hubs, receivers, external drives) and re-measure — a dramatic drop implicates a peripheral.
  2. Reconnect one at a time, measuring after each — the one that spikes interrupts is faulty or driver-broken.
  3. For the culprit: try a different port, update its driver, or replace it — a $20 receiver causing 15% constant CPU is a bad trade.
  4. Check Device Manager > Universal Serial Bus controllers for warning icons — a controller itself can be the problem.
  5. Disable USB selective suspend as a test (Power Options > advanced settings) — aggressive USB power management sometimes triggers interrupt storms on resume.

Fix 5: Address network adapter interrupts

Network drivers are classic interrupt spammers.

  1. In Device Manager > Network adapters > your Wi-Fi adapter > Properties > Advanced tab, look for Interrupt Moderation — ensure it’s Enabled (it batches interrupts instead of firing per-packet).
  2. Update the Wi-Fi and Ethernet drivers from Intel/Realtek or Lenovo’s site — network driver bugs are among the most common DPC offenders.
  3. As a test, disable Wi-Fi and use Ethernet (or vice versa) — if interrupts drop, the disabled adapter’s driver is the cause.
  4. In the adapter’s Power Management tab, uncheck Allow the computer to turn off this device as a test — power-state flapping generates interrupts.
  5. If you use a USB Wi-Fi dongle, suspect it first — they’re disproportionately represented in interrupt-storm cases.

Fix 6: Check the storage subsystem

Drives in distress shout via interrupts.

  1. Run wmic diskdrive get status — anything but OK means drive trouble; back up immediately.
  2. Run chkdsk C: /scan for file-system errors that cause retry storms.
  3. Update storage drivers: Intel RST / chipset storage drivers from Lenovo’s site — storport.sys high in LatencyMon points here.
  4. Check SMART data with CrystalDiskInfo (free) — reallocated sectors or CRC errors confirm a dying drive generating interrupt retries.
  5. If the drive is failing, replace it — no driver update fixes hardware retry storms, and an SSD replacement also transforms overall performance.

Fix 7: Repair the OS and firmware layer

For storms with no identified driver.

  1. Run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow in an elevated terminal — corrupted kernel components can mishandle interrupts.
  2. Update the BIOS to the latest from Lenovo — note the changelog for interrupt, power, or stability fixes.
  3. Reset BIOS to optimized defaults after updating — misconfigured firmware settings (IOMMU, power states) occasionally cause interrupt issues.
  4. Test in Safe Mode — minimal drivers mean minimal interrupts; a calm Safe Mode confirms a third-party driver (then re-enable devices methodically to find it).
  5. If Safe Mode still shows high interrupts, suspect firmware or hardware — contact Lenovo support with your LatencyMon data in hand. Microsoft’s hardware troubleshooting guidance covers the built-in diagnostics.

Closing

System Interrupts high CPU is a symptom with a specific author — a driver or device flooding the CPU with interrupt requests. Don’t fight the Task Manager entry; interrogate it with LatencyMon, update the chipset and suspect drivers from Lenovo’s site, unplug the peripherals, and check the drive. The shouting always has a source, and sources can be silenced.

Frequently asked questions

What is the System Interrupts process?
System Interrupts is not a real process — it is how Task Manager displays CPU time spent handling hardware interrupts, the signals devices send the CPU when they need attention. Some interrupt activity is normal, but sustained high percentages mean a device is spamming the CPU with interrupt requests. The fix is never aimed at System Interrupts itself; it is aimed at whichever driver or hardware is generating the interrupt storm.
How much System Interrupts CPU is normal?
At idle, System Interrupts should sit well under 1 to 2 percent, occasionally spiking during heavy I/O. Sustained readings above 5 percent at idle, or double digits, indicate a problem worth investigating. Note that the percentage is relative to total CPU, so on an idle machine even small absolute interrupt loads look larger — judge by persistence and by whether the fans and responsiveness suggest real load.
Can System Interrupts indicate failing hardware?
Yes, sometimes. A failing drive retrying reads, a dying USB device chattering on the bus, or a malfunctioning network card can all generate interrupt storms. But software is the more common cause: buggy drivers, especially after updates, generate most interrupt storms. The diagnostic approach is drivers first, then peripherals, then internal hardware — replacing hardware before ruling out drivers wastes money.
Why is this common on Lenovo laptops specifically?
Lenovo’s broad model range and frequent driver updates mean driver-OS mismatches surface regularly, particularly with power management, Intel chipset drivers, and Lenovo’s own system interface drivers. Lenovo Vantage sometimes installs driver versions that lag or conflict. The troubleshooting is the same as any brand, but Lenovo users should get drivers from Lenovo’s support site by exact model, since generic drivers miss Lenovo-specific hardware quirks.