How to Fix Low FPS and Stuttering in PC Games: A Safe Step-by-Step Guide

Correction October 5, 2026: in the August 2026 Steam Hardware & Software Survey the most common VRAM bracket was 16 GB, not 8 GB (8 GB at 25.74 percent was second), and AMD's product guidance lists 16 to 24 GB for 4K, not 20 to 24 GB. Sources: Valve Steam Hardware & Software Survey; AMD Radeon VRAM product page.

Photo: Atahan Demir / Pexels · Pexels License

Updated September 15, 2026. Every figure below was checked against the sources at the end of this article on that date.

Most low-FPS guides fail for one reason: they treat "my game runs at 45 fps" and "my game hitches every ten seconds" as the same complaint. They are not. Average frame rate is a throughput number. Stutter is a consistency number, and it lives in the 1% lows and in the frame-time graph, not in the big number in the corner of your screen. A machine can gain 20 fps of average and feel worse, because the hitches got no better and now arrive at a different rhythm.

So this guide does two things in order. First it helps you find out what is actually limiting your machine. Then it gives you a reversible, safe sequence of changes, with a clear note on which of them touch average FPS and which of them touch stutter. Almost nothing touches both.

Know what normal looks like before you call yours broken

Context matters, because a lot of "my PC is bad" posts are really "my PC is average and the game is demanding." According to the Steam Hardware and Software Survey for August 2026, the single most common GPU among surveyed users was the NVIDIA GeForce RTX 3060 at 3.76 percent of systems, the 8 GB video memory bracket held 25.74 percent of systems, second to the 16 GB bracket, the most common system memory was 16 GB at 41.20 percent, and the most common primary display resolution was 1920 x 1080 at 50.52 percent. Eight CPU cores was the most common core count at 28.04 percent, and Windows 11 64-bit accounted for 70.97 percent of the surveyed base.

Read that as a baseline, not a target. If you are running a 2026 AAA release at 1440p on 8 GB of VRAM, you are above the most common resolution and one bracket below the most common VRAM figure, and a lot of your problem is likely budget rather than misconfiguration.

Diagnose first: six causes, six different symptoms

Microsoft's own DirectX team draws the basic distinction plainly. A workload is GPU-bound when the CPU "generates rendering instructions so fast that there are times during which the CPU idle[s]," and CPU-bound when "the GPU is able to make quick work of the instructions it is given, which means there are times during which the GPU is idle." Everything else in the table below is a variation on which part of the machine is waiting.

Cause	Symptom that identifies it	What to measure
GPU-bound	Low but steady frame rate. Dropping resolution moves it a lot. Frame time line is flat and high.	GPU utilisation sitting near 95-100 percent while CPU utilisation is well below that.
CPU-bound	Frame rate barely changes when you drop resolution. Worst in towns, crowds, large battles.	GPU utilisation clearly below 90 percent with one or two CPU threads pinned.
VRAM exhaustion	Fine for a few minutes, then textures go blurry or pop in, and hitches get worse the longer you play.	Dedicated GPU memory in use versus your card's total. Watch it climb over a 15 minute session.
Shader compilation	Sharp hitches the first time you see a new effect, weapon or area. Gone on a second playthrough of the same area.	Whether the hitches repeat in the same spot after a driver update wiped the shader cache.
Thermal throttling	First few minutes are fine, then frame rate settles noticeably lower and stays there. Fans loud.	CPU and GPU clock speeds over time, plotted against temperature, not a single peak reading.
Storage / streaming	Hitches tied to movement through the world (traversal), long level loads, assets appearing late.	Disk queue and read activity during the hitch, and whether the game is on an HDD or a full drive.

Two of these are worth expanding. On thermal throttling, Intel describes it as "a mechanism in Intel Processors to reduce the clock speed when the temperature in the system reaches above TJ Max (or Tcase)," and notes that on laptops the OEM decides the power and current limits, which is why an identical chip throttles differently in two different chassis. On shader compilation, NVIDIA's engineering guidance is direct: "PSO creation is where shaders compilation and related stalls happen," and developers are told to "avoid runtime PSO compilations as they most likely will lead to stalls." That is the honest answer to why some games hitch on first encounter with an effect and why a shader pre-compilation step at launch exists. It is a developer-side problem. You can wait out the pre-compile step and avoid wiping the cache, but you cannot fix it from the Windows settings app.

On VRAM, AMD's own product guidance suggests 8 to 16 GB for 1080p, 12 to 16 GB for 1440p and 16 to 24 GB for 4K, and cites a measured peak of 11.7 GB in Far Cry 6 at 1440p maximum settings with ray tracing enabled. AMD also states plainly that "having ample VRAM reduces visual issues that can occur, like texture pop-in." Treat vendor capacity advice as a sales-adjacent floor rather than gospel, but the 1440p-with-ray-tracing number is a useful, concrete reference point against the 8 GB that most surveyed Steam users actually have.

