Why Is My PC Stuttering in Games? Frame Stutter vs Low FPS (2026)

By LK Wood IV · 2026-07-10 · ~9 min read · St. Louis County, MO

Search “PC stuttering in games” and every guide hands you the same 20-item checklist: update drivers, close background apps, turn off G-Sync, turn on G-Sync, reinstall Windows. People try all of it, in random order, and post the same thread a week later - “tried EVERYTHING, high-end rig, still stutters.” The reason the checklist fails is that “stuttering” is three different problems wearing the same word, and the fix for one does nothing for the others.

So before you change a single setting, do two things: figure out which of the three problems you actually have, then read the pattern that tells you the cause. Get that right and the correct fix is usually short and obvious.

Here is the whole problem in one picture. Two rigs, both averaging 120 FPS. One is butter-smooth, the other stutters badly - and the difference is invisible to the FPS counter because it lives in the distribution of frame times, not the average. This is where your frames actually land:

First: is it actually stutter?

Three completely different things get called “stuttering,” and they need opposite fixes:

• Low FPS - the whole game is just slow (a steady 35 FPS everywhere). The frames are evenly spaced, there’s just not enough of them. Fix: lower settings/resolution or get more GPU. This is not stutter.
• Frame-pacing stutter / hitching - the average FPS looks fine or even high, but the game lurches: brief freezes, hitches when you move or enter a new area, or a constant micro-jitter. The frames are arriving unevenly. This is the real topic of this guide.
• Network lag - only in online games: your character rubber-bands or warps while the local framerate is perfectly smooth. Fix lives in your connection, not your PC.

The tell that separates them is your 1% and 0.1% low FPS, not the big average in the corner. Average FPS hides the gaps between frames - a single 50ms frame buried in a stream of 8ms frames barely dents a 120 FPS average, but your eye catches it every time. The 0.1% low is exactly that worst frame, and it’s the number that tracks how smooth the game feels. A rig showing 300 FPS average with 0.1% lows of 15 FPS will stutter worse than a locked, even 90.

Measure your frametimes (the step everyone skips)

You cannot fix pacing by feel. Turn on a frametime graph and the problem becomes visible:

• In-engine or launcher overlay - many games and the Steam overlay show a frametime line. Steam’s performance overlay (Shift+Tab → Performance) has a detailed mode with a frametime graph.
• RTSS / MSI Afterburner - the enthusiast standard; add the “Frametime” graph, not just FPS.
• Intel PresentMon - a free, vendor-neutral capture tool that logs frametimes and 1%/0.1% lows to a file you can actually read back.

A healthy game draws a nearly flat frametime line. Stutter shows up as spikes shooting up off that line - each spike is one frame that took too long, and that’s a hitch you felt. Watch the graph and your GPU usage together for a minute of real gameplay and note two things: are the spikes regular (every few seconds like clockwork) or event-driven (only when you move, load, or enter a new zone), and does GPU usage stay near 99% or drop when a spike happens. Those two observations narrow the cause more than any checklist.

Route by the pattern

This is the shortcut the 20-item lists skip. Match your frametime-graph behavior to a row and you’ve found the likely cause before you change anything.

The single most useful clue is whether the GPU is pinned or coasting while it stutters. Pinned at 99% and still hitching points at shaders, VRAM, or pacing; dropping to 50-70% points at the CPU, RAM, or a background thread stealing time.

The causes, and the fix for each

Shader compilation (new areas, right after an update)

Modern DirectX 12 and Unreal Engine games compile shader programs on your specific GPU the first time each effect appears. While a shader compiles, that frame stalls - so you get hitching in fresh areas or for the first hour after a new install or driver update, then it smooths out as the cache fills. The community fixes, cheapest first: let the game finish its up-front shader step instead of skipping it; on Steam, keep “pre-cached shaders” enabled in Settings → Downloads so Steam downloads shaders others already compiled; and after a graphics driver update, clear the DirectX Shader Cache (Windows Disk Cleanup → DirectX Shader Cache) so it rebuilds clean. NVIDIA’s driver and the NVIDIA App added background shader-compilation handling in 2026 that helps here; keep the driver current and its shader cache size set generously. If a game is notorious for shader stutter (many UE5 titles are), that’s the engine, and a community patch or the title’s own “compile shaders” option is the real fix.

Background tasks and DPC latency (regular hitch, every few seconds)

