When System Interrupts shows a high CPU percentage in Task Manager, a hardware device or its driver is almost always interrupting the processor too often or for too long. Normal readings sit near zero. A reading that stays above roughly 20% points to a misbehaving driver, most often for the network adapter, audio or USB. You find it by isolating devices one at a time, then updating or rolling back the driver involved. Every step below is a change you can reverse.
The fix is rarely a mystery once you stop guessing. The trouble is that System Interrupts is not a program you can end, so most advice online jumps straight to random tweaks. Measure first, change one thing, and keep a way back. That is also how Tempered works: it shows live CPU, RAM, GPU, disk and uptime readings, explains them in plain language, and applies nothing without your approval, with a one-click Undo for every change.
TL;DR
- System Interrupts is not a real process. It is Task Manager's label for CPU time spent answering hardware signals.
- Brief rises up to about 10% are normal. Usage that stays above about 20% points to a driver or device problem.
- Network adapter drivers are the most common cause, followed by audio drivers, USB controllers and BIOS power states.
- Disable devices one at a time in Device Manager to find the culprit, then update or roll back that driver.
- If drivers are ruled out, suspect failing hardware such as a drive or power supply.
Table of Contents
- What System Interrupts actually is
- How much System Interrupts CPU usage is too much
- Signs a driver is the cause
- Step-by-step: find and fix the cause
- When a Windows update is the trigger
- Where Tempered fits in
- Perspective
- Try it on your own PC
- If it still won't go away
- Quick checklist before you start
- FAQ
- Sources
What System Interrupts actually is
System Interrupts is an official part of Windows, but it is not a true process. It is a placeholder that adds up the CPU time used by every hardware interrupt. An interrupt is a signal from a device, such as a keyboard press, a network packet arriving or a disk finishing a read, that tells the processor to pause what it is doing and deal with the device.
Here is what happens inside Windows. According to Microsoft's CPU Analysis documentation, the system suspends the running thread and runs an interrupt service routine (ISR), a short piece of driver code. ISRs must finish quickly, so they often hand the longer work to a deferred procedure call (DPC), which takes priority over all normal threads.

That priority is why it matters to you. While a processor core is running ISRs and DPCs, no regular threads can run on it. Heavy interrupt activity therefore shows up as CPU usage and can starve things that depend on steady timing, such as audio and video playback.
Microsoft engineers have described these routines as the silent killers of system performance. They run at the highest priority, the operating system cannot preempt them, and when they run too often or too long you get audio glitches, mouse freezes and frozen windows.
How much System Interrupts CPU usage is too much

