How to Fix Stuttering in Games (Even at High FPS)
Stuttering is a frametime problem, not an FPS problem. Learn to read the frametime graph, identify which of the six stutter types you have, and apply the fix that matches it.
The short answer
Stuttering is caused by inconsistent frame delivery, not low frame rate — which is why a game can average 140 FPS and still feel broken. Diagnose it by enabling a frametime graph in MSI Afterburner or CapFrameX and matching the shape of the spikes to a cause: shader compilation, traversal streaming, CPU thread bottleneck, VRAM overflow, background process interference, or a frame-pacing mismatch. Each has a distinct fix, and the single most effective general change is capping your frame rate 3-5 FPS below your refresh rate with RTSS.
Verified and last updated August 10, 2026.
- Time needed
- 1 hr
- Difficulty
- Intermediate
- Read time
- 10 min
Most stuttering advice starts in the wrong place. It tells you to update drivers and close background apps, which is the equivalent of a mechanic saying "have you tried turning it off and on again" — occasionally right, never diagnostic.
Stuttering is a frametime problem. Frame rate is an average; frametime is the actual interval between frames arriving. A game can average a very healthy 140 FPS while shipping four frames a second that take 50 ms each, and those four frames are the entire experience of stuttering. Until you can see them, you are guessing.
Key takeaways
Step 1: Put a frametime graph on screen
You need to see the spikes. Two ways, both free.
Live, while playing — MSI Afterburner + RivaTuner:
- Install MSI Afterburner, which bundles RivaTuner Statistics Server.
- Settings → Monitoring tab.
- Tick Frametime, then tick Show in On-Screen Display and set it to Graph.
- Also enable Framerate, GPU usage, GPU temperature, Memory usage (VRAM) and CPU usage.
- Apply, launch your game.
After the fact, with proper numbers — CapFrameX:
Free, open source, and better for actually understanding what happened. Record a 60-second capture of the problem, then read the 1% low and 0.1% low figures. Those two numbers are the stutter, expressed honestly. If your average is 140 FPS and your 1% low is 42 FPS, you have a stutter problem regardless of how good the average looks.
What you are looking for
A healthy frametime graph is a nearly flat line. Every visible vertical spike is a hitch you felt. What matters is the pattern of the spikes: are they random, rhythmic, tied to movement, or clustered at the start of a session? That pattern is your diagnosis.
Step 2: Match the pattern to a cause
The rhythmic case is worth calling out because it is so distinctive. If your spikes arrive on a metronome — every 5 seconds, every 30 seconds — that is not the game. Something on a timer is waking up: Windows Search indexing, a Steam or Epic background update check, an antivirus scheduled scan, a hardware monitoring app polling sensors, or OneDrive syncing. Open Task Manager, sort by CPU, and watch which process spikes in time with the graph.
Step 3: Fix shader compilation stutter
Modern engines compile shaders on demand, the first time each effect is drawn. Compiling takes a few milliseconds of CPU time in the middle of a frame, and that is your hitch. Unreal Engine 5 titles are the worst offenders; Unreal 4 and id Tech are much better behaved.
Give the driver a bigger cache. The default cache is small enough to thrash on a big game.
NVIDIA: Open the NVIDIA Control Panel → Manage 3D Settings → Shader Cache Size → set to Unlimited. This is not a placebo; there is well-documented evidence of games that stutter constantly at the 10 GB default running clean once the cache is allowed to grow past it.
AMD: Adrenalin → Gaming → Graphics → Shader Cache → AMD optimised.
Then clear the existing cache once, because a corrupted cache produces stutter that no amount of extra space fixes:
- Windows Search → Disk Cleanup.
- Select your system drive.
- Tick DirectX Shader Cache. Untick everything you care about.
- OK. Also delete the contents of
%localappdata%\NVIDIA\DXCacheand%localappdata%\D3DSCache.
Use the game's own pre-compilation step if it has one. Many recent titles offer "Compile shaders" or "Optimising for your hardware" on first launch or in the video settings. Let it finish. It is five minutes now instead of an hour of stuttering spread across your session.
Driver updates reset all of this
Every GPU driver update invalidates the shader cache, because the compiled output is driver-specific. If a game that was running perfectly starts stuttering the day after a driver update, this is why, and it will resolve itself as the cache rebuilds. It is also a good reason not to update drivers the night before something you care about.
Step 4: Cap the frame rate properly
This is the fix with the best effort-to-result ratio on the entire page, and it is routinely skipped because capping FPS feels like giving something up.
An uncapped GPU runs at 100% utilisation permanently, which means every frame is competing for a resource that is already saturated. Frametimes become variable because the GPU has no headroom to absorb a heavier frame. Capping just below your refresh rate leaves that headroom.
Use RivaTuner, not the in-game limiter. RTSS's frame limiter is significantly more precise than most in-game caps, because it uses busy-wait timing rather than a sleep call.
- Open RivaTuner Statistics Server.
- Add your game's executable, or set the Global profile.
- Set Framerate limit to 3-5 below your refresh rate. 141 for a 144 Hz monitor, 117 for 120 Hz, 57 for 60 Hz.
Why below refresh rather than at it: if you also run G-Sync or FreeSync, staying under the panel's maximum keeps you inside the variable refresh window. Hit the ceiling and VRR disengages, handing you to V-Sync or tearing — and the transition between the two states is itself a visible stutter.
The correct VRR configuration, for the record: G-Sync or FreeSync on, V-Sync on in the driver control panel but off in the game, and an RTSS cap below refresh. That combination gives you the low latency of a cap with V-Sync as a safety net against tearing at the boundary.
Ten FPS of average given up, and the 0.1% low frametime improved by a factor of three. The third row is a smoother game than the first by an enormous margin, and the FPS counter is the only thing that disagrees.
Step 5: Remove background interference
In rough order of how often each one turns out to be the culprit:
Overlays. Discord, Steam, NVIDIA App, Xbox Game Bar, MSI Afterburner's own OSD, Wallpaper Engine, Razer Synapse, GeForce Experience's Instant Replay. Each hooks the render pipeline. Turn off every one, confirm the stutter is gone, then reintroduce them one at a time. Instant Replay and Discord's overlay are the two most common offenders.
Xbox Game Bar and Game Mode. Settings → Gaming → Xbox Game Bar → off. Game Mode is genuinely a mixed bag: on modern Windows 11 it usually helps slightly, but on some configurations it causes periodic hitching. Test both states rather than assuming.
Fullscreen Optimizations. Right-click the game executable → Properties → Compatibility → tick Disable fullscreen optimizations. This is the standard fix for stutter that appears specifically after alt-tabbing.
Fast Startup. Control Panel → Power Options → Choose what the power buttons do → Change settings currently unavailable → untick Turn on fast startup. Fast Startup hibernates the kernel instead of shutting it down, which lets driver state accumulate across "restarts" that are not restarts. If your PC feels progressively worse over a week, this is why.
Memory Integrity / VBS. Windows Security → Device security → Core isolation → Memory integrity → off, then reboot. Verify with msinfo32 that "Virtualisation-based security" reads Not enabled. Worth 3-8% in CPU-limited titles. It is a real security reduction — make that call deliberately.
Power plan. Settings → System → Power → set Best performance. On desktops, also check that the CPU minimum processor state is not parked low; aggressive core parking causes frametime spikes as cores wake up.
Windows Search and antivirus scheduling. Both love to run mid-session. Exclude your game library folders from real-time scanning and set scheduled scans to a time you are not playing.
Step 6: Address VRAM and RAM pressure
When VRAM fills, the driver starts evicting textures to system RAM across the PCIe bus. Each eviction is a stall. This is the source of the most severe stutter spikes — 100 ms and up — and it is entirely settings-driven.
Watch VRAM usage in the OSD. If it is sitting at your card's maximum, you are over the limit. The settings that consume the most, in order: texture quality, shadow resolution, ray tracing, resolution scale. Drop texture quality one notch first. On most modern games the visual difference between Ultra and High textures is close to invisible and the VRAM saving is substantial.
Check system RAM too. 16 GB is workable and increasingly tight; if you play with a browser open and Discord running, you can genuinely run out, at which point Windows pages to disk mid-frame. Task Manager → Performance → Memory. If "In use" is near your total during play, close things or add RAM.
Traversal stutter is a storage problem. If the spikes coincide with movement into new areas, the engine is streaming assets faster than your drive can serve them. An NVMe drive largely fixes it. A hard drive cannot be fixed by settings — move the game.
ISLC for a specific case. Intelligent Standby List Cleaner helps when Windows' standby memory list grows large enough to force paging, which shows up as periodic large spikes on 16 GB systems. It is a targeted tool for a specific symptom, not a general optimiser — do not install it hoping for free performance.
What does not fix stuttering
What works
What doesn't
When the stutter is the game's fault
Sometimes it is. Unreal Engine 5 traversal stutter is a well-documented engine-level issue that appears on hardware far beyond what the game should need, and there is no client-side fix for it beyond capping frame rate and hoping for a patch.
The way to confirm it is not you: run a different game with a similar workload for half an hour. If that one is flat and the problem title is not, you have done everything you can and the remaining fix belongs to the developer.
If your stutter turns out to be network-related — rubber-banding, warping players, hitching only in multiplayer — that is a different diagnosis entirely, and the ping and jitter guide is the one you want. For a fast read on whether your connection is even in the right range for your genre, the ping quality checker grades it against competitive thresholds.
Frequently asked questions
Why do I have high FPS but the game still feels stuttery?
Because FPS is an average over a whole second and stuttering is what happens inside that second. A game running at 144 FPS delivers a frame every 6.9 ms on average, but if forty of those frames arrive in 4 ms and four of them take 45 ms, the average is still respectable while your eyes see four visible hitches. That is why the frametime graph matters and the FPS counter does not — you are looking for consistency, not height.
What is a normal frametime variance?
On a well-behaved system the frametime line should look almost flat, with variation under about 3 ms around the average. At 60 FPS you want frames landing consistently near 16.7 ms; at 144 FPS, near 6.9 ms. Occasional 2-3 ms wobble is invisible. A spike to double your average frametime is perceptible, and a spike above roughly 50 ms reads as an obvious hitch to almost everyone.
Does capping FPS actually reduce stuttering?
Yes, and it is counterintuitive enough that people skip it. An uncapped GPU running flat out produces variable frametimes because it is constantly at the edge of its capability, and it also feeds frames to the display at a rate that does not line up with the refresh cycle. Capping 3-5 FPS below refresh keeps the GPU below saturation and gives frame pacing a stable target. On our RX 6700 XT test box, capping from uncapped 150 FPS to 141 FPS cut 1% low frametimes from 31 ms to 9 ms.
Is shader stutter permanent or does it go away?
It goes away for content you have already seen, and comes back for content you have not. Shaders compile the first time a particular effect, material or weapon is drawn, so the first hour in a new game stutters and the second hour does not — until you reach a new area. It resets whenever you update your GPU driver, since driver updates invalidate the cache. That is why a game that ran perfectly can start stuttering again the day after a driver update.
Should I disable Memory Integrity for gaming?
It gives a measurable improvement, typically 3-8% in CPU-limited scenarios, and it is a genuine security reduction. Core Isolation Memory Integrity uses hardware virtualisation to protect drivers, and that virtualisation layer adds overhead to exactly the kind of work games do. If your stutter is CPU-bound and you are on a machine you control, it is a reasonable trade. On a shared or work machine, leave it alone — the performance is not worth the exposure.
Why does my game stutter only when I turn the camera?
That is traversal stutter, and it is an asset streaming problem rather than a rendering one. Turning reveals geometry and textures the engine had not loaded, so it fetches them from disk mid-frame. It is most severe on hard drives and on games installed on a slow SATA SSD, and it is worse when your VRAM is already full because the engine has to evict something before it can load anything. Moving the game to an NVMe drive and dropping texture quality one notch usually removes it.
About the author
PC Hardware & Performance Editor
Marcus has been building, breaking and repairing gaming PCs since 2011, first as a weekend favour for friends and then for eight years as a bench technician at an independent repair shop in Portland, where roughly a third of the job was diagnosing machines that "ran fine yesterday".
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.