Overclock.net - An Overclocking Community - Reply to Topic
Thread: GIGABYTE GTX 9xx H2O/AIR BIOS Tweaking ?(ô?ô)? Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
07-13-2020 12:30 AM
EndUser2015
Back for some fun ... I think ...

Well my monitors finally died at home and I looking to get one of those super fine samsung g9 displays ... issue is my DP version needs a bump so i can get the full refresh rate of the monitor ... as I am using a custom bios i cannot just use the nvidia tool now ... I saved my old bios's before taking the one provided ... but i want to do a sanity check before i flash back ... unless i can get a new copy of the existing one i got with the new DP firmware loaded ... my 980ti card is still kicking and i have a 8700k with a gtx 1080 ready to go but i still need to de-lid it and do the liquid metal mod so for now i need my 980 ti to step up before i retire it down media room gaming rig duty and move over my water cooling setup so i can OC the 8700k ....

Would appreciate any help on getting the 980 ti bios up'd to support the new display port protocols

Thanks
07-10-2020 02:33 PM
Frosted racquet
Quote: Originally Posted by Laithan View Post
Did you also try switching to a different display port output at when there is no post? I have seen where it can be picky which one is used when all are not populated.
I've tried all DisplayPorts, and they exhibited the same issue of no post screen. Just to be clear, I had the "blank screens on boot until the OS loads" issue.

If I have any new findings I'll post an update in this thread.
07-10-2020 02:18 PM
Laithan
Quote: Originally Posted by Frosted racquet View Post
Unfortunately I'm still having no video @ post. The sequence of events was:
-with stock DP BIOS (before flashing MUMOD), ran the nVidia tool and updated the FW. That fixed no video @ post.
-flashed MUMOD DP BIOS, now no video @ post. Ran the tool again, it says I need to update DisplayPort FW (again), but now it errors out.

As for the DP BIOS and Chrome issue, all is fixed. DP BIOS is now applied, so now I have both BIOSes modded. Games run well too. I was worried that I didn't mix up the BIOS flash but all is well.

Chrome issue was related to GPU Shader cache. Deleted it and now it works with HW acceleration.
Did you also try switching to a different display port output at when there is no post? I have seen where it can be picky which one is used when all are not populated.

I may have had to revert to the STOCK BIOS to run the tool also.. I don't remember it was so long ago. Variances could be which display is being used at the time of the update or possibly if the MUMOD BIOS was newer than your original BIOS. For example they shipped with the F3 BIOS, and have since released an F4 BIOS (if yours isn't based on F10). If you ran the tool and it worked with the F3 BIOS but the modified BIOS is now the F4 BIOS, maybe that throws something off. So you MIGHT have to flash the STOCK F4 BIOS, update the display port firmware with the F4 STOCK BIOS and THEN flash the modified F4 BIOS. It might be worth a try.

https://forums.guru3d.com/threads/nv...splays.421406/
https://www.reddit.com/r/nvidia/comm...rmware_update/
https://www.pcgamer.com/nvidia-relea...-hdr-monitors/


"Without the update, systems that are connected to a DisplayPort 1.3 / 1.4 monitor could experience blank screens on boot until the OS loads, or could experience a hang on boot.
The NVIDIA Firmware Updater will detect whether the firmware update is needed, and if needed, will give the user the option to update it.
If you are currently experiencing a blank screen or hang on boot with a DP 1.3 or 1.4 monitor, please try one of the following workarounds in order to run the tool:

Boot using DVI or HDMI
Boot using a different monitor
Change boot mode from UEFI to Legacy; or Legacy to UEFI.
Boot using an alternate graphics source (secondary or integrated graphics card)
07-10-2020 10:27 AM
Frosted racquet Hopefully a final update. The nVidia tool for updating DisplayPort firmware seems to try and reapply/re-flash the BIOS as well when updating the DisplayPort FW and likely fails because the BIOS is unsigned.
I've switched to HDMI, since it's the easiest solution for no video @ post.

