MSI Afterburner Gets First Stable Release In Months: 4.6.5 Brings Support For NVIDIA RTX 40 & AMD Radeon RX 7900 GPUs

Sep 20, 2024 - 21:09

0 1.3

MSI Afterburner Gets First Stable Release In Months: 4.6.5 Brings Support For NVIDIA RTX 40 & AMD Radeon RX 7900 GPUs

The latest version of MSI Afterburner has landed, bringing in stable support for NVIDIA GeForce RTX 40 & AMD Radeon RX 7900 GPUs.

MSI Afterburner is without a doubt one of the most popular GPU diagnostic and tuning utilities out there. It's been widely used by enthusiasts and overclockers to fine-tune their GPUs for benchmark and other purposes.

The latest MSI Afterburner 4.6.5 version comes out several months after the previous update which was due to the developer not receiving funds in a timely fashion due to the Russia & Ukraine war. It was revealed by the developer of MSI's Afterburner utility, Alexey Nicolaychuk aka "Unwinder", over at Guru3D Forums, the project ran into a funding issue due to the ongoing war and the political turmoil in Russia. International banks have seized SWIFT operations in Russia & US (plus its allies) have proposed a tech ban on Russia.

We asked MSI for an update back in January and the company stated to us that they are keeping in touch with Unwinder and trying their best to figure out this issue. With this recent update, it looks like the payment issue might have been resolved and the developer has resumed his work on his Afterburner project for MSI.

It is definitely a big relief and great to hear that MSI Afterburner is now back in action again and the new stable update brings more than just support for the AMD Radeon RX 7900 and NVIDIA GeForce RTX 40 GPUs as can be seen in the changelog below (via Guru3D):

Added NVIDIA GeForce RTX 40×0 series graphics cards support

Added voltage control support for GA103 and GDDR6X-based versions of NVIDIA GeForce RTX 3060 Ti

Added AMD RADEON RX 7900 series graphics cards support

Added total board power monitoring support for AMD RADEON RX 7900 series graphics cards

Added some future AMD and NVIDIA GPU PCI DeviceIDs to the hardware database

Added Intel Arc GPU support to the hardware monitoring module. Please take note that Intel Arc GPU overclocking and tuning is currently not supported due to Intel hardware control API support limitation to x64 applications only

Added experimental support for Intel 13th generation CPUs

Added experimental support for AMD Ryzen 7xxx CPUs

CPU usage data sources in the hardware monitoring module have been switched to an alternate implementation based on NtQuerySystemInformation(SystemProcessorIdleInformation), because traditional legacy idle time reporting in NtQuerySystemInformation(SystemProcessorPerformanceInformation) is broken in current Windows 11 22H2 builds

Added workaround for broken fixed fan speed programming API (Overdrive 5 compatible fallback path) for old Overdrive 7 GCN GPUs on 22.5.2 and newer AMD drivers

Added config file switch for disabling native reliability voltage control API on NVIDIA GeForce GTX 9×0 series graphics cards and forcing legacy P-state 2.0 voltage control API usage on such hardware. Power users may use this switch to bypass the voltage control lock on NVIDIA Maxwell series graphics cards on release 515 and newer drivers families

Improved correction formula parser with data format conversion, rounding, and min/max functions support

Added OCMailbox-based bus clock frequency monitoring for Skylake and newer Intel CPUs. Unlike traditional legacy timestamp clock-based bus clock frequency estimations, OCMailbox provides support for overclocked BCLK monitoring. Please take note that access to OCMailbox is blocked by the design of OS when HVCI is enabled

Improved SMART.dll monitoring plugin. Added temperature monitoring support for NVMe devices, including the secondary controller temperature for some Samsung NVMe drives

The default clock frequency limit of the voltage/frequency curve editor window has been extended to 3.5GHz. Please take note that you may still customize the limits via the config file if necessary

Update server location changed to new URL inside update checking system. The old update server location reached EOL