• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

rx580 wont show the bios

Vegapunk

New Member
Joined
Dec 25, 2024
Messages
16 (0.80/day)
Hey, thanks, but it doesn't seem to help.

This might be related my OS version.
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
That
This is what I downloaded:

View attachment 377629

My OS is Windows 11:

View attachment 377631
Yup thatll do it, lets try something here

Get the latest version of amdvbflash, unzip the folder to C drive but name folder amdvbflash5.0, open the folder and install the driver inside of it

The driver automatically unlocks the gpu eeprom.

Then on 11 desktop click start, type in cmd, right click it and open with admin rights. Then while in cmd navigate into the C:\amdvbflash5.0 folder.

Once inside of there type dir and hit enter and screenshot it please
 
Last edited:

Vegapunk

New Member
Joined
Dec 25, 2024
Messages
16 (0.80/day)
Here it is:

1735514133747.png


I also tried running amdvbflash.exe -i with this, with this version I don't get that Win8 Enhanced Security isssue:

1735514303857.png
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
I have ran the driver installer.
Ok open that .txt file and screenshot it, i dont know the commands off the top of my head
 

Vegapunk

New Member
Joined
Dec 25, 2024
Messages
16 (0.80/day)
Is it ok like this?

Code:
AMD IFWI Flasher Tool Version 5.0.567.0-External. Copyright© 2020-2022 Advanced Micro Devices, Inc. All rights reserved.


Debug logging related options:
  --debug-log-status arg         (Optional)This switch enables debug logging.
                                 By default debug logging is enabled.
                                 Usage:
                                     Enable Debug Logging:
                                         --debug-log-status=true
                                     Disable Debug Logging:
                                         --debug-log-status=false
                                        
  --debug-log-options            Lists the debug logging options for the tool.
                                 Usage:
                                     --debug-log-options
                                        
  --debug-log-filename arg       (Optional) Specifies the name of the debug log
                                 file name. The tool shall use this name
                                 suffixed with a number, where the number
                                 indicates an incrementing number indicating
                                 each instance of the binary. Be default the
                                 help file name starts with the name of
                                 process.
                                 Usage:
                                     --debug-log-filename=[Filename]
                                        
  --debug-log-filepath arg       (Optional) Specifies the location of the debug
                                 log file path. If this is empty or not
                                 specified then the following folders shall be
                                 used for generating debug log files:
                                        Windows: %APPDATA%\\AMD folder
                                        ESXi:    <datastore>/AMD/Logs/
                                        Linux:   /var/log/AMD
                                 Usage:
                                     --debug-log-filepath=[Filepath]
                                        
  --debug-log-filesize arg       (Optional)Specify the size of the Log file in
                                 MegaBytes (MB). 1 to 50. Defaults to 40 MB.
                                 Usage:
                                     --debug-log-filesize=[Size in MB]
                                        
  --debug-log-filepolicy arg     (Optional)Specify the policy to use when the
                                 log file size hits the size limit.
                                 Valid values are NEWLOG and REUSE. Defaults to
                                 NEWLOG
                                     NEWLOG(1): Generates a new log file
                                     REUSE(2): Continues using the same file
                                          (will start writing from the
                                          begining)
                                 Usage:
                                     --debug-log-filepolicy=NEWLOG
                                     --debug-log-filepolicy=REUSE
                                        

Generic options:
  --version                      Show the version of the binary.
                                 Usage:
                                     --version
                                        
  -h [ --help ] [=arg(=ALL)]     Displays this help text if no argument is
                                 specified. If an argument is specified then
                                 the help for the specified command is shown.
                                 Usage:
                                     --help/h/?
                                     --help/h/? <command>: --help
                                 debug-log-filepolicy
                                        
  --? [=arg(=ALL)]               Displays this help text if no argument is
                                 specified. If an argument is specified then
                                 the help for the specified command is shown.
                                 Usage:
                                     --help/h/?
                                     --help/h/? <command>: --help
                                 debug-log-filepolicy
                                        
  --show-progress                Shows progress for any long activity the tool
                                 does. Can be used along with any command.
                                 Usage:
                                     --show-progress
                                        
  --accept-EULA                  Accept the EULA agreement. You can see the
                                 EULA by --show-EULA.
                                 Usage:
                                     --accept-EULA
                                        
  -e [ --show-EULA ]             Shows the EULA for the tool
                                 Usage:
                                     --show-EULA
                                        