Thanks again for replying.
07-10-2020 05:38 AM
Frosted racquet
Quote: Originally Posted by Laithan View Post
Cool, making progress
Are you still having the issue not seeing video @ post?
Unfortunately I'm still having no video @ post. The sequence of events was:
-with stock DP BIOS (before flashing MUMOD), ran the nVidia tool and updated the FW. That fixed no video @ post.
-flashed MUMOD DP BIOS, now no video @ post. Ran the tool again, it says I need to update DisplayPort FW (again), but now it errors out.

As for the DP BIOS and Chrome issue, all is fixed. DP BIOS is now applied, so now I have both BIOSes modded. Games run well too. I was worried that I didn't mix up the BIOS flash but all is well.

Chrome issue was related to GPU Shader cache. Deleted it and now it works with HW acceleration.
07-09-2020 04:39 PM
Laithan
Quote: Originally Posted by Frosted racquet View Post
Update: flashed the DP BIOS, verified my clock settings/power limits (or lack thereof) and all is well in that department. But now the DisplayPort firmware is out of date again (didn't know the BIOS file contains DisplayPort FW as well). Running the nVidia DP firmware update tool results in an error this time. Is there a way to incorporate the latest DisplayPort FW into the modified BIOS and flashing it with nvflash?

Also, turning off hardware acceleration in Chrome is a workaround for my YouTube issues. Haven't figured out why exactly it's a problem now all of a sudden.
Cool, making progress
Are you still having the issue not seeing video @ post?

May want to double check the DD and DP again to make sure.

The BIOS' are just copies of the stock BIOS' and I didn't modify anything other than power, voltage and CLK values for the most part. AFAIK the DP firmware was not included otherwise this seperate download would not be required (my 980Ti's are gone now so I cannot check this).

Does it play games and run benchmarks ok? Just Chrome? If not ONLY Chrome I might try DDU first and then reload the latest drivers.

If ONLY with Chrome, zap it and do a fresh install.

Also, make yourself a bootable Win10 (free and easy to make) so you can boot into a fresh O/S, load the drivers and see what happens.


Quote: Originally Posted by Frosted racquet View Post

Ah, I see the problem. Since I'm only using DisplayPort, there's no guaranteed way to switch to a DD BIOS (the only one I modified before) since the DD BIOS DisplayPort is actually a "Schrodinger cat" situation since it can be both a DD and DP switch. Currently, I'm being forced to boot a DP BIOS regardless of which DisplayPort I plug the monitor in. I will flash the MUMOD DP BIOS and see how it goes.
If you use the display ports all the way on the end (the ones not active in the DD BIOS) it should force the DP BIOS so you know for sure it is running DP and not the DD slot with a DP BIOS. I do think that a single display port would most likely use a DP BIOS but it might depend on which of the 3 ports are used. I want to mention that sometimes the GPU may force you to use a different display port if they are not all populated. You can test yourself, if you get no video unplug and try a different port one by one in those situations should no video occur, same symptom but different reason. It's not clearly documented which combinations require you to use which ports since there are 3 of them you just have to experiment. I always had 3 display ports and HDMI populated at the same time so I didn't have any unused.

The biggest thing is to ensure that you are not using the DD slot with a DP BIOS. The only way to make sure which one is loaded is to use the ports that are exclusive to force it to load. Also I wonder if you need to run the update on EACH display port.. I wouldn't think so but maybe..

