“System interrupts” at 15% CPU looks alarming, but here’s the reframe that makes it fixable: it’s not a program misbehaving — it’s a measurement. Task Manager lumps all CPU time spent handling hardware interrupts into this line. Something in your Lenovo — a driver, usually — is generating an interrupt storm, and the CPU is spending its cycles acknowledging hardware instead of running your software. The job isn’t to “stop System interrupts”; it’s to find which driver is shouting and make it stop.

The telltale companions: audio crackling, mouse micro-stutters, and DPC latency spikes — all classic interrupt-storm symptoms. If your whole laptop is generally slow rather than showing this specific signature, see how to speed up a slow Windows 11 laptop instead.

Why this happens

  • Buggy Wi-Fi/Bluetooth drivers: the number one cause — Intel wireless drivers in a bad state spam interrupts, especially during power transitions.
  • Storage driver issues: AHCI/NVMe driver problems generating excessive interrupts per I/O operation.
  • Audio driver DPC storms: Conexant/Realtek audio drivers with bad DPC behavior, often audible as crackling.
  • USB device misbehavior: a flaky USB device or dock generating constant connect/disconnect interrupts.
  • Lenovo power management conflicts: Vantage power drivers fighting Windows’ native power management over device states.
  • Failing hardware: a dying drive or malfunctioning embedded controller spamming the interrupt line.
  • Outdated BIOS: firmware-level interrupt routing bugs fixed in newer BIOS releases.

How to fix it

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

Fix 1: Identify the guilty driver with LatencyMon

Guessing wastes hours; measuring takes ten minutes.

  1. Download and run LatencyMon (free, from Resplendence) — let it run for 5–10 minutes while System interrupts is high.
  2. Check the Drivers tab sorted by DPC count — the top entries name the exact .sys files responsible.
  3. Common findings: ndis.sys (network stack — points to the Wi-Fi driver), storport.sys/stornvme.sys (storage driver), HDAudBus.sys (audio), or a Lenovo/vendor .sys file.
  4. Note the highest DPC execution times too — a driver with huge max latency is the prime suspect even with moderate counts.
  5. This single test usually names your fix: whatever driver tops the list is what you update, reconfigure, or replace in the steps below.

Fix 2: Update the Wi-Fi and Bluetooth drivers

The most common LatencyMon finding — fix it first.

  1. Go to Lenovo Support , enter your model, and install the latest Wi-Fi and Bluetooth drivers.
  2. If Lenovo’s are old, get Intel wireless drivers directly via Intel’s driver detection tool — Intel’s releases fix interrupt bugs faster than OEMs certify them.
  3. In Device Manager > Network adapters > your Wi-Fi adapter > Properties > Advanced, try disabling power-saving features like “Allow the computer to turn off this device” as a test — power-state transitions are where interrupt storms breed.
  4. Also update Bluetooth — the Wi-Fi/Bluetooth combo card shares interrupts, and Bluetooth’s driver is a frequent co-offender.
  5. Re-run LatencyMon after updating — ndis.sys should drop off the top of the list.

Fix 3: Update storage and chipset drivers

For storport.sys / stornvme.sys findings.

  1. Install the latest chipset driver package from Lenovo Support for your model.
  2. Update the Intel Rapid Storage Technology driver (or AMD equivalent) — the AHCI/NVMe driver’s interrupt behavior is exactly what you’re fixing.
  3. In Device Manager > IDE ATA/ATAPI controllers, verify the controller uses the Intel driver, not the generic Microsoft one.
  4. Check drive health while you’re here: wmic diskdrive get status — a failing drive generates interrupt storms as it retries.
  5. Re-test with LatencyMon; storage-driver fixes show up as dramatically lower ISR/DPC counts.

Fix 4: Fix audio driver DPC issues

For crackling audio accompanying the CPU usage.

  1. Update the audio driver from Lenovo Support (Conexant/Realtek/Synaptics audio depending on model).
  2. In Device Manager > Sound controllers, try disabling audio enhancements: device Properties > Enhancements tab > check “Disable all enhancements.”
  3. Test with different sample rates: Sound settings > device Properties > Advanced — set to 16-bit 44100 Hz as a baseline test.
  4. If the internal audio driver is the confirmed culprit and updates don’t help, disabling the internal audio device in Device Manager (using USB/Bluetooth audio instead) is a valid workaround.
  5. Re-run LatencyMon — audio DPC storms are unmistakable in the drivers list and satisfying to eliminate.

