NV-UV: an undervolt companion for RTX 30, 40 and 50

A companion that assumes Afterburner is already there

NV-UV is positioned precisely in its README, and the positioning is the first thing to understand. It simplifies GPU undervolting by working alongside MSI Afterburner, and it is described as a companion tool rather than a replacement. For overclocking, the OSD, fan control and advanced curve editing, the documentation says Afterburner remains the tool of choice.

That division of labour defines the audience. Someone already running Afterburner on a desktop with an NVIDIA card who finds the voltage curve workflow tedious, not someone who wants a one-stop GPU utility. The feature list lines up with that reading: one-click presets, automatic game detection, crash recovery, a built-in DX12 and DXR stress-test scanner, and optional clock efficiency control for games.

The scope is bounded by hardware and platform too. The supported range is the RTX 30 series on Ampere, the RTX 40 series on Ada Lovelace and the RTX 50 series on Blackwell, and the platform line is unambiguous: Windows 10 or 11, 64-bit only, with no Linux or macOS support.

The clock efficiency feature has its own name in the release notes, Dynamic Clock Clapping, abbreviated DCC, and the newer versions also mention NVIDIA Auto-UV and NVIDIA Power Efficiency Mode as additions, alongside verified manual updates with rollback and optional private diagnostic reports.

The scanner is the part that decides whether a profile is safe

Undervolting a card and keeping the settings stable is a hardware risk, and the scanner is where the project tries to reduce it. It is described as a built-in DX12 and DXR stress-test scanner, and its behaviour has been tightened over several releases.

In version 0.99.6.1 the Voltage Step Scanner is documented as distinguishing four separate situations: missing readings, idle, insufficient test load and stale data, with voltage and GPU usage shown separately. The rule that matters is that missing readings alone do not block UV profiles, while unverified scan points remain unavailable for use. In other words, a scanner run that could not gather proper data does not disqualify the whole card, but it also does not hand you a curve built from points it never confirmed.

A second fix in the same release makes the scanner and optimizer keep crashes reported by the test process instead of labelling them only as unstable, which changes how a marginal curve is judged.

Setup is where most of the friction sits. Afterburner setup now checks GPU usage monitoring for the assigned NVIDIA GPU, including machines with integrated graphics and a discrete NVIDIA card present, and it offers to enable missing sources, preserves existing selections and rechecks them after applying. The release notes are careful to say that this does not add SLI support and that GPU1 and GPU2 refer to Afterburner's own GPU and sensor assignment, which is a distinction that matters when a machine has more than one adapter.

Failed restores now block further scanning

The most interesting behaviour in the release notes is a restriction rather than a feature. After a failed power-limit restore, further scans are blocked for the current session, and the documented recovery is to check or restore the power limit in Afterburner and then restart NV-UV before scanning again. The reason is given in the same release: power-limit restoration is only reported as successful after a successful driver call, and a failed restore preserves the saved target and shows a warning.

Related safety rules appear throughout. The 0.99.6.3 release adds a confirmed DCC recovery option for the case where a changed driver environment or the supported-clock list blocks startup recovery, and it keeps GPU identity and ownership checks in place, with the instruction to restart NV-UV after a successful recovery before making further GPU changes.

The 0.99.6.2 hotfix adds a layer of caution to the setup wizard itself. It fixes compatibility with MSI Afterburner 4.6.7 Beta 5, including installations with four or five voltage-control options, adds a Keep OOW, do not ask again option that is remembered across restarts, and adds safety checks to prevent an incorrect setup with unexpected Afterburner options. If Out of Warranty is selected, the wizard offers to switch back to standard MSI after confirmation.

Taken together, these are the behaviours that decide whether this tool is usable unattended. A profile that cannot be validated, or a card left in a state the tool will not touch until a human intervenes, is a deliberate design choice rather than a bug list.

NV-UV Play is the path without Afterburner

A separate product line sits alongside the main tool. NV-UV Play offers the same features with a focus on ease of use, and it works independently of MSI Afterburner. It handles its own undervolting profiles, fan curves and profile assignment per game, and for monitoring you can use RTSS alongside Play or Play's own overlay with the sensor readings available there.

For advanced users it also exposes experimental expert settings on supported GPUs, listed as Crossbar (XBAR), SYS and video clocks, NVVDD and MSVDD voltage limits, and Voltage Boost.

Two things about its status are worth stating plainly. Play is free, and it is currently available as a prerelease. A prerelease that runs alongside a stable tool is a reasonable arrangement, but it also means the two code paths are not the same thing, and features described in the main tool's notes are not automatically present in Play at the same level of maturity.

