System Interrupts high: idle-high is a device, in-game is traffic

Part of our guide on interpreting udp packet tests

Identify the exact device or driver causing high System Interrupts CPU by comparing idle and in-game states and measuring DPC latency.

What System Interrupts means in Task Manager

System Interrupts CPU usage represents the processor time spent handling hardware interrupt requests (ISRs) and deferred procedure calls (DPCs).

It is not a process you can end or uninstall; rather, it shows how much CPU resources devices or drivers consume when they signal the CPU.

Interrupts happen when hardware needs immediate attention, while DPCs are deferred work the CPU does afterward at lower priority.

This combined figure appears under a fake process called 'System Interrupts' in Task Manager. For the detail, see our notes on explaining ping versus speed test.

Interrupt requests vary by device type and activity. For example, a keyboard sends fewer interrupts than a high-speed USB mouse.

Interrupts also depend on hardware design; PCIe devices often generate more interrupts than onboard components.

You can expect System Interrupts CPU usage to fluctuate slightly even at idle, typically under 1%, as background hardware signals occur. We go through 1% packet loss for gaming step by step elsewhere on the site.

Interrupt storm symptoms can appear as prolonged high CPU usage by System Interrupts, often over 20%, even at idle. This usually means a hardware fault or driver conflict causing continuous interrupt requests.

For example, a faulty network card repeatedly sending interrupts can push System Interrupts CPU to 25%, making the PC lag. You can confirm by temporarily disabling devices one by one and watching CPU usage drop.

Checking the Event Viewer can reveal related hardware errors or driver failures accompanying high System Interrupts. Look under System logs for warnings or errors timed with the CPU spikes. The other half of this decision is steps to fix modem packet loss.

Idle vs in-game System Interrupts: what each means

Check System Interrupts CPU with Task Manager when your PC is idle, no apps running, then again during gaming.

If interrupts are high (above 5% CPU) when idle, a device or driver is misbehaving or polling constantly.

If interrupts spike only during gaming, the cause usually lies in network traffic, GPU drivers, or storage activity linked to the game workload. It helps to understand test MT7921 packet loss before going further.

Separating these states lets you target your troubleshooting to hardware faults or driver inefficiencies versus legitimate interrupt load.

Idle-high System Interrupts often mean a driver is polling hardware aggressively or a device is stuck in a loop.

In-game System Interrupts spikes can reflect legitimate workload, like GPU rendering or network packets processing. People in this spot often ask about ethernet and packet loss as well.

You might see spikes of 10-15% CPU usage from System Interrupts during gaming on some setups: this is normal if it returns to low levels after the game closes.

In some gaming setups, System Interrupts can spike above 15% briefly during intense GPU or disk access, yet this is still considered normal transient load.

If spikes remain elevated for minutes, it can cause stutter or input lag, showing the interrupts affect responsiveness. Monitoring frame times alongside CPU usage helps identify this.

Games with frequent network updates may push interrupts high on network adapters, but enabling interrupt moderation often smooths this, keeping spikes under 5%.

• Idle-high interrupts – point at a faulty device or driver, USB polling, audio, or storage interfaces.
• In-game-high interrupts – suggest network adapter, GPU driver DPCs, or disk I/O reacting to game traffic.
• Normal System Interrupts idle usage is 0.1-1% CPU on a multi-core processor.

How to name the device causing high System Interrupts

Task Manager shows total System Interrupts CPU but not which hardware or driver fires the interrupts.

Use a tool like LatencyMon to measure DPC and ISR execution time, listing drivers by their CPU use during interrupts.

Look for drivers with the highest execution time, not just total CPU, to spot the culprit device.

Monitoring per-core CPU usage helps confirm if one CPU handles heavy interrupt load, typical for problematic drivers.

Some devices use shared interrupt lines, making it tricky to pinpoint the exact source without detailed tools.

LatencyMon also reports the types of ISR and DPC events, helping distinguish between audio, storage, or network drivers.

Cross-referencing LatencyMon results with Device Manager and recent driver updates narrows down the culprit effectively.

1. Download and run LatencyMon during idle-high or in-game-high interrupts.
2. Let it run at least 5 minutes to gather meaningful ISR/DPC stats.
3. Sort drivers by highest execution time and note their names.
4. Cross-check device manager for matching hardware components.

Load-only suspects to test in order

If System Interrupts rise only during gaming or network load, start testing the network adapter settings.

Enable interrupt moderation on your Ethernet or Wi-Fi device to reduce CPU spikes caused by packet bursts.

Disable power saving features in the Wi-Fi driver to keep the interface stable under load.

Check the GPU driver DPC latency: outdated or buggy GPU drivers can cause heavy deferred procedure calls during game rendering.

If enabling interrupt moderation reduces spikes, it confirms the network adapter is the cause.

Sometimes rolling back to an earlier GPU driver version fixes heavy DPC latency in games.

Test changes one at a time with consistent load to isolate improvements clearly.

• Network adapter: interrupt moderation and driver updates.
• Wi-Fi driver: disable power saving and test stability.
• GPU driver: update or rollback to stable version if interrupts rise.
• Repeat measurements after each change.

Idle-high suspects and test order

When System Interrupts spike with no apps running, look first at USB devices and audio drivers.

High USB polling rates on gaming mice (1000 Hz) can cause interrupt storms; try lowering it to 500 Hz to test.

USB audio devices and some Realtek audio drivers are known to cause high interrupts due to driver inefficiency.

Check NVMe or SATA AHCI storage drivers as well; faulty or outdated storage controllers cause interrupts even at idle.

Lowering USB mouse polling rate from 1000 Hz to 500 Hz halves the interrupt frequency, often reducing CPU usage noticeably.

Unplugging USB audio and rechecking System Interrupts can confirm if the audio driver causes the problem.

Updating storage drivers also reduces interrupts from faulty NVMe or SATA controllers that repeatedly signal the CPU.

• USB mouse: reduce polling rate from 1000 Hz to 500 Hz to test.
• USB audio: unplug and test if interrupts drop.
• Realtek audio drivers: update or reinstall.
• NVMe/SATA AHCI drivers: ensure latest versions.

Normal readings and telling interrupts from thermal throttling

On a modern multi-core CPU, normal System Interrupts CPU usage is usually below 1% when idle and under 3-5% during gaming.

Interrupt spikes above 10% indicate a problem worth investigating.

Thermal throttling or power-limit throttling show as CPU clock drops and core temperatures rising, not as System Interrupts spikes.

Use core temperature and frequency monitoring tools alongside Task Manager to differentiate thermal issues from interrupt problems.

• System Interrupts normal idle: 0.1-1% CPU.
• System Interrupts normal gaming: up to 5% CPU.
• Thermal throttling: CPU frequency drops, high temps.
• Interrupts: CPU time spent servicing hardware requests.

Questions people still ask

I have diagnosed numerous gaming PCs by separating idle and in-game System Interrupts and using LatencyMon to pinpoint driver issues.