Atiflash download: AMDVBFlash / ATI ATIFlash (3.31) Download

BIOS Flashing Downloads | TechPowerUp

Sorting:
Latest Updates
Alphabetically
Popularity

NVIDIA NVFlash

• 5.792.0

  Oct 25th, 2022

• + 68 previous versions

AMDVBFlash / ATI ATIFlash

• 3.31

  Jan 28th, 2022

• + 40 previous versions

ATI Winflash

• ATI Winflash 2. 6.7

  Dec 18th, 2013

• + 6 previous versions

ATI Winflash (old)

• Winflash 1.26.1

  Sep 10th, 2007

• + 8 previous versions

ATI Flashrom

• Flashrom 2.40

  Oct 16th, 2005

• + 5 previous versions

Nov 3rd, 2022 18:46 CET
change timezone

Sign in / Register

• NVIDIA GeForce 526.47 WHQL
• AMD Radeon 22.10.3 Beta
• Intel
  IGP 101.3790
  /
  Arc 101.3793

• 18:44
  by
  N/A

  Does anybody know the connection of those little 21 plugs? (1)

• 18:37
  by
  lexluthermiester

  Do you use Linux? (130)

• 18:30
  by
  lexluthermiester

  TPU’s Nostalgic Hardware Club (15633)

• 18:26
  by
  SN2716057

  What are you playing? (16430)

• 18:24
  by
  nomdeplume

  Intel I225-V performs poorly in Windows 11 (1)

• 18:18
  by
  AusWolf

  The TPU UK Clubhouse (23904)

• 17:59
  by
  unclewebb

  is it ok to undervolt as much as possible? (12)

• 17:58
  by
  claes

  Unbuf ECC regular desktop driver pc (19)

• 17:40
  by
  NZRichard

  Help! — New Radeon RX 6600 XT problem (PC not booting, freeze before bios) (12)

• 17:24
  by
  phill

  Have you got pie today? (15765)

• Oct 11th, 2022NVIDIA GeForce RTX 4090 Founders Edition Review — Impressive Performance
• Oct 18th, 2022RTX 4090 & 53 Games: Ryzen 7 5800X vs Core i9-12900K Review
• Oct 31st, 2022RTX 4090 & 53 Games: Ryzen 7 5800X vs Ryzen 7 5800X3D Review
• Oct 17th, 2022NVIDIA GeForce 522. 25 Driver Analysis — Gains for all Generations
• Oct 21st, 2022NVIDIA RTX 4090: 450 W vs 600 W 12VHPWR — Is there any notable performance difference?
• Oct 20th, 2022Intel Core i5-13600K Review — Best Gaming CPU
• Oct 5th, 2022Intel Arc A770 Review — Finally a Third Competitor
• Oct 12th, 2022ASUS GeForce RTX 4090 STRIX OC Review
• Oct 20th, 2022Intel Core i9-13900K Review — Power-Hungry Beast
• Oct 5th, 2022NVIDIA GeForce RTX 4090 FE + 6x Custom Design Unboxing

• NVIDIA Cancels GeForce RTX 4080 12GB, To Relaunch it With a Different Name
  (423)
• AMD Cuts Down Ryzen 7000 «Zen 4» Production As Demand Drops Like a Rock
  (236)
• PSA: Don’t Just Arm-wrestle with 16-pin 12VHPWR for Cable-Management, It Will Burn Up
  (214)
• AMD Trims Q3 Forecast, $1 Billion Missing, Client Processor Revenue down 40%, Halved Quarter-over-Quarter
  (150)
• AMD Radeon RX 6900 XT Price Cut Further, Now Starts at $669
  (131)
• NVIDIA GeForce RTX 4070 isn’t a Rebadged RTX 4080 12GB, To Be Cut Down
  (120)
• NVIDIA RTX 4090 Scalped Out of Stock, Company Tests «Verified Priority Access» Buying Program
  (120)
• NVIDIA Tells AICs to Collect RTX 4090 Cards with Burnt Power Connectors, Send Them to HQ
  (105)

ATIFlash 4.

17 | en.hw-lab.com

3.79
– Fix issue with flashing Atmel AT25F512B ROMs

3.78
– Fix issue with flashing SST ROMs

3.77
– Fix -mb flag for Evergreen series asics when modifying SSID and SSVID

3.76
– Add support winbond W25X80A

3.75
– Add “-lockrom” and “-unlockrom” in Atiflash to lock rom for protection

