Riva tuner update: RTSS Rivatuner Statistics Server 7.2.3 Download

Some system components cannot be hooked right now

If you often encounter a message from RivatunerStatisticsServer, MSI AfterBurner, Direct3D9, etc. stating Some system components cannot be hooked right now, It is strongly recommended to restart the application then this post may help you. In short, this error prevents the user from monitoring the performance of different hardware components. With this error, one cannot observe the performances of RAM, GPU, or CPU on the MSI Afterburner. The issue is related to the RivatunerStatisticsServer and has been plaguing users for quite some time. In this post, we will share how you can fix the problem.

What is the Rivatuner Statistics Server?

What is the Rivatuner Statistics Server is a well-known FPS limiter. With this small utility, one can monitor frame rates and limit FPS with ease. It is also one of the best top-performance video capturing servers for a majority of graphic cards.

The Rivatuner Statistics Server also enables the user to monitor and overclock the NVIDIA graphics card.  That plays a significant role in PC gaming.

Though the popping up of this message can be frustrating, there are some ways to resolve the problem. Take a look at the methods you can use to fix the error

  • Restart Application
  • Reinstall or Update Software
  • Rollback recent Windows Update

You will need admin permission to resolve this

1] Restart Application

One of the simplest ways to resolve the RivatunerStatisticsServer error is to restart the application. By restarting the application, you are basically resetting the checking sequences associated with it. That way, it can fix the error. Moreover, if there has been any new hardware installation, restarting will help.

Restarting the application will reset it, ensuring that the error is resolved. Keep in mind that closing the application by clicking on the top-right corner will simply minimize it. That is not the way to restart it. However, to restart, you must use the Task Manager.

  • Use Control + Shift + Esc to launch the Task Manager
  • Locate the RivatunerStatisticsServer (RTSS.exe)  in the Processes list
  • Right-click on it and select End Task
  • Launch the application again from the Start Menu application list and check if the issue still exists.

Read: System doesn’t have any USB boot option

2] Reinstall or Update Software from which you are getting this error

In some cases, files fail to be downloaded fully while the application gets installed. However, this is one of the rare reasons contributing to this problem. Still, this might lead to an error. Thus, you need to re-install the application and make sure that the files are downloaded completely.

Moreover, installing the recent version is relatively easy. You need to click on the link to the latest version. After that, you must download the application. Make sure that you first uninstall the application, and then install it again.

You will need to uninstall the RivaTuner app which you can find in Settings > Apps.

Another way to resolve this error is to update the software. Keep in mind that the developers may have recently fixed the issue. You need to install the latest MSI Afterburn to get rid of this problem. Since RivaTuner and MSI Afterburner are integrated, it may help.

Read: Windows could not finish configuring the system

3] Rollback recent Windows Update 

Windows updates are an excellent way to remove bugs and glitches from the system. That is the main reason why people seem eager to install the latest updates on their PC. However, there is a downside to this too. Windows updates can interfere with the working of different applications.

One such application that can be affected is the MSI Afterburner. Several users have reported this error after installing the latest Windows update. Here, the only solution is to delete the latest update. You need to revert the changes you have made to the system. Undoing them will help in resolving the error.

  • Open Windows Settings using Win + I
  • Navigate to Windows Update > Update History
  • Scroll to the end to locate Uninstall updates settings.
  • Click to open and then find out the most recent update
  • Select and then choose to uninstall.

Ensure you do not do this for any of the old updates, but only for the recent ones after which the problem started happening.

Conclusion 

MSI Afterburner and Rivatuner Statistics Server is an excellent combination to monitor the performances of hardware pieces. That is why you must assess why the “Some System Components Cannot be Hooked Right Now” error keeps popping up. Luckily, there are multiple ways to handle the problem.

Does MSI Afterburner need RivaTuner?

It is true that RivaTuner is integrated with MSI Afterburner. But, MSI Afterburner does not need RivaTuner for functioning. RivaTuner is a freeware overclocking and hardware monitoring program for Nvidia video cards.

Does RivaTuner reduce FPS?

RivaTuner offers FPS capping, thus reducing FPS. Moreover, it also enhances CPU usage. It is essential to note that the impact it has on FPS is not much, it is instead 5-10%.

How do I show FPS on RivaTuner?

In order to show FPS on RivaTuner, you need to use the Standalone Rivatuner Statistics Server. There, you must enable the “Show own statistics” settings. This will lead to the on-screen display of FPS. You can then move it anywhere you want on the screen with ease.

Una nuova revision per Rivatuner

E’ disponibile per il download una nuova versione di Rivatuner, release 15.4. Rivatuner un popolare tool per l’ottimizzazione e il tweaking delle schede video, sia ATI che NVIDIA, che tra le varie funzionalit permette anche di effettuare overclock manuali.

Il download disponibile in locale dalla sezione software di Hardware Upgrade, a questo indirizzo.

Di seguito le note fornite a corredo con quetsa nuova revision:

Minor bugfixes:

  • Fixed crash on dual-head display adapters with display connected to the secondary RAMDAC
    under Windows 2000.
  • Duty cycle is no longer rounded improperly when trying to apply a fan speed matching
    with the current one.
  • Daylight saving time correction is no longer applied when viewing .hml files.
  • Minor UI fixes.