For anyone following along, DP BIOS does not stand for display port. It is just a coincidence so I tried not to refer to display port as DP but I had to edit a few places lol..
07-09-2020 09:52 AM
Frosted racquet Update: flashed the DP BIOS, verified my clock settings/power limits (or lack thereof) and all is well in that department. But now the DisplayPort firmware is out of date again (didn't know the BIOS file contains DisplayPort FW as well). Running the nVidia DP firmware update tool results in an error this time. Is there a way to incorporate the latest DisplayPort FW into the modified BIOS and flashing it with nvflash?

Also, turning off hardware acceleration in Chrome is a workaround for my YouTube issues. Haven't figured out why exactly it's a problem now all of a sudden.
07-09-2020 05:53 AM
Frosted racquet Thanks for the quick and detailed reply.

Quote:
(1) BIOS values changed despite having the MUMOD BIOS flashed: It sounds to me like the BIOS you are intending to use is changing as the BIOS used is controlled by the display outputs connected @ power on. Let's theortically say (may or may not match yours, but explains how it works) that the DD BIOS was flashed with the MUMOD BIOS.. changing monitor outputs from using DVI to DP is likely going to now trigger the DP BIOS to load @ power on. The fact that you are seeing stock clocks is because that BIOS is still STOCK on that BIOS slot. You have to flash the MUMOD BIOS to both DD and DP BIOS slots if you want it to be modded regardless of which display output is used (especially if you change them often as with a projector or a VR setup). This is always confusing and a PIA for Gigabyte cards but that's how "Flex display" works.

Ah, I see the problem. Since I'm only using DisplayPort, there's no guaranteed way to switch to a DD BIOS (the only one I modified before) since the DD BIOS DisplayPort is actually a "Schrodinger cat" situation since it can be both a DD and DP switch. Currently, I'm being forced to boot a DP BIOS regardless of which DisplayPort I plug the monitor in. I will flash the MUMOD DP BIOS and see how it goes.


Quote:
(2) No video @ post when using certain outputs: This can be even further confused if by any chance the DD BIOS was flashed to the DP slot, or the DP BIOS was flashed to the DD spot. Since there is no physical switch, this happened more often than anyone wanted. If this is done wrong, some outputs will work while some others will not. This ALSO could be an issue fixed by this firmware for DP itself: https://www.nvidia.com/en-us/drivers...fi-update-x64/
This looks to have solved the issue. I seem to remember trying to run the DisplayPort FW update before when I was using a DVI connection, but the tool (I don't remember if it was the one you posted) reported that there's no update needed. Now it applied the update and I can see the POST logo.

Quote:
(3) As far as the corrupted display, this COULD be because of a very rare issue where a BIOS has been modified but the overclocking app's profile of the previous BIOS values are loaded. That probably didn't make sense, so here is what can happen and how to fix it (it is not going to be fixed by drivers). Let's say that you flash a custom BIOS to your GPU and that custom BIOS has different power, voltage, default and boost clocks than the STOCK BIOS. You configure the GPU how you want it and then you save to a profile slot. Then let's say you reverted back to the STOCK BIOS and booted into windows where the profile of the modified BIOS is now loaded. This is going to apply values to your GPU that may not match the BIOS and I have seen odd things like this happen. It is rare but it is almost always when a BIOS is changed on the same GPU installed in the system but the overclocking app's profile wasn't deleted first so it thinks it is the same GPU and applies values that are not correct for the BIOS being used.

To fix this, just boot into windows and UNINSTALL MSI AB/EVGA Precision and the MOST important thing is to REMOVE ALL SETTINGS when asked. You don't want to save anything. Then reboot and all should be fine again. Now you can just re-install the same MSI AB/EVGA PRECISION and set everything up over again. You can also manually remove the profiles but it is easy enough just to uninstall.
I uninstalled MSI AB and removed all its settings but the issue with YouTube persist. I'll keep experimenting with this, if all else fails I'll reinstall Windows.
07-08-2020 05:07 PM
Laithan
Quote: Originally Posted by Frosted racquet View Post
I'm having weird issues after buying a new monitor that connects to DisplayPort. Previously, I used a DVI-D connection with a modified DD BIOS for my Gigabyte GTX980 G1 Gaming.

Now when I connect the DisplayPort to either the DD or DP BIOS group/switch I'm getting default factory clocks and opening MSI AfterBurner confirms that I don't have my previous profiles loaded or the ability to uncap BIOS limits - GPU-z will display VRel as a perfcap.

Furthermore, Youtube seems to have gone and messed itself up too, but it was working with the new monitor before, I don't know what broke it. I can load videos but they look like a garbled mess. I tried to uninstall my drivers (newest version btw), and after rebooting I couldn't get a signal. Managed to install the driver via TeamViewer (after jumping through their annoying "Commercial use" limitations) and at least I have picture.
Plus, I don't see the POST screen, and can't enter BIOS settings...

Any help?
Hmmm... Where do I begin lol

I see different issues here:

(1) BIOS values changed despite having the MUMOD BIOS flashed: It sounds to me like the BIOS you are intending to use is changing as the BIOS used is controlled by the display outputs connected @ power on. Let's theortically say (may or may not match yours, but explains how it works) that the DD BIOS was flashed with the MUMOD BIOS.. changing monitor outputs from using DVI to DP is likely going to now trigger the DP BIOS to load @ power on. The fact that you are seeing stock clocks is because that BIOS is still STOCK on that BIOS slot. You have to flash the MUMOD BIOS to both DD and DP BIOS slots if you want it to be modded regardless of which display output is used (especially if you change them often as with a projector or a VR setup). This is always confusing and a PIA for Gigabyte cards but that's how "Flex display" works.

(2) No video @ post when using certain outputs: This can be even further confused if by any chance the DD BIOS was flashed to the DP slot, or the DP BIOS was flashed to the DD spot. Since there is no physical switch, this happened more often than anyone wanted. If this is done wrong, some outputs will work while some others will not. This ALSO could be an issue fixed by this firmware for DP itself: https://www.nvidia.com/en-us/drivers...fi-update-x64/


** Notice that DVI-D is ONLY possible using the DD BIOS? This is a good way to connect your GPU to make SURE it is loading the DD BIOS.
** Notice that the first two DP ports are ONLY possible using the DP BIOS? Using one of those ports is a good way to make SURE it is loading the DP BIOS.
You can do this and then use GPU-z to extract the BIOS and check if the DD BIOS is loaded to the DD slot and the DP BIOS is loaded to the DP spot.
Another trick to load the DP BIOS is to use a single HDMI connection (even if HDMI -> DVI adapter is used). This will always select the DP BIOS when using HDMI only.


(3) As far as the corrupted display, this COULD be because of a very rare issue where a BIOS has been modified but the overclocking app's profile of the previous BIOS values are loaded. That probably didn't make sense, so here is what can happen and how to fix it (it is not going to be fixed by drivers). Let's say that you flash a custom BIOS to your GPU and that custom BIOS has different power, voltage, default and boost clocks than the STOCK BIOS. You configure the GPU how you want it and then you save to a profile slot. Then let's say you reverted back to the STOCK BIOS and booted into windows where the profile of the modified BIOS is now loaded. This is going to apply values to your GPU that may not match the BIOS and I have seen odd things like this happen. It is rare but it is almost always when a BIOS is changed on the same GPU installed in the system but the overclocking app's profile wasn't deleted first so it thinks it is the same GPU and applies values that are not correct for the BIOS being used.

To fix this, just boot into windows and UNINSTALL MSI AB/EVGA Precision and the MOST important thing is to REMOVE ALL SETTINGS when asked. You don't want to save anything. Then reboot and all should be fine again. Now you can just re-install the same MSI AB/EVGA PRECISION and set everything up over again. You can also manually remove the profiles but it is easy enough just to uninstall.

Let me know how it goes.
07-08-2020 02:24 PM
Frosted racquet I'm having weird issues after buying a new monitor that connects to DisplayPort. Previously, I used a DVI-D connection with a modified DD BIOS for my Gigabyte GTX980 G1 Gaming.

Now when I connect the DisplayPort to either the DD or DP BIOS group/switch I'm getting default factory clocks and opening MSI AfterBurner confirms that I don't have my previous profiles loaded or the ability to uncap BIOS limits - GPU-z will display VRel as a perfcap.

Furthermore, Youtube seems to have gone and messed itself up too, but it was working with the new monitor before, I don't know what broke it. I can load videos but they look like a garbled mess. I tried to uninstall my drivers (newest version btw), and after rebooting I couldn't get a signal. Managed to install the driver via TeamViewer (after jumping through their annoying "Commercial use" limitations) and at least I have picture.
Plus, I don't see the POST screen, and can't enter BIOS settings...

Any help?
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off