A healthy PC at idle shows System Interrupts at or near 0%, with short bumps when you move the mouse, copy files or stream video. How-To Geek puts normal at up to about 10% in brief bursts, and says usage that stays consistently above about 20% usually means a device or its driver is misbehaving. A failing power supply or hard drive can also cause it.
Use this as a rough guide:
| Reading in Task Manager | What it usually means | What to do |
|---|---|---|
| 0% to a few percent at idle, brief spikes | Normal | Nothing |
| 5% to 10% for short stretches during activity | Normal under load | Watch whether it settles |
| Above about 20%, staying there | Driver or device fault | Isolate the device (below) |
| 30% to 40% or more, with stutter or fans spinning | Driver flooding the CPU with interrupts | Isolate and replace the driver |
A Microsoft Q&A answer from May 2026 about a 30% to 40% case says the cause is a device driver flooding the processor with interrupts. It names network adapter drivers in over half of cases, then audio drivers (Realtek is mentioned) and USB controllers or BIOS power states.
Is it a real problem or just Task Manager?
Two checks keep you from chasing a ghost.
First, opening Task Manager can cause a brief false spike while its graph loads. Worry only if the Performance tab shows usage that stays high over a few minutes.
Second, Task Manager counts interrupt and DPC time that other measuring tools leave out. A Microsoft Q&A answer explains that per-process measurements exclude this time, which is why an app's own CPU figure can look lower than what Task Manager reports overall. Task Manager's number is the one that reflects what your processor is really doing.
If the total CPU is high but System Interrupts is low, the cause is something else. Our guide to finding the process hogging your CPU on Windows 11 covers that case, and high CPU usage in Windows 11 covers the broader picture.
Signs a driver is the cause
High System Interrupts rarely arrives alone. Look for these companions:
- Audio that pops, crackles or cuts out. Our page on audio crackling in Windows 11 walks through that symptom.
- Mouse movement that hitches or freezes, which we cover in mouse lag on Windows 11.
- Game stutter and long frame-time spikes with no obvious GPU load. See reducing game stutter with PresentMon traces to confirm whether the stutter is interrupt related.
- Fans that spin up at idle for no clear reason.
- The problem began right after a Windows update, a driver update or a new USB device.
That last point is the most useful clue. Interrupt problems usually have a recent trigger.
Step-by-step: find and fix the cause
Work through these in order. Change one thing at a time and watch System Interrupts in Task Manager (Performance tab, or Details tab sorted by CPU) after each step. If a step changes nothing, undo it before moving on.
1. Restart and install pending updates
Transient driver faults often clear after a full restart. Then open Settings, go to Windows Update and install everything pending, including optional driver updates. This is the cheapest step and it fixes a fair share of cases.
A note on restarting: with Fast Startup on, "Shut down" does not fully reset drivers, so choose Restart rather than shutting down and powering on.
2. Unplug non-essential USB devices
Disconnect everything except your keyboard and mouse, wait a minute, and watch the reading. If it drops, reconnect devices one at a time. A single faulty cable, hub or dongle can generate a constant stream of interrupts. A USB device that is the culprit will make the number jump again the moment you plug it back in.
3. Isolate the device in Device Manager
This is the test the Microsoft Q&A answer above recommends. In Device Manager, disable (do not uninstall) devices in this order, checking the CPU reading after each:
- Wi-Fi or Ethernet adapter under Network adapters.
- The sound device under Sound, video and game controllers.
- USB root hubs, one at a time, under Universal Serial Bus controllers.
When the number drops after disabling one, you have found the device. Re-enable it and move on to its driver. Choose Disable rather than Uninstall while testing so the change is simple to reverse. Do not disable the storage controller your system drive runs on, or the display, keyboard or mouse you are actively using.
Before you disable your network adapter, remember you will lose your connection for the test. Save your work and download any driver you might need first.
4. Update, or roll back, the driver
Once you know the device, take the driver from the PC or motherboard maker's support page, or from Windows Update. For a laptop, the maker's own package is usually the best match for the hardware.
If the problem started right after a driver changed, roll it back instead: in Device Manager, open the device's Properties, then the Driver tab, then Roll Back Driver.
Microsoft's answer lists network adapter causes such as a Wi-Fi adapter that keeps scanning, wake-on-LAN packet handling, or offload features like Large Send Offload and ARP offload that don't suit the driver. If your adapter is the culprit and a fresh driver doesn't help, those adapter advanced properties are the next place to look. Note what you change so you can put it back.
5. Check power settings
BIOS power states and USB or PCIe power saving can trigger interrupt storms on some machines. Set the Windows power plan to Balanced, and if the reading still looks wrong, test turning off USB selective suspend and PCIe Link State Power Management in advanced power plan settings. Test one setting at a time.
6. Trace the exact driver (for enthusiasts)
If you want proof rather than elimination, Microsoft's tooling can name the driver. The Q&A answer describes recording a trace with Windows Performance Recorder and analyzing it in Windows Performance Analyzer to see which .sys file is responsible. WCCFTech's DPC latency guide gives the capture commands: wpr -start GeneralProfile -filemode to begin and wpr -stop to save, then add the DPC/ISR graph in WPA and line the spike up with the moment the glitch happens.
Read the results with care. The same guide notes that a name like Wdf01000.sys only tells you a Windows Driver Framework device driver is involved, not which device. You still isolate the device afterward. Typical names to expect are ndis.sys (network), portcls.sys (audio) and USBPORT.sys (USB).
When a Windows update is the trigger
Sometimes the cause is a version clash rather than a faulty device. One documented example: dozens of testers traced high idle CPU on Windows 11 24H2 to an interaction between that Windows build and certain newer NVIDIA display drivers. Rolling back or moving to a later driver release brought idle CPU back down, while BIOS updates, power plan changes and malware scans did nothing.
The lesson applies broadly. When the trouble begins right after an update, check the driver and Windows version history for that exact change before you try generic tweaks. Generic optimization that is not tied to a measured cause often wastes your time.
Where Tempered fits in
Most of the steps above are about patience: watching a number, changing one thing, watching again, and remembering what you changed. That is exactly where people go wrong. They apply five tweaks at once, the number drops, and they never learn which one mattered. Or it doesn't drop and they can't remember how to go back.
Tempered is a Windows 10 and 11 tool built around the opposite habit. It analyzes live hardware metrics (CPU, RAM, GPU, disk and uptime), gives recommendations in plain language, and every change needs your explicit approval. Each change is tracked with a one-click Undo, so you can test a suggestion and return to where you started if it doesn't help. You don't need technical expertise or an AI API key to use it.
Tempered also manages background processes and startup options, which matters because extra background load makes an interrupt problem harder to read. It does not apply registry cleaning or invent issues, and it is anti-cheat safe for gamers.
Perspective
System Interrupts is a perfect example of why we built Tempered the way we did. The number in Task Manager is a symptom, and the cause lives in a specific driver or device. A tool that promises to "boost your PC" with one button can't know which one. It can only guess, and guessing at drivers is how people end up with a machine that is worse than before.
Our view is that a recommendation is only worth making when it is tied to something measured. That is why we show you the live CPU, RAM, GPU and disk readings, explain in plain words what a suggested change should do, and wait for your approval before touching anything. If the result isn't what you expected, every change has an undo path.
For gamers, that means you can chase stutter without worrying that something will upset your anti-cheat. For everyone else, it means you stay in control of your own system, with a record of what changed and why.
Ian
Try it on your own PC
If you would rather see your readings and decide with an explanation in front of you, Tempered has a Free plan with limited AI scans. Torque starts at $5.99 per month and Torque Max at $12.99 per month, with higher scan limits and premium features. You can compare them on the Tempered pricing page or start from the Tempered homepage.