Settings: what each one costs and what it actually fixes

Costs below are directional bands rather than measured percentages, because per-setting cost is engine specific and no vendor publishes a universal table. The mechanism column is the part that transfers between games.

Setting	Frame-time cost	Visual cost of turning it down	Helps stutter or only average FPS?
Resolution scale / upscaler	Largest single lever. Cost scales with pixel count, which is the square of the linear scale.	Moderate. Softer image, some shimmer on thin geometry.	Mostly average FPS. Helps stutter only when the stutter came from a GPU that was already saturated.
Ray tracing / path tracing	Very large, and it raises VRAM use at the same time.	High in reflective or indoor scenes, near zero in bright outdoor ones.	Both. Turning it off is one of the few changes that reliably cuts hitching on 8 GB cards.
Texture quality	Near zero while textures fit in VRAM. Cliff-edge once they do not.	High. This is the setting people notice most.	Stutter, and only stutter, and only if you are actually out of VRAM.
Shadow quality / resolution	Large, and it loads both CPU and GPU because extra shadow cascades mean extra draw calls.	Moderate. Visible mainly on shadow edges and at distance.	Both, when the game is CPU-bound in dense scenes.
View distance / crowd density	Large on the CPU side, modest on the GPU side.	Moderate to high in open worlds, low in corridors.	Stutter, especially traversal hitching in open worlds.
Anti-aliasing (TAA/MSAA)	Small for TAA, large for MSAA at high sample counts.	Low to moderate. Aliasing returns on edges and foliage.	Average FPS only. Rarely worth touching first.
Ambient occlusion, volumetrics, screen-space effects	Small to moderate each, but they add up.	Low individually.	Average FPS only.
Frame rate cap	Negative cost. It removes headroom you were not using.	None.	Stutter. A stable capped 60 feels better than an unstable 75.

The resolution lever is worth one concrete number. NVIDIA documents that its default upscaler modes "have input resolutions of 33%, 50%, 58%, and 66%" for Ultra Performance, Performance, Balanced and Quality respectively. Those are linear figures, so the pixel counts the GPU actually shades are roughly 11, 25, 34 and 44 percent of native. That is why the upscaler dominates every other setting on this list, and why the visual cost feels smaller than the arithmetic suggests.

What the Windows toggles really do

Three Windows settings get repeated endlessly as performance fixes. Here is what Microsoft actually says about them.

• Hardware-Accelerated GPU Scheduling. Microsoft describes it as letting "Windows offload most of the GPU scheduling to dedicated hardware on the GPU, reducing the load on your Central Processing Unit (CPU)." But the DirectX team's own introduction of the feature said the change "should be transparent, and users should not notice any significant changes," and that "we do not expect customers to experience performance regressions but if you encounter any, please be sure to file feedback." In other words, it is infrastructure, not a frame-rate switch. Try it both ways, keep whichever is stable, and do not expect a number.
• Optimizations for windowed games. This one has a documented mechanism. Microsoft says it "improves gaming performance for DirectX 10 and DirectX 11 games running in windowed and borderless windowed modes" by transitioning compatible games "from the legacy blt-model presentation to the newer flip-model, reducing frame latency," and it also enables variable refresh rate and Auto HDR. Path: Settings, System, Display, Graphics, under Default settings. Note Microsoft's warning that if Auto HDR is on, this option is forced on with it.
• Variable refresh rate. Microsoft is explicit that the OS toggle "enables VRR support for DX11 full-screen games that did not support VRR natively" and that it "doesn't override any of the settings you've already configured in the G-SYNC, FreeSync, or Adaptive-Sync control panels." So it is additive, narrow, and not a replacement for setting up adaptive sync on your monitor properly.

Note also that per-app settings on that same Graphics page override the system-wide preference, which matters on laptops where a game may be running on the integrated GPU without you noticing. Game Mode is the conspicuous absentee here: we could not retrieve a current Microsoft page that documents its behaviour in specific terms, so we are not going to tell you what it does. Leave it at its default and be sceptical of anyone who gives you a precise figure for it.

The procedure, in order of value per unit of risk

