MSI Afterburner adds color-coded V/F curve usage map
The latest beta can visualize which parts of the voltage/frequency curve the GPU actually uses.
MSI Afterburner v4.6.7 Beta 4 Build 17439 has been released with a new feature for the voltage/frequency curve editor. The update adds a V/F hit map that records and displays the operating points recently used by the GPU.
Users can enable the hit map by pressing the M key while the V/F curve editor is open. Afterburner then overlays the last 256 hit points directly on the curve. Color gradients indicate how frequently the GPU reached each point.
© Unwinder 
© Unwinder Afterburner can now show which parts of the V/F curve are actually used
The feature should be useful when tuning an undervolt or overclock. Instead of only seeing the configured curve, users can now check which voltage and frequency combinations the GPU has actually selected during operation.
This can also make it easier to identify sections of the curve that are rarely or never reached. The hit map does not change the V/F curve itself. It only adds telemetry showing recent GPU behavior.
GPUProbe included
The same beta also includes the revived GPUProbe plugin that we covered previously. GPUProbe provides low-level MMIO and I2C access for custom sensors, including example configurations for per-chip VRAM temperatures and ASUS ROG Astral 12VHPWR monitoring.
MSI Afterburner 4.6.7 Beta 4 also changes low-level monitoring behavior on unsupported GPU architectures. Afterburner can now disable the low-level monitoring path automatically when required. The package ships with RivaTuner Statistics Server v7.3.8 Beta 1.
MSI Afterburner v4.6.7 Beta 4 Build 17439 is available for download. Changes list includes:
- New improvements in V/F curve editor. Now you may press <M> button inside the editor to toggle V/F hit map. Hit map visualizes the positions of the last 256 hit points on V/F curve. Each point’s hit frequency is indicated by color gradations. More info about it in this post.
- It is no longer necessary to manually disable low-level monitoring inside GPU profile after unlocking direct MMIO access on modern GPUs via editing RTCore.cfg, e.g. when installing third party Hotspot.dll plugin created by asder00. Now MSI Afterburner automatically disables low-level monitoring path for unknown/unsupported GPU architectures.
- RivaTuner’s GPUProbe plugin from 2006 is returning back to MSI Afterburner. Original RivaTuner’s version of this plugin was used in the past to help GPU reverse engineering and to simplify the process of exploring undocumented GPU MMIO registers. It provided power users easy way of testing custom sensors, based on data read from arbitrary MMIO registers. GPU MMIO registers reverse engineering is getting popular again today, thanks to RTX 50×0 hotspot drama. So MSI Afterburner’s version of GPUProbe is providing modern researchers exactly the same functionality as original RivaTuner’s plugin – it helps you to explore contents of undocumented GPU registers/sensors. In addition to that, MSI Afterburner’s version of GPUProbe plugin can also be used to explore arbitrary registers on arbitrary devices on GPU I2C bus. Please take a note that by default MSI Afterburner unlocks low-level MMIO access on legacy GPU families only (e.g. NVIDIA Tesla and older GPU architectures). So to use GPUProbe you still need to unlock MMIO as explained in this post. GPUProbe comes with two demo scripts:
- GPUProbeNVGPU.cfg – sample script using GPUProbe’s arbitrary GPU MMIO access functionality and implementing SYS_TSENSE, GPU_OFFSET_MAX, GPU_OFFSET_AVG and per-chip VRAM temperature channels on NVIDIA Ampere, Ada and Blackwell architectures
- GPUProbeROGAstral.cfg – sample script using GPUProbe’s arbitrary GPU I2C access functionality and implementing per-pin 12VHPWR voltage and current seniors and virtual “12VHPWR alarm” sensor on ASUS ROG Astral series GPUs with IT8915FN56
- RTSS has been upgraded to v7.3.8 beta 1
Source: Afterburner 4.6.7 Beta 4
