You’re funny…
Anyone ?
Is it possible to enable UEFI in the BIOS of the GTS 450?
Doubt it, due to most size of ROM ICs being 64Kb, if you hava model with 128 you can try it (GF10x) as long as you know how to recover.
There’s also some vbios on TPU used on those fake 1050 Ti (GTS 450), that claims UEFI support.
EDIT:
No and never can be. Have you at least checked your IC model and rom size… it could be a wasting time search for nothing, if you have a standard IC unless soldered a new bigger IC or if the rom even likes your pcb…
Nothing more to add, over_n_out.
Yes, 64KB.
Where can I find the BIOS for the fake GTS 450? I would like to try to use it. Is he on 64KB?
I have a chip on 64KB.
Maybe it is possible to replace the chip with 128KB? How to do this and will there be a result?
Hi guys. It’s been a while. I would like to know, if there are some changes in GOP updater. Is there any new version besides GOP_Updater_v1.9.6.5.k_mod_v0.5.2 ? Is there any chance that I can update GOP driver on RTX 2080Ti using this tool or is it still only possible manually? Please, direct me guys to the way of how to update the GOP driver to the newest possible version on RTX 2080Ti Founder Edition.
Sill works for TUxxx (5001F), no further releases of the tool exists for now…
Another NVidia tool/updater here:
GOP Update and Extraction Tool (NVIDIA Only) - BIOS/UEFI Modding / BIOS Modding Guides and Problems - Win-Raid Forum (level1techs.com)
1 Like
Thanks. I’ve found the second tool just after asking. It Works. The first one throws back some errors. So I’m not sure it works properly with Turing GPU’s.
Gave it a shot with v0.4.8. It identifies that the file will end up too large (over 128KB) if using the latest GOP and keeping the identified microcode block near the end. However, it provides an option to use an older, smaller GOP instead that results in a file under 128KB even with the microcode maintained.
I did both, but of course the “option A” file (using the newer GOP and retaining the microcode) is over 128KB and so can’t be used as it won’t all fit.
However, the “option B” file using the older, smaller GOP is just 121KB, and I would guess it should work fine.
Cypress_w_GOP.zip (266.7 KB)
Don’t be concerned that the modded file isn’t exactly 128KB on the nose. GPU-Z and other tools that dump the rom from a card are exhaustive and copy out the entire contents of the flash chip regardless of the data, but there’s nearly always some wasted space that’s not actually storing anything.
If you open the unmodified cypress.rom in a hex editor, you can see that a huge chunk of the end, from 0x1e1e8 through 0x1ffff (7KB) is just padding consisting entirely of “FF”.
GOPupd just truncates any leftover padding from the end of the modified file before saving it (the “Removing unnecessary end padding.” message)
I had similar worries at first back when I used this tool to add a GOP to a Cedar-based HD5450 rom. The “stock” file GPU-Z dumped was exactly 128KB, while the modified one with the GOP added was only 116KB. After comparing the files and seeing that it was just a padding difference, I flashed it and it worked absolutely fine.