Game Stuttering: Causes and How to Fix FPS Lag Spikes

You are mid-fight in a demanding open-world title, framerates reading a smooth 90 FPS on the counter, when the screen suddenly lurches — one ugly freeze of 200 milliseconds that costs you the encounter. That is game stuttering, and it is arguably more disruptive than a consistently lower framerate. A locked 45 FPS feels more playable than 90 FPS punctuated by recurring hitches, a fact that Digital Foundry’s frame-pacing analyses have demonstrated repeatedly across console and PC platforms.

Understanding why stuttering happens is the first step toward eliminating it. The causes range from GPU driver bugs to Windows power settings, and most of them have actionable fixes that cost nothing but time. This guide walks through the most common culprits and the concrete steps to address each one.

What Game Stuttering Actually Is

Framerate and frame pacing are two different things. Framerate is how many frames your hardware produces per second. Frame pacing is how evenly those frames are spaced in time. Stuttering is almost always a frame-pacing problem: instead of frames arriving every 11 ms at 90 FPS, a stutter means one frame took 180 ms while the next took 2 ms. The average is still 90 FPS, but your eyes register a freeze followed by a blur.

Monitoring tools like CapFrameX or the 1% Low and 0.1% Low metrics in MSI Afterburner’s OSD reveal this clearly. A well-optimized session at 90 FPS average should show 1% Lows no further than 20–25% below the average. If your 1% Low drops to 15 FPS while average sits at 90, you have a serious pacing problem regardless of what the counter reads at any given moment.

Identifying the stutter type before applying fixes saves hours of trial and error. Is it periodic (every 30 seconds, like clockwork)? Random and brief? Only in the first minutes of play? Each pattern points to a different root cause.

It is also worth recording a short gameplay session using CapFrameX’s capture mode and reviewing the frame-time graph afterward. Spikes that appear visually in the graph but feel subtle during play are early warnings of a worsening problem, and catching them before they become severe saves considerably more diagnostic time later.

Shader Compilation and DX12/Vulkan Pipeline Stalls

The most widely reported stutter type in modern PC games is shader compilation stutter. Under DirectX 12 and Vulkan, games compile graphics shaders on-the-fly during gameplay rather than precompiling them at launch. Every time the engine encounters a new shader combination — a new lighting condition, a new material — the CPU halts frame delivery for tens to hundreds of milliseconds while it compiles that shader to your specific GPU’s instruction set.

This explains why the first playthrough of a game like Hogwarts Legacy or The Last of Us Part I on PC feels janky while subsequent sessions feel far smoother: the compiled shaders are cached to disk. Fixes for this issue include:

• Let shader pre-compilation finish at launch. Most modern games display a progress bar on first boot. Do not skip it or alt-tab during this phase.
• Delete and rebuild the shader cache after major GPU driver updates, since old cached shaders become invalid. On Windows, shader caches typically live under %LocalAppData%D3DSCache or within the game’s own folder.
• Enable Resizable BAR (ReBAR) if your CPU and GPU support it. AMD and Intel data show this reduces certain pipeline stalls by giving the GPU direct access to system memory, cutting CPU involvement in asset streaming.

Games using DX11 largely avoid this problem because they compile shaders ahead of time, which is one reason older titles often feel more consistent on mid-range hardware despite lower visual fidelity.

VRAM Overflow and Asset Streaming Bottlenecks

When a game’s active asset set exceeds your GPU’s VRAM capacity, textures and geometry must spill into system RAM and be fetched across the PCIe bus in real time. That round-trip — even on PCIe 4.0 — introduces latency that manifests as stutters whenever you round a corner or enter a new area.

A 4 GB GPU running a title that targets 8 GB VRAM will stutter heavily in dense scenes. MSI Afterburner’s VRAM usage graph is blunt about when you are in trouble: sustained usage above 95% of your card’s capacity predicts stutters reliably. Practical fixes:

• Lower texture quality one step. This single setting often drops VRAM usage by 1–2 GB with minimal visible impact at 1080p.
• Reduce draw distance in open-world games, which cuts the number of assets that must reside in VRAM simultaneously.
• Close background applications that use GPU memory — certain browsers with hardware acceleration, video players, and OBS running a GPU encoder all consume VRAM even when minimized.
• Upgrade storage to NVMe SSD if you are still on HDD or SATA SSD. Faster storage doesn’t eliminate VRAM overflow, but it reduces the penalty when the engine must pull assets from disk, which is common in streaming open worlds like Cyberpunk 2077.

One underappreciated factor is resolution scaling. Running a game at native 4K forces the engine to keep higher-resolution mip levels in VRAM at all times. Dropping to a quality DLSS or FSR preset at 4K can free several hundred megabytes of VRAM headroom without a perceptible sharpness penalty at typical viewing distances, providing meaningful relief before you consider a hardware upgrade.

GPU Driver Issues and Overlay Conflicts

GPU drivers are a frequent but overlooked stutter source. Both NVIDIA and AMD release updates that occasionally introduce regressions in specific game engines. A driver that improves performance in one title can add 80 ms hitches to another. Keeping a log of which driver version you installed alongside which games you started playing is a habit that pays off when hunting intermittent stutters.

Steps to isolate and fix driver-related stutters:

• Perform a clean driver install using DDU (Display Driver Uninstaller) in Safe Mode before installing a new driver version. Partial installs over old drivers leave registry and shader cache remnants that cause unpredictable behavior.
• Roll back the driver if stutter appeared immediately after an update. NVIDIA and AMD both allow rollback from Device Manager.
• Disable overlay software conflicts. Running NVIDIA GeForce Experience overlay, Discord overlay, Steam overlay, and MSI Afterburner OSD simultaneously is a known cause of intermittent hitches. Disable all but one to isolate the offender.
• Set power management mode to “Prefer Maximum Performance” in the NVIDIA Control Panel (or the equivalent in AMD Adrenalin). The default “Optimal Power” setting allows the GPU to downclock between frames, which introduces micro-stutters on systems with fast CPUs that submit frames quickly.