For someone who has never used Afterburner and wants a guided path into undervolting with fan curves and an overlay, Play is the entry point. For someone who already has Afterburner configured, the main tool is the one that adds the automation on top.

The hardware list, and the Linux tool that is not this one

The requirements section is explicit about which cards count. The listed Blackwell parts are the RTX 5090, 5080, 5070 Ti, 5070, 5060 Ti and 5060. The Ada Lovelace list covers the RTX 4090, 4080, 4070 Ti Super, 4070 Ti, 4070 Super, 4070, 4060 Ti and 4060. The Ampere list begins with the RTX 3090, and the requirements section is cut off there in the version of the documentation available here, so the remaining 30 series models are not listed in what can be read.

The operating system requirement is Windows 10 22H2 fully updated, or Windows 11, 64-bit.

The README also carries a warning about a similarly named project. It says explicitly not to be confused with doums/nvuv, a separate CLI tool for NVIDIA undervolting on Linux written in Zig, and it spells out the difference: different platform, different scope, different project. That is a useful distinction for anyone searching for an NVIDIA undervolting tool, since a Linux user looking for a command line utility is looking for a different program entirely and NV-UV will not run there.

The manual approach this tool automates also exists: undervolting through the vendor's own utilities or through Afterburner's curve editor by hand, which is slower, unglamorous, and works on the same hardware.

The repository publishes notes, not source

The top level of the repository holds three files: LICENSE.txt, README.md and THIRD-PARTY-NOTICES.txt. There is no source directory, no build script and no project file, so this is a distribution home rather than a development tree. The licence is a custom one that GitHub cannot classify, with the full text in the LICENSE file, and the third-party notices file records the licences of the components that ship inside the binary.

That has consequences for the people who would normally evaluate a tool like this. There is no commit history to read for intent, no issue-driven development visible in the tree, and no way to check what the scanner does to your card beyond trusting the release notes. The README is essentially a changelog, and it is well written in that role, with sections for bug fixes, GPU information, and the game database in each release.

The trust signals that are available are of a different kind. The NV-UV executable is digitally signed with a Certum code-signing certificate and an RFC 3161 timestamp, and the release notes report that VirusTotal reported 0 out of 67 detections for the signed release executable on October 10, 2026, with a link to the scan report. A signed binary with a timestamped certificate is at least verifiable on the machine that runs it.

The release cadence is fast, which is both a strength and a source of risk. Version 0.99.6.1 and 0.99.6.2 were published on 2026-10-10, 0.99.6.3 on 2026-10-14, and the last push was on 2026-10-14. The version number stays below 1.0, and the README offers a new feature list every few days.

The game database and the update path

Two supporting mechanisms run underneath the main features, and both are documented with unusual specificity.

The game database is what makes automatic game detection and DCC work. The 0.99.6.3 release bundles game database 2.37 with 731 entries, including the 20 recently requested games and mods, and notes that the same update is available through the shared library update in NV-UV and Play, so the two tools share one catalogue. The 0.99.6.1 release had shipped database 2.34 with 708 entries in total, so the database grows in step with the releases. The DCC identification logic was improved to handle games that share an executable name, using the full path and matching the NVIDIA profile, with Path of Exile and Path of Exile 2 named as the cases that prompted it.

The update path is described as verified manual updates with rollback, and the newest release fixed the cleanup of old update files, which is the kind of detail that shows the update mechanism is doing real work on disk. The same release also added optional private diagnostic reports, and earlier notes mention improved error-dialog handling and reconnection for the NVML telemetry process, with the requirement that the previous process be confirmed as stopped before reconnecting.

The practical picture is a tool that automates a hardware task, with a large catalogue of games to recognise, an installer-driven update path, and a set of guardrails that stop it from continuing after a failed operation. The guardrails are the part to read before the first scan.

Editorial conclusion

Adopt NV-UV if you own an RTX 30, 40 or 50 series card, already run MSI Afterburner, and want undervolting profiles applied per game without tuning voltage curves by hand. Skip it if you are on Linux or macOS, if you need overclocking, an on-screen display, fan control or advanced curve editing, since the README says Afterburner remains the tool of choice for those, or if you need source you can audit, because the repository contains only the README, a licence file and third-party notices. Before running the scanner, read the power-limit restore rules, check that Afterburner is set up with the correct GPU selected, and confirm your card appears in the supported list. The last push was on 2026-10-14 and v0.99.6.3 was released the same day.

Frequently asked questions

Official sources

1. christianp403-spec/NV-UV on GitHub
2. Issues
3. README
4. Releases