[Problem] Sapphire RX 470 doesn't work with Intel System

hello friends, i have encountered an unusual problem i have a Sapphire RX 470 8GB(NITRO+) video card rx 470 sapphire nitro 8 gb and the problem is that it is completely functional and works but only on Ryzen systems on intel systems it simply refuses to output an image through pci 1 x16 by trial and error i noticed that the card was able to give an image on intel but only in the second pci slot i have several systems on intel with different chipsets and the problem is the same everywhere the card does not output an image from the first pci


Edit by Fernando: Thread title customized

You’re saying that the dGPU doesnt have any output signal on several Intel platform boards and always failing when in PCIe x16_1 slot…
Is this a used mining dGPU card, if yes reflash original vbios from TPU.
CSM/Legacy or UEFI mb settings?

Hello, I don’t know, maybe the card was in mining, I bought it on eBay, I already flashed the BIOS but it didn’t help

here is a link from techpowerup to my card

This is the only BIOS I have found that can be flashed to my video card without any problems.

with the help of the gpt chat I found out that maybe the problem is in the GOP in its old version or absence I found similar discussions on this forum and found how to flash a new GOP to my BIOS and I did everything correctly but nothing changed the images in the first pci are still not there

maybe someone knows other bios for this card or a new GOP for video cards on the Polaris architecture, help me with whatever you can, I’m just about to give up

The issues on these RX400/500 are not solved using latest GOP version 1.70, instead an old modified “Magic GOP” 1.69, look for it, there’s no other vbios for them from AMD or OEM’s, the TPU ones are the correct ones.

ok I found those magic gop that you wrote about but I don’t quite understand what to do with these files and what needs to be done for this what exactly needs to be done with the ROM file?

So, what did you do here…??? The GOPs are applied to vbios ROM…lol

in the instructions that I found it was shown that you need to say GOP updater then you need to throw the bios of the card into it and then drag it GOPupd bat after which a window appears asking if you want to flash cop of the specified version I simply agreed found y after the process was completed the new firmware file that appeared I flashed through amdvbflash

don’t be angry, I’m a newbie in this business and maybe I misunderstood something or did something wrong, so I would be very grateful for a detailed explanation, since I didn’t find a detailed description of what and how to do

Assuming you did get the correct “MAGIC GOP 1.69” package/file…
So, have you dumped the newly done Magic GOP vbios after flashed and passed through the tool again to check if indeed the 1.69 was applied…? If yes then you’re done here, sell it or stay on that AMD platform with her.
That’s all, good luck.

I found a suitable GOP updater changed the bios file to a suitable magic gop, then flashed this bios file but nothing changed, there is still no image

Uploading: IMG_20250729_020000.jpg…

so i found a person with a similar problem and i used his version of gop updater and so the file magic gop

There is a chance chance that the issue is related to physically damaged one of PCIe lines after the initial 8. Especially visually inspect the capacitors near the slot on the card, sometimes they can be seen as physically damaged.

So in x8 slot it works fine, and in x16 slot the link negotiation fails. AMD systems are known to perform this negotiation in a slightly different and robust way, so there it may work. Maybe AMD is negotiating less-the-x16 width, check the effective width in GPU-Z of that AMD system.

To check this hypothesis you can temporarily cover by tape the part GPU PCIe connector that is wider that x8 (consult PCIE pinout on the wikipedia to correctly count lanes.). The motherboard would assume that card is an x8 PCI device plugged in x16 slot. If this would work - the problem would be very similar to the hardware one, not VBIOS-related one.

1 Like