CPU Bottlenecks, Windows Settings, and Background Load

Game engines submit draw calls and simulation updates from the CPU before the GPU renders them. If the CPU cannot keep the command queue full — because it is bottlenecked by clock speed, too-few cores, or background tasks — the GPU starves and produces irregular frame intervals.

A CPU bottleneck typically appears in CPU-heavy scenarios: large crowds in strategy games, dense NPC AI in RPGs, physics-heavy destruction engines. To check if the CPU is the culprit, compare GPU utilization during stutter events. If your GPU drops below 95% utilization precisely when the stutter occurs, the GPU is waiting on the CPU.

Windows-specific optimizations that materially reduce CPU-induced stutters:

• Set Windows power plan to “High Performance” or “Ultimate Performance.” The balanced plan throttles CPU frequency in microseconds, introducing latency between game thread scheduling and execution.
• Disable Xbox Game Bar and Game DVR (Settings → Gaming → Xbox Game Bar). These background recording hooks inject into game processes and consume CPU cycles.
• Enable Hardware-Accelerated GPU Scheduling (HAGS) on Windows 11 with a compatible GPU and driver. HAGS reduces CPU-to-GPU scheduling latency, and benchmarks show it cuts micro-stutter in CPU-bound scenarios by a measurable margin on RDNA 2 and Ampere-class hardware and newer.
• Check for background CPU consumers using Task Manager sorted by CPU %. Antivirus real-time scanning of game folders is a classic offender; adding the game directory to your antivirus exclusion list often yields immediate improvement.

Frame Generation, VSync, and Sync Technology Mismatches

Adaptive sync technologies — NVIDIA G-Sync and AMD FreeSync — were specifically designed to eliminate tearing without the fixed-interval penalty of traditional VSync. But misconfiguring them introduces its own stutter type. Running G-Sync with VSync disabled in-game often causes frame queuing issues; the NVIDIA-recommended configuration is G-Sync on with VSync forced on through the Control Panel and an in-game framerate cap 3–4 FPS below the monitor’s maximum refresh rate. This prevents the framerate from hitting the ceiling and triggering VSync’s input-latency penalty.

Frame generation tools like DLSS Frame Generation and AMD Fluid Motion Frames can also introduce perceived stutter when the underlying framerate drops below approximately 55–60 FPS. These tools interpolate frames between real frames — when real-frame delivery becomes uneven, interpolated frames compound the irregularity rather than hiding it. Frame generation is a performance amplifier, not a stutter fix; stabilize the base framerate first.

For players whose monitors lack G-Sync or FreeSync, a reliable alternative is using RTSS (RivaTuner Statistics Server) to apply a hard framerate cap 3 FPS below the monitor’s refresh rate. This creates a frametime headroom buffer that prevents VSync stutter at the cost of a small amount of throughput.

Conclusion

Stutter is rarely one problem — it is usually two or three interacting simultaneously. Start by profiling with CapFrameX or Afterburner to identify the pattern, then isolate the most likely cause based on when and where the hitches occur. Fix shader cache issues before touching driver settings; confirm VRAM headroom before blaming the CPU. Applying all tweaks at once makes it impossible to know what actually worked, and you will be back to square one the next time a new game ships with its own quirks.

FAQ

Why does my game stutter even though my FPS counter shows a high number?

High average FPS and smooth gameplay are not the same thing. Stutter is a frame-pacing issue: one frame taking 10× longer than the others produces a visible hitch even if the average remains high. Use 1% Low metrics in MSI Afterburner or CapFrameX to see the true picture.

Does more RAM help with game stuttering?

Yes, in specific scenarios. If the game’s working set of assets exceeds your installed RAM, the OS pages data to disk, causing severe stutters. Most modern titles benefit from 16 GB; memory-intensive open-world games increasingly recommend 32 GB. RAM speed also matters — faster dual-channel kits reduce CPU latency, which matters in CPU-bottlenecked scenarios.

Will reinstalling the game fix shader compilation stutters?

Reinstalling does force the shader cache to rebuild, which can resolve corrupted cache issues. However, if the game engine itself compiles shaders on-the-fly (common in DX12/Vulkan titles), the stutter will return on the next new session until the cache is fully populated. The fix is patience on first play, not reinstallation.

Is game stuttering a sign that my GPU is dying?

Stutter alone is rarely a sign of hardware failure. Dying GPUs typically produce artifacts, driver crashes, or black screens alongside performance issues. Isolated stutter without other symptoms almost always has a software, driver, or configuration root cause. Run a GPU stress test like FurMark to rule out hardware instability before assuming component failure.

Does enabling HAGS always improve stutter?

Not universally. HAGS benefits are most pronounced on RDNA 2, Ampere, and newer GPU architectures with supported drivers on Windows 10 version 2004 or Windows 11. On older hardware or with outdated drivers, HAGS can introduce additional instability. Test it enabled for a session and disabled for another, using frame-time graphs as your benchmark rather than subjective feel.

Can running the game in fullscreen mode reduce stuttering?

Exclusive fullscreen mode gives the game direct control over the display output, bypassing the Windows Desktop Window Manager compositor entirely. This reduces the scheduling overhead that borderless windowed mode introduces, and can meaningfully improve frame-time consistency — particularly on systems where Windows’ desktop composition is competing with the game for GPU resources. If your game supports it, exclusive fullscreen is worth testing before exploring deeper software changes.