Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →RivaTuner v2.24c is a genuine historical release of Alexey Nicolaychuk’s classic GPU-tuning utility, not the modern RivaTuner Statistics Server. Released in August 2009, it provided low-level NVIDIA and ATI/AMD graphics-card controls, overclocking, fan management, hardware monitoring, profiles, registry tweaks, and legacy Direct3D tools.
It is also effectively obsolete. RivaTuner v2.24c was built for 2000s-era GPUs and Windows Vista/Windows 7-era drivers. It may launch or partially work in some newer environments, but it is not a supported Windows 10 or Windows 11 tuning solution. Use it for compatible legacy hardware, archival work, or an isolated test system—not as the normal way to tune a modern GeForce, Radeon, or Intel Arc GPU.
As an Amazon Associate I earn from qualifying purchases.
RivaTuner v2.24c at a glance
| Item | Historical detail |
|---|---|
| Product | Classic RivaTuner low-level GPU-tuning and monitoring utility |
| Developer | Alexey Nicolaychuk, better known as Unwinder |
| Release | RivaTuner v2.24c, the final publicly documented revision of the classic 2.24 branch |
| Release timing | August 23, 2009 in archival version listings; contemporary coverage appeared August 24–26 |
| Target hardware | NVIDIA Riva TNT through approximately GeForce 200-series hardware, plus selected ATI Radeon cards |
| Important driver focus | NVIDIA ForceWare/GeForce 190.xx drivers, including 190.15, 190.38, 190.56, and 190.62 recognition |
| Bundled components | RivaTuner Statistics Server v3.1.1 and D3DOverrider v2.0.1 |
| Modern status | Legacy and unsupported on current GPU generations and current Windows installations |
The archived 3DCenter version entry and contemporary release reports identify v2.24c as the last publicly documented classic RivaTuner release. That means latest in the historical RivaTuner sense—not current software.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →What was RivaTuner?
Classic RivaTuner was much more than an FPS counter. It was a low-level graphics-card configuration environment that exposed controls normally hidden behind the graphics driver. Depending on the GPU, driver, and operating system, it could adjust core, shader, and memory clocks; control fan behavior; monitor temperatures and frequencies; apply per-game profiles; modify driver-level settings; and run registry or patch scripts.
#1 Best Overall
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5080
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
NVIDIA hardware was RivaTuner’s strongest focus, but the program also supported selected ATI Radeon cards. Its documented hardware range ran from the Riva TNT generation through the GeForce 200 series, with older ATI hardware also represented. A download page that simply says Windows All or lists modern graphics cards should not be interpreted as proof of current compatibility. The program’s internal driver database and low-level access methods date from the late 2000s.
RivaTuner was also associated with two other utilities:
- RivaTuner Statistics Server, or RTSS: originally bundled as a companion component and used for monitoring overlays and related functions.
- D3DOverrider: a legacy Direct3D utility used to force VSync and triple buffering in some older games.
Those components are the reason modern search results often create confusion. RivaTuner v2.24c and modern RTSS are separate products.
What did the c revision change?
The original RivaTuner 2.24 release appeared in February 2009. Its broader branch included new driver databases, monitoring fixes, hardware-detection improvements, and changes to the bundled utilities. The c revision was primarily a compatibility update for late-2009 NVIDIA drivers rather than a completely new feature release.
NVIDIA had changed internal driver-version numbering as the ForceWare/GeForce 190.xx family developed. RivaTuner 2.24c updated recognition for the relevant driver family, including databases for:
- ForceWare/GeForce 190.15
- ForceWare/GeForce 190.38
- ForceWare/GeForce 190.56
- The subsequently released 190.62 driver
It also revised recognition of unified Windows Vista and Windows 7 driver numbering. The practical benefit was that RivaTuner could identify the driver correctly instead of requiring a manual version override.
Some download pages reproduce the entire 2.24 changelog under the v2.24c heading. That can make it appear that every listed feature was added in the c revision. A more accurate description is:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, 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 minute- The 2.24 branch introduced the larger group of bug fixes, monitoring changes, hardware-database updates, LCD improvements, and detection work.
- v2.24c was the late revision that brought the branch’s NVIDIA driver recognition up to date for the 190.xx era.
Contemporary reporting says the revision was prepared around the 2009 MSI Master Overclocking Arena and retained the 2.24 label rather than becoming 2.25. See the period reports from Svět Hardware, TweakPC, and WinFuture.
Features in the RivaTuner 2.24 branch
The following list describes the wider 2.24 branch. Not every item was new specifically in the c revision.
GPU clocks and driver-level controls
RivaTuner could expose core, shader, and memory-clock adjustments when the installed GPU and driver supported the necessary interfaces. It also offered driver-level performance settings and low-level graphics-card options. On NVIDIA systems, the controls were often more extensive than those available in the standard driver interface of the time.
These controls were hardware- and driver-dependent. Seeing a slider did not guarantee that a particular setting was being applied correctly, especially when the installed driver was outside RivaTuner’s recognized range.
Fan control and detection
The 2.24 branch improved low-level fan control and fan-duty-cycle monitoring on some reference and alternate card designs. It added heuristic on-die PWM-controller detection for certain G92-based cards and improved detection of clock generators where clocks had switched to the PCI Express bus clock.
Rank #2
- Powered by Radeon RX 9070 XT
- WINDFORCE Cooling System
- Hawk Fan
- Server-grade Thermal Conductive Gel
- RGB Lighting
It also exposed two experimental power-user controls:
EnableNVPLLBypassingDetectionEnableMPLLBypassingDetection
These were specialized detection options, not universal fixes for modern clock-reporting problems. Fan control depended on the card’s firmware, controller, driver, and the low-level interface RivaTuner could access. A missing fan option usually indicates unsupported hardware or an inaccessible controller.
Fan-control warning: a displayed fan percentage is not automatically proof that the physical fan is running at that speed. Test conservatively and verify temperatures independently. A missing monitoring value is inconvenient; a failed fan-control change can allow a GPU to overheat.
Hardware monitoring and scheduled tasks
RivaTuner included graphs and hardware-monitoring data sources for items such as clocks, temperatures, and fan information. It could run scheduled monitoring tasks and trigger behavior based on hardware or application events.
The 2.24 fixes included correction for monitoring scheduled tasks that were ignored because of incorrect monitoring-module initialization during startup. It also corrected an erroneous 100 MHz memory-clock reading on G9x-based adapters and fixed incorrect sticky-graph height updates.
That history is worth remembering when reading old monitoring values: even on hardware within the original target range, a reported number could be wrong. On modern hardware, old readings should be treated as untrusted.
Profiles, launcher, and startup behavior
Profiles allowed users to save a group of settings for later activation. In practice, there were several different uses:
- Manual profile: saved settings that the user activated when needed.
- Application profile: associated with a particular game or executable.
- Startup profile: applied when Windows started.
- Monitoring or event task: triggered by a hardware or application condition.
A profile was not a guarantee of compatibility. If RivaTuner did not recognize the driver or could not access the card’s controls, the profile could fail silently or apply only part of its settings.
Registry editor and patch scripts
RivaTuner included built-in registry-editing and patch-script capabilities. These features were intended for advanced driver and operating-system modifications, including changes that were not exposed in ordinary control panels.
Patch scripts and registry changes are particularly inappropriate for experimentation on a current production PC. They can change system behavior without a clear modern recovery path. Use a restore point or, preferably, a virtual-machine snapshot or dedicated legacy system before testing them.
Logitech G15 LCD support
The 2.24 branch improved output to the Logitech G15 keyboard LCD. Changes included:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches- Separating on-screen-display output from LCD output.
- Adding a dedicated Show in LCD option.
- Retiring the older
MapOSDToLCDpower-user registry entry. - Exposing LCD font-size adjustment in data-source properties.
- Reconnecting to the LCD dynamically if the Logitech LCD software restarted.
Bundled RTSS and D3DOverrider
The v2.24c package included RivaTuner Statistics Server v3.1.1 and D3DOverrider v2.0.1, according to the archived release documentation reproduced by Nexthardware.
D3DOverrider was designed for older Direct3D games. It could historically force VSync or triple buffering in situations where the game or driver did not provide a satisfactory option. It was not a universal solution for modern Direct3D 12, Vulkan, modern desktop compositors, or protected games. Triple buffering can also increase input latency, so forcing it is a trade-off rather than an automatic improvement.
Rank #3
- AMD Radeon RX 550 Chipset, Silver plated PCB & all solid capacitors provide lower temperature, higher efficiency & stability
- 9CM unique fan provide low noise and huge airflow for your GPU
- GPU Boost Clock / Memory Speed : up to 1183 MHz / 4GB GDDR5 / 6000 MHz Memory, Stream Processors 512, Perfect for 3D CAD/CAM working, video and photo editing, Video Games @1080p
- Support: DirectX 12, Shader Model 5.0, OpenGL 4.6/4.5, 4K Video Decode
Compatibility: Windows and graphics cards
| Platform or hardware | Practical assessment |
|---|---|
| Windows 2000 and Windows XP | Within the historical operating-system range, assuming a compatible period GPU and driver. |
| Windows Vista, including 64-bit Vista | Historically targeted by the release, but still dependent on driver version, hardware, and kernel-driver requirements. |
| Windows 7 | v2.24c recognized the Vista/Windows 7-era driver numbering, but that does not mean every Windows 7 configuration was fully supported. |
| Windows 7 64-bit | Kernel-mode driver-signing requirements could prevent the included low-level driver from loading. Some original distributions included a driver-update/signature file. |
| Windows 10 | Unsupported legacy software. It may install or partially run in some environments, but there is no reliable current compatibility basis. |
| Windows 11 | Unsupported. Do not treat a successful launch as proof that clock, fan, monitoring, or driver controls work correctly. |
| GeForce Riva TNT through GeForce 200-era cards | These are the relevant NVIDIA generations for which the old database and controls were designed. |
| Modern GeForce RTX, Radeon RX, Intel Arc, and other current GPUs | Not a supported target. The driver database, WDDM assumptions, low-level interfaces, and monitoring methods are obsolete. |
Windows 10 and Windows 11 did not exist when v2.24c was released. Their WDDM generations, driver security model, graphics APIs, and hardware interfaces are outside the program’s design assumptions. Do not confuse it starts with it is safe or functional.
Why 64-bit Windows can reject it
RivaTuner v2.24c used kernel-mode driver components. Microsoft’s documentation explains the kernel-mode code-signing requirements that apply to 64-bit Windows Vista and later; see the Microsoft signing requirements and driver-signing policy.
Free tools Windows power users keep installed
One-click scans. No signup required.
Some 64-bit Vista and Windows 7 distributions included a driver update or signature file with a name similar to RivaTuner224MSIMOA2009EditionDrv.rtu. If you are preserving a period installation, use only the file that belongs to the verified original distribution and only if the operating system accepts it normally.
Do not permanently disable driver-signature enforcement. Do not install an unrelated signature-bypass utility simply to force this old driver to load. That weakens the security model and does not make the old hardware controls reliable.
How to obtain and verify RivaTuner v2.24c
Because the program is discontinued legacy software, acquisition deserves more care than downloading a current utility from its vendor.
- Prefer the original Guru3D distribution or a clearly identified archive. Guru3D was the historical hosting partner for RivaTuner-related software, and its archived file directory preserves the installer listing.
- Check the filename. The archived distribution is commonly named
RivaTuner224c-[Guru3D.com].exe. Some scan records identify the same artifact asRivaTuner224c.exe. - Avoid wrappers and repacks. Do not use modified portable editions, cracked versions, renamed installers, or download sites that provide an additional downloader.
- Verify the hash before running it. A matching hash identifies a particular file; it does not prove that every mirror is trustworthy or that the software is suitable for a modern operating system.
The archived Guru3D directory is the relevant historical file source. A typical archived installer is approximately 2.7 MB, although mirror packaging can change the exact size.
Recommended Free Tools
Known hashes for the archived installer
MD5: 7143346b59d803b063f1e815df7f8a30
SHA-1: 702314ce4f34f5403104fd7a22e86bc5444a8095
SHA-256: 6b58ec00d230cb22bf71f700fa8090b243d8f5ab41f26f547be1c24581363540On Windows PowerShell, run this from the folder containing the installer:
Get-FileHash .RivaTuner224c-[Guru3D.com].exe -Algorithm SHA256Compare the resulting SHA-256 value with the one above. The archived ANY.RUN report records driver installation and scheduled-task behavior while reporting no malicious indicators in the analyzed sample. That is best understood as a limited analysis of one file—not a guarantee of present-day safety.
Security context: this installer is old software with privileged behavior. It installs or interacts with low-level drivers and auxiliary processes. Verify it, scan it with current security tools, and use an isolated legacy machine or virtual machine where practical. Do not install it on a production PC just to get an FPS counter.
Historical installation workflow
The following is a period-oriented v2.24c workflow, not a universal Windows 10 or Windows 11 installation recipe.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Use compatible hardware and a period driver. A GeForce 200-era card and a driver from the supported ForceWare/GeForce range are a more realistic target than a current GPU.
- Verify the installer. Check the filename and SHA-256 before execution.
- Create a recovery point. Make a restore point on a physical system or snapshot the virtual machine. A dedicated offline legacy installation is preferable.
- Run the installer as administrator. Permit the installer to add its components only if the package is the verified original.
- Handle 64-bit driver requirements carefully. On Vista or Windows 7 x64, use only the matching driver-update/signature package included with the original distribution if Windows accepts it. Do not use a permanent signing bypass.
- Reboot if requested. Low-level driver and startup components may not become active until after a restart.
- Confirm recognition before changing anything. Check whether the GPU, driver, monitoring module, and tray components appear correctly.
- Save a default profile. Keep a known-good, unmodified profile available before testing clocks, fan settings, or driver changes.
Opening NVIDIA driver controls
A contemporaneous Guru3D guide described this general path:
- Open RivaTuner and allow it to build or update its internal hardware and driver database.
- Open the Main page.
- Under Driver settings, choose Customize.
- Select the system-settings or graphics-card icon shown for the detected device.
- Choose the relevant performance level before changing clocks.
Labels and available icons vary by GPU, driver, and detected support. The historical Guru3D forum guide illustrates the workflow, but it should not be treated as a current interface manual.
Rank #4
- Powered by the NVIDIA Blackwell architecture and DLSS 4. System Requirements: Minimum 850W PSU with 16-pin 12V-2x6 (12VHPWR) connector required. Verify before purchasing.
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability. Compatibility: 348mm (13.7") length, 3.6 slots, 4.3 lbs. Confirm case clearance and slot spacing. GPU bracket included.
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.6-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
Using the old controls safely
Overclocking
RivaTuner’s clock controls were intended for incremental testing, not one-click maximum performance. If you are working with compatible legacy hardware:
- Change one control at a time.
- Use small increments.
- Keep voltage changes out of the process unless the hardware and cooling are specifically understood.
- Monitor temperature, clocks, fan behavior, and visual output.
- Test each setting with a repeatable workload or game session.
- Keep a default or known-good profile ready.
- Reset immediately after artifacts, driver resets, crashes, black screens, shutdowns, or abnormal temperatures.
These precautions do not make overclocking risk-free. Incorrect settings can cause instability and, depending on voltage, temperature, cooling, and hardware condition, create hardware risk. Current MSI guidance for Afterburner similarly emphasizes resetting changes and testing for flickering, crashes, and shutdowns, although that documentation concerns Afterburner rather than the 2009 RivaTuner core; see MSI’s support guidance.
Fan control
Fan control is especially dependent on the exact graphics card. If there is no fan-control option, the card may use an unsupported controller, firmware behavior, or driver interface. Do not force a control merely because an online guide shows it on a different model.
While testing, compare RivaTuner’s readings with an independent temperature or fan check when possible. If the fan does not audibly or visibly respond as expected, restore automatic control and stop testing.
Profiles and startup settings
Use manual profiles first. Only after a profile has been tested should you consider assigning it to an application or applying it at startup. A startup profile that fails on a changed driver can leave the system unstable before the desktop is fully available.
If an application profile does not apply, check whether the executable path is correct, whether the driver is recognized, and whether the profile contains controls that the card can actually expose. Profiles saved on one GPU or driver should not be assumed portable to another.
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 problemsTroubleshooting common failures
RivaTuner says no display driver was found
Common causes include:
- The installed driver is newer than the v2.24c database.
- The GPU is too new or is not one of the supported NVIDIA or ATI families.
- The driver uses a WDDM model or interface the program does not understand.
- The installed package is the base 2.24 release rather than the c revision.
- A manually forced driver version is wrong.
Older guides sometimes recommend setting ForceDriverVersion manually. That may make controls appear, but it does not prove that the underlying driver interface is compatible. Do not use a forced version as a routine solution on modern drivers; it can create a false impression that a setting is safe or functional.
Driver settings disappeared after a driver update
This was already a limitation near the end of RivaTuner’s useful life. A 2010 report documented v2.24c losing driver-setting controls after NVIDIA driver 258.96, demonstrating that the compatibility window was closing soon after release. The sensible response is to restore the previous compatible driver in a legacy environment or stop using RivaTuner—not to keep forcing newer driver versions.
RivaTuner64.sys will not load
This usually indicates a driver-signing or compatibility problem on 64-bit Windows. Confirm that the system is a historically compatible Vista or Windows 7 installation and that the package is original. Do not permanently disable signature enforcement and do not use an untrusted bypass tool.
The installed folder mentions the MSI Master Overclocking Arena 2009 edition
A folder or program name such as RivaTuner v2.24 MSI Master Overclocking Arena 2009 edition is not automatically evidence of a wrong download. Contemporary packages and reports used that event-related name even when the download was labeled v2.24c. Verify the installer’s source and hash rather than judging it by the folder name alone.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Monitoring values look wrong
RivaTuner 2.24 itself fixed an incorrect 100 MHz memory-clock reading on G9x adapters. That historical bug is a reminder not to trust every value automatically. Cross-check readings with another tool, particularly when using hardware outside the original target range.
A tray icon is missing
The 2.24 changelog described a startup-daemon bug in which RivaTuner Statistics Server or D3DOverrider could launch without showing its tray icon. Check Task Manager to see whether the process is running, restart the affected component, and verify that the installer was not a modified repack. A missing tray icon does not necessarily mean that no component started.
Best Value
- System Compatibility Note: This 2‑slot card measures 249 mm (L) x 132 mm (W) x 41 mm (H) and requires a single 8‑pin power connector. Please verify available chassis clearance and ensure your power supply is rated for a recommended 550W before purchase.
- Dedicated Support: Please contact us directly through Amazon for any product questions or assistance you may require.
- Next‑Gen AMD RDNA 4 Architecture: Powered by the AMD Radeon RX 9060 XT GPU with 32 Compute Units featuring 3rd Gen Ray Tracing and 2nd Gen AI Accelerators, delivering exceptional 1440p gaming and AI‑enhanced performance.
- Blazing‑Fast Engine Clock: Delivers a boost clock of up to 3290 MHz and a game clock of 2700 MHz out of the box, providing the raw power for smooth, high‑framerate gameplay.
- 16GB GDDR6 Memory on 128‑Bit Bus: Equipped with 16GB of high‑speed GDDR6 memory running at 20 Gbps, offering ample capacity and bandwidth for modern game textures and creative applications.
The overclock is unstable
Use the reset or default control, return to the known-good profile, and reboot if necessary. Then test at stock settings. If instability disappears, make only one small change at a time and test it before adding another. Artifacts, flickering, crashes, black screens, driver recoveries, and abnormal temperatures are reasons to stop—not signs that the setting is almost stable.
RivaTuner v2.24c versus modern RTSS
| Product | Primary purpose | Best present-day use |
|---|---|---|
| Classic RivaTuner v2.24c | Low-level GPU tuning, driver settings, fan control, monitoring, profiles, registry tools, and patch scripts | Compatible legacy hardware, old operating systems, archival preservation |
| RivaTuner Statistics Server | In-game OSD, frame-rate and frame-time display, frame limiting, monitoring hooks, and capture-related functions | Modern overlay and frame-limiter use |
| MSI Afterburner | GPU tuning, voltage and fan controls, monitoring interface | Supported modern hardware, commonly paired with current RTSS |
The current Guru3D RivaTuner page primarily concerns RTSS and should not be read as evidence that the classic RivaTuner core is still being updated.
Recommended Free Tools
MSI’s current documentation treats Afterburner and RTSS as separate processes and identifies RTSS as the component needed for in-game monitoring overlays. Therefore:
- For a current FPS counter, OSD, or frame limiter, install a current RTSS build—not RivaTuner v2.24c.
- For modern GPU tuning, use a current supported tuning utility rather than the old RivaTuner core.
- Do not assume that the RTSS bundled with a 2009 installer is equivalent to a current RTSS release.
Better choices for a modern gaming PC
| Your goal | More appropriate tool |
|---|---|
| Modern GeForce tuning, automatic tuning, or performance overlay | NVIDIA App on supported GeForce systems |
| Modern Radeon overclocking, undervolting, fan control, profiles, and metrics | AMD Software: Adrenalin Edition |
| Supported third-party GPU tuning | MSI Afterburner, normally with a current RTSS build when an OSD is needed |
| ASUS graphics-card tuning and monitoring | ASUS GPU Tweak III, where the card is supported |
| Modern in-game OSD or FPS limiting | Current RTSS, rather than the classic RivaTuner package |
| Old-game Direct3D VSync or triple buffering | D3DOverrider only for a specific legacy title and compatibility environment, with latency and anti-cheat caveats |
AMD Adrenalin, NVIDIA App, ASUS GPU Tweak III, and MSI Afterburner are not interchangeable in every feature or hardware combination. Use the vendor’s supported software first, especially for voltage, fan, and automatic-tuning functions.
When does RivaTuner v2.24c still make sense?
There are a few legitimate reasons to keep a copy:
- You are restoring a Windows XP, Vista, or Windows 7 gaming system.
- You own a compatible GeForce or older Radeon card whose controls are better documented in RivaTuner than in newer utilities.
- You are preserving a historical PC configuration or benchmarking environment.
- You need to investigate a specific old Direct3D game and are prepared to test D3DOverrider in isolation.
- You are documenting how late-2000s GPU tuning software worked.
For those uses, an offline physical legacy machine or an isolated virtual machine with compatible passed-through hardware is preferable. A virtual machine cannot automatically provide the low-level GPU access RivaTuner expects, so a VM is useful for preserving the software and interface but may not reproduce real overclocking or fan control without appropriate hardware access.
Final verdict
RivaTuner v2.24c is real, historically important software and the final publicly documented release of the classic RivaTuner line. Its c update mainly brought recognition for NVIDIA’s ForceWare/GeForce 190.xx drivers and revised Vista/Windows 7 driver-version handling; it did not turn the 2009 utility into a modern GPU tool.
Use it only when you specifically need a compatible legacy utility. For a current PC, use modern RTSS for overlays and frame limiting, and use NVIDIA App, AMD Adrenalin, MSI Afterburner, ASUS GPU Tweak III, or another maintained, hardware-appropriate utility for tuning and fan control.
Frequently Asked Questions
Is RivaTuner v2.24c the same thing as RivaTuner Statistics Server?
No. RivaTuner v2.24c is the old low-level GPU-tuning application. RivaTuner Statistics Server began as a companion component and evolved into a separate overlay, monitoring, and frame-limiting utility. Modern search results often use the name RivaTuner for RTSS, but the products should not be treated as interchangeable.
Can I use RivaTuner v2.24c on Windows 10 or Windows 11?
It is not supported on either operating system. It may launch or partially work in some configurations, but its kernel driver, hardware database, WDDM assumptions, and monitoring interfaces are from the 2000s. Do not install it on a modern PC merely for an FPS overlay or frame limiter.
Is RivaTuner v2.24c malware?
The original installer is a legitimate historical program, but it has privileged behavior because it installs or uses low-level drivers and auxiliary startup components. Verify the installer’s SHA-256 hash, scan it with current security software, avoid modified repacks, and use an isolated legacy system where practical. A matching hash proves file identity, not that old software is safe for every modern environment.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What graphics cards did RivaTuner v2.24c support?
Its documented range covered NVIDIA hardware from the Riva TNT era through approximately the GeForce 200 series, along with selected ATI Radeon cards. Modern GeForce RTX, Radeon RX, Intel Arc, and other current GPUs are outside its intended support range.
What should I use instead of RivaTuner v2.24c for an FPS counter?
Use a current RivaTuner Statistics Server build for an in-game overlay or frame limiter. For modern GPU tuning, use NVIDIA App for supported GeForce systems, AMD Software: Adrenalin Edition for Radeon systems, MSI Afterburner with current RTSS where appropriate, or a current vendor utility such as ASUS GPU Tweak III.
The Bottom Line
Bottom line: RivaTuner v2.24c is a legitimate August 2009 legacy GPU-tuning release, not modern RTSS. It is worth preserving for compatible period hardware and software, but it is obsolete and unsupported on current Windows versions and GPUs. Verify any archived installer, avoid signature-bypass tools, and choose current RTSS or vendor-supported tuning software for a modern gaming PC.
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.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
