v0.1.25

Caution

You use this software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility. The author accepts no responsibility or liability of any kind.

Windows 10/11 x86_64:

• nvbios-gui.exe: editor window, one file with its own GTK 4. The first start unpacks the runtime to %LOCALAPPDATA%\NVIDIA VBIOS Vix Editor (a few seconds); later starts reuse it. Not code-signed: SmartScreen may ask once (More info → Run anyway).
• nvbios.exe: command line, one file.

Linux x86_64 (glibc 2.39+: Ubuntu 24.04+, Debian 13+, Fedora 40+, Arch):

• nvidia-vbios-vix-editor-0.1.25-linux-x86_64.tar.gz: editor window (nvbios-gui, needs the system GTK 4) and command line (nvbios).
• nvbios-0.1.25-linux-x86_64: command line only, one file, no dependencies.

SHA256SUMS covers all four files: sha256sum -c SHA256SUMS on Linux, Get-FileHash FILE in PowerShell.

Changes since 0.1.24:

• GPC curve offset (Blackwell, Ada and Ampere; experimental, advanced field). A new field, "GPC curve offset", stores a default offset of the core VF curve in the BIOS, from -500 to +500 MHz: a constant equation linked to the curve's root equation. No stock BIOS does this (NVIDIA shifts the curve inside its equations instead), and the constant also moves the curve's own floor and cap. That the driver adds it to every point of the curve is inferred. A tuning tool's offset still applies on top, and 0 restores the stock bytes. Large values can make the card unstable. Not tested on hardware yet.

Loaders: Linux VBIOS Vix Loader (current main) and Windows VBIOS Vix Loader 0.3.1. On Windows, if the GPU drives your screen, turn Restart the GPU now off and restart Windows instead. Loading works with NVIDIA 615.x drivers on Linux and 616.x and 617.x on Windows; a future driver may stop it working, so check after every driver update.

Edited images keep the original signature: do not flash them with nvflash. Experimental fields are not hardware-tested unless their notes say otherwise. See README, LICENSE and THIRD_PARTY_NOTICES.md. Full list in CHANGELOG.md.

v0.1.24

Caution

You use this software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility. The author accepts no responsibility or liability of any kind.

Windows 10/11 x86_64:

• nvbios-gui.exe: editor window, one file with its own GTK 4. The first start unpacks the runtime to %LOCALAPPDATA%\NVIDIA VBIOS Vix Editor (a few seconds); later starts reuse it. Not code-signed: SmartScreen may ask once (More info → Run anyway).
• nvbios.exe: command line, one file.

Linux x86_64 (glibc 2.39+: Ubuntu 24.04+, Debian 13+, Fedora 40+, Arch):

• nvidia-vbios-vix-editor-0.1.24-linux-x86_64.tar.gz: editor window (nvbios-gui, needs the system GTK 4) and command line (nvbios).
• nvbios-0.1.24-linux-x86_64: command line only, one file, no dependencies.

SHA256SUMS covers all four files: sha256sum -c SHA256SUMS on Linux, Get-FileHash FILE in PowerShell.

Changes since 0.1.23:

• Memory levels that follow the memory offset (Blackwell, Ada and Ampere; experimental, advanced fields). A memory offset only seems to move the top stored memory levels: once it takes the memory below the next lower level, the memory drops to a low idle clock instead (on one RTX 3050 Laptop GPU, below a -500 MHz offset it fell from 6001 to 810 MHz). The new fields, one per intermediate level ("Memory clock N MHz follows the memory offset"), set the bit the stock BIOS uses on the levels the offset moves. That this bit is what makes a level move is inferred, so it may or may not let the memory run between the stored levels; lower the memory offset floor too. Not tested on hardware yet.

Loaders: Linux VBIOS Vix Loader (current main) and Windows VBIOS Vix Loader 0.3.1. On Windows, if the GPU drives your screen, turn Restart the GPU now off and restart Windows instead. Loading works with NVIDIA 615.x drivers on Linux and 616.x and 617.x on Windows; a future driver may stop it working, so check after every driver update.

Edited images keep the original signature: do not flash them with nvflash. Experimental fields are not hardware-tested unless their notes say otherwise. See README, LICENSE and THIRD_PARTY_NOTICES.md. Full list in CHANGELOG.md.

v0.1.23

Caution

You use this software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility. The author accepts no responsibility or liability of any kind.