1. Measure before you change anything. Record a frame-time graph and a 1% low figure on one repeatable 60-second run. Without a baseline you cannot tell a fix from a placebo.
2. Close the background load. Browser tabs, overlays, capture software, launchers. This is free and reversible.
3. Install the current driver from the GPU vendor's own site, choosing the clean-install option. Reboot, then let the game rebuild its shader cache before you judge anything.
4. Check you are on the right GPU and the right display output. On a laptop, set the per-app GPU preference explicitly on the Graphics settings page.
5. Turn on adaptive sync at the monitor and in the vendor control panel, then cap your frame rate a few frames below your refresh rate. This is the single biggest improvement to perceived smoothness for most people, and it costs nothing.
6. Cut ray tracing first if you are on 8 GB of VRAM. It is the only setting that reduces GPU load and VRAM pressure at once.
7. Drop texture quality one step only if you measured VRAM exhaustion. Otherwise leave it high, because it is cheap and it is the setting your eyes care about.
8. Apply the upscaler. Quality mode first. Go to Balanced only if you still need frames.
9. Reduce shadows and view distance if the profile said CPU-bound. These are the CPU-side levers.
10. Improve cooling last, and physically. Clean the intake filters, raise a laptop off soft surfaces, and check that case fans still spin. If clocks drop over time, this is your problem and no software setting will fix it.

What not to do

• Do not run registry "optimiser" or "game booster" tools. They make undocumented, bundled changes you cannot individually undo, which is the opposite of a reversible fix.
• Do not install unofficial repackaged driver bundles. Get drivers from NVIDIA, AMD, Intel or your laptop OEM and nowhere else.
• Do not disable the paging file. Microsoft warns that if the system commit charge reaches the commit limit, "the system and processes might not get committed memory. This condition can cause freezing, crashing, and other malfunctions." Leave it system-managed.
• Do not overvolt or push voltage for stability. AMD's own tuning documentation states that its processors "are intended to be operated only within their associated specifications and factory settings," that operating outside them may cause damage and instability, and that resulting damage is "not covered under any AMD product warranty."

If the hitching is specifically a Windows 11 problem rather than a settings problem, our companion piece Fix Game Stuttering on Windows 11: A Practical Settings Checklist works through the OS-level items in more detail.

If it were my machine, here is where I would stop

My own order is narrower than the list above, and I would stop earlier than most guides let you. I would do three things and then re-measure: current driver with a clean install, adaptive sync plus a frame cap a few frames under refresh, and ray tracing off. On a typical 8 GB, 16 GB-of-RAM, 1080p machine of the kind the August 2026 Steam survey describes, that combination fixes the great majority of what people call stuttering, and it takes about fifteen minutes. If the frame-time graph is still spiky after those three, I would stop tuning and accept that I have identified a hardware or game-engine limit, not a configuration mistake. I would not go near voltage curves, third-party tweak utilities or service-disabling scripts, because the realistic upside there is a few percent and the realistic downside is an unstable machine you now have to debug on top of the original problem. The honest position is that the last 10 percent of tuning is where almost all of the risk lives and almost none of the benefit does.

The trade-off nobody states plainly

At some point the cheapest fix is money, and pretending otherwise wastes weeks. The two mistakes are not symmetrical. Spending a weekend on settings when you actually needed more VRAM costs you a weekend. Buying a new GPU when your real problem was a CPU-bound open-world game, a thermally throttling laptop or a game on a mechanical hard drive costs you several hundred dollars and fixes nothing. Under-spending is the cheaper mistake, so diagnose before you buy.

Where vendors disagree, the disagreement is usually about framing rather than fact. AMD's VRAM page argues for large capacity because AMD sells capacity. Microsoft is cautious about Hardware-Accelerated GPU Scheduling because Microsoft owns the regressions when it goes wrong. NVIDIA's advice about pipeline state objects is aimed at developers, not at you, which is precisely why it is trustworthy on the question of what causes shader stutter. Read each source with its incentive in mind, and prefer the one that has to live with being wrong. If you are about to spend money anyway, check the actual requirements first, as in our PRAGMATA PC Requirements: A Beginner's Buying Guide.

One last point on "smooth." Frame pacing is only part of the feel of a game. Input latency is the other half, and it is the half that settings pages never show you.

Tip: Once frame pacing is fixed, the remaining part of "feels smooth" is input latency, which is why polling rate and a low-latency wireless link are worth checking on your gaming mouse and gaming controller. (These are Amazon Associate links - we may earn a small commission on qualifying purchases.)

Sources

• Valve - Steam Hardware & Software Survey: August 2026
• Microsoft DirectX Developer Blog - CPU- and GPU-boundedness
• Microsoft DirectX Developer Blog - Hardware Accelerated GPU Scheduling
• Microsoft DirectX Developer Blog - Navigating the Redesigned Graphics Settings Page
• Microsoft DirectX Developer Blog - OS Variable Refresh Rate
• Microsoft Support - Optimizations for windowed games in Windows 11
• Microsoft Learn - Introduction to the page file
• NVIDIA Technical Blog - Advanced API Performance: Pipeline State Objects
• NVIDIA Technical Blog - Tips: Getting the Most out of the DLSS Unreal Engine 4 Plugin
• AMD - AMD Radeon VRAM Gives More Control Over Your Gaming Experience
• AMD Support - Customize GPU Performance Tuning with AMD Software: Adrenalin Edition
• Intel Support - What Is Throttling and How Can It Be Resolved?