How to Fix Low FPS and Stuttering in Games on Windows 11

Low FPS means your game is rendering too few frames; stuttering means frames arrive unevenly. Measure both first, then check drivers, power mode, temperatures, background activity, and overlays before lowering image quality. Change one variable at a time and compare the same scene so you can identify the fix.

Is it low FPS, stuttering, or both?

First separate a consistently low frame rate from brief hitches. Low average FPS usually means the GPU or CPU is handling more work than the hardware can sustain. Stuttering appears as pauses or uneven motion, even when the displayed FPS number looks acceptable.

The game feels choppy, pauses briefly, or drops frames during play

The hitch may appear when you enter a new area, turn the camera quickly, encounter many characters, load an effect, or open a menu. If the game pauses while the FPS counter remains high, inspect frame time rather than FPS alone. Frame time is how long each frame takes to render; uneven frame times produce visible judder.

Enable the game's performance graph if it has one. Otherwise, use a trusted FPS overlay that shows both FPS and frame time. A stable result has only rare, brief frame-time spikes. Repeated spikes, especially at regular intervals, point to background activity, shader compilation, streaming, or a CPU limit.

Check for network lag before changing graphics settings. Rubber-banding, delayed actions, teleporting players, or an unchanged local camera usually indicate a connection or server problem rather than rendering performance. Lowering resolution will not fix a network problem.

Record the same save point, map area, benchmark run, or route through a level each time. Write down the average FPS, the lowest noticeable dips, and whether the graph shows isolated spikes or sustained high frame times.

What should you check before changing graphics settings?

These checks apply to Windows 11 games using DirectX or Vulkan on desktop PCs and laptops. You normally need an Administrator account for Windows updates, driver installation, and some system changes. Save open work before restarting. Do not use registry cleaners, driver “optimizer” tools, or random DLL downloads as a first response.

Start with these safe checks:

• Confirm whether the problem affects more than one game. If only one title is affected, a game update, shader cache, or game-specific setting is more likely.
• Check whether the game is using the intended GPU. On a laptop, it may have switched from the dedicated GPU to integrated graphics.

Check Windows Update and install pending updates, then restart. Install the current graphics driver from NVIDIA, AMD, or Intel, using the package for your exact GPU and Windows 11. If the problem began immediately after a driver update, rolling back to the previous stable driver is more sensible than repeatedly reinstalling the newest one.

Set the laptop or desktop to a performance-oriented power mode while testing:

Settings > System > Power & battery > Power mode > Best performance

A laptop should be connected to AC power. Battery-saving modes can reduce CPU or GPU clocks. The setting may be unavailable until a manufacturer utility or power plan is changed; that does not by itself show that the GPU is faulty.

Watch temperatures and clock speeds with the GPU manufacturer's software or a reputable monitoring utility. A rising temperature followed by falling clock speed indicates possible thermal throttling. Clean blocked vents, improve airflow, and verify that fans are operating. Do not disable thermal protection.

Keep free space on the system and game drives. Windows, shader caches, and games need working space for updates and asset streaming. In Task Manager, sort by CPU, Memory, Disk, and GPU usage while the hitch occurs. Look for heavy browsers, recording software, cloud synchronization, antivirus scans, launchers, and update processes.

Finally, test with overlays disabled. Turn off Xbox Game Bar, Steam or Epic overlays, Discord overlay, NVIDIA or AMD recording overlays, and third-party monitoring overlays one at a time. Disable background recording if you do not use it. Restart the game after changing an overlay setting. If the hitch disappears, re-enable features one at a time to identify the conflict.

Which fixes usually stop the hitching?

Use these fixes in order. The early changes are reversible and often identify the cause without sacrificing image quality.

1. Close heavy background applications before launching the game. In Task Manager, select an application you recognize and choose End task; do not terminate Windows processes merely because their names look unfamiliar. Pause cloud synchronization and scheduled scans temporarily if they are actively using CPU or disk. The expected result is lower background CPU or disk activity. If the hitch remains, continue to the next step and restore paused tasks when testing is complete.
2. Disable every game overlay and recording feature for one test run. Use the relevant application settings, then restart the game. If hitching stops, re-enable features individually to find the one that conflicts with the game or driver. If nothing changes, restore the features you need and continue.
3. Update or roll back the graphics driver based on timing. A problem that began after a driver update calls for the previous driver; a long-standing problem on an old driver calls for the current driver. Choose a clean-install option only when the installer offers it and normal installation does not help. A clean installation is not a reason to delete unrelated driver files manually. The expected result is improved FPS or fewer frame-time spikes after restarting the game. If the result is unchanged, undo the driver change when practical and test the next cause.
4. Let the game finish shader compilation. Some games compile shaders at first launch or while new effects appear. Keep the game open while that process completes, and avoid repeatedly deleting its shader cache; doing so can make the same hitching return as shaders are rebuilt. If a patch introduced constant compilation stutter, check the game's support notes or community reports for a known fix. Fewer hitches after the compilation work finishes confirms that compilation was involved. If stutter continues in the same locations, continue testing instead of repeatedly clearing the cache.
5. Reduce the setting that matches the bottleneck rather than lowering everything. If GPU usage is near full and frame time rises with image quality, lower resolution scale, ray tracing, shadows, volumetric effects, reflections, or ambient occlusion. Texture quality often affects VRAM more than raw GPU compute; lower it when VRAM is full or assets pop in. The expected result is higher sustained FPS or fewer long frame times. If GPU usage was not near full, restore the setting and test CPU-heavy options instead.
6. If the GPU is underused while one or more CPU threads are saturated, lower CPU-heavy options such as crowd density, view distance, simulation detail, foliage density, and physics. Reducing resolution will do little in a CPU-bound scene. A frame-rate cap below the unstable peak can also smooth delivery by leaving headroom for sudden workload changes. The expected result is a steadier frame-time graph in CPU-heavy scenes. If one CPU thread remains saturated, the hardware or game engine may be the limit.
7. Use upscaling carefully. Set the game's quality mode to a clear preset, then adjust sharpening only if needed. Avoid aggressive sharpening and very low render resolutions, which can make motion look worse even when FPS improves. Test frame generation separately; it can raise displayed FPS but does not remove the underlying input latency or CPU bottleneck. Keep the setting only if the image and frame-time behavior improve in the repeatable test.
8. Test fullscreen, borderless, and windowed modes if the game behaves differently in each. Also try disabling Windows optimizations for that game's executable only when the game has a documented compatibility problem. Do not apply random compatibility flags globally. Keep the mode that produces the steadier result; if all modes behave the same, restore the original mode and investigate another cause.