Windows 10/11 x86_64:

• nvbios-gui.exe: editor window, one file with its own GTK 4. The first start unpacks the runtime to %LOCALAPPDATA%\NVIDIA VBIOS Vix Editor (a few seconds); later starts reuse it. Not code-signed: SmartScreen may ask once (More info → Run anyway).
• nvbios.exe: command line, one file.

Linux x86_64 (glibc 2.39+: Ubuntu 24.04+, Debian 13+, Fedora 40+, Arch):

• nvidia-vbios-vix-editor-0.1.23-linux-x86_64.tar.gz: editor window (nvbios-gui, needs the system GTK 4) and command line (nvbios).
• nvbios-0.1.23-linux-x86_64: command line only, one file, no dependencies.

SHA256SUMS covers all four files: sha256sum -c SHA256SUMS on Linux, Get-FileHash FILE in PowerShell.

Changes since 0.1.22:

• Fan zero RPM thresholds on Ada and Ampere (experimental, advanced fields). The lower and upper zero RPM thresholds added for Blackwell in 0.1.22 now also appear on Ada and Ampere cards that store them. They are editable where zero RPM is on, as on the GeForce Ada cards and most GeForce Ampere ones, and read-only elsewhere (for example the RTX 3080, 3090, 3070 and 3050 BIOSes of the corpus). Not tested on Ada or Ampere hardware yet. Turing BIOSes don't store these thresholds.
• Zero RPM upper threshold tested on one RTX 5080. With the upper threshold set to 60 °C (stock 50 °C), the fans stayed at 0 RPM at 59 °C during video playback; before, they started at about 52 °C. Reported in issue #12.
• Turing: a raised power limit confirmed on an RTX 2070. With the power limit raised from 200 to 225 W through the Windows loader, the card reached 225 W. Reported in Windows loader issue #4.

Loaders: Linux VBIOS Vix Loader (current main) and Windows VBIOS Vix Loader 0.3.1. On Windows, if the GPU drives your screen, turn Restart the GPU now off and restart Windows instead. Loading works with NVIDIA 615.x drivers on Linux and 616.x and 617.x on Windows; a future driver may stop it working, so check after every driver update.

Edited images keep the original signature: do not flash them with nvflash. Experimental fields are not hardware-tested unless their notes say otherwise. See README, LICENSE and THIRD_PARTY_NOTICES.md. Full list in CHANGELOG.md.

v0.1.22

Caution

You use this software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility. The author accepts no responsibility or liability of any kind.

Windows 10/11 x86_64:

• nvbios-gui.exe: editor window, one file with its own GTK 4. The first start unpacks the runtime to %LOCALAPPDATA%\NVIDIA VBIOS Vix Editor (a few seconds); later starts reuse it. Not code-signed: SmartScreen may ask once (More info → Run anyway).
• nvbios.exe: command line, one file.

Linux x86_64 (glibc 2.39+: Ubuntu 24.04+, Debian 13+, Fedora 40+, Arch):

• nvidia-vbios-vix-editor-0.1.22-linux-x86_64.tar.gz: editor window (nvbios-gui, needs the system GTK 4) and command line (nvbios).
• nvbios-0.1.22-linux-x86_64: command line only, one file, no dependencies.

SHA256SUMS covers all four files: sha256sum -c SHA256SUMS on Linux, Get-FileHash FILE in PowerShell.

Changes since 0.1.21:

• Fan zero RPM temperatures (Blackwell, experimental, advanced fields). Each fan and extra fan curve now shows the two temperatures stored with the zero RPM bits (43/50 °C on most cards): a lower and an upper threshold. Idle fans most likely stop below the lower one and start again above the upper one, so raising the upper one may keep them stopped longer at light load. That meaning is inferred from the firmware and the stored values, and it is not tested on hardware yet. Requested in issue #12.
• Fan curve hints. When a fan minimum or maximum is refused because of the curves, the row now names the curve points to change in the same edit, extra curves included.
• Fan minimum speed: lowering it did not lower the fans on one RTX 5080. With both minimums and the first curve points lowered from 1050 to 900 RPM and the override verified, the fans still ran at about 1050-1110 RPM at the driver's 30 %. Reported in issue #12.

