i updated an rx580 8gb succesfully with the gopupdater to run in pure UEFI, big thx for that tool !
but i wonder, will the gpu still work if Microsoft completely expire the old Secure Boot certificate 2011 and only 2023 will be available after June 2026?
i don’t want to disable Secure Boot, because some tools/games start to require this.
Hello!
Good question. Of course the video accelerator will work, it would be strange if it didn’t.
However, some programs and games may require it.
Thanks/
Which tool did You use? I have legac GOP_updater, GOP_Updater_v1.9.6.5.k_mod_v0.4.9 and GOP_Updater_v1.9.6.5.k_mod_v0.5.2. None of them work and I have a similar issue.
EDIT: I just tried GOP_Legacy 0.6.2 and it also doesn’t work. I get “Data after ROM and not part of EFI! Please report it!” error.
Sapphire Nitro+ RX 570 8GB
i have used the GOP_Updater_v1.9.6.5.k_mod_v0.5.2, what you need to do is backup the original Vbios, (keep in mind, it must be a Vbios that is not been modified before or it won’t work) then you open the file GOPupd.bat and drag and drop the original Vbios in it, once it’s completed flash it back to the GPU.
this method worked on a HD7870 and an RX580 that i have.
i hava amd rx6800 reference,use this 0.6.2 to errors, plz help,think you
WAITING FOR INPUT… DROP FILE NOW
Using compiled executable from #DATA_Files
Dumping info from = Navi21.rom
ID of ROM file = 1002-73BF
Found Unknown header before ROM start, size 0x14000
ID of ROM file = 1002-73BF
Extra EFI ROM found at offset 0x14000!
*** Extracting with UEFIRomExtract by AndyV ***
Found compressed EFI ROM start at 0x64
Input size: 38300, Output size: 65192, Scratch size: 13368
Found compressed EFI ROM start at 0x64
Input size: 39836, Output size: 72128, Scratch size: 13368
*** Extracting with GOPlegacy… ***
[!] Error: Unsupported VBIOS structure detected.
This generation is not yet supported.
Aborting to prevent damage.
Tool has answered itself to your doubts, no support for newer hw generations, simple as that.
I am currently developing a utility for next-generation AMD hardware.
Thank you for keeping this tool updated, but my RX6800 is not supported in this beta version
The RX 6000 series (RDNA 2) includes two separate GOP images to ensure the GPU can display a picture during boot-up on different systems:
x64: For standard Intel and AMD desktop PCs.
ARM64: For ARM-based devices (like Windows on ARM or ARM servers).
The reason: ARM processors cannot read the standard x64 BIOS code. By including both, the card is “cross-platform” and can show the BIOS menu and boot logo on both traditional and ARM-based hardware.
Because the VBIOS has to store both drivers, it uses nearly all available capacity, leaving very little free space on the VBIOS chip.
I see, thank you for the explanation.
Can you free up space by removing the GOP module of ARM64 and then upgrade the GOP of x64?
Yes, that’s possible; I’ve already been able to test it.
**Hello Ruin **
I found a bug/problem. The v0.6.2 package I am trying to update the bios on the rx 580 (ASUS DUAL RX 580 OC 8 GB) The program suggests updating to module versions 1.69 and 1.70. There was a problem with version 1.70. The motherboard was swearing at UEFI compatibility. 1.69 - works well.
hello walkman8196
Thanks for your feedback.
Hi everyone,
Our GIGABYTE AORUS RX 580 8GB was not working with the Colorful X870 Senna V14 motherboard. I searched for the reason and found your program. It’s great; the GPU worked perfectly after the update! I wanted to write a roadmap here in case someone else needs it.
Firstly, you need GPU-Z to export your stock BIOS. You will see a ‘UEFI’ checkbox on the left side; click the arrow button next to it and save your BIOS. Back it up both offline and online for your safety.
I used version v0.6.2 with GOP 1.69 because some people in this thread mentioned that 1.70 causes problems with some GPUs, so I started testing with the older version. I installed Python 3.14 from the Windows Store (say ‘Yes’ to all prompts during installation). After that, I installed colorama via PowerShell using the command: pip install colorama.
I tested a lot of ATIFlash versions, but they didn’t work for us. I found an AMD/ATi Flash Command Line (CMD) Syntax Mini Guide that suggested version 2.93. I followed the flashing steps in that guide, and it successfully worked . I Googled it, but TechPowerUp didn’t have a link for this exact version. I finally found AtiFlash 2.93+ (2.93+). If you don’t trust this link, please find an alternative online. Note: This version might not have the AMDVbFlash driver; if so, use the driver installer from another version and then use 2.93+ for the RX 500 series.
The custom BIOS installed successfully. I wanted to compare the VBIOS files after the installation was done. I opened GPU-Z, saved the new BIOS, and checked the SHA256 hashes using 7-Zip to compare three files:
1-Stock
2-Gopdate
3-The new ROM extracted from the GPU
The first one had a different SHA256 hash because it was our stock ROM, which is normal. The second and third files needed to have the same SHA256 hash. If they match, everything worked perfectly.
Thanks for this program guys, it saved us! I hope this helps someone else. Sorry for the long text!
Hi,
I need help getting UEFI GOP support added to my graphics card’s VBIOS so I can enable Secure Boot (required by Riot Vanguard/Valorant anti-cheat).
Card details:
System:
I have a clean backup of my current VBIOS (backup.rom, saved via amdvbflash v2.93, checksum 0x0D00) attached to this post.
Could someone patch GOP support into my exact VBIOS dump? I’d rather not flash a generic/similar VBIOS from another card due to bricking risk.
Thanks in advance!
Hi, I successfully removed the ARM64 GOP and upgraded the x64 GOP version to 3.9.11 using your v0.8 tool. However, the AMD GOP still limits the HDMI output EDID to below 340MHz, meaning a maximum output of 2K. Do you have any ideas on how to extend the HDMI output to 4K?
@dpae1133 do you have the techpowerup page of your vbios?
Hi,
I think there’s a misunderstanding about what the GOP actually does.
1. The GOP is pre-OS only
The UEFI GOP handles display output only before the operating system loads (BIOS setup, boot logo). Once Windows loads the AMD driver, the GOP is bypassed entirely. It has no say in your maximum resolution under the OS.
2. 340 MHz is the HDMI 1.4b TMDS limit
That’s a hardware spec. HDMI 2.0 runs at 600 MHz. If the port is physically HDMI 1.4, no firmware update can turn it into HDMI 2.0.
Important: 340 MHz does not mean “2K max”. Within that limit you get:
4K @ 30 Hz (297 MHz) 
4K @ 60 Hz with YCbCr 4:2:0 (297 MHz)
4K @ 60 Hz with 8-bit RGB / 4:4:4 (594 MHz) ✘
So if your monitor supports 4:2:0, you may already be able to get 4K@60.
3. EDID comes from the monitor
The EDID is provided by the display, not by the GOP. What’s limiting you here is the source (GPU/port), not the EDID being read.
4. If it really is a software limit
Then it lives in the VBIOS connector and display tables — not in the isolated GOP block my tool replaces. On top of that, it depends on the hardware: PHY speed, level shifters, possibly an LSPCon or redriver on the board. If one of those parts isn’t there, firmware won’t help.
My advice: Check the manufacturer’s specs first to see whether the port is rated for HDMI 2.0/2.1 at all. If it isn’t, the rest is moot.
The AMD RX6800 Reference supports HDMI 2.1, and I can output 5K 120Hz on a MAC system. However, at the UEFI stage, if HDMI supports output above 4K 60Hz, it needs high-frequency TMDS (i.e., breaking through 340MHZ) or enabling FRL mode. However, AMD’s GOP driver does not support high-frequency TMDS and does not have an embedded FRL driver, so it cannot output 4K60HZ. So I tried using 297MHZ at 4K30Hz, but there is no 4K30Hz mode preset in VBIOS; the maximum mode is 2K60Hz