3.70
– Fix: correctly report flash error code under linux
– Fix: correctly detect PCI devices under linux
– Fix: – Fixed segumentation fault when doing -pa -pavbpn on a gfx card with an invalid vbios part number

3.67
– update RV790 DID

3.66
– update BN number to 128

3.65
– Add RV740

3.64
– Fix Flash on AT25FS010N

3.63
– Add New ROM support for Atmel AT25FS010N

3.62
– Fix the save function to save bios > 64K
– Fix the RV710 flash BIOS configuration to ensure it didn’t triggle CTF

3.61
– Fix mb option to save the entire rom size if rom size is bigger than bios size

3. 60s
– Add support for RV710

3.60
– Use SCLK to flash BIOS on RV730 only (SCLK will be scaled down while flashing the BIOS)

3.59
– Add RV730 support

3.58
– Fix pa paramter, synchronize the same behaviour as ATIWinFlash

3.57
– Add R700 Support
– Reduce size

3.56
– Fix corrupted zip file. Same release as 3.55
– Add option (excl_memtrain_dtable) to keep memory training information while flashing new bios
– Add partial check for -pavbpn

3.54
– Add “nw” in help

3.53
– Add unique identifier for Ry7xx

3.52
– Add RV770 device ID support

3.51
– Add -AMD flag to allow searching for devices with AMD vendor ID

3.50
– update SPI write sequence to check for both WREN and BUSY bits to be deasserted before verifying the write (solves issues seen with intermittent write failures)

3.49
– update description for RV670 slave devices to identify uniquely on Gemini boards

3.48
– correctly print Old and New P/N when flashing with newer bioses

3. 47
– explicitly identify RV635 ASICs

3.46
– Fix problems with GPIO19 asserting the CTF signal on RV670 boards

3.45
– Fix problems with crashes on some systems when flashing onto blank ROMs

3.43
– Added -pavbpn (allows the use of -pa with VBIOS PN)
– Added support for new ROM used by multimedia cards (Quito and Lima)

3.42
– Fix -mb command for Ry6xx

3.41
– Fix Ry6xx SST support

3.40
– Fix RV610 + Rialto hang issue

3.39
– Fix RV610 write issue

3.38
– Add Quito support

3.35
– resolved -i/-ai corruption issue

3.34
-ai now displays full PCI ID information
– ATMEL flash procedurce redesigned for stability/reduced overall flash time
-ai -scansii combination will report SST/ATMEL firmware revision

3.33
– internal release

3.32
– Add flashing over 128KB

3.31
– resolved pak issues with SST/ATMEL

3.30
– update device ID support for RV630/M76 & 0x000 for Ry6xx

3. 29
– Add new option -pak to build flash package

3.28
– Add new option -fa to force flashing if the ROM is already programmed
– Add new option -fm to force flashing if legacy memory config mismatch
– Add new option -fs to force flashing if SSID mismatch
– Add new option -fp to force flashing if BIOS P/N mismatch
– Add new command -pa to search and program multiple adapters according to BIOS P/N
– Add new option -padevid to search for adapters of a specific PCI device ID when used with -pa command
– Add new option -passid to search for adapters of a specific subsystem ID when used with -pa command
– Add new option -pasvid to search for adapters of a specific subsystem vendor ID when used with -pa command

3.00
– initial release

ATI ATIFlash / AMD VBFlash 3.20

Useful programs

Author Dmitry Nikitin Reading 2 min Views 3.2k. Posted by 07 Aug 2021

ATIFlash or AMDVBFlash is a BIOS flashing program for AMD GPUs. AMD AMDVBFlash is used to flash the graphics card’s BIOS. The version released by ATI was called ATIFlash or simply WinFlash.

It supports all AMD Radeon graphics cards like RX 6900 XT, RX 6800 XT, RX 6700 XT, RX 5700, RX 5600, RX 5500. You can also flash BIOS for all AMD Radeon RX Vega, RX 580, RX 480 and all old ATI cards.

The AMDVBFlash BIOS updater runs under Windows.

AMD has changed the behavior of AMDVBFlash in newer versions. It now requires an always running Ring-0 kernel mode driver. This is a security risk, you really only need the driver for a few minutes when saving BIOS or flashing. This is why AMDVBFlash 3.15 and newer includes AMDVBFlashDriverInstaller.exe which installs/uninstalls the AMD driver with one click. This software was written by us at TPU and signed with our digital signature.

v3.20

• Added support for Radeon RX 6900 XT XTXH.

v4.71