What’s new:

  • Added ForceWare 75.xx driver family support.
  • Updated databases for Detonator and ForceWare driver families. Added databases for
    ForceWare 67.66, 71.22, 71.24, 71.25, 71.40, 71.50, 71.80, 71.81, 71.84, 71.90 and 75.90
    drivers.
  • Added Catalyst 5.1 and 5.2 detection.
  • Updated Catalyst 5.1 and 5.2 certified SoftR9x00, ATIOverclockingAntiprotection and
    ATIOverclockingAntiprotectionRuntime patch scripts.
  • Added NV4x-compatible driver-level overlay color correction.
  • Added «OpenGL version string override» option to the «Compatibility»
    tab of «OpenGL tweaks» dialog for the Detonator 27. xx and newer drivers. This
    option is useful for troubleshooting and can be used to solve problems with some
    incorrectly written OpenGL application, expecting harcoded OpenGL version string. For
    example, this option can be used to launch «The Chronicles of Riddick — Escape from
    Butcher Bay», which expects OpenGL 1.3 and doesn’t work properly on OpenGL 2.0
    drivers like ForceWare 75.90.
  • Now the list of application profiles for the ForceWare 56.xx and newer drivers in the
    main tab and the list of profiles accessible via the «Scan registry for existing
    profiles» button are sorted in ascending order.
  • Now RivaTuner displays / adjusts internal model ID instead of hardwired PCI DeviceID in
    the NVStrap driver configuration tab when custom graphics adapter identification mode is
    selected on display adapters with BR02 PCI-E to AGP or AGP to PCI-E bridge.
  • Added %RT% and %RTFolder% macro names support to RivaTuner’s launcher tab. These macro
    names can be specified to launch RivaTuner itself or to specify path to RivaTuner’s
    folder.
  • Updated ATI and NVIDIA graphics processors’ PCI DeviceID database.
  • Added an ability of starting RivaTuner’s launcher items via the command line by the name
    instead of GUID. The syntax is: RivaTuner.exe /L:»<name>», where
    <name> is a name of the item you want to launch. Take a note that this syntax is
    ambiguous, as it is allowed to create multiple items with the same name, so use it with
    caution.
  • Improved low-level graphics subsystem diagnostic module:
    • Added PCI-E bus type detection.
    • Added maximum / current PCI-E link width detection for PCI-E display adapters.
    • Internal «NVIDIA CK804» codename is replaced with «NVIDIA nForce4
      series» in RivaTuner’s northbridges database.
  • Considering that some competing developers started bad practice of cloning RivaTuner’s
    hardware monitoring module concepts, features and even visual appearance, this version
    introduces bunches of hardware monitoring related user interface enhancement and new
    features to leave clonemakers back in the dust. The list of enhancements includes:

    • Added experimental fan voltage level monitoring for reference design NV30, NV35, NV38
      and NV40-based display adapters. This graph is helpful for understanding driver-level fan
      speed adjustment system. Take a note than this graph is trustworthy only when the fan is
      physically connected to the PCB’s fan voltage control circuit. So don’t rely on this graph
      if you have a boards with non-reference cooling system with no software voltage-based fan
      speed adjustment capability (e.g. ASUS or MSI 6800 series).
    • Added monitoring thresholds support. Now you can define unlimited count of thresholds
      for each monitoring data source and setup each threshold to launch any external
      application on upward / downward threshold crossing event. The primary aim of this feature
      was to give users an ability of performing emergency system shutdown when a temperature
      exceeds the threshold. However, considering that you may use a threshold’s command line to
      access to RivaTuner itself, the threshold can be configured to execute any of RivaTuner’s
      launcher items, so you may implement temperature based overclocking etc via newly
      introduced thresholds technology.
    • Considering that the graphs with multiple defined thresholds usually require more
      detailed Y-axis than the graphs with the rest monitored parameters (e.g. clock
      frequencies), now each graph can use either the previously available automatic height
      scaling mode to fit in the entire window or fixed size height mode. Fixed graph height
      mode can be activated either visually by dragging its’ upper / lower sizing border or
      manually by entering desired height in the graph’s properties window.
    • Added  button to the bottom-right corner of fixed height graph for quick switching
      it to automatic height mode.
    • Added button to the top-right corner of the graph for quick closing a graph window.
      Take a note that this button is available only when two or more graphs are displayed
      simultaneously.
    • Added framerate monitoring graph. Take a note that framerate monitoring can be
      implemented via API hooking only, and I treat this technology as potentially troublesome
      and virus-styled, affecting whole operating system and all running applications. That is
      why I continue «no API hooks in RivaTuner» politics, so framerate statistics
      collecting is performed via external RivaTunerStatisticsServer application, which must be
      loaded simultaneously with RivaTuner in order to monitor framerate via RivaTuner’s
      hardware monitoring module. Take a note that RivaTuner’s installer creates a shortcut for
      RivaTunerStatisticsServer in the Start menu. RivaTunerStatisticsServer can be also started
      via launcher by specifying %RTSS% macro as the path to the application.
      RivaTunerStatisticsServer v1.0 provides the following features:

      • Framerate statistics collecting for fullscreen Direct3D8 / Direct3D9 applications (for
        Windows XP only). RivaTunerStatisticsServer uses original OS GDI thunk hooking approach,
        which is not used in any of currently existing framerate monitoring software and greatly
        simplifies DirectX framerate monitoring implementation.
      • Framerate statistics collecting for both windowed and fullscreen OpenGL applications.
        Known limitations: currently total FPS is monitored when multiple windowed OpenGL
        applications are running simultaneously.
      • Ability to unload currently loaded RivaTunerStatisticsServer via launching new
        RivaTunerStatisticsServer instance with «-u» command line switch.
      • Even considering that performance impact of RivaTunerStatisticsServer is rather low
        (above 1%), there is still room for optimization left, so the performance impact can be
        and will be reduced in the future versions.
      • An ability of using RivaTunerStatisticsServer’s statistics in any other application via
        named shared memory. The sample code is available upon e-mail request, sample application
        will be included in SDK in the next version.
    • Added range selection operations support. Now you can hold <Shift> when pressing
      left mouse button on the first position on the graph, then move mouse cursor to the second
      position and release left mouse button to select this range. As soon as the range is
      selected, you may see its’ statistics (minimum, average and maximum values) and perform
      some selection-specific operations (discussed above). This feature was added special for
      simplifying framerate statistics analysis.
    • Added asynchronous operations support. Now all tracking markers related operations (e.g.
      manual tracking marker setting, «Mark minimum . ..» / «Mark maximum
      …» / «Remove all markers» commands) and all selection related operations
      can be applied to all graphs simultaneously as well as to the focused graph only.
      <Ctrl> modifier is reserved for asynchronous operations now, for example left mouse
      button click synchronously sets tracking markers on all graphs, but <Ctrl> + left
      mouse button click sets tracking marker on the focused graph only.
    • Added «Select all» / «Deselect» and «Select range»
      commands to the graph’s context menu. The last command is only active when two tracking
      markers are set in the graph and allows you to select a range between these markers.
    • Added monitoring statistics filtering functions, available via «Filter … over
      maximum limit» / «Filter … under minimum limit» commands from the graph’s
      context menu. These functions force RivaTuner to process statistics and to clean up the
      values, which lie outside the range specified with vertical scaling sliders. These
      functions were added for framerate statistics analysis simplification and they allow you
      to remove abnormally high or abnormally low values from it (e.g. abnormally high framerate
      caused by splash screen rendering between the tests in 3DMark, or 0 framerate during level
      loading in Quake III).
    • Now all the commands depending on hardware monitoring statistics (e.g. «Mark
      minimum …» / «Mark maximum …» / «Scale to fit» etc) are
      applied to selected range only, or to whole statistics when there is no range selected.
    • Changed tracking marker removal approach. Now existing marker can be removed by
      double-click instead of <Ctrl> + click, which is reserved for different purposes.
    • Optimized graph rendering code (up to 10 times faster under certain conditions).
    • Monitoring graph’s statistics is no longer reset when graphs’ list is changed or
      reordered.
    • Monitoring window can be maximized now by double clicking its’ caption.
    • It is no longer necessary to close RivaTuner in order to save the states of monitoring
      window control buttons (e.g. «Enable background monitoring»).
    • Added monitoring log file size limiting option.
    • Removed obsolette «Fan duty cycle» option from the data sources list in
      hardware monitoring setup window for RV360 based display adapters.
    • Added negative temperatures monitoring support for LM63-capable ATI display adapters.
    • Added clipping for above 100% duty cycle values displayed on the monitoring graphs for
      LM63-capable ATI display adapters.
    • Added fan duty cycle monitoring for F75373S-capable ATI display adapters.
  • Updated SDK / RTHMSharedMemorySample application to display statistics for sources
    supplying no data (e. g. framerate source when no Direct3D / OpenGL applications are
    running) correctly.
  • Improved low-level graphics subsystem diagnostic report module:
    • Changed undocumented NVIDIA registers naming scheme. Revised the list of dumped NVIDIA
      GPU registers, added some new registers, removed some obsolete ones.
    • Revised the list of dumped ATI VPU registers.
  • Improved fan control manager for LM63-based ATI display adapters:
    • Added option for restoring fan speed after resuming from suspended mode.
    • Added fan control for R430 and R480 based display adapters.
    • Minimum duty cycle guardband limit (25%) can be customized via the registry now.
  • Easter eggs updates:
    • New drivers support for some scripts.
    • Updated I2C dumping utility.
      • Added additional unlocking routines for some NVIDIA display adapters with locked I2C
        bus.
      • Added additional delays in NVIDIA I2C access routines to minimize the risk of
        collisions.
    • Added command line based access to NVIDIA CRTC registers (Read, Write, AND, OR and
      XOR-styled commands).

Riva Tuner Update Server Hatası

  • Sık Sorulan Sorular

JavaScript devre dışı bırakılmış. Daha iyi bir deneyim için tarayıcı ayarlarından JavaScript’i etkinleştiriniz.