DPC Latency: The Stutter You Can’t See

You can hold a rock-steady 200 FPS and still feel the game hitch every few seconds, like it briefly trips over itself. The cause often isn't your GPU or CPU at all — it's how a driver handles interrupts: one badly written handler stalls the whole system for a fraction of a millisecond, and that fraction is what you feel. Because the frame counter stays calm, people blame their hardware for months while the real culprit goes unnoticed.

What a DPC actually is

When a device needs the CPU, Windows defers the heavy lifting into a queue of Deferred Procedure Calls (DPCs). While one driver runs its DPC, others wait their turn — and if a handler hogs the CPU too long, your audio buffer and frame pipeline don't get serviced in time. The usual offenders are network and Wi-Fi adapters, audio drivers, and occasionally the GPU driver itself, especially older or generic versions pushed through Windows Update.

Measure it, don't guess

Never fix this blind — diagnose first. The free tool LatencyMon runs for a few minutes under load and names the exact driver with the worst DPC execution times; for rare spikes, xperf/WPR from the Windows Performance Toolkit gives sharper detail. As a rough guide, steady highest-latency values in the low microseconds are usually fine, while repeated spikes into the hundreds of microseconds or into milliseconds are what you actually hear and feel. Test both at idle and while a game is running, since the guilty driver often only acts up under real load.

What to actually change

Start by updating — or sometimes rolling back — the specific driver LatencyMon flagged; that alone fixes most cases. After that, in rough order of payoff: disable power saving on the network adapter and set the power plan to High Performance, turn off unneeded overlays and background audio/RGB 'enhancers,' and if you're on Wi-Fi, test whether it's the source — a wired connection sometimes ends the problem outright. Change one thing at a time and re-measure, or you'll never know which fix worked.

The cost of every tweak

None of this is free. High Performance mode and disabled NIC power saving raise heat and drain a laptop's battery; rolling a driver back can reintroduce an old bug or a security hole; killing overlays loses you handy features like monitoring and clip capture. So resist the urge to delete services or hand-edit the registry on a hunch — on modern Windows that breaks more than it fixes. If you're not sure, it's safer to have someone experienced handle it.

Verdict

DPC latency is real, not a placebo tweak: a misbehaving driver genuinely ruins the feel of a game even at a perfect frame rate. Run LatencyMon, pin down the one culprit, and fix it surgically, one change at a time. In most cases it comes down to a single network or audio driver — sort that out and the micro-stutter usually clears up, without any risky surgery on Windows.