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

I have a bricked XFX Radeon RX 580 8GB GPU. HELP!

Joined
Apr 2, 2022
Messages
32 (0.03/day)
Good evening guys,

I recently got an XFX Radeon RX 580 GB off FB marketplace. The seller was very honest in that he said it was fairly unstable when playing games. On BIOS 1 (left), there was video but my Windows 10 PC would hang. On BIOS 2 (right), there was lots of artifacts but at the least Windows 10 would boot. I did make a backup of BIOS 1. That said, when attempting to flash BIOS 1, I set it incorrectly to BIOS 2 and I bricked the card. Now, even when connected, Device Manager doesn't even see it at all in either BIOS 1 or BIOS 2.

I'm hoping that's not the case, so I'm hoping someone can help me.

For reference, here's the info off the white sticker on the back of the card (see attached picture as well):

RX-580P8D VN.3
GTS XXX ED RX 580 8GB OC+ 1386M D5 8P
3xDP HDMI DVI
 

Attachments

  • IMG_1239.jpg
    IMG_1239.jpg
    362.2 KB · Views: 89
Last edited:
I do. That's how I know that the RX580 is bricked. I'm able to boot into Windows 10 on an old mobo that has a PCIe slot with an integrated GPU. That old ATI Xpress is seen by GPU-z. In the past, when I've had issues like this (with an old HD 7950) whenever I selected the drop down for the GPU, I would see something like "Windows Basic Display Adapter". This time, I don't have a drop down option except for the integrated ATI Xpress.
 
Last edited:
Good evening guys,

I recently got an XFX Radeon RX 580 GB off FB marketplace. The seller was very honest in that he said it was fairly unstable when playing games. On BIOS 1 (left), there was video but my Windows 10 PC would hang. On BIOS 2 (right), there was lots of artifacts but at the least Windows 10 would boot. I did make a backup of BIOS 1. That said, when attempting to flash BIOS 1, I set it incorrectly to BIOS 2 and I bricked the card. Now, even when connected, Device Manager doesn't even see it at all in either BIOS 1 or BIOS 2.

I'm hoping that's not the case, so I'm hoping someone can help me.

For reference, here's the info off the white sticker on the back of the card (see attached picture as well):

RX-580P8D VN.3
GTS XXX ED RX 580 8GB OC+ 1386M D5 8P
3xDP HDMI DVI
I don't see anywhere you are mentioning the memory on the card. Did you verify before flashing which brand and part number is on the memory? I think you must verify this before trying again.

You can apply the pin "1-5" method (People are calling it wrongly pin 1 and 8 on the internet!!!)
 
If I recall correctly, from the original GPUz screenshot I grabbed before I bricked it, it was a combination of Samsung and Hynix memory. I will post it shortly.
 
If I recall correctly, from the original GPUz screenshot I grabbed before I bricked it, it was a combination of Samsung and Hynix memory. I will post it shortly.
Cant be both. Remove cooler and find out what is physically on the graphics card.
 
If I recall correctly, from the original GPUz screenshot I grabbed before I bricked it, it was a combination of Samsung and Hynix memory. I will post it shortly.
Pull the card apart please
 
A few pictures attached. Although hard to tell, I double checked and all 8 chips are Samsung.
 

Attachments

  • IMG_1270.JPG
    IMG_1270.JPG
    2.1 MB · Views: 122
  • IMG_1271.JPG
    IMG_1271.JPG
    2.1 MB · Views: 138
  • IMG_1272.JPG
    IMG_1272.JPG
    1.5 MB · Views: 122
Yeah you will never see a gpu with mixed ram from 2 different makers. Unless if its a deep fake with a custom fake bios.

You have specifically Samsung FC


Your card specs are in the link
 
Thanks @eidairaman1 ! So, which PUYA 25D21H chip should I solder or jump pins 1 and 5 together to flash it (U11 left, U300 top right, or U4503 bottom right)? As of now, the card is not "seen" at all on Windows 10 by GPUz.
 

Attachments

  • IMG_1273edited.JPG
    IMG_1273edited.JPG
    3.3 MB · Views: 96
A few pictures attached. Although hard to tell, I double checked and all 8 chips are Samsung.
I also see traces appear damaged on the card by some ram chips

Thanks @eidairaman1 ! So, which PUYA 25D21H chip should I solder or jump pins 1 and 5 together to flash it (U11 left, U300 top right, or U4503 bottom right)? As of now, the card is not "seen" at all on Windows 10 by GPUz.
Get a better picture, it's blurry as hell
 
Last edited:
I also see traces appear damaged on the card by some ram chips
That appears to be the lighting.

Here's a better picture of the back side with the EEPROM chips. Camera lenses were smudged.
 

Attachments

  • IMG_1274.JPG
    IMG_1274.JPG
    2.4 MB · Views: 87
Last edited:
That appears to be the lighting.

Here's a better picture of the back side with the EEPROM chips. Camera lenses were smudged.
Better? We can't read the text on the chips.

 
I stand corrected. Two of the three EEPROM chips (U11 left and U4503 bottom right) read

PUYA
P25201H
*0ATE918

U300 (top right angled) reads

APL3952A
PW4ES

EDIT: Thanks for the video! I will try that trick and see if that clears the EEPROM.
 
I stand corrected. Two of the three EEPROM chips (U11 left and U4503 bottom right) read

