Game stutters even though FPS is high? Frame pacing, shader stutter and how to fix it
The FPS counter says 90 but every few seconds the game hitches, or the motion just never feels smooth. The counter is telling the truth, just not the part that matters.
Average FPS hides the hitches
| Second of gameplay | Frame times | FPS counter | How it feels |
|---|---|---|---|
| Even | 60 frames of 16.7 ms | 60 | Smooth |
| One spike | 56 frames of about 16.4 ms + one of 80 ms | 57 | A visible hitch |
| Uneven | Alternating 10 ms and 23 ms | 60 | Micro-stutter: never quite smooth |
That's why reviews quote 1% lows (the frame rate of the slowest 1% of frames) next to the average. A big gap between the two means stutter. To see it yourself, turn on a frame-time graph: the Steam performance overlay, MSI Afterburner with RivaTuner, CapFrameX, or the Nvidia / AMD overlays. A flat line is smooth; spikes are hitches.
Find your cause
| What you notice | Likely cause | Fix |
|---|---|---|
| Steady judder, worse when panning, FPS just under the refresh rate (e.g. 45-58 on 60 Hz) | V-Sync on a fixed-rate screen repeating frames | Turn on VRR (G-Sync / FreeSync / HDMI VRR), or cap at a rate the game always holds: 30 or 60 on 60 Hz, 72 on 144 Hz |
| Hitches the first time you see an effect, enemy or area; gone on a second visit | Shader compilation | Let the game finish "compiling shaders" at launch; don't clear the driver shader cache; set the Nvidia shader cache size to a larger value; avoid reinstalling drivers right before playing; check for game patches |
| Hitches when moving into new areas, at the same spots | Asset streaming / traversal stutter | Install the game on an SSD (NVMe if possible); close other heavy downloads; some engines just do this, so patches help more than settings |
| Fine at first, worse after a while or at high textures | Video memory (VRAM) full | Lower texture quality one step; lower resolution or ray tracing; watch the VRAM use in the overlay |
| A hitch every few seconds, like clockwork | Background task, overlay, RGB or monitoring software polling hardware | Close overlays and hardware-monitoring apps one at a time; pause cloud sync and antivirus scans |
| Choppy on a laptop, fine on charge | Battery power mode throttling | Plug in; set Windows power mode to Best performance |
| High FPS, but the GPU is far below 100% and one CPU core is maxed | CPU limit | Lower CPU-heavy settings (crowds, view distance, physics); enable the memory's XMP / EXPO profile in the BIOS; use two RAM sticks (dual channel), not one |
| Smooth-ish but "floaty" with frame generation on | Frame generation from a low base frame rate | Use it only when the base is about 60 fps or more; keep Reflex / Anti-Lag 2 on |
| Films and TV judder on pans, games are fine | 24 fps film on a 60 Hz screen (3:2 pulldown) | Use a 120 Hz or 24 Hz output mode, or the TV's "match frame rate" / Judder reduction setting |
Why 50 can look worse than 30
On a fixed 60 Hz screen with V-Sync, 30 fps shows every frame for exactly two refreshes: chunky but even. 50 fps shows most frames once and every fifth or so twice, so motion goes step, step, stumble. That uneven rhythm is judder, and it's why a steady cap often feels better than a higher but wobbly number. The interactive flip-book lesson lets you set 50 on 60 and watch the repeated pages appear, then switch to VRR and see them go.
A fix order that usually works
- Check the screen is at its full refresh rate, and turn on VRR if you have it (see screen tearing fixes for the settings).
- Cap the frame rate a little below what the game reaches in busy scenes, using the game's own limiter or the driver. Even frames beat high frames.
- Update the graphics driver and the game, then let shaders build at launch.
- Put the game on an SSD and drop textures a step if VRAM is close to full.
- Close overlays and background apps; plug the laptop in.
Lag is a separate problem from stutter: a perfectly smooth game can still feel slow to respond. The input lag calculator shows how frame rate, V-Sync and the screen add up to press-to-picture delay.
Related
Laptop slows down when hot · Coil whine in games · Monitor stuck at 60 Hz · Screen tearing: how to fix it · HDR looks washed out on PC · VRR, G-Sync and FreeSync explained · 60 vs 120 vs 144 Hz · Reflex and Anti-Lag
Questions
Why does my game stutter when FPS is high?
Because FPS is an average. A few slow frames (frame-time spikes) cause visible hitches without moving the average much. Common causes are shader compilation, loading new areas, full video memory and background software.
What are 1% lows?
The frame rate of the slowest 1% of frames. If the average is 100 fps but the 1% lows are 35, you will feel stutter even though the counter looks good.
Does capping FPS reduce stutter?
Often, yes. A cap the game can always hold keeps frame times even, and with VRR a cap just below the refresh rate keeps VRR active. It also leaves the processor and graphics card some headroom for busy moments.
What is shader compilation stutter?
The game has to prepare graphics programs (shaders) for your card the first time an effect appears, and if it does that mid-game the frame takes much longer. Precompiling at launch and keeping the shader cache avoids most of it.
Will more RAM fix stuttering?
Only if you are running out. Using two sticks in dual channel and enabling XMP / EXPO often helps more than adding capacity, especially when the processor is the limit.
Why do films judder on my 60 Hz TV?
Films are 24 frames a second, which doesn't divide into 60, so frames are shown alternately three and two times (3:2 pulldown). A 120 Hz or 24 Hz mode shows every frame for the same time.
Published .