AMD and Nvidia GOP update (No requests, DIY)

@FPSUsername Did You try to flah a bios updated with GOP for GF10x on GF114? I am also curious if this would work.

GOP Updater v1.9.6.5.j

- Added 2.12.0.0.0 AMD GOP Uefi Table (for VEGA cards)

Thanks to @SoniX and @Ruin

GOP_Updater_v1.9.6.5_j.rar (5.87 MB)

Hello @Sylar76 , I stumbled on your thread while searching for a solution to a problem I have. My new NVIDIA 1650S (Palit StormX OC) makes my PC hang after a reboot on the UEFI logo when a DisplayPort monitor is connected. Shutting down and normal starting is fine, but the reboot command screws it up and it’s very annoying because many things depend on restarts. From my long research it seems to be from the UEFI interaction between my MB UEFI and the GPU UEFI - the GOP. The fact that it runs fine when Windows 10 is installed in Legacy Mode reinforces this.

I read and ran your tool and it found a newer GOP version than the ones you have - 0x50013. I will post if for you so you can add it here but my question is could you help me with my issue? Maybe to try and revert to an older version of the GOP? Or modify the motherboard UEFI BIOS (I have an ASUS 990FX Sabertooth R2.0 with an FX-8350). I have contacted NVIDIA and Palit, reinstalled the VBIOS and tried running the DisplayPort update tool (didn’t run, as expected) but all that hasn’t been of much help… I have seen that the problem occurs with NVIDIA 1000-series and later and I wonder what’s up with that, why hasn’t it been fixed yet and who needs to fix it - GPU or MB manufacturer? I can provide a MB BIOS too if you’d be generous to give me a hand :slight_smile: (latest one).

TU116_BIOS_info.PNG

UEFI_GOP_1650S.PNG

TU116.rom_newGOP.zip (266 KB)

@trax7

0x50013 is an old table. Did you use the v1.9.6.5.j version linked above ?


Thank you for the quick answer!
Hmm. The OP and your tool said it’s newer and that you don’t have it in the database. I used the version from the second post but I can try with this one too! :slight_smile:
Is there a way to upgrade anyway?

EDIT: My bad. It seems 1.9.6.5.j updates the GOP successfully to 0x0015 but it’s saying that I need to report some things as well. Here is a screenshot and the BIOS files before and after. Are they good…? Cheers! :slight_smile:



EDIT 2: Also attaching the differences after executing #Nvidia_ROM_Info.bat on the images before and after updating. I see that InfoROM and License placeholder are gone…

GOP_Updater.zip (1.32 MB)

i try to update EVGA RTX 2080 XC gop with 1.9.6.5j, I got error message that gopupd.exe is not compatible with the version of windows you’re using


with 1.9.6.5 on the same computer running win7 X86, it shows updated successfully but “Please report it!” is it safe to nvflash with updated firmware that 1.9.6.5 created??


Do you have python installed? Does the version of python matches your windows arch? (e.g. x86 or x64)


Yes it is - no issue, but please check which nvflash you’re using - 2080 (non SUPER and TI) needs an older one - V 5.541.0 for example

What installation of python do you have?
Never ever seen, the regular one, installing into your Users folder?
More or less - the path for python is simply too long - as side as it might be the wrong version.
Try uninstalling it completely - check your Windows Environment Variables for remains of it and remove them also.
The latest GOP Updater works completely without any python installed - but if python is installed you need to add "colorama" plugin via ‘pip -install colorama’ in scripts directory of your python installation.

i finally updated my EVGA 2080 GOP version to 0x50015 with 1.9.6.5 j on win10 x64 w/o error message


the windows security keep deleting cecho.exe, because it says the file has virus in it, i have to allow it in order to update gop

@trax7

On some Turing cards there are some nvflash different reports once updated to latest gop and I don’t know why as I haven’t any Turing card to make tests.

The only thing I do is to update the tool when a new uefi gop table has been published.

@gtishtar

You can also use the original Lordkag file.
However, this can also lead to false virus reports …

Unbenannt.png

cecho.zip (23.7 KB)

Hi, thanks for this tool that gives me hope to fix Displayport issues in boot/uefi with an OEM HP RTX 2060
I could patch the Rom with updated GOP but InfoROM is missing and no luck flashing

Would appreciate any suggestion, thanks !





compare command



Flashing starts then stop at 65 %, driver stopped in device manager, tried --protectoff before flashing, same error

@trax7

I’ve found the way to properly update TU1xx cards in order to show right nvidia inforom !!
Try the attached bios please.

@JFK73

Please link me your original bios dump and I’ll try to do the same work.

TU116_NEW.zip (676 KB)

Awesome!
If I understand correctly nvflash is waiting for a matching infoROM data in patched rom but GOPupd removes it ?

I extracted inforom.ifr from original bios but how to inject it in the patched rom, Do you know a Nvflash command to do this or you’ve to manually HEX edit ?

Bios and Inforomifr.zip (672 KB)

@JFK73

Ok, Here you go. Try the attached bios please !

BackupRtx2060_NEW.zip (674 KB)

@JFK73

Of course, report feedback please. As far as I’ve known the latest UEFI Gop Table is smaller than the original one and thus the Inforom infos are shifted to a different offset.
The trick is to insert padding data (FF) to shift again to the original offset the inforom thus making file size the same of the original dump.

Yes sure, the log file looks much better now but still failing at 65 %
Should everything match with --compare command ?

output1.zip (3.19 KB)

The only mismatch thing is the Firmware Certificate and I don’t know how to fix it.

Anyway you found a nice trick for InfoROM
That was very instructive, appreciate thank you !

@JFK73

Did you try a different nvflash version to bypass the certificate check ?