A hitch that arrives on a clock - every few seconds no matter the game - is almost always something outside the game waking up. The usual suspects: RGB and fan-control suites, hardware monitors polling sensors too fast, browser tabs with hardware acceleration, Discord/overlay capture, cloud sync (OneDrive/Dropbox), the Xbox Game Bar’s background recording, and antivirus scans. Close them one at a time and watch the frametime graph. If hitches persist with everything closed, run LatencyMon (free) - it points at the specific driver holding the CPU too long. The fix is usually updating or rolling back a network, audio, or chipset driver, since those are the classic DPC-latency offenders. Turning off Game Bar background capture and browser hardware acceleration clears a surprising number of these.

A CPU or RAM bottleneck (FPS dips, GPU coasting at 50-70%)

If GPU usage falls when you stutter, the graphics card is idling while it waits on the rest of the system - the full diagnosis for a coasting card lives in low GPU usage: real bottleneck vs fake. The most common free fix by far: your RAM is running at its slow default speed because XMP (Intel) or EXPO (AMD) was never enabled in the BIOS - flip it on and stutter and 1% lows often improve immediately. Beyond that, a genuine CPU bottleneck (frequent in simulation, strategy, and busy open-world scenes) shows as maxed CPU threads and coasting GPU; there’s no setting that fully fixes it, but closing background CPU load, capping FPS to a steady number, and making sure the CPU isn’t thermal-throttling all help. If your CPU is running hot, throttling itself reads as exactly this stutter - see CPU overheating to rule that out. Builders on r/pcmasterrace have chased “ghost” micro stutter on high-end 9800X3D/RTX 50-series rigs all the way down to the CPU being power-choked on a weaker board, GPU usage collapsing to 50% under transient load - a reminder that “coasting GPU” can mean power delivery, not just a slow CPU.

VRAM overflow (stutter that worsens over a session)

If a game runs smooth for ten minutes then degrades into stutter, or stutters hard only at high texture settings, you may be out of VRAM. When the card runs out of video memory it swaps textures across the PCIe bus, and every swap is a hitch. Drop texture quality one notch, turn off frame generation (it costs VRAM), and watch whether dedicated VRAM usage is sitting at the card’s limit. If it is, you’re asking for more than the card holds - our guide to how much VRAM you need has the real numbers by resolution.

Frame pacing and VRR (jitter/tearing near your refresh rate)

An uncapped game whose FPS swings wildly delivers frames at constantly changing intervals, which your eye reads as stutter even at high averages. Two moves smooth it. Cap your FPS to a rate your PC can hold steadily (a stable 90 beats a jumpy 90-200), using an in-engine limiter or RTSS. And if you have a G-Sync/FreeSync display, cap a few frames below your refresh - 141 on a 144Hz panel - to stay inside the VRR window where the monitor syncs to the GPU. That combination kills both tearing and range-exceed stutter. If tearing itself is the visible problem, fixing screen tearing covers the V-Sync/VRR interplay in full.

After a Windows update (started out of nowhere)

If smoothness vanished right after a Windows feature update, treat it as a regression, not a hardware fault. Do a clean graphics driver install (DDU then reinstall), then flip Hardware-Accelerated GPU Scheduling long enough to see whether the stutter follows it. Put it back on afterwards on a modern card. Our HAGS on-or-off guide makes that case in full, including NVIDIA’s requirement that DLSS Frame Generation only runs with it enabled. Check the GPU vendor’s forums for a known-issue driver, and roll back if a specific driver version introduced it.

The quick-win order

If you want a sequence rather than a diagnosis, do these free steps first, in order, checking the frametime graph after each:

1. Enable XMP/EXPO in the BIOS - the biggest single new-build win.
2. Close background apps - RGB suites, browsers, capture/overlays, sync, monitors.
3. Clean-install the current GPU driver (DDU), then let a couple of games build their shader caches.
4. Cap your FPS to a steady number and enable G-Sync/FreeSync a few frames below refresh.
5. Confirm the CPU isn’t throttling and the RAM profile is actually applied.

Only after those - if a frametime graph still shows spikes you can’t explain - do you start looking at DPC latency, VRAM limits, or hardware. Most stutter dies somewhere in the first four steps; the people who “tried everything” almost always tried them blind, in the wrong order, without ever looking at a frametime graph. If your system is freezing outright rather than hitching, that’s a different problem - computer keeps freezing covers hard locks - and if a specific game crashes to desktop instead of stuttering, start with the GPU driver crash fixes.