Unstable frametime: why a game can stutter with high FPS

How to recognize the problem

Frequent causes

Shader compilation, asset streaming, a CPU thread reaching its limit, a GPU at full load, memory pressure, a slow disk, driver behavior, overlays, capture tools, and background Windows services can all create long frames.

A frame cap that does not match the display, unstable VRR settings, or a queue created by V-Sync can also change the feel. Network jitter can feel similar, but it does not create local frametime spikes.

Test one layer at a time

1. Repeat the same route or scene with the same graphics settings.
2. Watch frametime together with CPU, GPU, disk, memory, and temperature data.
3. Test with overlays, recording, and unnecessary launchers closed.
4. Compare a stable frame cap with uncapped output.
5. Run the test after shaders have warmed up, then test a fresh area to identify compilation or streaming.

Practical fixes

• Keep a little CPU and GPU headroom instead of running every component at its limit.
• Let shader caches build once and avoid deleting them without a reason.
• Use a frame cap that the system can hold consistently.
• Close capture, overlay, browser, and sync tools that wake during play.
• Check free disk space and whether the game is installed on a drive with high I/O latency.
• Record driver and game versions before testing a new update.

Do not confuse stutter with network latency

A local frametime spike affects rendering and camera motion even in an offline game. Ping or jitter affects communication with the server. Test offline or compare a frametime graph before changing router settings.

What Latence can help you check

Latence helps connect the symptom to Windows activity and a repeatable before-and-after measurement. Use it with the FPS and frametime benchmark and keep a rollback if a change makes pacing worse.