Low FPS Troubleshooting: A Step-by-Step Fix for Stutter

There's a specific kind of frustration that comes from a game that used to run fine. The frame rate sags, the camera hitches every few seconds, and suddenly a build you were proud of feels like a compromise. I've spent years chasing these gremlins across dozens of rigs, and the good news is that stutter and low FPS almost always have a findable cause. The trick is to stop guessing and start measuring, in the right order.

Below is the exact process I run through, from the cheap five-minute checks to the deeper diagnostics. Work top to bottom and you'll usually catch the culprit before you reach the end.

First, Separate "Low FPS" From "Stutter"#

These two problems feel similar in the chair but they're rarely the same fault, and treating them as one is the fastest way to waste an afternoon.

• Low FPS is a consistently low number. The game runs at 45 FPS the whole time. That points to raw horsepower, settings, or a bottleneck.
• Stutter is inconsistency. Your average might be a healthy 90 FPS, but every few seconds a single frame takes far too long and you feel a lurch. That points to something intermittent: shader compilation, background tasks, thermal spikes, or storage.

The tool that makes this distinction visible is frametime, not FPS. FPS is an average that hides the spikes. A frametime graph (available in MSI Afterburner/RivaTuner, CapFrameX, or your GPU vendor's overlay) shows each frame's render time as a line. A smooth line at 11ms means a locked 90 FPS. A flat line with occasional tall spikes is stutter, even if the FPS counter looks fine. Turn on a frametime graph before you change anything else, because it tells you which of the two problems you actually have.

The Five-Minute Checks#

Roughly half the low-FPS reports I look at get solved here, so don't skip them out of pride.

1. Update your GPU driver — but do it deliberately. Newest isn't always fastest; a recent driver occasionally regresses in a specific title. Grab the current one from NVIDIA, AMD, or Intel directly, and if performance drops right after an update, roll back one version and see.
2. Kill background apps. Browsers with a hundred tabs, Discord with hardware acceleration, overlays stacked three deep (Steam + Discord + GeForce Experience + a capture tool) all fight for CPU and GPU time. Close what you don't need and disable overlays you're not using.
3. Check your power plan. On a desktop, make sure Windows isn't running a power-saving profile. On a laptop, this is the single biggest one — plugged in versus on battery can halve your frame rate, because most laptops aggressively throttle the GPU on battery no matter what the settings say.
4. Confirm the game is using the right GPU. On laptops and some desktops with integrated graphics, a game can quietly launch on the iGPU. In Windows Graphics Settings, pin the game's executable to the high-performance GPU.
5. Look at free storage. A nearly full boot drive, especially a SATA or older NVMe one, slows everything down and worsens texture streaming stutter.

If the problem vanishes here, great. If not, it's time to measure.

Read the Overlay: Find Your Bottleneck#

Bring up an overlay that shows, at minimum, CPU usage (overall and per-core), GPU usage, GPU VRAM, and system RAM. Now play for a minute in a spot where the problem shows up and watch which resource is pinned.

GPU at 95–99%#

This is actually the healthy state for a demanding game. It means your graphics card is the limiting factor and it's working as hard as it can. If your FPS is still too low here, the fix is straightforward: lower settings or resolution. The heaviest hitters are usually:

• Shadows and ray tracing (huge cost, often modest visual gain past "high")
• Volumetric fog / clouds
• Screen-space reflections at ultra
• Render scale / resolution itself

Drop those first before you touch textures, which barely cost frame rate as long as you have the VRAM for them.

GPU below ~90%, one CPU core maxed#

This is a CPU bottleneck. Your graphics card is sitting there waiting for the processor to feed it. You'll see it most in CPU-heavy genres: simulation games, strategy titles, busy open worlds, and anything with lots of NPCs or physics. Fixes here are different:

• Turn OFF CPU-bound settings: draw distance, crowd density, physics detail, and often ray tracing (which has a hidden CPU cost).
• Lowering resolution won't help — that only offloads the GPU, which isn't your problem.
• Cap your frame rate to something your CPU can sustain. A stable 60 beats a jittery 75-to-50 swing every time.

VRAM full or near full#

If your VRAM usage is slammed against its limit, the GPU starts swapping texture data over the PCIe bus, and that produces some of the worst stutter you'll feel. Turn texture quality down a notch and watch whether the hitching stops. This is increasingly common on 8GB cards at 1440p with ultra textures and ray tracing stacked on.

Hunting Down Stutter Specifically#

If the frametime graph showed spikes rather than a low-but-flat line, work through these in order.

Shader compilation stutter#

Many modern engines (Unreal Engine 4/5 titles are notorious) compile shaders on the fly the first time an effect appears. The result is a hitch the first time you enter a new area, fire a new weapon, or trigger a new effect.

• If the game offers a "compiling shaders" step at launch or in settings, let it finish — don't skip it.
• Clear the shader cache after a driver update; a stale cache can cause a fresh round of compilation.
• Sometimes the honest answer is that a first playthrough of an area will stutter once and be smooth forever after. That's an engine trade-off, not your hardware.

Background and storage hitches#

Regular, clock-like stutter every 30 seconds or so often isn't the game at all.

• Windows Search indexing, antivirus scans, Steam downloading an update, or cloud sync all cause periodic disk contention. Watch your disk activity in Task Manager while the stutter happens.
• Games installed on a slow or dying drive stutter during texture streaming. Moving a title from a hard drive to an SSD is one of the most reliable stutter fixes there is.

Thermal throttling — the silent one#

This is the culprit people miss most, because the game runs fine for the first ten minutes and then degrades. That pattern is the tell.

Log your GPU and CPU temperatures over a longer session. Watch for:

• GPU core sustained around 83°C+ or hotspot/junction temps climbing much higher
• CPU hitting its thermal limit (commonly around 90–100°C depending on the chip) and dropping clock speed
• Clock speeds falling over time even as temps stay high — that's throttling in action

If you see it, the fixes are physical: clear dust from filters and fins, improve case airflow, re-check that fan curves aren't set too conservatively, and on an older machine consider that the thermal paste may simply be past its prime. A laptop that throttles hard often improves dramatically with a cooling pad and a raised rear edge, unglamorous but effective.

When Nothing Obvious Shows Up#

A few less common causes worth ruling out:

• VSync and frame-rate caps fighting each other. Double-check you don't have VSync forced in the driver and in-game, plus a third cap in something like RivaTuner. Pick one limiter. If you have a G-Sync or FreeSync display, cap your FPS a few frames below the monitor's max refresh for the smoothest result.
• Resizable BAR off (or on) can swing performance a few percent either way depending on the game — worth toggling in BIOS if you're chasing every frame.
• Windows power features like a mismatched refresh rate (running a 144Hz panel at 60Hz in display settings) will make everything feel worse than the numbers suggest.
• A single bad mod or overlay. If a previously-smooth game suddenly stutters, think about what changed. Test with a clean, unmodded profile.

Build a Repeatable Test#

The one habit that separates real troubleshooting from flailing: change one thing at a time and re-test the same scene. Pick a specific spot in the game, ideally a demanding one, and run the same 60-second loop after each change while logging frametime. If you alter five settings at once and the stutter goes away, you've learned nothing about which one mattered, and you'll be back here next month.

Conclusion#

Low FPS and stutter feel like mysteries, but they're really just a search for a bottleneck, and the bottleneck always leaves fingerprints. Start with the free five-minute checks, then let the overlay tell you whether your CPU, GPU, VRAM, thermals, or storage is the weak link. Separate a low-but-steady frame rate (a settings-and-horsepower problem) from genuine stutter (usually shaders, background tasks, or heat). Work methodically, change one variable at a time, and you'll not only fix the game in front of you, you'll understand your own machine well enough to fix the next one in minutes.