Restart the game after changing a rendering or overlay setting. If one change has no effect, restore it before testing the next unless you are deliberately building a new configuration.

How do you know the fix worked?

Use the same route through the same scene before and after each change. A single smooth minute proves very little: the game may not have streamed new assets, compiled a shader, or reached the busy part of the level.

1. Restart the PC if you changed a driver or system power setting. Launch only the game and the monitoring tool.
2. Load the same save or benchmark. Follow the same camera movement or route for the same period of time.
3. Record average FPS and frame time. Keep the overlay visible long enough to catch the original hitch. Prefer a graph or percentile view over a single “maximum FPS” number.
4. Repeat the run once. If the result changes dramatically between identical runs, background activity, shader compilation, asset streaming, or thermal behavior may still be involved.
5. Restore one setting at a time if you are searching for the best image quality. Stop when the game remains within the frame rate target your display and hardware can sustain.

A successful fix produces both higher sustained FPS and a less spiky frame-time graph when the original problem was rendering load. If FPS rises but frame-time spikes remain, you fixed the average workload but not the hitch source. If neither changes, undo the setting and inspect temperatures, clocks, VRAM, RAM, drivers, and game-specific reports instead.

For a repeatable software check, compare the same Windows performance counters or overlay readings rather than relying on how the first few seconds feel. The expected result is a similar or better average FPS with fewer long frame-time spikes in the same scene. There is no universal FPS target; compare your result with your own previous result on the same hardware and settings.

When is the real problem hardware or the game itself?

A hardware limit is likely when the GPU stays near full utilization during demanding scenes and lowering GPU-heavy settings improves FPS. That is normal performance scaling, not necessarily a fault. A CPU limit is more likely when GPU utilization falls while a CPU core or thread remains busy, especially in crowded areas or simulation-heavy games.

Thermal throttling has a recognizable pattern: temperatures climb, clock speeds fall, and performance declines after several minutes rather than immediately. Improve cooling and airflow first. If temperatures are normal but clocks remain unusually low, check the laptop's performance profile, charger, firmware, and manufacturer power limits.

Insufficient VRAM can cause texture pop-in, severe hitching when turning the camera, or sudden drops as new assets load. Insufficient system RAM can cause disk activity and pauses when switching areas or applications. Lower texture quality for VRAM pressure and close memory-heavy programs for RAM pressure; adding hardware may be the lasting fix when the game exceeds available memory.

A driver regression is suspect when several games become worse after the same driver release. Test the previous known-good driver, keep the installer from the GPU vendor, and report the result through the vendor's support channel. Do not install unofficial modified drivers.

A game patch is the likely cause when only one title changed, the problem began immediately after its update, and other games remain normal. Check the developer's patch notes and support discussions for shader compilation, anti-cheat, overlay, or streaming issues. Verify the game's files through its launcher, but do not delete saves or configuration folders unless the developer specifically instructs you and you have made a backup.

If the problem survives driver changes, clean background tests, reasonable settings, and temperature checks, compare with another demanding game. A failure across many games points toward Windows, drivers, cooling, power delivery, or hardware. A failure in one game points toward that game's engine, settings, or current patch.

Conclusion

Run the same scene with an FPS and frame-time graph, then test power, temperatures, drivers, background activity, overlays, and the setting that matches the bottleneck. If the problem remains limited to one game or began with a patch, investigate that title rather than repeatedly changing Windows settings.

Frequently Asked Questions

Should I lower resolution first to fix stuttering?

No. Lowering resolution helps a GPU-bound game, but it usually will not fix CPU spikes, shader compilation, disk streaming, overlays, or network lag. Check GPU usage and frame time first, then change the setting that matches the bottleneck.

Can Windows 11 Game Mode cause low FPS?

Game Mode is not a universal cause of low FPS. Test with it enabled and disabled only after checking drivers, power mode, background processes, and overlays. Compare both runs in the same scene.

Why does FPS look high while the game still stutters?

An average FPS counter can hide individual long frames. Use a frame-time graph or a metric that shows spikes. Uneven frame delivery can feel choppy even when average FPS is high.

Should I delete the shader cache?

Usually not as a first fix. Deleting it forces the game to compile shaders again and can temporarily increase stuttering. Do it only when the game's developer or driver support instructions identify a corrupted cache as the likely cause, and expect another compilation period afterward.