High-FPS hitching, in fix order

The single most common cause of hitching on a powerful rig is frames arriving faster than the panel can pace them. Uncapped FPS above the refresh ceiling defeats variable refresh and reintroduces stutter and tearing at the moments that matter.

When monitors run at different refresh rates, Windows has to reconcile the refresh domains, and anything animating on the slower panel (chat, a browser video, a dashboard) can periodically stall the game monitor. Invisible to benchmarks, very visible in a match.

On machines with an integrated GPU alongside the discrete card, a monitor plugged into the motherboard's video port routes frames through the integrated GPU. Frames get copied between adapters, and that copy is a direct cause of hitching.

Kernel drivers that poll hardware constantly add DPC latency, which surfaces as micro-stutter no framerate counter explains. The names that come up most often in enthusiast troubleshooting threads: Nahimic and A-Volute audio stacks, Killer and Rivet networking suites, Wi-Fi adapter drivers, and RGB or peripheral suites (iCUE, Armoury Crate, Mystic Light, Synapse). Treat that as a starting list, not a verdict on any of them: the driver holding your CPU is a fact about your machine, and LatencyMon is what establishes it.

A browser playing video on the second monitor, an animated wallpaper, overlay hooks (Discord, GeForce Experience, a second capture tool), antivirus scans, cloud-sync bursts, and background game recording all contend for the GPU, CPU, or disk in bursts that land as random hitches.

Shader-compilation stutter is real, but it correlates with new areas, fresh drivers, and first runs, not with steady-state hitching in a familiar game. It is the suspect people reach for first and the answer least often.

If you run the Vera collector, part of this checklist is already answered from your own record: which of the known driver offenders are actually on your machine, whether an integrated GPU sits alongside your card, and whether your monitors run mixed refresh rates. Newer collectors (v0.4 and up) can also measure frame pacing itself while a recognized game runs: aggregate statistics only, read through the operating system's own event tracing, with no injection into any game and no per-frame data ever leaving your machine. The session pages show it as a Performance card when a measurement exists.

And so nobody mistakes absence for proof, what the record cannot see: your G-Sync, V-Sync, and frame-cap state; driver version numbers; and shader compilation, which happens inside the game. Those checks stay yours, which is why this page exists.