• Added support for Radeon RX 6900 XT Navi 21 XTXH flash chips (Device ID 73AF) RX 6800XT, RX 6900XT.
• Adds the AMDVBFlashDriverInstaller.exe written by us in the TPU, which makes it easy to install/uninstall the AMD driver now required to perform flashing.

v2.93

• Added support for Navi Radeon RX 5700 Series BIOS firmware.

Installing and running AMDVBFlash

The normal distribution of AMDVBFLASH requires software to be installed on your system, and it will install the ring-0 kernel mode driver that is always running, which is a security risk.

The version in this archive is distributed as a portable package that does not require this installation.

Due to the way AMD designed AMDVBFLASH, you first need to run AMDVBFlashDriverInstaller.exe, which installs the driver required by AMDVBFLASH to access the hardware.
This driver is independent of your «graphics driver».

When the firmware is finished, run AMDVBFlashDriverInstaller.exe again to stop and uninstall the driver.

Rate this author

(No rating yet)

BIOS flashing on AMD

cards Windows, Hardware

• Recluse
• 03/20/2017
• 61 955
• 13
• 12/11/2020
• 11
• 11
• 0

• Article content
  • Introduction and preparation
  • Flashing via GUI
  • Flashing via command line
  • Known issues and bugs
  • Driver update
  • Comments to the article ( 13 items )
  • Add a comment

You perform all actions from this article at your own peril and risk! The resource administration does not bear any responsibility for any malfunctions or damage that may occur after the actions described below.

Introduction and preparation

This article will discuss how to flash the BIOS in AMD graphics cards. To flash the video card, you will need the AMD VBFlash utility, which can be downloaded from this link.

It is recommended to disable the graphics card BIOS before flashing it in Windows. To do this, open « Device Manager «, and in the item « Display Adapters » select the one you need, right-click on it and select « Disable «.

Next, we will discuss two possible ways to use the ATI Winflash utility — through its graphical interface, and through its console version.

Flashing via GUI

Run ATIWinflash with administrator rights. We make sure that the video adapter you need is selected in the upper right corner of the program.

This is how ATIWinflash shows a single video card.

If the number of video cards in the system is more than 3, then the program will not be able to correctly display the entire list — the fourth and subsequent video cards simply will not fit in the window. In this case, you will have to use the firmware method via the command line (you can read about it in the same article below).

And this is how four video cards are shown in the ATIWinflash program — only three of them are visible, the fourth simply did not fit on the screen.

After selecting the desired video card, click on the «Load image» button, and select the BIOS file with which we want to flash the video card.

And then press the «Program» button.

After that, we wait until the video card firmware procedure is completed, which will be reported by a separate notification.

And then you will be prompted to reboot, which is necessary for the video card to work with the new BIOS.

If after a reboot your video card is detected in Device Manager but refuses to work, it may be due to AMD drivers blocking custom BIOSes. You can read about how to deal with this in this article.

Flashing via command line

Most useful ATIFlash commands:

• atiflash. exe -i — will show the list of video cards installed in the AMD system. Useful for flashing the BIOS on a specific graphics card.
• atiflash.exe -p — flash the video card with the specified BIOS number from the specified file.
• atiflash.exe -pa — flash on ALL video cards with the specified BIOS file.

Usage examples:

• A single AMD graphics card is installed in the system. In this case, everything is simple — we indicate the flashing of all card cards in the system using a file with a modified BIOS (let’s say it is called BIOS_mod_470.rom):

  AtiFlash.exe -pa BIOS_mod_470.rom

• Two different video cards are installed in the system — AMD Radeon R9 390 and AMD Radeon RX 470, you need to flash the BIOS only on RX 470:

  Run the program with the parameter -i , and look at the list of video cards in the system. We remember the number of the video card RX 470.

  AtiFlash. exe -i

  Seeing that the RX 470 (hidden behind the name Polaris10) has number 0, we indicate to flash the video card at number 0 with the file BIOS_mod_470.rom:

  AtiFlash.exe -p 0 BIOS_mod_470.rom

After entering the BIOS flashing command, we patiently wait for the procedure to complete. Upon completion, the program will display the following message on the command line:

Restart System To Complete VBIOS Update.

Which implies that you need to restart the computer to finish updating the BIOS of the video card. After the reboot, you can consider the BIOS flashing procedure completed.

Known Issues and Errors

• Computer or system freezes while updating graphics card BIOS.
  When updating the BIOS of a video card, it is recommended to disable the video card through the «Device Manager». How to do this is written at the very beginning of the article.