b00nz/mVolt v0.50.8 on GitHub

On RTX 50, driver 621.01 and later accept voltage limit offsets but no longer enforce them. This release adds Voltage offsets (experimental) to BIOS override.

Once they are installed and verified, the Core and MSVDD voltage limits cards, XOC voltage range and Voltage boost work again on these drivers.

Open Settings → Advanced tuning → BIOS override, Voltage tab.
Set Voltage offsets (experimental) to On, choose Save limits, then Restart GPU or Restart Windows.
Wait until the voltage cards no longer show Reading… or Voltage offsets unverified, then tune as before.

Good to know:

RTX 20/30/40: the 621.01 restrictions no longer apply. Voltage limit offsets, XOC voltage range, Unlock OCP limits and the board-current auxiliary limit work again on 621.01 and later (#81).
On RTX 50 with 621.01 and later, Unlock OCP limits stays unavailable. Raise OCP on the Power & current tab, as before.
Undo: set Voltage offsets to Off, or choose Remove BIOS override, and restart as offered.
Before going back to v0.50.7 or older: remove the BIOS override in v0.50.8 and restart. v0.50.7 can't open your profiles once one of them has per-fan curves or clock locks.

What's new

This release brings voltage control back on RTX 50 with driver 621.01 and later, and limits the 621.01 restrictions to RTX 50. It also adds per-fan software curves, Check for updates and a Black-screen fix switch.

New logo: a blue lightning bolt replaces the old app icon.

BIOS override

New Voltage offsets (experimental) row on the Voltage tab (RTX 50, driver 621.01 and later).
New Black-screen fix row. NVIDIA's driver lowers MSVDD REL by 50 mV to prevent black screens; Off removes this after a GPU restart.
BIOS overrides made by other tools show as BIOS override not managed by mVolt+. Use current BIOS keeps the active BIOS as the new starting point and writes nothing. Remove BIOS override stays available.
XOC BIOSes that use one value for REL, ALT/OP and OV are edited as one value.
A different BIOS with a fixed VMIN can now be saved when the active BIOS calculates VMIN.

Fans

Per-fan software curves (#84): on cards with several fans, the mVolt+ curve has a fan menu (All fans, Fan N) and an Own curve switch. Other fans follow the shared curve. Profiles keep the own curves.

Profiles

Details and Save colour NVVDD/MSVDD offsets: accent when the BIOS override changed that limit, the pending colour when they no longer fit, grey when the driver ignores rail offsets. Hover shows the voltage each offset gives now.
Load for editing now opens profiles whose offsets no longer fit. Apply still refuses them and names the rail.
Profiles save clock locks again: Boost Lock, the V/F editor's Lock voltage point and Limit max clock. A profile without a lock leaves the current lock alone; Reset all releases it.
Optional Load for editing pen in the profile menu: set "profile_edit_button": true in appearance.json.

Settings and updates

Check for updates (Settings → General) and Check for updates at startup (off by default). A check only asks GitHub for the latest release.
Update to vX replaces mVolt+.exe and restarts it. Tuning is not changed. If anything fails, the old version stays.
Extended voltage offsets is removed. Voltage demand (Core/XBAR/SYS/Video) has no mVolt+ limit: the slider opens at −25…+50 mV and widens to fit the value.

Fixes

Enter after dragging a dashboard slider applies the value.
Laptops (#85): if the laptop changes the GPU power request right after a logon profile applies, mVolt+ keeps the laptop's value and shows a startup warning instead of failing.
Thermal limits can be changed on driver 621.01.
The Profile Details hover updates when moving along the same row.

Command line

--status and the state object no longer have voltage_demand_limit_min_mv, voltage_demand_limit_max_mv or voltage_demand_extended_range.
--core-vdemand, --xbar-vdemand, --sys-vdemand and --video-vdemand have no mVolt+ range; the driver's range applies.
With verified Voltage offsets, --nvvdd-offsets, --msvdd-offsets, --xoc and --boost use them. While they are unverified, a nonzero --boost fails.
Rail errors start with "NVVDD:" or "MSVDD:" and name the voltages.
--boost-lock now marks the applied profile as Custom, like other direct changes.