Loaders: Linux VBIOS Vix Loader (current main) and Windows VBIOS Vix Loader 0.3.1. On Windows, if the GPU drives your screen, turn Restart the GPU now off and restart Windows instead. Loading works with NVIDIA 615.x drivers on Linux and 616.x and 617.x on Windows; a future driver may stop it working, so check after every driver update.

Edited images keep the original signature: do not flash them with nvflash. Experimental fields are not hardware-tested unless their notes say otherwise. See README, LICENSE and THIRD_PARTY_NOTICES.md. Full list in CHANGELOG.md.

v0.1.21

Caution

You use this software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility. The author accepts no responsibility or liability of any kind.

Windows 10/11 x86_64:

• nvbios-gui.exe: editor window, one file with its own GTK 4. The first start unpacks the runtime to %LOCALAPPDATA%\NVIDIA VBIOS Vix Editor (a few seconds); later starts reuse it. Not code-signed: SmartScreen may ask once (More info → Run anyway).
• nvbios.exe: command line, one file.

Linux x86_64 (glibc 2.39+: Ubuntu 24.04+, Debian 13+, Fedora 40+, Arch):

• nvidia-vbios-vix-editor-0.1.21-linux-x86_64.tar.gz: editor window (nvbios-gui, needs the system GTK 4) and command line (nvbios).
• nvbios-0.1.21-linux-x86_64: command line only, one file, no dependencies.

SHA256SUMS covers all four files: sha256sum -c SHA256SUMS on Linux, Get-FileHash FILE in PowerShell.

Changes since 0.1.20:

• Turing: PCIe slot power on the MSI GTX 1650. That slot-powered BIOS stores its slot power limit (63 W rated, 74 W ceiling) in a form the editor did not know, so it showed no slot field and the card stayed near 66 W whatever the board power. slot_power_rated_w and slot_power_max_w now edit it. Raising it is not tested on Turing yet; above 66 W rated the slot can be asked for more than the PCIe specification allows. Reported in issue #5.
• Ampere laptop: a lowered power ceiling confirmed on one RTX 3050 6GB Laptop GPU (70 W ceiling, 55 W default, Windows loader). It is the first laptop report; a raised ceiling is not tested on a laptop, where the platform (Dynamic Boost) sets the running limit. Reported in issue #4.
• Ada laptop images: a clear refusal. Saving a loader payload for an Ada laptop image now says that Ada laptop images are not supported yet, instead of only the byte counts: their laptop-only tables do not fit the 512 KiB the GSP firmware accepts.

Loaders: Linux VBIOS Vix Loader (current main) and Windows VBIOS Vix Loader 0.3.1. On Windows, if the GPU drives your screen, turn Restart the GPU now off and restart Windows instead. Loading works with NVIDIA 615.x drivers on Linux and 616.x and 617.x on Windows; a future driver may stop it working, so check after every driver update.

Edited images keep the original signature: do not flash them with nvflash. Experimental fields are not hardware-tested unless their notes say otherwise. See README, LICENSE and THIRD_PARTY_NOTICES.md. Full list in CHANGELOG.md.

v0.1.20

Caution

You use this software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility. The author accepts no responsibility or liability of any kind.

Windows 10/11 x86_64:

• nvbios-gui.exe: editor window, one file with its own GTK 4. The first start unpacks the runtime to %LOCALAPPDATA%\NVIDIA VBIOS Vix Editor (a few seconds); later starts reuse it. Not code-signed: SmartScreen may ask once (More info → Run anyway).
• nvbios.exe: command line, one file.

Linux x86_64 (glibc 2.39+: Ubuntu 24.04+, Debian 13+, Fedora 40+, Arch):

• nvidia-vbios-vix-editor-0.1.20-linux-x86_64.tar.gz: editor window (nvbios-gui, needs the system GTK 4) and command line (nvbios).
• nvbios-0.1.20-linux-x86_64: command line only, one file, no dependencies.

SHA256SUMS covers all four files: sha256sum -c SHA256SUMS on Linux, Get-FileHash FILE in PowerShell.

Changes since 0.1.19:

