GPU BIOS and Tuning Tools for Mining Rigs: VBIOS Flashing, Power Limits and Recovery

This page is for rig owners who want to save or restore a graphics card BIOS, cut power draw, set fan curves, tune memory or get a multi-GPU board to boot. The short version: most tuning today happens in the driver, the miner or the mining OS, not in a flashed BIOS. Flash a VBIOS only to back up or restore an official image, and keep a copy of every original first.

Lower power draw cuts your electricity cost for the same work, but no tool here makes a rig profitable. That depends on your power price, hardware and the coin price. Flashing firmware can brick a card or board and usually voids the warranty. Tune only hardware you own or are authorised to use.

The short list

Back up every BIOS before you touch anything

A backup is only useful if you can match it to its card. On a rig of identical cards, name each file by slot, model and serial number, and copy the files off the rig.

amdvbflash -i
amdvbflash -s 0 slot0_rx6600_SN1234.rom
amdvbflash -s 1 slot1_rx6600_SN5678.rom

On NVIDIA cards, NVFlash and GPU-Z can both save the current BIOS. mmpOS includes amdvbflash and nvflash at the command line. Also keep the motherboard BIOS file and a photo of every changed UEFI setting, because a CMOS reset wipes them.

Flash a VBIOS and recover from a bad flash

When flashing still makes sense

BIOS mods used to be the main way to tune mining cards; that era is mostly over. NVIDIA cards from the GTX 10 series onward accept only signed BIOS images, and Radeon RX 5000 and newer check the VBIOS signature too, so a hand-edited image will not run. The realistic jobs today are restoring your backup, moving to an official revision from the card maker, and editing Polaris cards (RX 470/480/570/580).

Red BIOS Editor from igor’sLAB covered that last job. Its final release supports only Polaris and RDNA1 images; on Polaris the edited file is written with AMDVBFlash. On RX 5000 the signature check blocks edited images, so use MorePowerTool instead.

Flashing steps

1. Close the miner, tuning tools and monitoring apps.
2. Check the image is for your exact model and memory type, from the card maker’s support page.
3. Flash one card at a time by index from an elevated prompt: amdvbflash -p 1 new.rom.
4. Never interrupt the flash; use a UPS if your power is unreliable.
5. Reboot, reset the driver, and check clocks and memory size before mining.

The -f switch forces a flash when IDs do not match. It exists for recovery; using it to cross-flash a different board design is the most common way miners brick cards.

Recovery

• Dual BIOS switch. Flash only one position. If it fails, set the switch to the untouched position so the card works while you prepare the restore.
• Integrated graphics or a second GPU. Boot from the iGPU or a known-good card with the bad card in a secondary slot; the flash tool can usually still see it by index.
• Program the original. Restore your saved file, with -f only if the IDs no longer match.

If the tool cannot read the chip at all, it may be failing; that needs an external programmer.

Power limits and undervolting

This is where most of the efficiency is. The workflow is the same everywhere:

1. Note stock clocks, power and hashrate for each card.
2. Lower the power limit or core voltage in small steps.
3. Mine for several hours and watch for rejected or invalid shares, crashes and driver resets.
4. Keep the last stable step, then back off one notch for margin.

AMD cards

Start with the tuning page in AMD’s Radeon software; it is often enough. For Polaris, Vega 20, RX 5000 and RX 6000, MorePowerTool goes further: it writes a SoftPowerPlayTable (SPPT) to the Windows registry, which the driver uses instead of the BIOS values. “Write SPPT” plus a reboot applies it; “Delete SPPT” plus a reboot undoes it. It does not support RX 7000 or RX 9000; for clock tuning on RX 6000 to RX 9000, igor’sLAB offers MoreClockTool. Newer drivers ignore some SPPT values on RDNA 2, which explains most changes that do nothing.

NVIDIA cards

The driver’s nvidia-smi sets a power limit and can lock clocks on Windows and Linux, with administrator or root rights:

nvidia-smi -q -d POWER
nvidia-smi -i 0 -pl 150
nvidia-smi -i 0 -lgc 1200,1200
nvidia-smi -i 0 -rgc

The first command shows the allowed power-limit range. Clock locking needs card and driver support. Settings do not survive a reboot, so use a startup script. Numbers are placeholders.

Miners can do the same job. Rigel takes per-GPU lists for --cclock, --mclock, --lock-cclock and --pl, with an underscore to skip a card. OneZeroMiner uses --cclk, --mclk and --pl, with an asterisk to skip. GMiner has --cclock, --mclock and --pl on Windows only, run as administrator, and is frozen at 3.44. NiceHash QuickMiner offers Lite, Medium, High and, on some cards, Efficient profiles, plus manual tuning in OCTune.

The rule that prevents most mystery crashes: set clocks in one place only. If the miner applies an overclock, do not also run MSI Afterburner or a mining OS profile. NiceHash also warns against enabling start with Windows before a profile is proven stable, because an aggressive overclock applied at boot can cause a crash loop.

Fan curves and thermals

Watch two temperatures. Core temperature is easy to read, but on cards with GDDR6X memory the memory junction temperature is usually the limit; HWiNFO and GPU-Z show it on cards that report it. Then set protections in the miner:

rigel ... --temp-limit tc[60-70]tm[105-115]
miner ... --templimit 80 --templimit_mem 100 --tfan 65 --tfan_min 30 --tfan_max 85