Options related to the console:
  --cls                          Clear the screen
                                 Usage:
                                     cls
  --exe arg                      Load and execute macro file (db32 script)
                                 Usage:
                                     exe [ScriptName]
  --open arg                     Open a file to log the session activities
                                 until the close command. Additionally multiple
                                 open commands will redirect the console
                                 activity to the last opened file.
                                 Usage:
                                     open [File]
                                        
  --close                        Closes the last opened session log file.
                                 Usage:
                                     close
                                        
  --flush                        Flushes the text to the last opened session
                                 log file.
                                 Usage:
                                     flush
                                        

Common tool ptions:
  -i [ --device ] [=arg(=-132)]  ASIC on which the operation has to be
                                 performed. This is a 0 based index.
                                 Usage:
                                     --device/-i=0
                                         : Specifies ASIC at index 0
                                     --device/-i=0,1
                                         : Specifies ASICs at index 0 and 1
                                     --device/-i=-1
                                         : Specifies to work on all ASICs
                                 detected
                                     --device/-i
                                         : Same as above i.e., specifies to
                                 work all ASICs detected
                                        
  -a [ --advanced ]              When this flag is specified, it tells the tool
                                 to work in advanced mode. The work will depend
                                 on the tool. This has to be used along-with -i
                                 option
                                 Usage:
                                     --advanced/-a
                                         : Work to show/perform advanced
                                 operations
                                     --advanced --device/-ai:
                                         : Work to show/perform advanced
                                 operations
  --show                         This flag instructs the tool to show
                                 information. What information is to be shown
                                 is specified by the other switches.
                                 Usage:
                                     --show --device
                                         : Show device inforamtion
                                     --show --device --advanced
                                         : Show advanced device inforamtion

Command line switches for the flash capability:
  -s [ --save ] arg              This flag instructs the tool to save the VBIOS
                                 image. This has to be used along-with the
                                 --device switch and the --vbios-info. If
                                 --vbios-file is not specified then the file
                                 name is constructed at run time with the
                                 following format [ASIC]_[BDF]_[Index].rom
  -p [ --flash ] arg             Write VBIOS image in file <file> to flash ROM
                                 in ASIC <Num>.
                                 Usage:
                                     -p <Num> <File>, or
                                     --flash --device [Num] --vbios-file <File>
  --vbios-info                   This flag when used along with --show flag
                                 instructs the tool to show the VBIOS
                                 Information from the file specified by using
                                 the --vbios-file option
  --vbios-file arg               Specify the VBIOS file to work with. This
                                 option can be used to save the VBIOS image to
                                 this file as well as to read VBIOS image from
                                 this file
  --bios-file-info arg           Display the BIOS info in the given file
  --savefile-at-end              This flag instructs the tool to save the whole
                                 VBIOS content read from the ROM Controller at
                                 the end of read operation. This should always
                                 be used only with --save flag. If not used, by
                                 default the tool keeps writing ROM contents
                                 read in each iteration to the file.
  --save-flashed-bytes           This flag instructs the tool to save the bytes
                                 being flashed to the SPIROM to a file for
                                 debugging purpose. This will enable the user
                                 to additionaly verify what and how many bytes
                                 have been written to the SPIROM at the end of
                                 flash operation. This flag should always be
                                 used with --flash command only. If not used,
                                 by default the bytes won't be additionally
                                 saved to a file.
  --fa                           This flag enables force flashing the same IFWI
                                 version. Should be used with the --flash
                                 switch.
                                 Usage:
                                     -p <Num> <File> -fa, or
                                     --flash --device [Num] --vbios-file <File>
                                 --fa
  --fp                           This flag instructs the tool to bypass BIOS
                                 part number check and perform a force flash.
                                 This flag should always be used with --flash
                                 command only.
                                 Usage:
                                     -p <Num> <File> -fp, or
                                     --flash --device [Num] --vbios-file <File>
                                 --fp
  --fv                           This flag enables downgrading the IFWI by
                                 performing a force flash. This bypasses
                                 checking the VBIOS/IFWI version. This flag
                                 should always be used with --flash command.
                                 Usage:
                                     -p <Num> <File> -fv, or
                                     --flash --device [Num] --vbios-file <File>
                                 --fv
  --config arg                   This flag allows the config file parameter to
                                 be skipped for comparision if all the config
                                 params match with corresponding value in IFWI
                                 file. This flag should always be used with
                                 --flash command.
                                 Usage:
                                     -p <Num> <File> -config <ConfigFile>, or
                                     --flash --device [Num] --vbios-file <File>
                                 --config=<ConfigFile>
                                        
  --checkpn arg                  Compare Part Number of the current IFWI in the
                                 device with the Part Number in the IFWI image
                                 specified.
                                 Usage:
                                     --/-checkpn <Num> <File>, or
                                     --/-checkpn --device <DeviceIndex>
                                 --vbios-file <IFWI Image>
                                        
  --cr arg                       Calculates the 16-bit ROM checksum for device
                                 <Index> of size if size is specified and
                                 compare with sum if expected sum is specified.
                                 Usage:
                                     -cr <Num> <size> <sum>, or
                                     --cr --device [Num] <size> <sum>
                                        
  --complete                     This flag instructs the tool to calculate
                                 checksum of Complete IFWI.This flag should be
                                 used with --cr/--cf command only.
                                 Usage:
                                     -cr <Num> <size> <sum> -complete, or
                                     --cr --device [Num] <size> <sum>
                                 --complete
                                        
  --biosimage                    This flag instructs the tool to calculate
                                 checksum of VBIOS image in IFWI.This flag
                                 should be used with --cr command only.
                                 Usage:
                                     -cr <Num> <size> <sum> -biosimage, or
                                     --cr --device [Num] <size> <sum>
                                 --biosimage
                                        
  --cf arg                       Calculate 16-bit checksum for file <File> and
                                 if expected checksum has been specified then
                                 compare the calculated checksum with the
                                 specified checksum.
                                 Usage:
                                     -cf <file> <sum>, or
                                     --cf --vbios-file <File> <sum>
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
Restart your system and get back into amdvbflash for cmd prompt
 

