Windows FPS drops: why a game slows down at certain moments
A drop can come from the game, GPU, CPU, a Windows service, or an app that wakes during the session. The useful first step is to identify which layer changes.
Latence helps prepare a before-and-after test and keep a rollback when a setting does not suit your PC.
Download LatenceSimple definition
An FPS drop is a sudden or repeated decrease in frames per second. It can appear in the average, but it is often clearer in 1% lows, 0.1% lows, and frametime spikes.
Common causes
Local load
A CPU thread, GPU, RAM, VRAM, temperatures, or power limit can become the bottleneck at a specific moment.
Windows activity
Updates, antivirus scans, indexing, cloud sync, launchers, overlays, and capture tools can wake during a match.
Game and driver changes
A patch, driver, shader compilation, asset streaming, graphics preset, or frame-cap change can alter frame pacing.
How to diagnose it
- Record the exact moment, scene, and game mode where the drop occurs.
- Compare average FPS with frametime, CPU/GPU usage, temperatures, clocks, and disk activity.
- Repeat the same route after closing overlays and background apps.
- Test one graphics setting or Windows change at a time.
- Keep the old profile so you can restore it when the result gets worse.
If the GPU is already at 99%, reducing a CPU-side Windows tweak will not create much headroom. If one CPU thread is full while the GPU is waiting, lower CPU-heavy settings or inspect background activity instead.
Practical fixes
- Check temperatures, clocks, power mode, and whether the system is throttling.
- Close unnecessary overlays, capture tools, browsers, and launchers.
- Update or roll back the GPU driver only when the timing matches the symptom.
- Keep enough free disk space for shader caches, pagefile activity, and updates.
- Use a stable frame cap when uncapped rendering creates uneven pacing.
- Measure the same scene again after each change.
Mistakes to avoid
Do not call every drop a network problem. Ping affects server communication, while FPS and frametime are local rendering signals. Do not apply a long list of tweaks at once: you lose the ability to identify the cause or roll back safely.
What Latence can help you check
Latence helps you connect a Windows state to a measurable before-and-after result. Pair this guide with benchmarking FPS and frametime, frametime diagnosis, and GPU driver testing.
Can a Windows service cause FPS drops?
Yes. A scan, update, sync process, or overlay can consume CPU, disk, or GPU resources at the wrong moment.
Should I lower every graphics setting?
No. First identify whether the CPU, GPU, memory, disk, or background activity is the limiting layer.
Are FPS drops the same as high ping?
No. FPS drops and frametime spikes are local. High ping is a network timing problem, though both can feel like delayed actions.
Measure the drop before optimizing
A controlled test tells you whether the cause is Windows, the game, the hardware, or the network.
Test Latence on Windows