High DPC latency: find the driver responsible, then fix it

What DPC latency actually is

When a piece of hardware needs attention, its driver responds in two stages. A very short interrupt handler runs immediately, and any longer work is queued as a deferred procedure call, or DPC, to run soon afterwards at a high priority. While DPCs run, ordinary work on that processor core waits, including the audio and game threads that need to meet strict deadlines.

A well-behaved driver keeps both stages brief. A badly behaved one, often a network, storage, audio or power management driver, occasionally holds the processor far longer than it should. The rest of the system misses its deadlines, and you hear it as a crackle or pop in the audio, or see it as a stutter that repeats on a rhythm unrelated to what is happening in the game.

Symptoms that point to DPC latency

• Audio crackles, pops or drops out briefly, particularly under load or when the network is busy.
• A stutter that repeats every few seconds regardless of what is on screen.
• Mouse movement that skips or hitches despite a healthy frame rate.
• Problems that appear or worsen when a particular device, such as Wi-Fi, Bluetooth or a USB audio interface, is in use.

If your stutter instead follows what happens in the game, such as new areas or effects, the Windows 11 stuttering guide is the better starting point.

Find the driver with LatencyMon

LatencyMon, a free tool from Resplendence, measures how long drivers spend in interrupt and DPC routines and names the worst offenders. It only observes, so running it changes nothing on your PC.

1. Close unnecessary programs, then start LatencyMon and press its start button.
2. Use the PC the way that normally produces the problem for several minutes: play the game, stream music, use the network.
3. Stop monitoring and open the Drivers tab. Sort by highest DPC routine execution time.
4. Note the top few drivers by file name and look up which device each belongs to; the description column usually makes it clear.
5. Check the Stats tab, which summarises whether the system is judged suitable for real-time audio and which driver is most responsible.

The driver at the top of that list is where every fix below should be aimed. Changing system-wide settings before you know which driver is responsible usually just adds new variables.

Fix: update, roll back or replace the named driver

Most DPC problems are fixed at the driver itself. If LatencyMon points at a network, Wi-Fi, audio or storage driver, install the latest version from the motherboard or PC maker, not a generic one found by a driver updater. If the problem started after a driver update, roll back through Device Manager, under the device's Driver tab. Graphics drivers should come from NVIDIA, AMD or Intel directly, and a clean installation clears leftover settings.

Update the motherboard firmware and chipset driver too, because power management and interrupt handling live partly there. If a driver has no fixed version, test with the device disabled in Device Manager for a session; if the problem vanishes, a different adapter, such as a wired connection instead of Wi-Fi or a different USB audio device, is the practical fix.

Fix: power management behaviour

Aggressive power saving makes processor cores and devices sleep and wake constantly, and some drivers handle those transitions badly. Test with a performance-oriented power plan, and on the network adapter's Power Management tab in Device Manager, stop Windows turning it off to save power. USB controllers that suspend idle ports can cause similar trouble for audio interfaces and mice, which the USB selective suspend reference explains. On a laptop, test while plugged in, since battery modes are the most aggressive of all.

Interrupt and timer tweaks: last, and with care

Guides about DPC latency often jump straight to low-level changes: forcing message-signalled interrupt mode on the graphics card, pinning a device's interrupts to particular cores, or changing timer behaviour through boot configuration. These can help in specific cases where LatencyMon points at the device involved, but they are not general fixes. Windows normally lets each driver decide these things, and forcing them on a device or driver that does not handle them well can cause instability or a device that stops working.

If you do go there, change one thing, reboot, measure again with LatencyMon, and reverse it if nothing improved. The MSI mode reference, the interrupt affinity reference and the HPET and timer reference explain what each setting does and how to undo it. Timer resolution is a separate topic again, covered in the global timer resolution reference.

Wireless adapters and peripheral software

Wireless network and Bluetooth adapters are among the drivers LatencyMon names most often, partly because they wake constantly to scan, reconnect and manage power. If a wireless driver tops the list, test the problem with that adapter disabled in Device Manager and a wired connection in its place. If the crackle or stutter disappears, a newer driver from the laptop or motherboard maker, a different adapter, or simply staying wired are all reasonable fixes.

Software bundled with peripherals can cause similar trouble. RGB lighting controllers, keyboard and mouse utilities and audio enhancement suites sometimes install their own drivers or poll hardware frequently. Close or uninstall them one at a time while LatencyMon runs, and keep only those whose removal made no difference. Where the maker provides firmware updates for a USB audio interface or headset, install them too, since its driver and firmware work as a pair.

Where an optimizer fits, honestly

An optimizer cannot fix a badly written driver, which is the usual cause here. It can apply power management settings, and some offer the interrupt-level changes described above, which is where caution matters most.

JINSHI PC Tweaks, our product, includes an "Enable MSI Mode for GPU" toggle described in the app as lowering DPC latency. We label it High Risk and leave it out of the app's recommended set, because it only makes sense when LatencyMon points at the graphics driver, and it can cause instability otherwise. Is a PC optimizer safe? lists all six High Risk changes and why. Every change is on the complete tweak list and reversible on its own. If the power settings above are what you need, the JINSHI Tweaks homepage shows what PC Tweaks covers, and gaming optimizers versus cleaners explains where this kind of tool fits. For the full checklist, see how to choose a PC optimizer.