Its always nice to have a dual bios switch on your video card just in case. Made the process less stressful knowing I could revert the bios at any time.

@lordkag:

I ran your tool (v2) before posting. There was no text '.... report ....' -> see attached screenie.
If it would have been displayed I of course would have posted it with the above file.

Of course it wasn't any there, you didn't run the update. This is how it looks when you run the update:



It doesn't makes much sense in processing the whole file at once, maybe the user just wants to check its GOP version, maybe the user wants to see the colours, maybe something else. This is why the script has two stages, the first one is the extraction part (decompressing EFI ROM and extract+display the version), the second happens when the user agrees to the update and the file is processed in entirely. Maybe you misunderstood the tool: it does NOT update your firmware on the spot, it just produces the file for you to flash. Where you not even interested in seeing the result? I am being honest here, I am feeling a strange mix of amusement and angriness right now, for I'm not being able to convince the users to try the tool: they either skip it entirely or run it just half. In case you missed it, I have uploaded a new version that fixes the recovery of the extra data, plus I added a warning about the original VBIOS file. You should try the update on the file produced with GPU-Z or on the one from Asus (if any). The ones from techpowerup tend to be rather old or can be from another card, so compare them and choose wisely. If you think the one from techpowerup is still the best one, then run it with v3. I have tested the resulting file and it is OK on my end, with CRC32 91e2168c and SHA-1 07789cad7a5ad88e76a45a8bb4eaa25217d64be3. But the warnings are still the same as in previous post, regarding the legacy tables and extra DJH block.

Based on your input, I guess I have no other way than to impose military rules: user should provide a screen of the tool, a hash of the updated file, a link to original VBIOS.

Zitat von lordkag im Beitrag #22

---

Yes, it is possible, but how can I be sure if you don't post a link to your VBIOS?

---

I should add this to my signature: "What we've got here is failure to communicate". I don't know how else to explain it better.

@RoughBoy

Plutomaniac was kind enough to print the requirements. I thought they would be common sense, but I've been forced to apply them due to unforeseen consequences. Yes, running the tool is a must, otherwise it would defeat the purpose of uploading it. Not to mention that it is saving you the trouble to ask for a GOP, in case you are already updated. There is also one warning about using files from techpowerup, which could be older than the one your card is using at the moment. So do yourself a favor and dump the VBIOS with GPU-Z, than see which one is newer.

Here is for your link:





As you can see, the update is minor. However, if you want something newer, there is one attached, 0x10030 from Sep 18 2014. Simply replace the one from #GOP_Files folder. There is a warning about it: it comes from a VBIOS with a class code of 030200, which stands for 3D controller or soldered GPU. There is nothing in the GOP that would suggest a custom version that would not work for all GPUs, but you never know. So consider you have been warned! If you want safety, use the GOPupd_v3 as it is, if you want latest, use the one attached.

Was wondering if there are any whitepapers or changelogs released by nvidia regarding each gop release?

Dear users, for the last time: when I say provide the VBIOS file, I don't mean it as in a request. The tool, the process, the requirements, everything is in the first post. What I really mean is for you to be extra careful and check back with me before flashing, to get a second opinion. I'm being a nice guy, by providing an extra support and extra assurance, when I could have just added a big "USE AT YOUR OWN RISK!" and leave it at that.

@davidm71

No, I haven't seen any changelog, neither from Nvidia, nor from AMD. But I suppose they are working on something, as demonstrated by your case. Since the GOPs are so old in some cases, it is obvious that a new version only comes along when there is a solid update.

Edit: actually, for AMD it could be simpler than that. The newer GOPs usually add/remove some IDs, so we can say that they are supporting new cards or removing unused IDs. But some fixes could still be there.

I'll do some web searching and see what I can find out. They must have whitepapers they distribute to hardware vendors but not us curious types. Thanks.

@lordkag
@plutomaniac

Many thanks for your support.
I found this interesting thread when I was not at home.
So I couldn't dump the BIOS of my graphics card and so on.
I'll do all the things you suggested when I'm back home on Tuesday and then I'll post the results too.
Of course I'll be careful to prevent bricking my graphics card.

Hi,

Just wanted to share I have another system based on an Asus p8z68 deluxe motherboard and two 780 GTXs (a B1 and A1 variant) and it has the same uefi no post bug when set to 'EFI Rom Priority' mode. So I ran GOP update on the roms after first flashing the latest EVGA roms I found on techpowerup database. The gop versions were 0x1001F and 0x10026 so I assumed it was the same issue as my Z87X system and flashed to 0x1002D on both cards using gopupdate but this bios uefi bug still persists. System still works but its interesting that updating gop wont solve every problem. I even tried disabling every on board device including JMB and Marvell devices. Unfortunately the 'Deluxe' version of this motherboard doesn't have an external DVI connection to test the onboard gpu functionality.