• Turing: board and connector power confirmed on one RTX 2080 Ti. With 500 W board power and 250 W per connector, the card reached about 458 W under load; the power limiter no longer triggered, the voltage limiters did. The stop near 300 W reported in 0.1.19 went away once the per-connector limits were raised. The voltage fields are still not tested on Turing hardware. Tested by @Cancretto.
• Turing: the Galax HOF XOC voltage layout is accepted. That image points REL and ALT at the OV equation (1125 mV). The editor showed no voltage field for it; it now shows REL, ALT and OV read-only and keeps VMIN editable. On a stock image, fixed REL and ALT at 1125 mV (advanced) give the same values; not tested on Turing hardware.
• Fan zero RPM confirmed on one RTX 5090. On an HP Omen RTX 5090, whose BIOS ships with the fan-stop bits clear, an image with fan_zero_rpm set to 1 loaded through the Windows loader: all three fans stood still at idle, started under load and stopped again after cooling down. Other boards are not tested. Tested by @dsemprich.
• GUI: a section says when some of its fields are not shown, when part of an image uses a layout the editor does not support yet.
• GUI: no more "Unknown" placeholder rows (input current limit, OCP, single-rail MSVDD ceiling). nvbios fields and the JSON keep them.

The loaders do not change: Linux VBIOS Vix Loader (current main) and Windows VBIOS Vix Loader 0.3.0. Loading works with NVIDIA 615.x drivers on Linux and 616.x and 617.x on Windows; a future driver may stop it working, so check after every driver update.

Edited images keep the original signature: do not flash them with nvflash. Experimental fields are not hardware-tested unless their notes say otherwise. See README, LICENSE and THIRD_PARTY_NOTICES.md. Full list in CHANGELOG.md.

v0.1.19

Caution

You use this software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility. The author accepts no responsibility or liability of any kind.

Windows 10/11 x86_64:

• nvbios-gui.exe: editor window, one file with its own GTK 4. The first start unpacks the runtime to %LOCALAPPDATA%\NVIDIA VBIOS Vix Editor (a few seconds); later starts reuse it. Not code-signed: SmartScreen may ask once (More info → Run anyway).
• nvbios.exe: command line, one file.

Linux x86_64 (glibc 2.39+: Ubuntu 24.04+, Debian 13+, Fedora 40+, Arch):

• nvidia-vbios-vix-editor-0.1.19-linux-x86_64.tar.gz: editor window (nvbios-gui, needs the system GTK 4) and command line (nvbios).
• nvbios-0.1.19-linux-x86_64: command line only, one file, no dependencies.

SHA256SUMS covers all four files: sha256sum -c SHA256SUMS on Linux, Get-FileHash FILE in PowerShell.

Changes since 0.1.18:

