How to Fix Random Stutters in Games (Step-by-Step Troubleshooting)

Random game stutters usually come from shader compilation, driver issues, Windows graphics settings, background apps, or storage/thermal bottlenecks. This step-by-step checklist helps you isolate the cause quickly, apply

TL;DR

• Make sure it’s stutter (spikes in frame times), not low FPS. Use a repeatable test spot in the game.
• If the stutter seems to happen mostly just after updates/new areas are added: look to shader compilation + shader cache.
• Do a clean install of the GPU driver (or vendor clean-up) if it started “all of a sudden.”
• Toggle Windows graphics features on and off, one at a time (HAGS, VRR, Optimizations for windowed games).
• Shut down overlays/background recorders and try (Discord/Steam overlay, capture tools, RGB suites).
• If that didn’t help, clean boot Windows to identify the conflicting service/start-up app.

What “stutter” usually is (and how it differs from low FPS)

You’ve seen low FPS, where it’s just slow, no way around it. “Stutter” is the art of being slow some of the time but showing you a “fine” average FPS overall, just freezing, hitching for a fraction of a second. In practice, stutter is very close to always being a frame-time problem (one or more frames, taking too long to draw).

The idea is to make the stutter happens on-demand, and then start changing things one-at-a-time until it no longer happens. Change five things at once, and you’ll never know what removed it, and what to go back to later.

Step 1: Confirm the pattern (the 3-minute stutter test)

1. Pick a repeatable scenario: the same save point, same area of a map, same camera pan, or built-in benchmark.
2. Run the test for 2–3 minutes and write down what you see: (a) how often it hitches, and (b) what were you doing when it hitches (turning the camera, entering a new area, opening menus, combat, etc).
3. Now repeat once after a full PC reboot (this matters for shader caches, background tasks, and driver state). If the stutter is ONLY during online play, throw in one quick offline test (single-player/training mode) so you don’t spend a lot of time on graphics fixes for what’s actually a networking problem.

Step 2: Use this quick diagnosis table to choose the right branch

Step 3: Fix shader compilation stutter (the most common cause)

Shaders are software snippets for the GPU. Many games compile shaders when they start (or during gameplay), and compilation is a frequent culprit for stutter here. Shader caches exist so as not to have to recompile the same shaders every time you run the game. Sometimes the cache isn’t large enough or gets wiped/corrupted – when this happens stutter comes back.

3A) NVIDIA: bump up Shader Cache Size (often helps instantly)
Close your game. Open NVIDIA Control Panel → Manage 3D settings. Find “Shader Cache Size.” Bump it up (for many users, 5 GB or 10 GB is a reasonable test; if you’ve lots of free SSD and play a lot of colossal games, feel free to test higher). Click Apply and relaunch your game. Ping yourself back to the 3 minute stutter test from Step 1.
Why this works: NVIDIA informs us “Shader compilation during gameplay is a common cause of stuttering,” and that the “Driver shader cache stores compiled shaders, saving time on shaders that have already been compiled during previous runs of the game. When the cache’s size limit is too small, older shaders can be ejected from the cache and that can result in stuttering.”

3B) NVIDIA: delete/rebuild the NVIDIA shader cache (hit & miss debug)
If your stutter began suddenly (especially if you might have encountered some crashes/visual artifacts, or bad hitching first) try clearing the NVIDIA shader cache, so it can be rebuilt. Follow NVIDIA’s guidance to temporarily set Shader Cache Size to Off, then reboot, then delete cache files by following one of NVIDIA’s methods, then re-enable shader caching. Expect some stutter as the cache is rebuilt, and then retest in the same scenario.

3C) AMD Radeon: reset shader cache AMD Software: Adrenalin Edition
Close your game. Open AMD Software: Adrenalin Edition. Go to Settings → Graphics (then expand Advanced if needed).
Find “Reset Shader Cache” and run it.
Launch the game and re-test. Expect a short term increase in stutter until the cache is rebuilt.

AMD describes shader cache as a means to reduce CPU usage and speed loading times by compiling and storing frequently used shaders, and the reset option removes saved shader cache files (which can resolve issues if they have become corrupt).