Makes me wonder how Asus could release a half-arse bios in the first place. Anyhow just wanted to also tell @Lordkag that his version of NVflash is an old one and doesnt disable the gpus prior to flashing in device manager unlike the newer Joe Dirt version that automatically disables the gpu prior to flashing. Its also interesting to note that typing 'NVFlash --lspci' gives you a run down of your components installed in your system. Aside from that we should all ask the devs behind GPU-Z to add GOP version info display into their utility..

Thanks.

As you can see in this thread, the situation is not new and the latest GOP won't fix it. Basically, the bug is in Asus yard and they will provide a fix if you ask them. Just give them a nice story with many details, write that you received a GOP update from GPU manufacturer (if you mention a custom VBIOS they might reject your request), make them a "request they can not refuse". They are very aware of the issue, but will play innocent if you don't prove the bug is in their code.

Are you sure about flashing from techpowerup? I already wrote a warning that the file from database might be older than the one from your card or manufacturer site, not to mention the risk of flashing a wrong VBIOS. I hope you saved a dump from your cards before flashing, it is always recommended to have a working backup.

Since you mentioned nvflash, I will also update the first post with this warning: DO NOT use the attached files for flashing! It was not my intention to add the files for flashing, they are present only for dumping info from ROM files, not to mention that the AMD flasher is stripped down from several dlls and the Nvidia one is 32 bit only. I will consider renaming the #Flash-Info folder to avoid such confusing. A link to the AMD/Nvidia flashers it is in the second post and was added only as a courtesy. If a user is not accustomed with flashing his GPU, he should not proceed with this GOP update.

Both AMD and Nvidia #Flash-Info folders are up to date. Nvflash is at 5.218 and it was offered by me in this post long before it appeared on overclock.net. The only reason I use the modified JoeDirt in my package is that I have only found the 64 bit of original nvflash 5.218 and I need the 32 bit version to be compatible with both OS architectures. But I will consider reversing his reversing of nvflash, to offer a vanilla nvflash, to not scare the users and to prevent a flashing from within GOPupd folder. Like I said, I only offer the updated ROM file, the rest is in user's hand.

I asked 'Raja' from Asus on Hardforum about this a couple months ago and this was his answer:

Zitat

---

No update that I am aware of. Some third party cards may not work if they have not implemented GOP support correctly.

---

and

Zitat

---

Link to original ASUS pos - does not say anything about the 6 series there unfortunately:
http://rog.asus.com/forum/showthread...st-Boot-update
Could be the VGA GOP BIOS version as well. Assuming the install was performed in GPT or are you trying to install now?
Not much else I can suggest. There are no planned updates for this at this stage.

---

As far as making a request they cant refuse I don't know what to do short of sending them a horse head in the mail but thats not fair to horses. Never mind the motherboard says 'UEFI' all over the motherboard. About the techpowerup database yes I'm sure as far as my two EVGA 780GTX ACX cards are concerned their vbioses were newer (80.80.21.00.80 vs 80.80.31.00.82 and 80.10.37.00.80 vs 80.10.3A.00.80). I checked using a hex editor and was surpised to find out that my two 780s weren't even identical as I bought them almost together. Ones a newer revision with a different device id: 3842-2784 vs 3842-0784 but I used the latest patched nvflash64 to flash without having to disable gpus in device manager and I did save a copy of the rom before flashing. Using your utility to update the gops was uneventful. Thanks for the advice.

It is OK, you used the techpowerup database in the right way, because you are an advanced user. But I can't include all the details about using the database, because it will fall outside this thread, and I can't recommended for all users to download the VBIOS from there, because someone might download the wrong file. This way, by adding a warning about it and telling users to use the VBIOS from card/manufacturer, I can address both novices and advanced users.

Maybe the technician you talked was unaware of the issue. But in the thread I linked above you will find all the details. I had already offered him an updated GOP and the bug was still there. Later I discovered that Asus had a fix all along. After a request, that was ported to his mainboard. So it is Asus task to fix it, yours is to ask it the right way. But anyway, there is already a thread to discuss about this bug, so please write in there if you have anything more to add.

Zitat von lordkag im Beitrag #36

---

---