Why Games Stutter Even at High FPS — and How to Fix It

You're getting 120 FPS. The game still feels awful.

This is the most common and most misdiagnosed problem in PC gaming, and it happens because average FPS is the wrong number. A frame rate counter reading 120 tells you 120 frames arrived in the last second. It tells you nothing about when — and if 118 of them arrived smoothly while two took 40 milliseconds each, you felt those two and ignored the rest.

That's stutter. It isn't one problem with one fix; it's at least five different failures that all produce the same sensation. Here's how to tell them apart, and what to do about each.

First: Stop Watching the Wrong Number

Before changing a single setting, change what you're measuring.

Watch frametimes, not FPS. Frametime is how many milliseconds each frame took. A steady 16.7 ms is a perfect 60 FPS. A sequence of 16, 16, 45, 16, 16 averages out to something that still reads near 60 on a counter, but you will feel that 45.

Most overlays — the Steam overlay, MSI Afterburner/RivaTuner, Nvidia's and AMD's built-in performance panels — can display a frametime graph. Turn it on. A flat line is good. Spikes are your problem, and when they spike tells you which problem you have.

Then look at 1% lows. The 1% low is roughly the frame rate of your worst 1% of frames. If your average is 120 and your 1% low is 110, you have a smooth game. If your average is 120 and your 1% low is 35, you have a stutter problem that no amount of extra average FPS will fix. This is also why what counts as a good FPS is a more complicated question than the number on the box.

Now match your symptom to one of the five below.

1. Shader Compilation Stutter

Symptom: Hitches in the first 20–60 minutes of a new game, or the first time you see a new weapon, effect or area. Often gone on a second playthrough of the same section. Comes back after a GPU driver update.

Cause: Modern APIs — DirectX 12 and Vulkan — moved shader compilation out of the driver and into the game. When a game encounters a graphics pipeline it hasn't built yet, it compiles it right then, on your CPU, mid-frame. The result is a hitch. This is the signature failure of Unreal Engine 5 titles, and it's why a game can feel broken for an hour and fine afterwards.

What you can do now:

• Let the precompilation step finish. If a game offers a "compiling shaders" screen or an optional precache pass, run it. Skipping it moves the pain into gameplay.
• Don't skip the first-run warmup. Play a low-stakes area for ten minutes before judging performance.
• After a driver update, expect a repeat. The shader cache is invalidated. This is normal, not a broken install.
• Don't clear your shader cache as a troubleshooting step unless something is genuinely corrupt. You're just paying the cost again.
• Increase the driver shader cache size. In the NVIDIA Control Panel and AMD's Adrenalin software you can raise the cache limit from the default — useful if you rotate between many games. Our NVIDIA settings and AMD Radeon settings guides cover where these live.

The real fix is arriving. Microsoft's Advanced Shader Delivery, part of the DirectX Agility SDK, moves compilation off your machine entirely: shaders are precompiled for specific GPU and driver combinations and downloaded when you install the game or update your driver. Microsoft's own demonstration has Forza Horizon 6 first-launching in about four seconds with the feature enabled, versus nearly a minute and a half without it, on a Radeon RX 7600 and Ryzen 7 5800.

The catch is rollout. It currently works on AMD Radeon GPUs, and only for games launched through the Xbox app. Nvidia support — which covers the large majority of desktop gaming GPUs — is expected later this year, and Intel has committed to implementing it. Coverage also depends on games and storefronts adopting it, which is why reporting on the feature has framed full implementation as a multi-year project rather than a patch.

Individual games are also solving it themselves. Gears of War: E-Day is shipping precompiled shader delivery as a headline PC feature — we covered the full list — and it's arguably the most valuable thing on it.

2. Traversal Stutter

Symptom: Hitches specifically when you move — crossing into a new area, turning a corner into a dense scene, fast travel, a vehicle at speed. Standing still is fine.

Cause: The game is streaming assets off your drive and decompressing them as the world loads in around you. When the pipeline can't keep up, everything waits.

Fixes:

• Install on an NVMe SSD. This is the single biggest lever. A SATA SSD is acceptable; a mechanical hard drive is not, and hasn't been for years. Several 2026 releases now list an SSD as a hard requirement rather than a recommendation. See how much SSD storage you need if you're planning around this.
• Lower texture streaming quality and foliage/vegetation density. These two settings drive streaming volume more than almost anything else.
• Leave free space on the drive. A nearly full SSD writes and reads more slowly.
• Accept that some of it isn't yours to fix. Beast of Reincarnation, released last week to solid reviews, ships with traversal stutter that shows up on hardware well above its recommended tier. When the engine's streaming is the problem, settings only soften it.

3. VRAM Exhaustion

Symptom: The nastiest one. Fine for five or ten minutes, then progressively worse. Textures load in blurry and sharpen late. Hitching that gets worse the longer you play, and resets when you restart.

