How to Back Up Your GPU VBIOS Before Flashing

A VBIOS flash that goes wrong—wrong file, interrupted write, voltage spike during the process—leaves you with a card that cannot initialize a display. On most modern dual-BIOS cards this is recoverable. On single-BIOS cards it is not, unless you have a backup. The backup takes five minutes and eliminates an entire category of unrecoverable outcomes.

VBIOS (Video BIOS) is firmware stored on a small flash chip on the GPU PCB. It initializes the GPU hardware before the operating system loads, defines power limits, fan curve defaults, clock table entries, and memory training parameters. When you flash a new VBIOS, you overwrite this chip. If the flash completes successfully with a compatible file, the new firmware takes effect on next boot. If the flash fails or the file is incompatible, the chip may contain corrupted data the GPU cannot boot from.

Dual-BIOS vs single-BIOS cards

Many enthusiast desktop GPUs include two BIOS chips: a primary that is written during a flash, and a secondary that holds the original factory firmware and is not normally writable through software. The small physical switch on the PCB edge selects which chip boots. ASUS ROG Strix and TUF cards, MSI Gaming X Trio cards, and EVGA FTW3 cards typically have dual BIOS. Founders Edition and reference-design cards usually do not.

If your card has dual BIOS, a failed flash can be recovered by flipping the switch to the secondary BIOS, booting, and reflashing the primary from a known-good state. You should still back up the secondary BIOS before any flash session, because the secondary is a recovery tool only if it is untouched and you know where the switch is.

If your card has single BIOS, a failed flash with no backup and no hardware programmer leaves the card non-functional. The recovery path then involves physically programming the flash chip with an SPI programmer, which requires soldering equipment or desoldering the chip for off-board programming. Having a backup stored safely on your PC and a USB drive makes recovery from any flash failure a 10-minute process instead of an electronics repair project.

Method 1: GPU-Z BIOS backup (simplest)

GPU-Z from TechPowerUp is the easiest way to extract your current VBIOS. Download and run GPU-Z. On the main tab, look at the BIOS Version field. To the right of the BIOS Version field is a small arrow icon. Click it and select Save to file. GPU-Z will extract the current VBIOS from the flash chip and save it as a .rom file. Name the file with your GPU model, the current date, and the word "original"—for example, RTX4080-Strix-2026-06-25-original.rom.

GPU-Z works in Windows and is the preferred method for most users because it requires no command line and extracts the live firmware from the running hardware, which is guaranteed to be the currently active BIOS regardless of any prior flashes.

Method 2: NVFlash backup for NVIDIA (command line)

NVFlash is NVIDIA's official VBIOS flash tool distributed by TechPowerUp and other enthusiast sources. It runs from a command prompt. To back up using NVFlash, open a command prompt as Administrator, navigate to the folder containing nvflash64.exe, and run: nvflash64.exe --save backup.rom

NVFlash will query the GPU, identify the BIOS chip, read its contents, and write them to backup.rom in the current directory. If your system has multiple GPUs, NVFlash will display a numbered list and ask which GPU to target. Select the correct index (usually 0 for the primary card). For cards with the protection override prompt, add the --protectoff flag if NVFlash warns that write protection is active.

NVFlash backup is preferable to GPU-Z for users who plan to use NVFlash for the actual flash, because it reads the BIOS through the same low-level interface that will write it. The backup file is guaranteed to be in a format that NVFlash can reflash if needed.

Method 3: ATiFlash backup for AMD

For AMD GPUs, the equivalent tool is ATiFlash (also called AtiWinFlash for the GUI version). Run AtiWinFlash, select your GPU from the adapter list, and click Save. The tool writes the current VBIOS to a .rom file. The command-line version of ATiFlash uses: atiflash -s 0 backup.rom where 0 is the adapter index of your AMD card.

Verifying the backup

After saving the backup file, verify it is not zero bytes and is not an obviously truncated size. A typical desktop GPU VBIOS is between 128 KB and 512 KB. An RTX 4080 VBIOS is around 256 KB. An RX 7900 XTX VBIOS is typically 256 to 512 KB. If your backup.rom is a few hundred bytes, the extraction failed and the file is not a valid backup. Try again, and if it continues to fail, check whether another GPU control software is interfering.

Open the .rom file in a hex editor (HxD is free and works well). The first few bytes of a valid NVIDIA VBIOS should read 55 AA, which is the standard x86 option ROM signature. A valid AMD VBIOS starts with the same signature. If the file opens to all zeros or random-looking garbage, the backup is corrupt.

Storing backup files long term

Name each backup file with enough information to identify it without opening it: GPU model, board partner and variant, date, and status (original or the name of the modified VBIOS if it is a post-flash backup). A folder structure like GPU-BIOS/RTX4080-Strix-OC/ with files named by date makes it straightforward to retrieve the right file if you need to recover from a flash years later. VBIOS files are small and worth keeping permanently.

What to do if no backup exists and the card does not boot

If you are reading this after a failed flash with no backup, you still have options. TechPowerUp's VBIOS database at techpowerup.com/vgabios contains community-contributed BIOS dumps for thousands of GPU models, including multiple board partner variants. Search for your exact GPU model and board partner name. Download the most downloaded version with a matching part number to your card's sticker, and attempt a reflash in DOS mode (some NVFlash versions can flash even when the GPU is not producing display output, using the integrated graphics output instead). Recovery procedures are GPU-model-specific and go beyond the scope of this guide, but having the correct BIOS file from the database is the starting point.