Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC 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 & 11The “Some system components cannot be hooked” message comes from RivaTuner Statistics Server (RTSS), the companion component MSI Afterburner uses for its on-screen display (OSD), frame-rate limiting, frametime data, and related overlays. It means RTSS could not attach to one or more running processes—not that your graphics card or Windows installation is necessarily damaged.
If the OSD still appears in the game you care about, the warning can be informational: RTSS may have skipped a protected launcher, browser process, system component, or anti-cheat module. If the overlay is missing in one title or everywhere, use the diagnosis and repair sequence below.
As an Amazon Associate I earn from qualifying purchases.
What the error actually says
The complete dialog is commonly shown as: “RivaTunerStatisticsServer. Some system components cannot be hooked right now. It is strongly recommended to restart application.” “Hooking” is the process RTSS uses to connect its overlay and frame-management code to another program while that program is running.
Free tools Windows power users keep installed
One-click scans. No signup required.
RTSS can enumerate many processes at startup, but Windows permissions, protected processes, anti-cheat systems, security software, or another overlay can prevent attachment to a particular process. A failed attachment therefore describes an RTSS integration problem, not a general hardware fault. MSI Afterburner can often continue polling temperatures, clocks, fan speed, voltage, and other sensors even when RTSS cannot draw an overlay.
#1 Best Overall
- Chipset: NVIDIA GeForce RTX 3060
- Video Memory: 12GB GDDR6
- Memory Interface: 192-bit
- Output: DisplayPort x 3 (v1.4a) / HDMI 2.1 x 1.Avoid using unofficial software
- Digital maximum resolution: 7680 x 4320
What RTSS provides—and what may still work
Overlay and frame features
RTSS is responsible for displaying the FPS counter, frametime graph, GPU and CPU statistics, and other OSD elements configured in MSI Afterburner. Its frame limiter and several per-application presentation features also depend on a successful hook. If a target process is skipped, those functions may be unavailable for that process.
Afterburner’s independent functions
MSI Afterburner’s hardware monitoring and tuning controls do not require every process to accept an RTSS overlay hook. You can therefore see current clocks or temperatures in the Afterburner window while the in-game display is absent. This distinction is useful: troubleshoot the missing feature instead of treating a warning as evidence that the entire installation has failed.
Identify the scope before changing anything
Launch the exact game or application that matters and check the feature you expect to use. The scope of the failure determines how invasive the next step should be.
| Observed result | Most likely interpretation | First response |
|---|---|---|
| Warning appears, but the OSD and frame limiter work in the target game | RTSS skipped an unrelated background or protected process | Leave security settings unchanged and monitor the game you actually use |
| OSD fails in one game only | That title, its launcher, API, profile, or anti-cheat is rejecting the hook | Reset the title’s RTSS profile and test competing overlays |
| OSD fails in every game | Version mismatch, permissions, damaged files, or a system-wide conflict | Restart both programs, match privilege levels, then update the paired software |
| Afterburner sensors work, but RTSS crashes or cannot save settings | RTSS installation or configuration data may be damaged | Back up settings and consider a clean reinstall |
Safe troubleshooting sequence
1. Test the target application first
Start the game or application and look for the configured FPS counter, frametime graph, GPU statistics, or frame limiter. Test the specific title rather than relying on the warning alone. A working OSD means the failed hook may belong to a process you never intended to monitor, so changing Windows security settings would add risk without improving your result.
2. Close duplicate processes and restart in order
- Exit the game or application.
- Close MSI Afterburner and RTSS from their notification-area icons. If an icon is hidden, expand the tray first.
- Open Task Manager and check for more than one
RTSS.exeprocess. End a leftover instance only after confirming that you have closed the normal RTSS interface. - Open RTSS, then open MSI Afterburner, and launch the game again.
RTSS normally attaches while a target process is starting. Restarting after all old instances have exited removes stale hooks and ensures the current profile is loaded before the game creates its graphics device.
Rank #2
- Chipset: NVIDIA GeForce RTX 5080
- Video Memory: 16 GB GDDR7
- Memory Interface: 256-bit
- Output: DisplayPort x 3 (v2.1a) / HDMI 2.1b x 1
- Digital maximum resolution: 7680 x 4320
3. Match Windows privilege levels
Windows can block a normal-privilege overlay from attaching to a game or launcher running as administrator. Check the shortcut or executable properties for the target and for both MSI Afterburner and RTSS. For a test, run all involved programs at the same privilege level. Do not permanently set everything to administrator unless the monitored application genuinely requires it; elevated programs increase the impact of mistakes and can create a different mismatch later.
4. Disable competing overlays one at a time
Multiple injectors can target the same graphics process. Temporarily disable the overlays supplied by Steam, Discord, NVIDIA, AMD, Xbox Game Bar, Overwolf, individual game launchers, ReShade, and recording or capture utilities. Change one item, restart the game, and test again so you know which component affected the result.
If disabling one overlay restores the OSD, keep the two features separate or change their startup order rather than enabling every overlay simultaneously. You can usually retain the least intrusive overlay and turn off the one that provides duplicate FPS or performance data.
5. Update MSI Afterburner and RTSS as a pair
Install a current stable MSI Afterburner package from MSI’s official distribution page and the compatible RTSS release from a legitimate RTSS distribution page such as Guru3D’s download listing. Reboot Windows after installation, then test before restoring custom profiles. Avoid pairing a newly released RTSS build with a much older Afterburner build unless you are intentionally testing a documented beta combination.
Version alignment matters because the two programs exchange configuration and monitoring data. A partial update, an interrupted installer, or a security product that quarantined one executable can leave the OSD unavailable even though the Afterburner window opens normally.
Rank #3
- Chipset: NVIDIA GeForce RTX 5080
- Video Memory: 16 GB GDDR7
- Memory Interface: 256-bit
- Output: DisplayPort x 3 (v2.1a) / HDMI 2.1b x 1
- Digital maximum resolution: 7680 x 4320
Repair a single-game failure
Lower application detection temporarily
Open the RTSS interface and select the affected game profile. Set application detection level to Low or Medium while troubleshooting. Keep OSD support enabled. This reduces how aggressively RTSS attempts to identify and attach to a process without turning the overlay off completely.
Remove unusual profile options
For the affected profile, temporarily turn off Stealth mode, custom Direct3D support, and unusual frame-limiter settings. Test with the game’s normal executable and graphics API first. If the OSD returns, re-enable one option at a time to identify the setting that caused the conflict.
Recreate a corrupted profile
A damaged per-game profile can preserve a bad executable path or incompatible option. Delete or rename only that profile so RTSS can create a clean one, then launch the game and configure the overlay again. Record your preferred limits and detection level before removing the file; do not delete the entire RTSS configuration when only one title is affected.
Anti-cheat protection is a deliberate boundary
Easy Anti-Cheat, BattlEye, Riot Vanguard, EA AntiCheat, and similar systems may intentionally reject overlay injection. A warning in a competitive title can therefore be expected behavior rather than a defect. Anti-cheat software is designed to prevent code from attaching to protected game processes, and a successful hook in one game does not imply that it should work in another.
- Do not replace RTSS files with unsigned DLLs or modified builds.
- Do not use unknown launch arguments or injection utilities to force an attachment.
- Disable the RTSS overlay for the protected title, or use that game’s built-in FPS and performance display.
- Keep RTSS enabled for applications that explicitly permit overlays.
Forcing a hook can violate a game’s rules, trigger anti-cheat action, or expose the system to untrusted code. Treat a protected process as a compatibility limitation, not an invitation to bypass its safeguards.
Rank #4
- Chipset: NVIDIA GeForce RTX 5080
- Video Memory: 16 GB GDDR7
- Memory Interface: 256-bit
- Output: DisplayPort x 3 (v2.1a) / HDMI 2.1b x 1
- Digital maximum resolution: 7680 x 4320
When a clean reinstall is justified
Reinstalling is appropriate when the overlay fails across several unrelated games, RTSS crashes on launch, settings cannot be saved, or antivirus software quarantined a required file. It is excessive for a warning that leaves the target game’s OSD working.
- Close the game, MSI Afterburner, and RTSS.
- Uninstall MSI Afterburner and RTSS through Windows’ installed-apps interface.
- Reboot Windows so locked files and old processes are cleared.
- Install the current MSI Afterburner package with its compatible RTSS companion.
- Reboot again.
- Test in a simple, non-competitive game before restoring custom profiles, overlays, or frame limits.
If the fresh installation works, restore profiles one at a time. A failure immediately after importing a profile points to that profile’s settings rather than to the new installation.
Suppressing the dialog without repairing the hook
RTSS has a silent setting that hides the notification. To use it, close MSI Afterburner and RTSS, open the RTSS ProfileTemplatesConfig file with administrative rights, change Silent from 0 to 1, and save the file. Reopen the programs afterward.
This setting suppresses the message only. It does not restore an absent FPS counter, frametime graph, or frame limiter. Use it only when you have confirmed that the warning concerns an irrelevant process or you deliberately accept the missing feature; otherwise, complete the diagnostic steps first.
Use the least invasive fix that matches the symptom
| Option | Scope | Invasiveness | Security implication |
|---|---|---|---|
| Do nothing after verifying the OSD works | Warning only | None | No security change |
| Restart RTSS and Afterburner | Stale or duplicate processes | Low | No security change |
| Match privilege levels | One game or launcher with elevation | Low | Avoid permanent elevation where possible |
| Disable conflicting overlays | One or more games | Low to moderate | Removes competing injectors rather than weakening protection |
| Reset a game profile | Single-title failure | Moderate | Leaves anti-cheat protections intact |
| Update the paired packages | Broad or version-related failures | Moderate | Use legitimate installers only |
| Clean reinstall | Several games, crashes, or damaged files | High | Rebuilds configuration without bypassing protections |
Set Silent=1 |
Notification suppression | Low | Hides evidence; does not fix functionality |
Preventing the warning from becoming a recurring problem
- Keep MSI Afterburner and RTSS updated together instead of mixing releases from different periods.
- Launch RTSS and Afterburner before the game so profiles are available when the target process starts.
- Maintain one primary FPS or performance overlay and disable duplicate displays from launchers and capture tools.
- Use a separate RTSS profile for each game that needs different detection or frame-limit settings.
- Expect overlays to be unavailable in titles whose anti-cheat software blocks injection.
- After a Windows, graphics-driver, or game update, test the OSD before changing advanced RTSS options.
Final decision checklist
Use this order: verify the feature in the actual game, restart all RTSS and Afterburner processes, match privilege levels, remove overlay conflicts, update both packages, reset the affected profile, and reinstall only when the problem is broad or the files are damaged. If the title uses anti-cheat protection, accept the block and use an approved in-game display. Hide the dialog with Silent=1 only when you have confirmed that no needed overlay function is missing.
Quick Recap
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.