Rigel pauses a card when core or memory temperature hits the limit and resumes once it cools; --fan-control sets fixed or automatic curves. GMiner’s --tfan holds a target temperature on Windows. On Linux rigs, Hive OS has AutoFan for a target temperature, and mmpOS sets target temperature and fan behaviour per GPU. Airflow matters more than the curve; if cards keep climbing, lower power before raising fans.

Memory clocks and timings

On memory-bound algorithms the memory clock moves hashrate more than the core clock, and it is also the setting most likely to cause silent errors. Raise it in small steps and watch for invalid shares. GMiner warns when a memory overclock produces errors, and Rigel has memory tweaks for Pascal GDDR5/GDDR5X cards.

Custom timing straps in the BIOS were a Polaris practice and do not apply to RX 5000 and newer. For CPU mining, system RAM timings count: on ASRock boards, ASRock Timing Configurator shows the timings the board really applied. Make permanent changes in the UEFI setup.

GPU profiles, safe configs and “best settings”

There are no universal best settings. Two cards of the same model can need different voltages. Build a tested profile per card model and algorithm, then copy it: MorePowerTool saves tables to a file, SimpleMining OS uses overclocking groups, mmpOS has global presets, and Hive OS sets overclocks per card or per rig. Test each card after copying.

A safe config is one with margin: clocks a step below the last stable value, temperature limits in the miner, a watchdog, and a note of stock values for rollback. Re-check after every driver update. For managing profiles across many rigs, see our mining OS comparison.

CPU-side tuning for CPU mining

On a Windows CPU rig, Quick CPU handles the platform: core parking at 100% in a dedicated power plan, a lower Intel PL1 while you watch package power and hashrate, and a stress test after an undervolt. The BIOS can lock the Intel-only section, and many settings reset after a reboot unless a startup profile applies them. Huge pages, 1 GB pages on Linux and the MSR mod belong to XMRig, not Quick CPU. Microcode updates through UEFI BIOS Updater can fix bugs but sometimes lower performance, so compare hashrate before and after.

Two retired tools from old guides deserve an honest note. S3TurboTool is a community BIOS patcher for Chinese X99 boards such as Huananzhi that unlocks all-core turbo and undervolting on Xeon E5 v3; it has been inactive since about 2021 and bundles OEM firmware tools. SetFSB changed the base clock from Windows through the clock generator chip; it was discontinued around 2013 and does not support most boards made after 2009.

Motherboard BIOS settings for multi-GPU rigs

Menu names differ by board, so check your manual:

• Above 4G Decoding: usually needed to boot with many GPUs; some boards also need CSM disabled.
• PCIe link speed: try Gen1 or Gen2 if cards on risers drop out or go undetected.
• Boot order: mining OS drive first; use the primary slot for a monitor when troubleshooting.
• Power on after AC loss: the rig restarts by itself after an outage.
• Integrated graphics: keep it available as a recovery display.

Updating the board BIOS

Use your board maker’s file and its own tool: the built-in flasher (ASUS EZ Flash, MSI M-Flash, Gigabyte Q-Flash, ASRock Instant Flash) or BIOS Flashback where available. The tools old posts on this site offered are different. AFUDOS, AFUWIN, AMIBCP, AMI ChangeLogo and MMTool are AMI utilities licensed to motherboard makers, not public downloads; an end user legitimately gets AFU only inside a vendor’s BIOS package. AFUDOS is the legacy DOS version, which boards without CSM cannot boot. Intel FPT goes to OEMs only. AMIBCP-edited images must be re-signed before standard flashing accepts them.

How to choose

1. Back up first: AMDVBFlash for Radeon, NVFlash or GPU-Z for NVIDIA, plus the board BIOS and settings.
2. Software before firmware: Radeon software or nvidia-smi, then miner flags, then MorePowerTool on supported Radeon cards.
3. Flash a VBIOS only for official images or Polaris timing work, with a recovery path ready.
4. One place for clocks: miner, OS or tuning app, never two.
5. Farms: let the mining OS hold profiles. To pick the miner, see best GPU mining software.

Antivirus products often flag miners as potentially unwanted, because miners are abused in malware. Get each tool from its official source, check the checksum, and use a folder exception rather than disabling protection.

FAQ

Can I flash a modded BIOS on an RX 6000 or RTX card?

No. Radeon RX 5000 and newer and NVIDIA GTX 10 series and newer accept only signed images. Tune them through the driver, MorePowerTool (RX 5000/6000) or your miner.

How do I fix a GPU after a failed BIOS flash?

Use the dual-BIOS switch if there is one. Otherwise boot from the iGPU or another card, find the bad card’s index and program your saved original.

Where can I download AFUWIN, AMIBCP or Intel FPT?

There is no public download; these are AMI and Intel tools licensed to board makers. Update with your vendor’s flasher or BIOS Flashback.

Does undervolting lower hashrate?

Often only slightly, because many algorithms depend more on memory than core speed. Measure your own cards; profit still depends on power price, hardware and coin price.

Is SetFSB or S3TurboTool still worth using?

SetFSB is discontinued and does not support modern boards. S3TurboTool is an inactive patcher for specific X99 boards. Neither is a safe general recommendation.

Why do my overclock settings reset after a reboot?

nvidia-smi settings and many Quick CPU settings are not persistent, and driver updates can drop a MorePowerTool table. Apply them at each boot with a startup script, a startup profile or your mining OS.

Last updated: 2 November 2026 · soft4mining editorial team. Licence, version and platform details are checked against each developer's official documentation.