• Turing: more fields (experimental). Besides the board power limits: PCIe slot and connector power limits, slot and connector current thresholds, NVVDD output current limit (advanced), minimum voltage (VMIN), core and memory clock offset ranges, fan PWM, limits and curves, and the fixed REL/ALT voltages (advanced). On one RTX 2080 Ti the override loaded through the Windows loader and nvidia-smi showed the edited board power limit, but the card still stopped near 300 W under load; raising the connector limits too may be needed (not confirmed). Nothing else is tested on Turing hardware. If you own a Turing card, please help test: see the tester guide.
• Ada: REL and ALT follow OV (advanced, experimental). nvvdd_rel_alt_follow_ov now works on Ada (1200 mV OV on every Ada image; on the RTX 4080, REL goes from a fixed 1075 mV to 1200 mV). Not tested on Ada hardware.
• Ada: fixed REL and ALT voltages (experimental). nvvdd_rel_fixed_mv / nvvdd_alt_fixed_mv where the equation is a constant (RTX 4090 newer image, RTX 4080, RTX 4000 Ada; ALT alone on the 4080 SUPER, 4070 Ti SUPER and 4060). Until now the RTX 4080 showed only VMIN under Voltage. Not tested on hardware.
• Blackwell: REL and ALT follow OV confirmed on one RTX 5090.
• Fan zero RPM (experimental, opt-in, GB20x). New field fan_zero_rpm. Not hardware-tested. Contributed by @bitninja0 (PR #2).
• Ampere: connector power sum (experimental). connector_sum_power_rated_w / connector_sum_power_max_w, the row that caps the 12 V connectors together (300/350 W on an RTX 3080 Ti with two 8-pin connectors). Raising the per-connector limits alone may have no effect there; the GUI now says so on each connector row.
• Ampere: connector current thresholds (experimental, opt-in). Not hardware-tested.

The loaders do not change: Linux VBIOS Vix Loader (current main) and Windows VBIOS Vix Loader 0.3.0.

Edited images keep the original signature: do not flash them with nvflash. Experimental fields are not hardware-tested unless their notes say otherwise. See README, LICENSE and THIRD_PARTY_NOTICES.md. Full list in CHANGELOG.md.

v0.1.18

Caution

You use this software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility. The author accepts no responsibility or liability of any kind.

Windows 10/11 x86_64:

• nvbios-gui.exe: editor window, one file with its own GTK 4. The first start unpacks the runtime to %LOCALAPPDATA%\NVIDIA VBIOS Vix Editor (a few seconds); later starts reuse it. Not code-signed: SmartScreen may ask once (More info → Run anyway).
• nvbios.exe: command line, one file.

Linux x86_64 (glibc 2.39+: Ubuntu 24.04+, Debian 13+, Fedora 40+, Arch):

• nvidia-vbios-vix-editor-0.1.18-linux-x86_64.tar.gz: editor window (nvbios-gui, needs the system GTK 4) and command line (nvbios).
• nvbios-0.1.18-linux-x86_64: command line only, one file, no dependencies.

SHA256SUMS covers all four files: sha256sum -c SHA256SUMS on Linux, Get-FileHash FILE in PowerShell.

Changes since 0.1.17:

• Turing (experimental, not tested on any Turing GPU). TU102, TU104, TU106, TU116 and TU117 images (GeForce RTX 20 and GTX 16, TITAN RTX, Quadro RTX, T series; BIOS 90.xx) are recognized, desktop, laptop and Max-Q.
  • Only the board power limits are editable: power_max_w, power_default_w and power_min_w. The power table decodes like the Ampere one on the 22 Turing images examined (for example 260/338 W on the RTX 2080 Ti, 75 W on the GTX 1650), and edits go to both banks with their checksums. Voltage, clock and fan tables are not decoded on Turing.
  • Turing images carry a signed digest list over the power table that the editor cannot update; whether the driver checks it is unknown.
  • Saving an edited Turing copy saves two loader files: <name>-loader.bin (the first bank, unchanged; load it first) and <name>-loader-e0end.bin (the same bank ending at its last data image, without the digest list; try it if the first does not apply the edit). From the command line: nvbios normalize edited.rom payload.bin --representation turing-e0-end-v1.
  • If the driver rejects an override, the card runs its stock VBIOS. If you own a Turing card, please help test: follow the tester guide and report in an issue.

Turing needs the new loaders: Linux VBIOS Vix Loader (current main; re-run the setup so the module is rebuilt with the Turing chips) and Windows VBIOS Vix Loader 0.3.0. Both are open source under the same license.

Edited images keep the original signature: do not flash them with nvflash. Experimental fields are not hardware-tested unless their notes say otherwise. See README, LICENSE and THIRD_PARTY_NOTICES.md.

v0.1.17

Caution

You use this software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility. The author accepts no responsibility or liability of any kind.

Windows 10/11 x86_64:

• nvbios-gui.exe: editor window, one file with its own GTK 4. The first start unpacks the runtime to %LOCALAPPDATA%\NVIDIA VBIOS Vix Editor (a few seconds); later starts reuse it. Not code-signed: SmartScreen may ask once (More info → Run anyway).
• nvbios.exe: command line, one file.

Linux x86_64 (glibc 2.39+: Ubuntu 24.04+, Debian 13+, Fedora 40+, Arch):

• nvidia-vbios-vix-editor-0.1.17-linux-x86_64.tar.gz: editor window (nvbios-gui, needs the system GTK 4) and command line (nvbios).
• nvbios-0.1.17-linux-x86_64: command line only, one file, no dependencies.

SHA256SUMS covers all four files: sha256sum -c SHA256SUMS on Linux, Get-FileHash FILE in PowerShell.

Changes since 0.1.16:

• Windows: the programs start again on CPUs without AVX-512. The 0.1.15 and 0.1.16 .exe files closed at once, without a message and before unpacking anything, on CPUs without AVX-512 (most Intel CPUs and AMD Ryzen 5000 and older): the compiler built their memory-copy routine for the CPU of the build machine. The build now targets baseline x86-64 and fails if AVX or AVX-512 code reaches either program (0.1.14 needed AVX2 for the same reason). The editor itself and the Linux packages are unchanged; see 0.1.16 for its latest changes (evaluated VMIN, REL/ALT follow OV, fan percent).

The loaders are open source too, under the same license: NVIDIA Linux VBIOS Vix Loader and NVIDIA Windows VBIOS Vix Loader (its Verify button checks that the driver is running the loaded image; the loader is built differently and was not affected).

Edited images keep the original signature: do not flash them with nvflash. Experimental fields are not hardware-tested unless their notes say otherwise. See README, LICENSE and THIRD_PARTY_NOTICES.md.

v0.1.16

Caution

You use this software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility. The author accepts no responsibility or liability of any kind.

Windows 10/11 x86_64:

• nvbios-gui.exe: editor window, one file with its own GTK 4. The first start unpacks the runtime to %LOCALAPPDATA%\NVIDIA VBIOS Vix Editor (a few seconds); later starts reuse it. Not code-signed: SmartScreen may ask once (More info → Run anyway).
• nvbios.exe: command line, one file.

Linux x86_64 (glibc 2.39+: Ubuntu 24.04+, Debian 13+, Fedora 40+, Arch):

• nvidia-vbios-vix-editor-0.1.16-linux-x86_64.tar.gz: editor window (nvbios-gui, needs the system GTK 4) and command line (nvbios).
• nvbios-0.1.16-linux-x86_64: command line only, one file, no dependencies.

SHA256SUMS covers all four files: sha256sum -c SHA256SUMS on Linux, Get-FileHash FILE in PowerShell.

Changes since 0.1.15:

• Minimum voltage (VMIN), experimental. New nvvdd_vmin_mv / msvdd_vmin_mv fields edit the equation the driver actually evaluates as VMIN: on Blackwell the constant equation selected at rail row +0x13, on Ada and Ampere the equation at rail row byte 7 when its clamp pins the value.
  • The value can go from 450 mV (Blackwell) or 400 mV (Ada, Ampere) up to the lowest value REL can take, less the most the equations chained after VMIN can add, so VMIN never ends up above REL (for example up to 753 mV on the RTX 2000 Ada and 814 mV on the RTX 4080).
  • Tested on an RTX 5080: 800 → 850 mV made the driver report VMIN 850 mV, and the card idled at 850 mV.
  • Tested on an RTX 2000 Ada: the driver reported the stored value plus 90 mV (650 mV stock, 790 mV with 700 mV stored). The offset may differ on other boards.
  • Other shapes (for example the min/max equation trees of the RTX 5090 MSVDD and RTX PRO 4000 SFF rails) are read-only, and so is the RTX 5080/5070 Ti MSVDD VMIN. Not tested on Ampere.
• The old "VMIN equation ceiling" is not VMIN. *_vmin_equation_max_mv is the slot the driver's rail info lists as VMIN, but the driver does not evaluate it as the minimum voltage. It is now read-only on every image and relabelled; the key is unchanged.
• REL and ALT follow OV (advanced, experimental, not tested on hardware). On Blackwell, behind Show advanced XOC-style fields, nvvdd_rel_alt_follow_ov = 1 points the NVVDD REL and ALT selectors at the OV equation, as the ASUS XOC and MSI Lightning RTX 5090 images do: a flat voltage limit equal to OV (1.2 V on the RTX 5090).
  • The rail table lives in the legacy image, which has its own SHA384 object directory. The editor now reads it (integrity.legacy_directory) and repairs its hashes, digest and checksum on this edit. On the stock ASUS RTX 5090 image the result matches the XOC image's rail table byte for byte.
  • Save it on its own. Once a copy has it at 1, the field is read-only, so keep the original image to go back. Images without an ALT selector (such as the RTX PRO 4000 SFF) move REL alone.
  • Power and clock limits still apply: a higher voltage limit only helps when voltage is what holds the card back.
• Fan percent. The driver maps its fan percent linearly from 30 % at the minimum speed to 100 % at the maximum speed (measured on four Blackwell models). The fan descriptions now say so: the 30 % setting runs at fan_N_min_rpm.
• Ada and Ampere: min/max equations now read their child links correctly when the editor checks whether an equation is shared. On the tested images this changes no field.

The loaders are open source too, under the same license: NVIDIA Linux VBIOS Vix Loader and NVIDIA Windows VBIOS Vix Loader (its Verify button checks that the driver is running the loaded image).

Edited images keep the original signature: do not flash them with nvflash. Experimental fields are not hardware-tested unless their notes say otherwise. See README, LICENSE and THIRD_PARTY_NOTICES.md.