A counter that reads 160 FPS means nothing if the frames are delivered at the wrong times. At 60Hz your display refreshes every 16.67 milliseconds. A single frame that takes 10 ms too long still fits inside that window without a visible hitch. At 144Hz the refresh interval shrinks to about 6.94 ms, at 165Hz to 6.06 ms, and at 240Hz it collapses to roughly 4.17 ms. That tiny timing slack is why a render-time hiccup that’s invisible at 60Hz turns into obvious choppiness at high refresh rates. The monitor demands cleanly paced frames far more often, so any inconsistency goes straight to your eyes.
The problem is rarely the average frame rate. It’s frame-time variance. For a broader explanation of how average FPS, frame time and 1% lows affect perceived smoothness, read our guide to why high FPS can still feel stuttery. A game that swings between 4 ms and 22 ms frame times will feel jittery even if the average still lands at, say, 160 FPS. The display never sees the average; it sees each individual interval, and the bad ones dominate perception. Open-world titles with heavy asset streaming often get calmer at a locked 60 FPS because the intervals become uniform. Competitive shooters only feel liquid at 165Hz or 240Hz when frame times almost never deviate.
A second villain is the render queue. When a GPU runs completely uncapped, the graphics driver starts buffering frames ahead. The deeper that queue, the more it acts like a sponge that releases frames in bursts. Sudden workload spikes make the queue drain unevenly, creating micro-stutter and extra input latency. The game feels sluggish and uneven, despite the on-screen FPS counter staying high. Capping the frame rate just below your monitor’s maximum kills that queue before it grows and restores tight frame pacing—a trick we’ll get to.
If the game feels choppy at other refresh rates—or the problem appears only after Alt-Tabbing, during mouse movement, after an update, or under heavy GPU load—use our PC game stuttering troubleshooter to identify the symptom path that fits your system.
The Diagnostic Toolkit – Before You Change Any Setting
Don’t guess. Collect data. You need an on-screen graph of frame times, not just FPS. MSI Afterburner with RivaTuner Statistics Server (RTSS) is the standard tool. Turn on the frametime graph and set it to display in milliseconds. A flat line near your monitor’s reciprocal value—for example, 6.9 ms for 144Hz—means perfect pacing. Spikes or a saw-tooth pattern confirm frame-time instability. If the graph confirms spikes but you cannot identify whether the CPU, RAM, storage or background software is responsible, follow our guide to finding the real bottleneck behind frame-time spikes.
Watch the 99th-percentile FPS reading. If average FPS is high but the 99th-percentile drops into the 40s or 50s, your worst frames are destroying the experience. Compare uncapped versus a sensible RTSS cap. If the frametime graph flattens dramatically under a cap, you’ve just confirmed a render-queue or GPU saturation problem.
Also monitor GPU usage and clock speeds during the stutter. A GPU that sits at 100% usage with a large render queue will thump out irregular frame times. If usage is lower but your CPU threads are maxed, the CPU is the pacing bottleneck. Note any sudden clock speed drops on either component—a telltale sign of thermal throttling or power management interference that can inject exactly the type of spike high refresh rates punish.
Test with all overlays and background apps closed. Even Discord hardware acceleration, Nvidia overlay, or browser video playing on a second monitor can introduce tiny system interrupts that become visible at 240Hz.
Step-by-Step Troubleshooting Order
Work through these in sequence. Each step eliminates a common cause. Only skip one when you’ve already verified it’s not your issue.
Set Windows and GPU power plans to maximum performance.
In Windows, use the “Ultimate Performance” or “High Performance” power plan so the CPU doesn’t park cores or throttle PCIe link states. In Nvidia Control Panel, set “Power management mode” to “Prefer maximum performance” for the affected game. AMD users do the equivalent under Performance > Tuning. At high refresh rates, even a brief clock dip can cause a noticeable frame-time spike.Strip background processes and overlays to the bone.
Open Task Manager, sort by CPU and GPU usage, and end anything non-essential. Browsers, Launchers, RGB software, and hardware monitoring polls can all steal interrupt time. Disable the Steam overlay, Discord overlay, and Nvidia GeForce Experience in-game overlay. For stubborn apps, temporarily set the game’s CPU priority to “High” in Task Manager—this sometimes smooths out hitches caused by background thread contention.Enable an FPS cap 3–7 FPS below your monitor’s refresh rate.
This is the single highest-impact move. Use RTSS (front-end for RivaTuner) for a CPU-level framerate cap that doesn’t add a frame of latency. If the game’s built-in limiter is precise you can use it, but RTSS is the gold standard. Targets:- 144Hz → cap at 138–141 FPS
- 165Hz → cap at 158–162 FPS
- 240Hz → cap at 233–236 FPS
Capping prevents the GPU from ever building a deep render queue. The render chain stays tight, reducing both input-latency variance and frame-pacing spikes. Despite the slightly lower peak FPS the game will feel dramatically smoother.
Pair VRR with the cap, or handle non-VRR carefully.
If you own a G-Sync or FreeSync monitor, enable it in the driver and in the display’s OSD. Then globally set V-Sync to “On” inside the Nvidia Control Panel (or AMD equivalent) and stick to the in-game cap 3 FPS below max refresh. This keeps VRR active at all times without ever bumping into the V-Sync latency ceiling.
Without VRR, do not blindly enable traditional V-Sync because it adds significant input lag. Use the FPS cap alone. It reduces tearing compared to completely uncapped output and fixes pacing, but some tearing may remain. If screen tearing is unbearable even when capped, try “Fast Sync” (Nvidia) or “Enhanced Sync” (AMD). Those options discard excess frames instead of queuing them, which helps pacing at high refresh rates with less lag than full V-Sync.Check for thermal throttling and clock consistency.
While the game runs, watch GPU and CPU clock speeds in HWMonitor or Afterburner. A sudden drop from 1900 MHz to 1400 MHz during intense scenes will produce the exact frame-time spike that ruins 240Hz fluidity. Improve case airflow, repaste if needed, or lower power limits. Some laptops also require undervolting to stay out of thermal throttling territory. High refresh gaming is unforgiving with thermal management.Compare in-game and RTSS limiters, then lock in the best one.
Some engines (particularly Unreal Engine 4) produce poor internal frame pacing when their own limiter is used. Test your title both ways: RTSS cap only, then in-game cap only. Choose whichever delivers the flatter frametime graph. Occasionally a game engine needs a specific refresh rate fraction—for example, capping at half refresh (72 FPS on 144Hz) can resolve engine-level pacing bugs, but treat that as a last resort when everything else is ruled out.Use exclusive fullscreen, not borderless windowed.
Windows’ Desktop Window Manager forces a layer of triple-buffered V-Sync onto borderless windowed mode. That adds input lag and can interfere with the consistent frame delivery needed at 165Hz or 240Hz. Switch the game to exclusive fullscreen unless you specifically need seamless alt-tabbing. If you must use borderless, test the “Disable fullscreen optimizations” compatibility flag on the game’s executable—sometimes it reduces the DWM interference.
Common Mistakes That Make High Refresh Rate Gaming Feel Broken
Capping exactly at the refresh rate with V-Sync on.
When V-Sync is enabled and the frame rate hits exactly the maximum (e.g., 144 FPS on a 144Hz panel), the render pipeline flips to a backpressure mode that can suddenly introduce huge latency swings. The cap must be a few frames below to stay inside the VRR window or avoid that boundary.
Using uncapped FPS as a performance flex.
An uncapped GPU quickly becomes a frame-time nightmare. Every time a complex scene pushes usage to 100%, the render queue fills and empties unpredictably. You’re trading smoothness for a higher number that doesn’t reflect what your eyes perceive.
Dismissing a “minor” background app.
At 240Hz the system has only 4.17 ms to deliver each frame. A single DPC latency spike from a network adapter, RGB polling, or a hardware monitor can blow that deadline. Even a well-tuned gaming PC can be brought down by one misbehaving driver. Use LatencyMon to identify problematic drivers if background stripping doesn’t fix it.
Blindly copying settings from a YouTube guide.
A 141 FPS cap that works flawlessly on one system may stutter on another because of different CPU frametime consistency. Always verify with your own frametime graph and 99th-percentile numbers.
Edge Cases: When the Usual Fixes Aren’t Enough
Dual-monitor setups with mixed refresh rates.
Running a 240Hz screen next to a 60Hz second monitor forces the Windows compositor to sync to the slowest panel at times, especially if any motion—like a Twitch stream—is present on the 60Hz screen. This causes visible stutter on the main gaming display. Disable hardware acceleration in your browser, move all animated content to the gaming monitor, or set the secondary monitor to 120Hz if it supports it. In extreme cases, gaming with the second screen off is the only way to get perfect pacing.
Engine-level frame pacing bugs.
Some titles (e.g., Elden Ring, older Bethesda games) ship with internal timing issues no driver setting can fully fix. Third-party mods like Special K can fix frame pacing, but they are game-specific. In these cases, locking to a steady, lower frame rate can produce a smoother experience than a fluctuating high FPS.
Aggressive monitor overdrive causing visual chop.
If your frame-time graph is perfectly flat but motion still looks choppy or smeary, the monitor’s overdrive setting may be to blame. Too much overdrive creates inverse ghosting—bright corona trails that mimic stutter. Drop the overdrive level one notch and retest. This is often mistaken for a frame delivery problem.
Frequently Asked Questions
Does capping FPS below my monitor’s refresh rate add input lag?
A few FPS below max adds a nearly imperceptible increase in theoretical latency—typically fractions of a millisecond. In practice, the reduced render queue depth and elimination of backpressure actually lower average input lag and make motion feel far more responsive than uncapped, queue-bloated output.
I have G-Sync or FreeSync. Should I still cap my FPS?
Yes. Cap 3 FPS below the maximum refresh rate. This keeps the display permanently inside the variable refresh range and prevents the sudden V-Sync latency spike that occurs when the frame rate touches the ceiling.
My frametime graph is dead flat but the game still feels choppy. What’s left?
Look at the monitor end. Misconfigured overdrive, a slow pixel response time mode, or even a bad DisplayPort cable that degrades signal integrity can produce motion artifacts. Reset the monitor’s settings to default and test with a different cable before assuming the PC is at fault.