PUYA
P25201H
*0ATE918

U300 (top right angled) reads

APL3952A
PW4ES

EDIT: Thanks for the video! I will try that trick and see if that clears the EEPROM.
U11 and U4503 are the chips you need to flash.

When the bios switch is moved towards the PCI-E power, that position should provide you the primary bios (U11) during POST.
See the video I shared earlier.
 
That appears to be the lighting.

Here's a better picture of the back side with the EEPROM chips. Camera lenses were smudged.
Idk, 2 closeups appeared with spotted areas in the wet patches between ram chips. Trace damage can cause artifacts besides wrong bios or a damaged mc on gpu die. Anyways i found several files that should match your card.












 
Idk, 2 closeups appeared with spotted areas in the wet patches between ram chips. Trace damage can cause artifacts besides wrong bios or a damaged mc on gpu die. Anyways i found several files that should match your card.
Thanks again! I noticed that my card sticker says it's an OC+ rated at 1386MHz. The links you provided are for 1366MHz. Does it really matter if I use a lower MHz BIOS?
 
Thanks again! I noticed that my card sticker says it's an OC+ rated at 1386MHz. The links you provided are for 1366MHz. Does it really matter if I use a lower MHz BIOS?
If you did your home work, you would have know 1366MHz is the actual clock speed for your card and flashed a bios with the correct memory support.

1744007304034.png

Source: https://www.xfxforce.com/gpus/amd-radeon-tm-rx-580-gts-xxx-edition-8gb-3
Watch this to find out what OC+ means:

Here are the validated XFX bioses with Samsung K4G80325FC support.

Bios switch towards PCI-E Power:

Bios switch towards PCI Bracket:
 
Thanks everyone for your help! Even after jumping the pins on the primary BIOS chip, the fans spin up, and one of 2 things happen:

1. mobo refuses to boot - fans rev up really loud
2. else, after a long time (20-30 minutes), mobo boots up into Windows 10 but card is not visible at all using GPUz or AMDVBFlash (error message: discrete card not found)

UPDATE: I finally was able to unbrick the card by using the amdvbflash.efi to boot via EFI. U11 (primary BIOS) would not unlock even after jumping pins. I ended up jumping U5403 (secondary BIOS) and finally booted up. I was able to unlock it first using the amdvbflash -unlockrom -0 command. Then, I downloaded the 2 BIOS files provided in the links that @VuurVOS shared. Since I had the pins jumped on U5403 (secondary BIOS), I flipped the BIOS switch to primary and flashed U11 first. Then, I removed the jumper and rebooted using the primary BIOS and flipped the switch to secondary BIOS and flashed it.

That said, the BIOS files that I used: XFX.RX580.8192.190820.rom and XFX.RX580.8192.190820_1.rom did unbrick the card, the card is still not running correctly. When it booted up, the colors are off and the fans are not spinning.

UPDATE #2: I'm reading some of the forums and from what I understand, the fans do not engage until a certain temperature is reached, so it may be normal that the fans do not spin. That said, the colors are still "off" when using the DVI-D port. At first, I thought maybe it was the DVI cable itself but I tested it with another card and the colors are fine.

When using the HDMI port out of the card, the colors are fine, so wtf?!

JP
 
Last edited:
Here's the latest GPUz screenshot after I was able to unbrick. Question: Under GPU clock, memory shows 0 MHz?!
 

Attachments

  • RX580-BIOS1-PCIe.PNG
    RX580-BIOS1-PCIe.PNG
    59.6 KB · Views: 56
Here's the latest GPUz screenshot after I was able to unbrick. Question: Under GPU clock, memory shows 0 MHz?!
Doesn't look healthy...can you make a picture of those strange "colors"?

This bios isn't the correct one for your card but you can try it. Its slightly overclocked.
 
Thanks again! I noticed that my card sticker says it's an OC+ rated at 1386MHz. The links you provided are for 1366MHz. Does it really matter if I use a lower MHz BIOS?
If you look on the specs page your stock clock is 1366

That cards done, either mc is bad or the traces are damaged.
 
If you look on the specs page your stock clock is 1366

That cards done, either mc is bad or the traces are damaged.
I'm pretty sure this card was used for mining, which is why I'm having all these problems. I'm waiting to hear back from XFX on an updated BIOS.
 
I'm pretty sure this card was used for mining, which is why I'm having all these problems. I'm waiting to hear back from XFX on an updated BIOS.
With the wetmarks on the board is a giveaway
 
I heard back from XFX and they provided me this link, which they said it's for my card (original release 5808SMD2.M81):


Opinions? This link is for a 1100MHz memory speed, not 1366MHz.

Here are the screenshots of the weird "colors" I'm getting during bootup. Once the Windows 10 bootup screen appears, colors are back to normal. In addition, I keep getting a nagging message from the monitor DDC/CI enable/disable, which I'm sure it's related to the incorrect BIOS.
 

Attachments

  • IMG_1281.JPG
    IMG_1281.JPG
    4.6 MB · Views: 35
  • IMG_1282.JPG
    IMG_1282.JPG
    4.4 MB · Views: 34
  • IMG_1283.JPG
    IMG_1283.JPG
    3.6 MB · Views: 33
  • IMG_1284.JPG
    IMG_1284.JPG
    5.8 MB · Views: 30
Last edited:
Back
Top