3D) Windows/DirectX: Know why clearing “shader cache” sometimes helps (and sometimes hurts)

DirectX 12 supports per-title, disk-based shader caches that persist from run to run, and can be cleared externally (say, by a disk cleanup utility). Clearing caches can fix corruption, but it can also reintroduce stutters until caches rebuild—treat as a test when targeted, not routine maintenance.

Step 4: Clean GPU driver

If your stutters noticeably started after a driver update (or you’ve been updating drivers “on top of” old ones for ages), do a clean reinstall. It’s one of the high-impact fixes for sudden stuttering.

4A) NVIDIA: Use “Perform a clean installation” built in options

1. Download the NVIDIA driver you want to install (latest or known-stable).
2. Run the installer → select Custom (Advanced).
3. Check “Perform a clean installation.”
4. Finish the install and reboot.
5. Re-test with the exact same in-game scenario from Step 1.

4B) AMD: uninstall or use AMD Cleanup Utility (for stubborn driver conflicts)

1. First try a normal uninstall of AMD Software via Windows “Installed apps”, then re-install the Adrenalin version you want.
2. If still having problems, the AMD Cleanup Utility can be run before re-installing AMD Software: Adrenalin Edition to remove AMD graphics/audio driver software and prepare your system for a fresh install (AMD runs it in Safe Mode).
3. Re-install AMD Software: Adrenalin Edition and reboot; retest.

4C) Intel (integrated graphics): run an Intel clean installation

1. Download the right Intel graphics driver for your system (or use your laptop/desktop manufacturer’s driver if recommended).
2. Run the Intel installer – select the option to execute a clean installation if present.
3. Reboot; retest in-game for the stutter scenario.

Step 5: Fix “windowed / borderless-only” stutter (presentation mode issues)

If the game stutters (or kills your FPS) mainly in borderless/windowed mode but improves in exclusive fullscreen, dig into Windows’ presentation features. Windows 11 has “Optimizations for windowed games” for DirectX 10/11 windowed/borderless games, and lets you toggle it globally or by game. Do the following:

1. Settings → System → Display → Graphics. Toggle “Optimizations for windowed games” ON, retest.
2. If stutter gets worse, toggle it OFF, retest.
3. If your game offers both Exclusive Fullscreen and Borderless options, see which if either of those help (don’t just assume Borderless is better).

Step 6: Toggle Windows graphics features that can cause stutter on some systems (one at a time)

6A) Hardware-Accelerated GPU Scheduling (HAGS)

HAGS alters how GPU scheduling is performed. Microsoft documents the setting and where to find it in Windows graphics settings. If you suspect it is a factor in your stutter, the easiest way to find out for sure is to toggle it and retest.

1. Open Settings → System → Display → Graphics.
2. Select “Change default graphics settings” (wording varies by Windows version).
3. Toggle Hardware-Accelerated GPU Scheduling ON (or OFF) then reboot.
4. Retest in the same location and see if the change affected how frequently stutter occurred.

6B) Variable Refresh Rate (VRR), refresh rate, and Dynamic Refresh Rate (DRR)

A possible stutter culprit is a mismatch between the game frame cap, monitor refresh rate, and VRR/DRR behavior. Microsoft documents how to change refresh rate, and explains DRR at a high level. For testing purposes, start simple, with a stable configuration. Set your monitor as intended in Windows Advanced display (i.e. actual game refresh rate of 120 Hz or 144 Hz).

• If DRR is enabled and you think it could be capping a games’ refresh, disable DRR temporarily and retest.
• If you use VRR too, test VRR enabled, then VRR disabled (some multi-monitor setups are quite picky).
• In-game cap with a value just below your refresh rate and retest frame pacing.
• If you turn a lot of things off at once here, make sure that’s fine, then work your way through just one thing at once.

Turn OFF (temporarily):

• Xbox Game Bar widgets
• Discord overlay
• Steam overlay
• GeForce overlay
• AMD overlay
• 3rd party FPS counters

Pause downloads/updates:

• Steam downloads
• Xbox app downloads
• Windows Update
• Epic/Battle.net game launchers that update themselves in the background

