What Causes Frame Pacing Issues?
Frame pacing describes how evenly frames are delivered to your display. A game running at 144 FPS can still stutter if frames arrive at intervals of 1 ms, 14 ms, 1 ms, 14 ms rather than a steady 6.9 ms apart. FPS is an average — frame pacing is the consistency behind that average.
FPS vs Frame Time
FPS (frames per second) is a count of frames rendered per second. Frame time is the duration of each individual frame in milliseconds. Perfect 144 FPS requires every frame to take exactly 6.94 ms.
Frame pacing variance is the deviation between frame times. A 0 ms variance means perfectly smooth motion. High variance at stable FPS creates microstutter — frames arriving too close together appear as judder, even though the frame counter shows a healthy number.
A game showing 144 FPS average but 1% lows of 60 FPS has severe frame pacing issues. The 1% low represents the worst frame times in a 100-frame window — directly perceptible as stutters.
Common Causes
CPU Bottleneck & Thread Scheduling
When the CPU can't feed the GPU fast enough, the GPU finishes a frame and sits idle waiting for the next draw calls. This creates irregular GPU-active windows — variable frame times even when average FPS looks fine.
Desktop Window Manager (DWM) Interference
Windows' compositor (DWM) introduces a processing layer between your game's rendered frame and the display scanout. On non-exclusive-fullscreen modes (including borderless windowed), DWM can hold frames, combining or skipping them on scanout boundaries.
Thermal & Power Throttling
GPUs and CPUs reduce clock speeds under thermal pressure. Frame time spikes correlate directly with these thermal events. Cleaning dust, reapplying thermal paste, and improving case airflow address root causes that no software can compensate for.
Memory Bandwidth & Latency
Games that stream large asset sets can hitch as the CPU fetches data from RAM. Insufficient RAM bandwidth (slow DDR4, single-channel configs) causes irregular stalls in the render pipeline.
GPU Driver Bugs
Specific driver versions are known to introduce frame pacing regressions on certain GPU families. Always check community benchmarks (Hardware Unboxed, Digital Foundry) before updating to a new major driver release.
V-Sync & Adaptive Sync
Traditional V-Sync synchronizes frame delivery to display scanout, eliminating tearing. The tradeoff: if a frame misses its scanout window, it waits for the next one — doubling its display time and creating a visible stutter.
G-Sync and FreeSync stretch or compress the display's scanout window to match the GPU's render speed, eliminating both tearing and sync-induced stutter within their supported FPS range (typically 48–240 Hz). Operating outside this range (above maximum or below minimum) reintroduces either tearing or V-Sync-style stutters.
Diagnosing Frame Pacing
Tools: CapFrameX or FCAT-VR for detailed frame time analysis, MSI Afterburner's frame time graph overlay during gameplay, and GPU-Z for thermal data. Focus on 1% and 0.1% lows rather than average FPS.
Our Responsiveness Lab's Frame Stability test visualizes frame delivery consistency directly in your browser — useful as a baseline indicator of your system's general scheduling behavior.
Fixing Frame Pacing
Use Exclusive Fullscreen
Exclusive fullscreen bypasses DWM entirely, giving the game direct control of display scanout. This eliminates DWM-induced frame pacing irregularities.
Cap FPS Below Refresh Rate
Capping your framerate at 3–5 FPS below your monitor's refresh rate (e.g., 237 FPS on a 240 Hz panel) prevents the GPU from trying to push frames faster than the display can accept, reducing micro-tearing and sync stalls.
Enable NVIDIA Reflex / AMD Anti-Lag
These technologies manage the GPU render queue to prevent excessive frame queuing, which is a major source of both latency and frame pacing irregularities.
Frequently Asked Questions
Test your setup