Vegapunk

New Member
Joined
Dec 25, 2024
Messages
16 (0.80/day)
Okay, so now it worked with the version 2.93:

1735516459609.png


I do first get this as before, but after I click OK, I get the result of the command:

1735516493848.png


Can I now proceed with the flash procedure as from the guide?
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64

Vegapunk

New Member
Joined
Dec 25, 2024
Messages
16 (0.80/day)
I now went through the flashing procedure, as much as I can tell it went well.

1735517168887.png


However, the motherboard BIOS still remains invisible.

But since we deduced that in the other GPU BIOS switch position the motherboard BIOS shows up normally, I really wouldn't want to trouble you with this any further.

You already went above and beyond with the help and advice.
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
You can try it with other files i provided

You might consider switching vid ports on the gpu
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
It's working!

I can see the MB BIOS in this switch position as well now.

The BIOS I installed is:


View attachment 377642
Ok good, make sure you remove that amdvbflash driver by running the installer again, its a hard bypass tool which could allow a security exploit to occur.
 

Vegapunk

New Member
Joined
Dec 25, 2024
Messages
16 (0.80/day)
Removed amdvbflash driver.

@eidairaman1

I really want to thank you a lot for your help!

You are as the quote in your signature says, a paragon of patience and expertise.

Cheers!
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
Removed amdvbflash driver.

@eidairaman1

I really want to thank you a lot for your help!

You are as the quote in your signature says, a paragon of patience and expertise.

Cheers!
I try but you just gave an invariable workaround for 2.93, it needs to be tagged and I need to update my guide for the change

@VuurVOS
 

velvo

New Member
Joined
Jan 11, 2025
Messages
3 (0.75/day)
Hello, I have the same problem with not being able to see my bios, no image until i get into windows, I would really appreciate if you could help me.

newly built pc,

CPU:5600x
motherboard: b450m vdh pro max
gpu: rx 580 8gb gigabyte. bought used from someone that was selling a lot of them saying they were used in office/gaming but i'm guessing they were used for mining

i've tried looking for a vbios myself, but i couldn't find one with micron memory.
i also noticed the clock speed is only 1150 mhz and power draw is about 80w when the gpu is 100 percent in use if it's any relevant at all.

just in case, i also have a cpu with integrated graphics if the new vbios doesn't boot so i can swap it with the vbios it came with.
1736585315946.png
1736585377928.png
1736585393532.png
1736585590976.png
1736585607486.png
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
Hello, I have the same problem with not being able to see my bios, no image until i get into windows, I would really appreciate if you could help me.

newly built pc,