If it still won't go away
When drivers, USB devices and power settings are ruled out, the Microsoft Q&A answer is direct: if WPA points to drivers such as ndis.sys or usbport.sys, reinstall or replace the associated driver, and if driver updates don't solve it, failing hardware is a likely cause.
The usual suspects, per How-To Geek, are a failing hard drive and a failing power supply. A drive can be checked with Check Disk or a S.M.A.R.T. utility. A power supply can really only be tested by swapping it. If you aren't comfortable opening a desktop, or the machine is a laptop under warranty, contact the manufacturer's support, since a hardware fault is theirs to repair.
Also confirm the basics. A CPU that is overheating lowers its clock speed, which makes every workload, including interrupt handling, take a bigger share of the processor. Clean dust from vents and check that fans spin normally. For a business workstation, take the same steps but make a restore point first and avoid BIOS changes on managed machines without your IT department's approval.
Quick checklist before you start
- Confirm the reading stays high for several minutes, not just when Task Manager opens.
- Write down when it started and what changed just before: update, new device, new driver.
- Restart (not shut down), then install pending updates.
- Unplug USB extras, then disable network, audio and USB hubs one at a time.
- Update or roll back only the driver you identified.
- Keep notes of each change, or use a tool that tracks them for you.
FAQ
What are System Interrupts in Task Manager?
System Interrupts is a placeholder that totals the CPU time Windows spends answering signals from hardware like your network adapter, keyboard, disk and USB ports. It is a normal part of Windows. You cannot end it, and you shouldn't need to, because it only becomes a problem when a driver makes the total too large.
Is it normal for System Interrupts to use 10% CPU?
Brief rises up to about 10% are normal, for example while copying files or streaming. If it sits well above that, especially past 20%, at idle, a driver or device is likely misbehaving and worth isolating with the Device Manager test above.
Can I disable System Interrupts?
No. It is not a process or a service but a measurement of interrupt handling, so there is nothing to turn off. What you can do is find the device or driver generating too many interrupts, then update, roll back or replace it.
Why does System Interrupts cause stutter or audio crackling?
While a core is busy running interrupt routines, normal threads can't run on it. If those routines run too often or too long, timing-sensitive work like audio buffers and game frames gets delayed, which you hear as pops and see as stutter.
Sources
- What Is the "System Interrupts" Process and Why Is It Running on My PC?
- CPU Analysis | Microsoft Learn
- ISRs and DPCs, The Silent Killers | Microsoft Learn
- System Interrupts process constantly causing high CPU usage | Microsoft Q&A
- High CPU usage when opening task manager | Microsoft Q&A
- CPU Usage Difference Between Code and Task Manager | Microsoft Q&A
- How To Diagnose and Fix High DPC Latency in Windows
- High System CPU Usage on Windows 11 24H2 Caused by NVIDIA Drivers
