@Fitnesstrainer
Do you still have that GPU? If you do, could you please upload the BIOS version 86.07.39.40.E0 for me? I can’t find it anywhere and would really appreciate it. Thank you
I still have the GPU. ASUS ROG Strix GTX 1050.
The GPU has GOP 30007.
I updated to GOP 30013 and flashed it. No problems.
But it’s only signed with Microsoft Corporation UEFI CA 2011. Secure Boot issues will likely occur in 2026.
nvbios_original.zip (154.1 KB)
Can’t this software be updated with a new certificate? For example, Microsoft UEFI CA 2023. How can we obtain this certificate? Or is there nothing else we can do for these signatures since the GOPs here actually come directly from AMD or Nvidia?
We cant obtain this certificate.
Msi motherboards and asrock with secure boot on default settings they don’t check option rom certificates so when microsoft update secure boot with ca 2023 they will continue to work.
They check only boo-table certificates in a usb for example.
1 Like
What? You can download it from Microsoft site. There are links here for the current trio of Windows UEFI CA 2023, Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023. These should be integrated to Secure Boot db Database.
Yes this is the easy part you will integrate in the motherboard the certificates but your gpu has a gop certificate only uefi ca 2011.
they need to make a gop with 2023 certificate.
i have try GOP_Updater_v1.9.6.5.k_mod_v0.5.2 on two GT240(gt215 core Tesla 2.0 architecture) + one GT220(gt216 core Tesla 2.0 architecture) , yes , i have a lots old cards. but none of them can be enable pure uefi with god , i can confirm the process is correct , and i had change to a larger 128kb（and 1024kb）25 Series flash chip. the cards can boot after flash gop updated bios and work as usual (only in csm) , and gpu-z show gop supported also , but , when i turn csm off , i get black screen（had try on different MB , get the same result） !
Strangely, i try many of g210 and g205 (both of them are gt218 core Tesla 2.0 architecture) , all off them work correctly with god enable in pure uefi mode as i want .
are there any different in gt2xx core Tesla 2.0 architecture cards leading this peoblem ?
had anybody did this successfully (turely get pure uefi enabled with gop ; the indicater of uefi support in gpu-z is not correct)on gt2xx core (except gt218 core ; this always work correctly for me) old cards ？
i am trying to UPDATE GOP at mxm 1070 ( what installed at GT73EVR 7RE Titan)
but it seems to me that something is wrong here
Summary
Dumping info from = 104.rom
NVIDIA Firmware Update Utility (Version 5.735.0)
Copyright (C) 1993-2021, NVIDIA Corporation. All rights reserved.Sign-On Message : GP104 E2914 SKU 10 VGA BIOS
Build GUID : 00000000000000000000000000000000
IFR Subsystem ID : Blank
Subsystem Vendor ID : 0x1462
Subsystem ID : 0x11FF
Version : 86.04.56.00.3A
Image Hash : 91C3A20E278E045774F8FEE9B16CD5FD
Product Name : GP104 Board
Device Name(s) : GeForce GTX 1070
Board ID : 0xED0F
Vendor ID : 0x10DE
Device ID : 0x1BE1
Hierarchy ID : Normal Board
Chip SKU : 725-0
Project : 2914-0010
Build Date : 11/03/16
Modification Date : 11/10/16
UEFI Version : 0x30006 ( x64 )
UEFI Variant ID : 0x0000000000000007 ( GP1xx )
UEFI Signer(s) : Microsoft Corporation UEFI CA 2011
XUSB-FW Version ID : N/A
XUSB-FW Build Time : N/A
InfoROM Version : G001.0000.01.03
InfoROM Backup : Not Present
License Placeholder : Not Present
GPU Mode : N/A
CEC OTA-signed Blob : Not PresentPress any key to exit…
************************* GOPupd 1.9.6.5.k mod v0.5 *************************
************************ Drop VBIOS file on this .bat ***********************
Using python from GOPupd
Dumping info from = 104.rom
ID of ROM file = 10DE-1BE1
Different sizes in ROM header and PCI structure of Legacy ROM!
Found Unknown header before ROM start, size 0x38A00
ID of ROM file = 10DE-0000
Different sizes in ROM header and PCI structure of Legacy ROM!
*** Extracting with UEFIRomExtract by AndyV ***
Found compressed EFI ROM start at 0x50
Input size: 67504, Output size: 129408, Scratch size: 13368
*** Extracting with GOPupd… ***
Nvidia GOP 0x30006 Variant 0x0000000000000007 = GP1xx
Dated: Oct 26 2016 Changelist 21305424
Most likely signed by: Microsoft Corporation UEFI CA 2011
Machine Code = x64
Checksum CRC32 = 812D99BE
*** Processing with Python… ***
Latest available GOP is 0x30013
Different sizes in ROM header and PCI structure of Legacy ROM!
EFI ROM is not last image!
Do you want to update GOP to 0x30013? Y for yes or N for no: Y
There are other ROM images in this binary! Please report it!
EFI is NOT last image!
Fixing ID, last-image-bit and checksum for EFI image.
File “104_updGOP.rom” with updated GOP 0x30013 was written!
Press any key to exit..
NVIDIA Firmware Update Utility (Version 5.735.0)
Copyright (C) 1993-2021, NVIDIA Corporation. All rights reserved.Sign-On Message : GP104 E2914 SKU 10 VGA BIOS
Build GUID : 00000000000000000000000000000000
IFR Subsystem ID : Blank
Subsystem Vendor ID : 0x1462
Subsystem ID : 0x11FF
Version : 86.04.56.00.3A
Image Hash : 91C3A20E278E045774F8FEE9B16CD5FD
Product Name : GP104 Board
Device Name(s) : GeForce GTX 1070
Board ID : 0xED0F
Vendor ID : 0x10DE
Device ID : 0x1BE1
Hierarchy ID : Normal Board
Chip SKU : 725-0
Project : 2914-0010
Build Date : 11/03/16
Modification Date : 11/10/16
UEFI Version : 0x30013 ( x64 )
UEFI Variant ID : 0x0000000000000007 ( GP1xx )
UEFI Signer(s) : Microsoft Corporation UEFI CA 2011
XUSB-FW Version ID : N/A
XUSB-FW Build Time : N/A
InfoROM Version : G001.0000.01.03
InfoROM Backup : Not Present
License Placeholder : Not Present
GPU Mode : N/A
CEC OTA-signed Blob : Not PresentPress any key to exit…
As far as I understand, the mxm card is essentially a separate board with its own BIOS?
But the lines during the update are confusing, since this laptop has hardware switching of cards, and if the built-in one is enabled, 1070 will not be available.
I’m trying to flash it because with the latest drivers, starting with 576.02, the driver reboots during logon, freezing the logon process (black screen ). With the latest 580.xx drivers, the brightness also drops to minimum until I manually reset it. I suspect the problem might be with the GOP.
Maybe I’m wrong and the card actually uses the ROM built into the UEFI and not its own.
MSI_104_mxm_1070_rom_dump.zip (147.8 KB)
The tool is old and a “homemade” project… flash it at your own risk, if you know and have the skills of recovering.
But be warned that the EFI GOP driver is a low hw UEFI initialization driver and not used after system post/OS, the issue lies elsewhere…
Yes it’s driver problem , it’s broken for that GPU statring from 576.02
latest working correct 572.83 ( i manually installed them all before bug start appear )
so no reason try upadate GOP at that GPU , i know this gop util work for standart PCI GPU 10xx perfect. But if even with them go wrong i have many PCI cards so it’s simple replash. But with that mxm and custop PC Laptop hybride system from MSI , resulat will be unknown.
I’m also confused by the warnings…
Hello, I have a Sapphire Nitro RX 570 4Gb that has troubles displaying the GOP when connected to a 4K TV.
The card has this BIOS:
I’ve tried updating the GOP module using both GOPUpd v1.9.6.5.k mod v0.5.2 and GOPUpd_v1.9.6.5_(MAGICgop_AMD_1.69).rar from 2nd post above and I didnt notice any changes.
The TV is a TCL model C835 which has both HDMI 2.0 4K/60 and HDMI 2.1 4K/120-144 ports. The card displays the GOP when connected to the 4K/60 port but not when connected to the 4k/120 port (I would like to use the HDMI 2.1 port because when connected to the HDMI 2.0 port the card is unable to detect the screen as native HDMI 2.0/60Hz and falls back to YUV420 to achieve 60Hz).
Is there any other GOP I could try to overcome this limitation?
EDIT: the card has dual bios controlled by a hardware switch, I have only tried the above bios, the other BIOS is apparently the same with downgraded clocks (labeled “Silent BIOS” by TPU).
Is there any point in trying to update the GOP in that BIOS? (kept it untouched for failsafe)
Some issues are also related to cables…models/vendors, related to GOP can’t add anything else than what you researched, but the output is 2.0b not 2.1.
I have tried several cables and made no difference.
I dont expect to achieve 4K/120 of course, just BIOS and boot screen displaying at whatever resolution, right now I only get any image once the windows display driver load.
Side note, I have an RX580 (Asus manufacturer though) and with stock ROM GOP I get boot image when connected to a Lenovo 4K monitor without any troubles. Pity I’m not able to test the RX570 with the Lenovo 4K because its at a different location.
I suppose it could be something related to the TV’s particular HDMI implementation, maybe EDID?
Out of my league…
Hi, on my Gigabyte Aorus Radeon RX580 4GB (GV-RX580AORUS-4GD) I managed to get UEFI boot, but I can’t get it to work properly with SECURE BOOT. I use Magic GOP 1.69. Is there another GOP with which UEFI+SECURE BOOT works? Secure Boot has several options on my motherboard (Gigabyte Z270 Gaming K3)…
Will the graphics card work once the UEFI CA 2011 certificates expire, or will the GOP need to be updated?
You had need to apply the 1.69M?
Try lower or higher ones…
My VBIOS Rom came from factory with GOP version 1.62.0.15.50, I have tried GOP 1.69.0.15.50 (Magic) with result (UEFI-YES and Secure Boot-NO) and GOP 1.70.0.15.50 with result (UEFI-NO and Secure Boot-NO) When I say Secure Boot-NO the computer ends up loading WINDOWS 11x64 (UEFI+GPT installation) but the boot throws 5 beeps and the GPU light on the Motherboard is on but it boots Windows (Losing access to the Motherboard BIOS, no image until the Windows login page). What can I try to get UEFI+SECURE BOOT? Any “Custom” SECURE BOOT configuration, another version of VBIOS or GOP?
I don’t know if it’s the Stock Rom or Modified because I bought the card second hand, I don’t know how I can find that out. I have some doubts about getting an original ROM. On the manufacturer’s website, there are only VBIOS ROMs for revision 1.1, and I don’t know which revision mine is since the sticker on the card is damaged. In any case, even if it were revision 1.1, as I think I see on the sticker, I think I have the VBIOS ROM “F10”, and the manufacturer’s website offers VBIOS “F81”, “FY1”, and “FZ1”, which correspond to other VBIOS ROMs. At the bottom of the page, it indicates that the “F10” can be updated with “F11-F19”, but I don’t see them available. I could try the VBIOS from “TechPowerUp”, but they don’t specify the revision, and I’m not sure which one to choose since they also differentiate themselves by memory manufacturers: “SKHYNIX”, “Micron”, or “Samsung”. Mine is “Hynix” according to GPU-Z.
Nothing know…
No know “special” configuration
No other “know” GOPs that resolve both issues.
I would advise Gigabyte support ticket for original/updated vbios or forum…but not without SN sticker…
Advance users can try to cross flash other vbios, usually MBA OEMs vbios like PowerColor (TUL)/ SAPPHIRE, but some skills are necessary.
EDIT:
Usually yes, the 16.9M is a case apart.
Notice than im not a user that had any contributions to this project and the tool had no development for a long time, im just giving some answers based on my PoV.
Aside from that, still it has some utility and had solved many users problems…
Thank you very much for your work and answers. I’ve contacted Gigabyte to obtain the most up-to-date and original VBIOS possible, and I’ll continue testing from there to see if I find any improvements. For now, I’m ruling out updating with a VBIOS from a “compatible” motherboard unless someone with more experience has tested it on a card like mine and gotten good results in terms of performance and UEFI+SB options.
I’d like to ask if I’m performing the GOP update correctly. My card’s ID, 1002-67DF, doesn’t appear in all the “GOP Update” lists I have. Could this cause any problems? Should I enter it manually in the .txt or somewhere else?
In my “Original” VBIOS the temporary file generated in the GOP update is “AMD GOP 1.62.0.15.50_signed_93D6E2E3” and when I update the GOP, the temporary file is “AMD GOP 1.69.0.15.50_signed_3B62F1AF”, that is, the CRC32 Checksum changes after updating with Magic GOP, I have seen in another version for example 1.67.0.15.50 which indicates D803F7B9. In the previous case when trying to update the GOP Magic 1.69 with the GOP 1.70 I get an error regarding the GOP / Checksum, but such error does not appear if I use the GOP 1.70 on the original VBIOS (1.62) Is it preferable to always do the update on the original VBIOS? Is it advisable to keep the CRC32 checksum with the original VBIOS numbering?
Thanks for your time, best regards!
P.S. If no improvements are made, UEFI+Secure Boot OFF+TPM is sufficient for me to run Windows 11. I hope Secure Boot won’t be necessary in the future.
1.62 to 1.70 (Original to GOP 1.70)
1.69 (GOP Magic Update) to 1.70 (GOP Update)
Hello everyone,
I’m looking for the correct AMD GOP module for Navi22 (RX 6700 OC 10GB, Sapphire).
I already have the latest GOPupd v1.9.6.5 pack, but it only contains older GOP files (up to Vega).
Could someone please share or point me to the latest AMD_GOP_Navi22_2.14.0.17.50.bin (or newer, 2.18.x) file that works with GOPupd?
My goal is just to add UEFI/GOP support for a Mac Pro 5,1 (no overclock, no modding).
Thank you very much in advance for your help!