If RivaTuner Statistics Server (RTSS) still shows frame rates above your chosen limit, the usual cause is not a broken installation. The cap is commonly set on the wrong executable, left at 0, blocked by an incompatible rendering path, or competing with another limiter or overlay.
For the fastest test, close the game, open RTSS, add the game’s actual rendering executable, set its Framerate limit to 60, choose Application detection level: Low, disable other limiters temporarily, and relaunch the game. If it still runs well above 60 FPS, continue with the checks below.
As an Amazon Associate I earn from qualifying purchases.
Quick checklist
- RTSS is running in the Windows notification area.
- The selected RTSS profile belongs to the game’s real
.exe, not its launcher. - Framerate limit is set to a value such as
60, not0. - You changed the game-specific profile rather than only the global profile.
- You restarted the game after changing RTSS settings.
- Other frame limiters and overlays are disabled while testing.
- Frame generation is disabled for the initial test.
1. Make sure RTSS is actually running
RTSS must remain open while the game is running. Look for its icon in the Windows notification area and open the main RTSS window. An MSI Afterburner installation does not automatically guarantee that RTSS is installed or active: Afterburner and RTSS are separate utilities, although they are commonly used together.
Also check that you are editing the same RTSS installation that is active. Multiple installations can leave you changing settings in one copy while another instance controls the game. Exit RTSS, close MSI Afterburner, and use Task Manager to confirm that no RTSS process remains before reopening it.
#1 Best Overall
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
Download RTSS only from a trustworthy source. The Guru3D RTSS page identifies Guru3D as the official hosting partner and warns against unofficial download sites. That page lists RTSS 7.3.7 Final and describes it as freeware; availability can change, so treat the page’s current listing as authoritative rather than assuming 7.3.7 will always be the newest release.
2. Add the game’s actual executable
RTSS applies per-application settings according to the process that renders the game. Adding a launcher is one of the most common reasons a cap appears to do nothing.
- Launch the game.
- Press
Ctrl+Shift+Escto open Task Manager. - Open the Details tab.
- Identify the process that owns the game window and note its exact executable name, such as
Game-Win64-Shipping.exe. - Exit the game.
- Open RTSS and click Add.
- Browse to and select that executable.
- Select the new profile and configure the cap there.
Do not add only launcher.exe, a store shortcut, or an anti-cheat launcher. Some games also switch processes after startup or use separate 32-bit and 64-bit executables. If the profile works in menus but not gameplay, check whether the game changes process or rendering path once gameplay begins.
The RTSS information pages at Guru3D explain that manually adding applications lets RTSS apply configured settings to programs that are not automatically listed.
3. Check the Framerate limit field
Select the game’s profile in RTSS and inspect Framerate limit. A value such as 60, 120, or 141 enables a cap. A value of 0 means unlimited.
For diagnosis, use an obviously low value such as 30 or 60. Click away from the field or press Enter so the value is committed, then restart the game. If the game continues far above a 60 FPS test cap, this is not a minor pacing variation: the selected profile’s limiter is not being applied.
Rank #2
- QHD Resolution (2560 x 1440) has 1.7 times the pixel density of Full HD for incredibly detailed pinsharp images
- HDR10 provides brighter highlights and nuanced shadow for added depth - making every scene feel more vivid and realistic
- The 180Hz refresh rate minimizes lag for gameplay with ultra-smooth action. Plus, the 1ms response time helps capture your moves in real-time, allowing you to react fast for gaming precision
- AMD FreeSync reduces choppiness, screen lag and image tearing, ensuring that your fast-paced, complex in-game action is stable with minimal stutter
- Ergonomic stand allows for tilt, pivot and height adjustments to maximize gaming comfort
Some RTSS versions and configurations also expose a frametime-limit mode. The RTSS documentation history describes switching between Framerate limit and Frametime limit by clicking the field label. Leave this advanced option alone until ordinary frame-rate limiting works; it will not fix a wrong executable or a failed hook.
Recommended Free Tools
4. Set Application detection level carefully
In the game-specific RTSS profile, start with Application detection level: Low. Restart the game after changing it.
- Low: the best first troubleshooting setting.
- Medium or High: worth testing if RTSS does not detect or control the game.
- None: useful as a diagnostic option when profile or overlay behavior is inconsistent.
- Stealth mode: not a universal compatibility fix.
Changing detection level to High before confirming the executable often obscures the real problem. Stealth hooking can also introduce compatibility issues. RTSS documentation notes that stealth hooking is not supported in 64-bit applications and advises against combining RTSS with other 64-bit OSD software. Do not use it as a method to evade anti-cheat systems.
5. Test the game’s rendering API
RTSS supports monitoring and limiting for DirectX, Vulkan, and OpenGL applications, but compatibility can vary by game, API, driver, and presentation method. A title may offer separate DirectX 11, DirectX 12, and Vulkan modes, or behave differently in exclusive full-screen, borderless-windowed, and windowed modes.
As a diagnostic test, switch temporarily to another renderer exposed by the game, restart RTSS and the game, and apply the deliberately low cap again. If it works in DirectX 11 but not DirectX 12 or Vulkan, report the result accurately: that is an API-specific compatibility issue, not proof that RTSS is universally broken.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThe Guru3D listing for RTSS 7.3.7 describes Vulkan-hooking improvements and compatibility work involving NVIDIA Smooth Motion and frame-generation-related paths. Updating may help, but no RTSS version guarantees compatibility with every modern renderer or game. If a title works reliably only with its own limiter, use that limiter instead.
Rank #3
- Smooth motion: 240Hz refresh rate and fast 0.5ms response time provide crisp visuals and fluid movement with less input lag.
- Seamless gaming: FreeSync Premium and HDMI VRR eliminate tearing for smooth, responsive PC and console gameplay.
- Fast IPS: Faster 0.5ms response with excellent color accuracy across wide IPS viewing angles.
- Rich color: 99% sRGB color coverage delivers vivid, detailed imagery with strong accuracy.
- Eye comfort: TÜV Rheinland 3‑star certified display lowers blue light while preserving color quality.
6. Disable competing limiters and overlays
Temporarily turn off every other frame-rate control so you can test RTSS by itself:
- The game’s built-in FPS limit.
- NVIDIA Control Panel or NVIDIA App Max Frame Rate.
- AMD driver-level frame-rate controls.
- V-Sync.
- Steam, Discord, Xbox Game Bar, NVIDIA, and AMD overlays.
- OBS, FrameView, capture software, and other monitoring utilities.
Multiple limits do not behave identically in every game. Depending on the API, driver, and synchronization mode, one may take precedence or the lowest active limit may determine the result. NVIDIA documents interactions among driver-level frame-rate controls in its Max Frame Rate support information.
After RTSS works alone, re-enable features one at a time. This reveals whether the problem is a second cap, V-Sync presentation behavior, an overlay hook, or a latency or frame-generation feature.
Free tools Windows power users keep installed
One-click scans. No signup required.
NVIDIA’s FrameView guide warns that RTSS and similar utilities can prevent its overlay from appearing because they hook similar application processes. That does not prove that every overlay conflict will disable the RTSS limiter, but it is a reason to test with only one monitoring or overlay tool enabled.
7. Check V-Sync, VRR, and your target rate
V-Sync controls how application output is synchronized with the display. The number shown by a game or overlay may therefore reflect monitor refresh and presentation behavior rather than simply the RTSS value. NVIDIA documents V-Sync and driver-level maximum frame rate in its Manage 3D Settings reference. AMD describes V-Sync and frame-rate targeting as separate controls in its support documentation.
For a variable-refresh-rate display, a common starting point is to cap slightly below the panel’s maximum refresh rate:
Rank #4
- 27” 240Hz 1500R Curved FHD 1080P Gaming Monitor for Game Play.
- Prioritizes Gaming Performance: Up to 240Hz high refresh rate, more immersive 1500R Curvature, FreeSync, MPRT 1ms Response Time, Black Level adjustment(shadow booster), Game Modes Preset, Crosshair.
- Cinematic Color Accuracy: 130% sRGB & DCI-P3 95% color gamut, 4000:1 contrast ratio, 300nits brightness, HDR, Anti-flicker; Anti-Glare.
- Plug & Play Design: HDMI & DP1.4 & Audio Jack(No built-in speakers), durable metal stand, tilt -5°~15, VESA 100*100mm compatible.
- Warranty: Money-back and free replacement within 30 days, 1-year quality warranty and lifetime technical support. Pls contact SANSUI service support first if any product problem.
| Display refresh | Common starting cap |
|---|---|
| 60 Hz | 58 or 60 FPS |
| 144 Hz | 141 or 144 FPS |
| 165 Hz | 162 or 165 FPS |
| 240 Hz | 237 or 240 FPS |
These are practical starting points, not universal rules. The best value depends on the display’s VRR range, driver settings, synchronization method, and whether your priority is latency, smoothness, or lower GPU usage.
8. Temporarily disable frame generation
Frame generation can make an apparent FPS counter exceed the RTSS value without proving that the limiter is entirely inactive. Modern games and tools may report base-rendered FPS, generated FPS, displayed FPS, or a value measured before or after presentation.
For a clean test:
- Disable DLSS Frame Generation, AMD FSR Frame Generation, NVIDIA Smooth Motion, Lossless Scaling, or any other frame-generation system.
- Use native or upscaled rendering without generated frames.
- Set RTSS to 60 FPS and test a fixed gameplay scene.
- Compare RTSS’s counter with the game’s counter.
- Re-enable frame generation and observe which counter changes.
NVIDIA Reflex and proprietary frame-generation pipelines can also change where limiting and latency control are most effective. If the game recommends its own limiter when Reflex or frame generation is enabled, that is usually the safer choice. Do not assume RTSS will cap generated frames at the same stage or in the same way as native frames.
9. Rule out anti-cheat and permission conflicts
RTSS interacts with the game’s rendering process. Some games and anti-cheat systems restrict injected overlays or hook-based monitoring. Guru3D lists anti-cheat restrictions and incompatibilities with some third-party OSD programs among RTSS limitations.
Disable nonessential overlays, leave RTSS enabled, and test again. If the game crashes, refuses to launch, or behaves differently only when RTSS is active, stop stacking compatibility modes and use the in-game or driver limiter. RTSS is not an anti-cheat bypass.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsMatch privilege levels when necessary. If the game runs as administrator, try launching RTSS as administrator too. If the game is not elevated, avoid permanently elevating RTSS unless testing shows that it is required. Forced administrator or compatibility settings are not a general solution.
Best Value
- 1800R curve monitor the curved display delivers a revolutionary visual experience with a leading 1800R screen curvature as the images appear to wrap around you for an in depth, immersive experience
- Hdmi, VGA & PC audio in ports
- High refresh rate 75Hz.Brightness (cd/m²):250 cd/m2
- Vesa wall mount ready; Lamp Life: 30,000+ Hours
- Windows 10 Sceptre Monitors are fully compatible with Windows 10, the most recent operating System available on PCs.Brightness: 220 cd/M2
10. Verify the result with more than one counter
An OSD proves that some monitoring or injection function is active; it does not prove that the selected profile’s limiter is active. Compare at least two observations:
- RTSS’s FPS or frametime display.
- The game’s built-in counter.
- Steam’s FPS counter.
- The NVIDIA or AMD performance overlay.
- PresentMon or another independent measurement tool.
Use a fixed scene, wait for shader compilation and asset streaming to settle, and repeat the same movement or route. Examine frametime as well as the headline FPS number. A steady 60 FPS corresponds to approximately 16.67 ms per frame; 144 FPS corresponds to approximately 6.94 ms. Occasional one- or two-frame excursions can result from measurement and presentation differences, while sustained values far above the test cap indicate that the limiter is not controlling the measured stage.
11. Rebuild RTSS profiles or reinstall cleanly
If settings revert, the profile behaves unpredictably, or an update caused the OSD to disappear:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →- Exit the game.
- Exit RTSS and MSI Afterburner.
- Use Task Manager to confirm no RTSS process remains.
- Reopen RTSS and recreate the game profile.
- Confirm that you are editing the active installation and the correct executable.
If that fails, perform a clean uninstall of RTSS and Afterburner with profile removal, then reinstall from the trusted Guru3D distribution. Guru3D specifically recommends a full uninstall with profile removal when an update causes overlay problems. Reinstalling should be a recovery step after checking the executable, profile, cap value, and conflicts—not the first response to every uncapped game.
When RTSS is the wrong limiter
RTSS is a good fit when the game accepts its hook, you need per-game caps, or you want a detailed OSD and frametime graph. Its accuracy and latency behavior are not universal; they depend on the particular game, API, driver, synchronization mode, and limiter implementation.
Prefer the in-game limiter when RTSS is blocked by anti-cheat, causes crashes or stutter, or the game has a limiter integrated with Reflex or its own frame-generation pipeline.
Prefer the GPU-driver limiter when RTSS cannot hook the renderer or you want a driver-level cap without an injected overlay. NVIDIA users can use Max Frame Rate through the NVIDIA Control Panel or NVIDIA App. AMD users can use the frame-rate and synchronization controls provided by AMD Software: Adrenalin Edition, although labels and availability vary by driver version and GPU.
Quick Recap
Symptom-to-fix matrix
| Symptom | Likely cause | Recovery |
|---|---|---|
| FPS remains far above the cap | Wrong profile or cap set to 0 |
Add the actual game executable and test with 60. |
| OSD appears but FPS is uncapped | Monitoring works, but the limiter profile does not | Select the correct per-game profile and remove global/profile confusion. |
| RTSS detects only the launcher | Wrong executable | Find the rendering process in Task Manager’s Details tab. |
| It works in DX11 but not DX12 or Vulkan | API-specific compatibility | Update RTSS, switch API, or use the game or driver limiter. |
| It works in menus but not gameplay | Different process or rendering path | Verify the active executable during gameplay. |
| FPS exceeds the cap with frame generation | The counter includes generated or displayed frames | Disable frame generation and compare base-rendered FPS. |
| The game crashes with RTSS enabled | Hook, anti-cheat, or overlay conflict | Disable other overlays and use the in-game or driver limiter. |
| The overlay disappeared after an update | Corrupt profiles or installation | Clean-uninstall with profile removal, then reinstall. |
| Stutter starts after enabling RTSS | Limiter, API, or overlay interaction | Compare RTSS with the game and driver limiters separately. |
| Settings revert after restart | Wrong installation or permissions | Exit all RTSS instances and recreate the profile. |
| The cap is one or two FPS high | Counter or presentation differences | Compare frametime and an independent counter. |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