Cause: You've allocated more video memory than the card has. The GPU starts moving data back and forth across the PCIe bus to system RAM, which is dramatically slower. Unlike a GPU that's simply too slow — which gives you a low but steady frame rate — running out of VRAM produces exactly the jagged, unpredictable behaviour that feels worst.

Fixes:

• Lower texture quality one notch. Texture resolution is the largest VRAM consumer and, at one step down, usually the least visible loss. Our graphics settings that matter most ranks the trade-offs.
• Turn off or reduce ray tracing. RT carries a significant VRAM cost on top of its frame cost.
• Watch actual VRAM usage in an overlay, not the number the game's menu estimates. Menus guess; overlays measure.
• Frame generation increases VRAM use. If you're near the limit, it can push you over.
• Know your ceiling. How much VRAM do you need has the current numbers by resolution — and it matters more than usual right now, given that memory pricing is what's driving GPU prices up this month.

4. CPU Spikes and Bad 1% Lows

Symptom: Consistent hitching in crowded scenes, large multiplayer matches, big cities, heavy physics or particle moments. Lowering your resolution or graphics settings changes almost nothing.

Cause: Your CPU is the limit, not your GPU. That's the diagnostic: if dropping to 720p Low doesn't improve your frame rate, you are not GPU-bound.

Fixes:

• Confirm it first with the bottleneck calculator rather than guessing.
• Turn down CPU-side settings, which are a different list from the GPU-side ones: crowd density, draw distance, view distance, physics quality, shadow count (as opposed to shadow resolution).
• Check your RAM is running in dual channel and at its rated speed. A single stick, or a kit running at JEDEC defaults because XMP/EXPO was never enabled in BIOS, costs real frames in CPU-bound games. This is the most common free performance fix there is — see how much RAM for gaming.
• Understand what you'd be buying. If you're considering an upgrade, cores vs clock speed and which X3D CPU to buy cover what actually helps games, and the CPU ranking shows where yours sits.

5. Frame Pacing and Display Mismatch

Symptom: Regular, rhythmic judder rather than random spikes. Feels worst when your frame rate hovers right around your monitor's refresh rate. The counter looks great.

Cause: Frames are being produced at an uneven cadence, or delivered out of sync with the display's refresh.

Fixes:

• Cap your frame rate a few FPS below your refresh rate when using G-Sync or FreeSync — for a 144 Hz panel, cap around 138–141. This keeps you inside the variable-refresh window instead of bouncing off the ceiling.
• Use one frame limiter, not three. In-game, driver-level, and RTSS all fighting each other produces worse pacing than any one of them alone.
• Turn variable refresh on. If your monitor supports G-Sync or FreeSync and it isn't enabled in the driver control panel and the monitor's own menu, it isn't on. Our monitor buying guide covers what your panel can do.
• Uncapped isn't always better. Beast of Reincarnation is a current example: unlocking above 60 introduces stutter on strong hardware, and a 60 cap produces the smoother experience. A locked 60 beats a fluctuating 85 more often than people expect.

The Fix Order That Actually Works

When you don't know which one you have, work through this in order. It's arranged by effort-to-payoff, and each step is cheap.

1. Clean-install the current GPU driver. Not an upgrade over the top — a clean install. This resolves more launch-week stutter than anything else on this list.
2. Confirm the game is on an SSD, with free space on the drive.
3. Turn on a frametime graph and note when it spikes. That single observation usually identifies the category.
4. Cap the frame rate to something your system holds consistently. Stable beats high.
5. Enable XMP/EXPO in BIOS and confirm dual-channel RAM.
6. Close overlays and background applications — Discord, browser tabs, capture software, RGB utilities. Test with everything off, then add back.
7. Try Hardware-Accelerated GPU Scheduling both ways. HAGS genuinely helps some systems and games and hurts others. There is no universally correct setting; test it. It's in Windows Settings → System → Display → Graphics, and covered in our Windows 11 gaming settings guide.
8. Set the Windows power plan so the CPU isn't downclocking mid-session.
9. Lower textures one notch to rule out VRAM.
10. Test at 720p Low. No improvement means CPU-bound. Big improvement means GPU-bound. This is the cleanest diagnostic in PC gaming and takes 30 seconds.

If nothing helps and the game is crashing as well as stuttering, that's a different problem — 10 fixes for games that keep crashing covers it.

Bottom Line

Stutter is a frametime problem. Chasing a higher average FPS to fix it is the single most common wasted upgrade in PC gaming — people buy a faster GPU to solve a CPU bottleneck, a VRAM limit or a shader compilation hitch, and are baffled when the hitching survives the purchase.

Diagnose first: watch the frametime graph, note when it spikes, and test at 720p Low to find out which half of your system is the ceiling. Then fix the category you actually have.

And if you're weighing hardware rather than settings, do it with numbers instead of vibes — Can I Run It checks a specific game against your exact CPU, GPU and RAM, and the FPS calculator estimates what you'd actually gain before you spend anything. In a year where GPU prices are climbing again, the upgrade you don't need to make is the best deal available.