nvidia-windows-vbios-vix-loader README

README проекта с github.com/Panchovix/nvidia-windows-vbios-vix-loader. Одним файлом markdown: README.md.

NVIDIA Windows VBIOS Vix Loader

English | Español

Loads a modified VBIOS for an NVIDIA GPU on Windows without flashing it. The image is stored in the GPU's driver registry key, where the NVIDIA driver looks for a VBIOS override, and it applies after you restart Windows. verify checks that the driver is running it, and unload removes it again. The card's flash chip is never written.

Works with NVIDIA 616.x, 617.x and 621.x drivers (616.56 or newer; tested on 621.01 in the driver's default mode, and with versions up to 0.3.2 on 617.42 and 617.70). It may stop working in a future driver if NVIDIA decides to change or remove the registry override, so click Verify after every driver update.

Thanks to @pantsoftime (overclock.net), whose original vbios_override work this project family is built on. Without it, none of this would have been possible.

To modify the VBIOS, use NVIDIA VBIOS Vix Editor. For Linux, see NVIDIA Linux VBIOS Vix Loader. This repository only loads the VBIOS on Windows.

This project is not affiliated with or endorsed by NVIDIA. NVIDIA and GeForce are trademarks of NVIDIA Corporation.

Warning. A modified VBIOS can raise power, clocks and voltages beyond the card's design limits. You can damage hardware. Keep a copy of your original ROM and use this at your own risk.

What it does

load writes these values in the GPU's driver key, HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\NNNN:

Value Type Content
vbios REG_BINARY The VBIOS image chain from your file: from the legacy image to the end of the last image. Bytes before and after it in the file are not stored.
VixLoaderPreviousEnableGpuFirmware REG_SZ The EnableGpuFirmware value before the first load, saved on the first load only so unload can restore it: absent, a DWORD such as 0x00000012, or, if it was not a 4-byte REG_DWORD (another tool or a hand edit can leave a REG_SZ, REG_QWORD, REG_BINARY or a DWORD of another size there), an exact copy of its type and bytes written the way a .reg file writes them, for example hex(1):31,00,00,00.

It also deletes romOverride00 to romOverrideFF if present, flushes the key and reads the values back. It leaves EnableGpuFirmware as it is, except that it puts back the value saved by an older version that set it to 0x11.

Versions up to 0.3.2 also set EnableGpuFirmware to 0x11, which turns on the driver's GSP firmware mode. On Windows the driver does not use that mode by default for GeForce and RTX workstation cards (RTX 50 included), and on an RTX 4070 it made the display driver reset every time Apple Music started, even without an override. In its default mode the driver reads the override itself.

Restart Windows to apply the change. The driver keeps the image until Windows restarts, so restarting only the GPU is not enough to apply or remove an override. Shutting down and turning the PC back on works too when Windows Fast Startup is off. With Fast Startup on (the default on many PCs), a shutdown keeps the running driver in the hibernation file and the next start resumes it, so the change waits for the next restart. Nothing is lost either way, and nothing has to be loaded or removed again.

mVolt+ stores its BIOS file in the same vbios value (and sets EnableGpuFirmware to 0x11), so a BIOS loaded with mVolt+ on the same GPU is replaced. If EnableGpuFirmware was already 0x11 before the first load, it stays, and so does GSP firmware mode. For the driver's default mode, delete EnableGpuFirmware before the first load. If the override is already loaded, run unload first (it puts 0x11 back), then delete the value, load again and restart Windows. This project is not affiliated with mVolt+. Other values in the key are left alone.

unload deletes vbios and any romOverride records, restores EnableGpuFirmware exactly as it was before the first load, with the same type (or deletes it if it was absent), and deletes VixLoaderPreviousEnableGpuFirmware. It does not restart the GPU: restart Windows. If the saved value starts with hex(, remove the override with version 0.3.2 or newer: older versions don't read that form, so they delete it and leave EnableGpuFirmware at 0x11.

It does not flash the card, edit the VBIOS, or change clocks, fans or power limits by itself. unload returns the key to its state before the first load, except that an override written by another tool (mVolt+ vbios or romOverride records) is not restored; in that case load says so, and unload leaves EnableGpuFirmware as that tool set it.

Upgrading from 0.4.x

0.5.0 is the same loader rewritten in Rust. It keeps the registry values, commands, options, --json output, exit codes and window of 0.4.x, so an override loaded with 0.4.x is recognized: status, verify and unload work on it, and nothing has to be loaded again.

Upgrading from 0.3.2 or older

Versions up to 0.3.2 set EnableGpuFirmware to 0x11 on every GPU with an override, which keeps those GPUs in GSP firmware mode. Load the same file again with 0.4.0 or newer (it puts the saved value back), or remove the override, and restart Windows. status, and the Messages area of the window, show the GPUs that still have GSP firmware mode on from an older version.

Antivirus warnings

Up to 0.4.x, some antivirus programs and online scanners flagged the two exes (for example generic or "ML" detections, or "Python DLL sideloading"): each exe was a Python program packed with Nuitka --onefile, which unpacked the Python runtime into a temporary folder when it started. From 0.5.0 the exes are native programs written in Rust: they are not packed, unpack nothing and import only Windows system DLLs (Verify also loads the NVIDIA driver's nvapi64.dll from System32). They are still not code-signed. The loader does not use the network. The exes are built by GitHub Actions from this repository (see Tests).

If an antivirus flags a file, compare it with SHA256SUMS to confirm that it matches the published asset, and report the detection to that antivirus vendor as a false positive. If you still don't want to run the exes from the releases, build them yourself from the source the same way the workflow does (see the end of Usage).

And lastly, if you don't want to use this loader for an edited VBIOS, you can use the BIOS override of mVolt+ (Blackwell only, https://github.com/b00nz/mVolt) instead. Issues related to mVolt+ go there, not to this repo.

Status

The driver's default mode, the state 0.4.0 and newer leave (vbios stored, EnableGpuFirmware absent or at its default 0x12), was tested with driver 621.01 on an RTX 4090, an RTX 5070 and an RTX A2000 (the A2000 drives the display): after a Windows restart, Verify confirmed the override on all three, and the edited power limits (raised maximums and lowered minimums) applied and held under load. On the A2000, Apple Music opened and ran without a driver reset. It has since worked on Turing, Ampere, Ada and Blackwell GPUs, desktops and laptops alike (an RTX 2070 Laptop GPU among them), except RTX 40 (Ada) laptop GPUs, where it does not work. Drivers other than 621.01 are not tested in the default mode yet. If a GPU does not start in the default mode, remove the override in Safe Mode (see If the GPU does not start) and open an issue; version 0.3.2, which turns GSP firmware mode on, stays available.

Earlier results, with versions up to 0.3.2 (GSP firmware mode):

GPU family State
Blackwell GB20x (GeForce RTX 50, RTX PRO Blackwell) Uses the same registry values that mVolt+ uses to load BIOS files on Blackwell. Tested on an RTX 5070 (driver 617.42): an edited VBIOS loaded and worked after a GPU restart, without restarting Windows.
Ada AD10x (GeForce RTX 40, RTX Ada) Tested on an RTX 4090 (VBIOS 95.02.18, driver 617.42) with an ada-relocated-v2 payload: a raised power limit (671 W) and core clock offset range (+1200 MHz) applied. Other Ada GPUs are untested.
Ampere GA102–GA107 (GeForce RTX 30, RTX A series) Tested on an RTX A2000 (driver 617.42) with an ampere-relocated-v1 payload: a lowered power floor (5 W) applied. On an RTX 3050 6GB Laptop GPU (driver 617.42) a lowered power ceiling (70 W) applied; a raised one is untested on laptops. Other Ampere GPUs are untested. GA100 (A100, A30, A800) is not supported.
Turing TU102–TU117 (GeForce RTX 20, GTX 16, TITAN RTX, Quadro RTX, T series) Experimental. Tested on an RTX 2080 Ti (ROG Matrix BIOS, driver 617.70): with the board and connector power raised, the card reached about 458 W under load. An RTX 2070 reached 225 W with its power limit raised from 200 W, and an RTX 2070 SUPER also ran an edited image. Other Turing GPUs are untested. If the override is refused, the card runs its stock VBIOS. See the Turing tester guide.

If you try it, please open an issue with the GPU, driver version and result.

Requirements

Which file to load

The file must contain exactly one VBIOS for this GPU's PCI ID with a valid checksum. Full flash dumps with two banks are refused: export a single-chain payload with Vix Editor's command-line tool (nvbios.exe).

With Vix Editor 0.1.11 or newer, saving an edited Ada or Ampere copy also saves <name>-loader.bin next to it: load that file. The commands below do the same from the command line.

Usage

Window

  1. Download vbios-loader-gui.exe from the releases and check it against SHA256SUMS.
  2. Run it. Windows asks for administrator rights (it writes to the GPU's registry key).
  3. Select the GPU in the list. The list shows each NVIDIA GPU with its PCI location, driver version and override state.
  4. Click VBIOS file... and choose the file. The window checks it for the selected GPU right away and shows either OK (family, bytes to store, sha256) or why it is refused.
  5. Click Load (the same as load), read the confirmation (GPU, file, registry changes) and accept. Then restart Windows to apply the override.
  6. After the restart, click Verify to check that the driver is running the loaded VBIOS (the same as verify, see Verify).
  7. To go back to the card's own VBIOS, select the GPU, click Remove override (the same as unload) and restart Windows.

Every result and warning is also written in the Messages area. The window is in Spanish when Windows is; the Language menu, or vbios-loader-gui.exe --lang en / --lang es, changes it. It is dark when Windows uses the dark app mode; the Theme menu, or --theme light / --theme dark, changes it.

Command line

Download vbios-loader.exe from the releases, check it against SHA256SUMS, and open an elevated PowerShell in its folder.

# List NVIDIA GPUs: index, PCI location, driver version and override state.
.\vbios-loader.exe status

# Show what would be written, without writing anything.
.\vbios-loader.exe load .\payload.bin --gpu 0 --dry-run

# Store the override, then restart Windows to apply it.
.\vbios-loader.exe load .\payload.bin --gpu 0

# After the restart, check that the driver is running the stored override.
.\vbios-loader.exe verify --gpu 0

# Remove it, then restart Windows.
.\vbios-loader.exe unload --gpu 0

The override stays in the GPU's registry key until you remove it, so it applies again at every Windows start. A clean driver installation or a driver update can recreate the driver key and drop the override. Run status after updating and load again if needed.

To build the exes from source, install Rust with the MSVC toolchain (x86_64-pc-windows-msvc) and the Visual Studio Build Tools with the C++ workload, which include the linker and the Windows SDK, then run cargo build --release in the repository: the exes are in target\release. The build embeds the version information and the manifest of each exe with the Windows SDK's rc.exe; without it cargo prints a warning, and vbios-loader-gui.exe then does not ask for administrator rights.

Verify

Verify in the window, or verify on the command line, reads back through NvAPI the VBIOS image that the driver is running, twice, and compares it byte by byte with the override stored in the registry. It writes nothing and needs no administrator rights. After loading or removing an override, restart Windows before checking. The result (state in --json) is one of:

NvAPI returns at most 1,024,000 bytes, so a longer override is compared on those bytes only: the result then says that the first 1,024,000 bytes match, not that it was verified byte by byte. Verify needs a driver whose NvAPI has NvAPI_GPU_GetVbiosImage (617.42 and 621.01 have it); with an older one the error says so. It does not work inside a virtual machine with a paravirtualized GPU (GPU-P).

If the GPU does not start

Test first on a GPU that is not driving your display (use the integrated graphics or another card for the screen), so you can always run unload.

If Windows shows no image or the GPU fails in Device Manager:

  1. Boot into Safe Mode: hold Shift while clicking Restart, then Troubleshoot → Advanced options → Startup Settings → Restart → 4 (Enable Safe Mode). Without a usable desktop, turn the PC off during boot two or three times (or boot Windows installation media → Repair your computer) to reach the same Troubleshoot menu. The NVIDIA driver does not load in Safe Mode, so the screen works there.

  2. Open vbios-loader-gui.exe, select the GPU and click Remove override; or, in an elevated PowerShell, run .\vbios-loader.exe unload --gpu 0 (use the GPU's index from status). Then restart Windows normally.

  3. If that does not work, open regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}. Open the numbered subkey whose DriverDesc is your GPU (status shows it as driver_key). If VixLoaderPreviousEnableGpuFirmware starts with hex(, use step 4 instead. Otherwise delete vbios, set EnableGpuFirmware back to the saved value, or delete EnableGpuFirmware if the saved value is absent. Then delete VixLoaderPreviousEnableGpuFirmware and restart Windows.

  4. If the saved value starts with hex(, EnableGpuFirmware was not a 4-byte REG_DWORD before the first load, and the saved text is an exact copy of it in .reg file notation. The easiest way to put it back is a .reg file instead of step 3: save these lines in Notepad as restore.reg, with NNNN replaced by the subkey number and the text after "EnableGpuFirmware"= replaced by the saved value. Double-click the file (or run reg import restore.reg in an elevated PowerShell) and restart Windows. It also deletes vbios and the saved value.

    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\NNNN]
    "vbios"=-
    "EnableGpuFirmware"=hex(1):31,00,00,00
    "VixLoaderPreviousEnableGpuFirmware"=-
    

Tests

cargo test

The tests use synthetic files and a fake registry; they run on Linux and Windows and never touch a GPU or a driver key. On Windows a few more tests check the registry calls on temporary keys under HKEY_CURRENT_USER\Software, which they delete, and list the display adapters. The workflow in .github/workflows/build.yml runs them on Linux (with cargo fmt and clippy) and on Windows, builds vbios-loader.exe and vbios-loader-gui.exe with Rust, checks the exes (no C runtime DLL, the manifest and version information, no AVX-512 instructions), checks that the window opens (with a screenshot), and publishes tagged versions as releases with SHA256SUMS and the third-party license texts.

License

Copyright (C) 2026 panchovix. GNU General Public License v3.0 or later (GPL-3.0-or-later), see LICENSE: you can use, study, change and share it, and changed versions you share must stay under the same license. See also THIRD_PARTY_NOTICES.md. Version 0.1.0 was released under the MIT license.

nvidia-windows-vbios-vix-loader (Panchovix/nvidia-windows-vbios-vix-loader)

Ищем в базе…

Что это такое?Инструмент для Windows, который загружает изменённый VBIOS видеокарты NVIDIA через реестровое переопределение драйвера, не перепрошивая сам флеш-чип карты.
Это приложение с графическим интерфейсом или утилита командной строки?И то, и другое: vbios-loader-gui.exe — графический интерфейс для Windows, а vbios-loader.exe — утилита командной строки с командами load, unload, verify и status.
Как вообще загрузить VBIOS?Скачайте exe со страницы Releases и проверьте его SHA256, запустите от имени администратора, выберите свою видеокарту, укажите файл VBIOS-payload, подготовленный в NVIDIA VBIOS Vix Editor, нажмите Load, затем перезапустите GPU или Windows.
Что нужно перед тем, как попробовать?Windows 10 или 11 (64-бит), учётная запись администратора, драйвер NVIDIA из диапазона 616.x, 617.x или 621.x и файл VBIOS-payload с одной цепочкой (single-chain) для вашей конкретной модели видеокарты, экспортированный сопутствующей утилитой NVIDIA VBIOS Vix Editor.
В чём главный риск?Изменённый VBIOS может поднять мощность, частоты и напряжения выше конструктивных пределов карты и повредить железо; качество поддержки сильно зависит от поколения GPU (Turing — экспериментальная, карты для дата-центров на GA100 не поддерживаются), а будущий драйвер NVIDIA может убрать реестровое переопределение, на котором держится этот инструмент.
Инструмент выходит в интернет или нужен доступ к сети?Нет, он пишет только в локальный ключ реестра драйвера GPU и никогда не обращается к сети; некоторые антивирусы помечают exe-файлы как ложное срабатывание, потому что они не подписаны и собраны из Python-кода упаковщиком Nuitka.
На каких поколениях GPU это реально работает?Проверено, что работает на Blackwell (RTX 50), Ada (RTX 40) и Ampere GA102-GA107 (RTX 30, A2000); поддержка Turing TU102-TU117 (RTX 20, GTX 16) экспериментальная; чипы GA100 для дата-центров (A100, A30, A800) не поддерживаются.
Что именно проверяет Verify?Он считывает через NvAPI образ VBIOS, который сейчас выполняет прошивка GSP видеокарты, и побайтно сравнивает его с переопределением, сохранённым в реестре; выдаёт статус override-active, override-not-active, no-override или unstable, если два чтения дают разные результаты.
Можно ли аккуратно отменить переопределение?Да: unload удаляет сохранённое значение vbios и все записи romOverride, восстанавливает прежнее значение EnableGpuFirmware точно в том виде, как было (включая исходный тип), и перезапускает GPU, чтобы он снова работал с собственным VBIOS карты.
Будет ли конфликт с mVolt+, если использовать оба?Они пишут в одни и те же значения реестра, поэтому загрузка BIOS через этот инструмент заменяет ранее загруженный через mVolt+, и наоборот; проект никак не связан с mVolt+.
Что делать, если после загрузки экран почернел?Если изменённая видеокарта выводит картинку на ваш монитор, снимите отметку «Restart the GPU now» и перезагрузите Windows целиком, так как перезапуск видеокарты, которая выводит изображение, на месте может оставить её без сигнала до полной перезагрузки.
Автор
Panchovix
Размер
0.6 MB
Звёзды
256
Возраст
1 мес
Коммиты · 90 дней