Zitat von rootuser123 im Beitrag #135

---

I think the BIOS chip might be too small to fit an additional GOP Driver.

---

@zocker
Sure, blame it on me. In the meantime, check the first two posts (they are linked), then read your first post. Is the procedure not written in there, are any of your questions not covered in there, am I the one who lucks the manners? I may not help as much as others here, but there are a few who have obtained my help without been forced to give a single "pretty please". The difference between me and others is that I have low tolerance for those who abuse my help with tons of unrelated or easy answerable questions, I haze zero tolerance for those who post for the first time without reading the first post(s) and the rules. I won't go as far as other forums that instruct "use search option", because a search might give different results based on different keywords. I believe that if you can't get an answer from first or last posts, you are entitled to write your question(s). Now, if you want to try this again (after reading first and second post), we can forget this ever happened. But if you want to show your character and close your account, then BOO HOO! I hope I'll be able to sleep tonight.

@rootuser123
That information is on the second post. But you wanted to help, not to ask for help, so there is no problem with that. As a side note, I won't recommend going with that old version for pre-Maxwell. NVFlash 5.19x should work just as well, the issue is in 5.2xx versions. However, proper support for Win10 was added in 5.2xx, so users should test all the available options, starting with the last one.

@d4v1d3
Was it an error in GOPupd or ATIFlash? Was the error on the screen or the program just closed? Your file is not attached, compress it before uploading or use a public host and post the link. I believe your card has a 128KB chip and enough space for GOP, the only problem would be the presence of a microcode. But GOPupd will inform you of that, plus I need the VBIOS file to check on my own.

@lordkag
After some tests, I solved the problem of start the both programs. I added the GOP, but the bios reached a size of 120 KB instead of 128 KB; I think that is not good for the flash. What is the problem of the presence of microcode? Thank you.

The final size is not important, it just needs to be smaller or equal to chip size. That padding will be discarded anyway by the flasher, but if it makes you feel better, just add padding to equal the dump size. But you do this on your own risk, I'm not responsible for any change you make to the updated file. Your VBIOS has no presence of a microcode, nothing you should worry about.

Zitat von lordkag im Beitrag #139

---

The final size is not important, it just needs to be smaller or equal to chip size. That padding will be discarded anyway by the flasher, but if it makes you feel better, just add padding to equal the dump size. But you do this on your own risk, I'm not responsible for any change you make to the updated file. Your VBIOS has no presence of a microcode, nothing you should worry about.

---

The .BAT file is working fine on my system. Are you sure you have used the right way ?

Anyway, here is your updated .ROM file

Wow Superrr Thanks...

@lordkag
I flashed the bios modified (120 Kb) without problem. Now the Ultra Fast Boot works. Thank you very much

@tecnics

You probably did something wrong, as I have no problem in running it on Win10. It is not my daily OS, but I tried with numerous samples and test cases since RTM was released.



My little guess is you double clicked on GOPupd.bat instead of doing what it is written on first post, to drop the VBIOS on GOPupd.bat. I cannot account for all the extensions that OEM use, dropping the file on GOPupd.bat is the only way I know what file to process, not to mention that this way I can bulk test many files at once.

@d4v1d3

Thank you for the feedback. If I'm not mistaken, it is the first AMD report. More than that, it is on a card that is labelled as incompatible, if you were to ask AMD and other manufacturers.

I was semi successful in enabling GOP on my 2 GTX 680s(GK104). Patched ROMs with GK1xx GOP(option 4) and flashed. Managed to boot with CSM disabled and didn't get the usual message that my GPUs were not UEFI capable.
But after a couple of reboots my 1440p monitor connected via displayport started to boot in Windows 10 at 1080p, display properties showed that was the max resolution available, there was no 1440p option. At first it was stacked at 1080p avery other boot but after some tries it was stuck continuously at 1080p max. Enabled CSM and problem persisted, reverted back to the unpatched roms still the same. After cutting power to the motherboard, CMOS reset and reapplying my BIOS settings, the monitor was recognized as 1440p.
Can't exclude that it could be a bug of my MB's BIOS.
Attached is a zipped file containing both the unpatched and the patched rom.
Also attached is a GTX650 ROM that is factory UEFI enabled.

I see no issue in the updated file. As a rule of thumb, it is recommended to shutdown the system after the flash is successful. For Win8.x/Win10 it is also recommended to restart the system, as this is the way to fully reload the OS like shutdown was for Win7. For UEFI systems (basically anyone who comes here), you could also start the system once with Fast Boot disabled. I know this is the opposite of what you wanted, but you need to let the system to acknowledge the new hardware or firmware before switching to Fast Boot. Lastly, the CMOS reset is always recommended when you see the BIOS going crazy.

If the issue will return, write here and I will provide some older versions of GK1xx GOP, just to rule out any problems in the last version.

@lordkag
Many shutdowns (cold shutdowns too) and reboots were done, the only thing I didn't test is a CMOS reset with the GOP enabled and checking if the problem persists also with a DVI connection. I also tried unpluging and repluging the monitor and cutting its power in hopes it would be correctly regognized. After some reboots sometimes the problem would fix itself and the max resolution would be recognized but eventually it got stuck at 1080p.
Will try again this weekend when I have some free time and see if I can get it to work, thankfully reflashing is quite painless. I will also try if the problem appears in Windows 8.1 too.
Any suggestions for something to check inside windows, any settings?

Are you saying the problem is still there after a CMOS reset? How about if you boot with CSM disabled and Fast Boot also disabled? I'm not sure if Windows is at blame, but I remember reading at ROG forums and at Nvidia driver releases about monitor issues. I suspect you don't have a different monitor laying around, so investigating the driver route is the only available option.

Zitat von lordkag im Beitrag #148

---

Are you saying the problem is still there after a CMOS reset? How about if you boot with CSM disabled and Fast Boot also disabled? I'm not sure if Windows is at blame, but I remember reading at ROG forums and at Nvidia driver releases about monitor issues. I suspect you don't have a different monitor laying around, so investigating the driver route is the only available option.

---

Reflashed the GOP ROM and tested my PC again. Did a lot of restarts(cold ones too), changed BIOS settings and everything worked OK for most of the day.
After shutdown for 3 hours and starting up, the problem appeared again. My monitor was recognized as 1080P(Ultra HD, HD,SD section) and 1050P(PC section), AFAIK MonitorInfoView correctly recognized my monitor and all its capabilities (1440P).

- Changed to Windows 8.1 which had also an older NVIDIA driver and the problem persisted.
- The problem doesn't affect the DVI port only DisplayPort.
- Changing any display related settings(boot image, show ROM) or disabling fast boot/enabling CSM in BIOS doesn't fix the problem.
- Forcing the 1440P resolution by creating a custom resolution, sends a downscaled 1440P to 1080P resolution to the monitor.
- If you go to BIOS via the UEFI settings option of Windows 10 and then exit to Windows, then the problem will go away for that Windows session, it will come back next boot/restart.
- The problem persists if you flash the original ROM until you fix it via a BIOS reset or going to BIOS via the UEFI settings option of Windows 10.

Correct if I am wrong, doesn't the GPU ROM contain info regarding the ports of the graphics card and flashing a ROM from another cards with different ports could possibly disable a port.
Could the EFI GOP that I am flashing having different info for the ports causing my DisplayPort malfunctioning?
Or could it be a problem with my MB's BIOS?

I am back now to the original ROM, everything works OK and probably will stay here as I don't want to test my luck with a bricked card from a failed flash.
Thanks for your work.