CPU:5600x
motherboard: b450m vdh pro max
gpu: rx 580 8gb gigabyte. bought used from someone that was selling a lot of them saying they were used in office/gaming but i'm guessing they were used for mining

i've tried looking for a vbios myself, but i couldn't find one with micron memory.
i also noticed the clock speed is only 1150 mhz and power draw is about 80w when the gpu is 100 percent in use if it's any relevant at all.

just in case, i also have a cpu with integrated graphics if the new vbios doesn't boot so i can swap it with the vbios it came with.
View attachment 379516View attachment 379517View attachment 379518View attachment 379519View attachment 379520
Last i recall there were other menu options under the Advanced tab of gpu-z there should be 1 that mentions the word bios?

Kind of looking for a pcb part number sequence as inspite of the card showing rev 1.1 sometimes info to specify if a card is rev 1.0 or 1.1 is not given by the end user on a bios upload.

Also i see you have a 450 chipset motherboard, so i presume it's on the latest stable bios?
 
Last edited:

velvo

New Member
Joined
Jan 11, 2025
Messages
3 (0.75/day)
i took the motherboard to a pc shop and they updated the bios for me since at the time i didn't have a cpu that i could update the bios with. i'm not sure if it's a stable version.
bios version: e7a38ams.bn2
build date: 8/30/2024
here is a picture with the bios when i had the icpu in:
1736590365398.png
1736590437306.png

Last i recall there were other menu options under the Advanced tab of gpu-z there should be 1 that mentions the word bios?

Kind of looking for a pcb part number sequence as inspite of the card showing rev 1.1 sometimes info to specify if a card is rev 1.0 or 1.1 is not given by the end user on a bios upload.

Also i see you have a 450 chipset motherboard, so i presume it's on the latest stable bios?
 
Joined
Mar 20, 2008
Messages
1,910 (0.31/day)
System Name Ryzen5900X
Processor AMD Ryzen 5900X
Motherboard Gigabyte B550 AORUS PRO AC
Cooling NZXT Kraken X62
Memory 4x G.Skill F4-3600C17D-8GTZ
Video Card(s) AMD Radeon RX 6800XT Midnight Black
i took the motherboard to a pc shop and they updated the bios for me since at the time i didn't have a cpu that i could update the bios with. i'm not sure if it's a stable version.
bios version: e7a38ams.bn2
build date: 8/30/2024
here is a picture with the bios when i had the icpu in:View attachment 379526View attachment 379527
E7A38AMS.BN2 is a beta bios. The last digit should be a zero for MSI Motherboards to be a stable bios. Since AM4 is EOL, this is the latest (beta) bios.

Part number "GV-RX580GAMING-8GD-MI" on your card is a mining card.

These bioses belong to GV-RX580GAMING-8GD and have Micron memory support:
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
E7A38AMS.BN2 is a beta bios. The last digit should be a zero for MSI Motherboards to be a stable bios. Since AM4 is EOL, this is the latest (beta) bios.

Part number "GV-RX580GAMING-8GD-MI" on your card is a mining card.

These bioses belong to GV-RX580GAMING-8GD and have Micron memory support:
Hey man the sub system ids are different, also the og bios code has F90 in it.

These 2 are closer in that sequence of what he has above.


 
Last edited:

velvo

New Member
Joined
Jan 11, 2025
Messages
3 (0.75/day)
Hey man the sub system ids are different, also the og bios code has F90 in it.

These 2 are closer in that sequence of what he has above.


i flashed the first bios and now i can get in the bios and the clock speed is 1340mhz now. thank you very much.
 
Joined
Mar 20, 2008
Messages
1,910 (0.31/day)
System Name Ryzen5900X
Processor AMD Ryzen 5900X
Motherboard Gigabyte B550 AORUS PRO AC
Cooling NZXT Kraken X62
Memory 4x G.Skill F4-3600C17D-8GTZ
Video Card(s) AMD Radeon RX 6800XT Midnight Black
Hey man the sub system ids are different, also the og bios code has F90 in it.

These 2 are closer in that sequence of what he has above.


Both are still mining bioses, isn't it beter to flash a regulair RX 580 Gaming bios instead ?
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
43,094 (6.73/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
Both are still mining bioses, isn't it beter to flash a regulair RX 580 Gaming bios instead ?
The 1 I gave is gaming, which is 1340/2000, ga cards tend to be picky with the bios loaded
 
Top