Close hardware companions:

• RGB control suites
• Motherboard monitoring tools
• Fan controllers
• Peripheral software (mouse/keyboard) if it has actual polling/overlays

If you stream/record: test a run with recording OFF. If your stutter goes away, your fix is most often in encoder settings (NVENC/AMF), bitrate spikes, or storage write speed.

How to verify: If just disabling some manner of overlay fixes the problem for example, start re-enabling one at a time until you find what’s the culprit. Leave the one that’s the issue off, or update it, don’t just leave everything off forever.

Fix power & thermal “throttling” (on Laptops):

• Make sure to plug-in jack power (many hard limit GPU power on battery, causing “random” stutter)
• Set Windows power mode to “Best performance” (or your OEM gaming literally mode).
• Force the game to use the High performance GPU in Settings → System → Display → Graphics (especially if you have an iGPU + dGPU).
• Check temperatures whilst the stutter happens. If either CPU temp or GPU temps go up and their clocks drop significantly, you’re throttling (clean the dust, improve airflow, adjust the fan curve, reduce power limits if you can safely do so).

Step 9: Fix storage related stutter (asset streaming, low free space)

1. Confirm that the game is on an SSD. Preferably an NVMe for newer open-world titles.
2. Make sure you have healthy free space on that drive; games that stream lots of assets are prone to stutter when the drive is nearly full.
3. Temporarily disable real-time scanning for the folder with the game in, as a test (any antivirus can hitch if it is doing large file reads).
4. If you are relying on Storage Sense/Cleanup recommendations as your way to free space, then do that after testing to avoid cleaning up caches in the middle of this process unless you are testing for caches.

Microsoft documents how Storage Sense and Cleanup recommendations can help clear up temporary files in order to help free up drive space, and low disk space can also lead to side-affect performance problems (i.e. updates failing, windows paged space being slower, etc as caches cannot grow).

Step 10: Apply the “two toggle” rule for stutter you can’t explain

If you’ve done shader cache + clean driver install and still get random stutters, your next best move is to see if the stutters are (A) game-specific or (B) system-wide.

1. Toggle #1: Run the game with ALL third-party overlays turned off (Step 7).
2. Toggle #2: Change your display mode (Exclusive Fullscreen ↔ Borderless) and retest.

If either toggle makes the stutter disappear, you’ve narrowed the problem down to a specific interaction (overlay hook or presentation mode). If neither makes any difference, move on to a clean boot (Step 11).

Step 11: Clean boot Windows and find a conflicting service or startup app

A clean boot of Windows loads the system with a minimum set of drivers and startup programs. It’s one of the best ways to catch “something in the background” that’s responsible for the periodic hitches (telemetry tools, audio enhancements, overlay services, device utilities, etc.).

1. Open Search and type msconfig. Open System Configuration.
2. On the Services tab, check Hide all Microsoft services, then click Disable all and Apply.
3. On the Startup tab, open Task Manager and click to disable any startup apps. Start over and test the stutter scenario again.
4. And if the stutter is gone, start re-enabling items back in halves until you work out WHAT service/app re-introduces the stutter.

Step 12: When to suspect hardware (and how to test safely)

• If the stutter happens across the games and desktop, and it survives a clean boot: check temperatures, check RAM stability (disable XMP/EXPO as a test), storage health (SMART).
• If the stutter is accompanied by USB dropouts/a crackle from audio: try with less stuff connected, update chipset/usb drivers, try a different USB port/controller.
• If the stutter appears ONLY after a fun half hour – 60 minutes of play: suspect heatsoak and throttling (Step 8)

Common mistakes: (together make stutter hunting a prick)

• Clearing shader caches multiple times while testing (you keep making the damn shader thing to recompile only for testing it).
• Benchmarking in different places each time (you can’t repeat).
• Also in changing multiple things and calling a new test (no root cause).
• Chasing “optimization packs” or tweaking things in the registry rather than a clean install + toggles in measured increments.
• Ignoring the display mode (Exclusive vs Borderless) and the alignment of refresh on cap.

FAQ