Fix 5: Isolate USB and dock interference

External devices are interrupt sources too.

  1. Disconnect all USB devices, docks, and hubs — run LatencyMon bare for 10 minutes.
  2. If System interrupts drops, reconnect devices one at a time, watching LatencyMon after each.
  3. Update the dock’s firmware and drivers if a dock is implicated — docks are notorious interrupt generators.
  4. In Device Manager > USB controllers, update the USB 3.x extensible host controller drivers from Lenovo.
  5. For a chronically bad USB port, stop using it — a damaged port generating connect/disconnect interrupts isn’t worth the port.

Fix 6: Calm Lenovo Vantage and power management

Lenovo’s own software can contribute to the storm.

  1. Update Lenovo Vantage to the latest version — old Vantage device-polling loops are a known contributor.
  2. In Vantage, avoid aggressive custom power/thermal profiles; test with Windows’ native Balanced plan instead.
  3. In services.msc, check Lenovo services (ImController and friends) — set non-essential ones to Manual as a test.
  4. Update the BIOS from Lenovo Support if the changelog mentions interrupt, DPC, or stability fixes — flash on AC power, battery charged.
  5. After BIOS updates, load defaults — carried-over ACPI settings cause their own interrupt weirdness. Microsoft documents power management officially at the Windows support hub .

Fix 7: When it’s hardware

If every driver is current and the storm continues.

  1. LatencyMon pointing at hal.dll/ntoskrnl.exe with no vendor driver on top suggests hardware-level interrupt generation.
  2. Run Lenovo’s built-in diagnostics (Vantage > Device > Run diagnostics, or F10 at boot) — mainboard and embedded-controller faults show here.
  3. Test with the battery removed (if removable) or on AC only — failing batteries and charging circuits generate interrupts.
  4. A persistent storm with clean drivers and diagnostics is a service-center problem — bring your LatencyMon screenshots; they turn a vague complaint into a specific fault.
  5. Back up your data before any service trip — board-level work risks the drive.

Closing

System interrupts high CPU is a driver-hunting exercise, and LatencyMon is the hunting dog: ten minutes of measurement names the .sys file, and from there it’s just updating the right driver. (If Task Manager shows MsMpEng.exe rather than interrupts as the hog, that’s a different hunt — see taming Antimalware Service Executable .) On Lenovos it’s the Wi-Fi driver more often than not — update it, watch the interrupts collapse, and enjoy the silence (and the battery life that comes back with it).

Frequently asked questions

What are 'System interrupts' in Task Manager?
System interrupts isn’t a real process — it’s Task Manager’s label for CPU time spent servicing hardware interrupts and deferred procedure calls (DPCs). When a driver mishandles its hardware, the CPU spends excessive time in interrupt handling, and Task Manager buckets that time under this pseudo-process. High ‘System interrupts’ CPU therefore always means a driver or hardware problem, never a runaway application.
Is System interrupts high CPU dangerous?
Not directly harmful, but it’s a symptom of something wrong: a driver stuck in an interrupt storm, failing hardware spamming interrupts, or a misconfigured device. Sustained high interrupt CPU causes stuttering, audio crackles, and battery drain even though temperatures look normal. The underlying cause deserves fixing — interrupt storms don’t resolve themselves and occasionally precede hardware failure.
Why is this common on Lenovo laptops?
Lenovo’s hardware mix — Intel Wi-Fi/Bluetooth combos, Conexant/Realtek audio, Synaptics touchpads, and Lenovo’s own power management drivers — includes several historically interrupt-happy components. Outdated Wi-Fi drivers are the single most common trigger across all brands. Lenovo Vantage’s device polling can add to it. The good news: it’s almost always fixable with driver updates, no hardware replacement needed.
Can I just end the System interrupts process?
No — and Task Manager won’t let you. There’s no process to kill; it’s accounting for kernel interrupt time. The only fix is addressing the source: the driver or device generating the interrupts. Tools like LatencyMon identify the specific driver file (often ndis.sys for network, storport.sys for storage, or a vendor driver), and updating or reconfiguring that driver resolves it.