[WIP] Nvidia-vBIOS-Clock-Power-Tweaker

[JadeRover]

Hello everyone !

 

linked is my very very very early version of a pascal to ada lovelace vbios editor.

 

as of right now it can only read bioses !!

 

Here is the link, the details are explained in the repository

https://github.com/JadeRover/Nvidia-vBIOS-Clock-Power-Tweaker

 

Pictures :

 

[ssj92]

6 hours ago, JadeRover said:

Hello everyone !

 

linked is my very very very early version of a pascal to ada lovelace vbios editor.

 

as of right now it can only read bioses !!

 

Here is the link, the details are explained in the repository

https://github.com/JadeRover/Nvidia-vBIOS-Clock-Power-Tweaker

 

Pictures :

 

Super excited to try this in the future. my rtx 5000 is 90w. t1000 is 50w. 

[ifrit05]

Kinda works on Linux, have to comment out line 25. Great work so far.

[JadeRover]

2 hours ago, ifrit05 said:

Kinda works on Linux, have to comment out line 25. Great work so far.

Yes that bitmap icon is killing me! It prevented me from exporting to a single exe file 😞 I would get an error

[JadeRover]

Updated the repository -> version 0.3

 

Now turing cards read properly and the standalone windows exe works.

 

@ssj92 You can now properly read the clock values of your T1000 and RTX5000

[SuperMG]

Hello. It really needs the display table views.

 

A/B/C/D/E, very important for eDP users and for users who want to use DVI/DP externally 

[JadeRover]

Yes, agreed, that info would be crucial.

I had started a draft that would show the display table, all the info relative to "dispkay outputs" is stored in the DCB table :

 

see here https://nvidia.github.io/open-gpu-doc/DCB/DCB-4.x-Specification.html

 

Luckily this table has not been updated for a while so it should be compatible with all the bios from the Pascal-Lovelace era.

 

If you want to help out you can contribute to the github.

What we need is algorithms going through all the table entries and parsing the data in a user friendly format showing :

DP_X = such interface + i2c controls ? (basically if it supports eDP) + enabled ?

[SuperMG]

8 minutes ago, JadeRover said:

Yes, agreed, that info would be crucial.

I had started a draft that would show the display table, all the info relative to "dispkay outputs" is stored in the DCB table :

 

see here https://nvidia.github.io/open-gpu-doc/DCB/DCB-4.x-Specification.html

 

Luckily this table has not been updated for a while so it should be compatible with all the bios from the Pascal-Lovelace era.

 

If you want to help out you can contribute to the github.

What we need is algorithms going through all the table entries and parsing the data in a user friendly format showing :

DP_X = such interface + i2c controls ? (basically if it supports eDP) + enabled ?

I only understand PHP, JS, Node.js, web development. Very hard for me to make random hex into readable data. But yes we need to know what video output is for A/B/C/D/E (type and if it's enabled or not).

 

With GPU-Z we can read them but we don't know which is A/B/C/D...

 

I would pay 20€ to someone who can bypass the eDP checks (if enabled or disabled) when the drivers loads (for 4080 and 4090 MXM cards)

[Tenoroon]

My 115w 2070S in my P870TM has been killing me! I never was able to figure out how to up the power limit because I know it can run at 200w with the dual vapor chamber heatsink. If this works in the future, this would be wonderful!

I am willing to do any testing if needed, just let me know. I also have a 1.8v vBIOS programmer if any crazy stuff needs to happen.

[ssj92]

On 5/3/2026 at 8:27 AM, JadeRover said:

Yes, agreed, that info would be crucial.

I had started a draft that would show the display table, all the info relative to "dispkay outputs" is stored in the DCB table :

 

see here https://nvidia.github.io/open-gpu-doc/DCB/DCB-4.x-Specification.html

 

Luckily this table has not been updated for a while so it should be compatible with all the bios from the Pascal-Lovelace era.

 

If you want to help out you can contribute to the github.

What we need is algorithms going through all the table entries and parsing the data in a user friendly format showing :

DP_X = such interface + i2c controls ? (basically if it supports eDP) + enabled ?

Is there anyway to change the outputs in vBIOS?

 

Example changing eDP from DP_C to DP_D etc? Assuming the physical card/connections are supported of course. 

[JadeRover]

5 hours ago, ssj92 said:

Is there anyway to change the outputs in vBIOS?

 

Example changing eDP from DP_C to DP_D etc? Assuming the physical card/connections are supported of course. 

 

Hello, yes there is a way to do so. The mac rumor vbios have different output table from stock vbios + documentation exists on the "DCB" table (display table) of nvidia vbios, that's the next step of the program is to read and edit these outputs.

 

Unfortunately when testing with an RTX3000 gpu, my custom vbios did not work, the card would be bricked with error 43.

 

Moreover, changing 2 adjacent bytes in the bios by doing +1 and -1 to the hex value (so that checksum is the same) results in a brick as well for this Turing card = meaning that Turing has more security checks then Pascal and any custom vbios bricks the card (also this was documented on mac rumors).

 

AKA turing custom vbios won't be possible 😞

[JadeRover]

Version 1.0 is released : 

Release v1.0 | Nvidia-vBIOS-Clock-Power-Tweaker · JadeRover/Nvidia-vBIOS-Clock-Power-Tweaker

 

Editing and saving vbios is possible + checksum is fixed.

 

Therefore I need volunteers with an external flasher to test on pascal cards these modifications !

[SuperMG]

7 minutes ago, JadeRover said:

 

Hello, yes there is a way to do so. The mac rumor vbios have different output table from stock vbios + documentation exists on the "DCB" table (display table) of nvidia vbios, that's the next step of the program is to read and edit these outputs.

 

Unfortunately when testing with an RTX3000 gpu, my custom vbios did not work, the card would be bricked with error 43.

 

Moreover, changing 2 adjacent bytes in the bios by doing +1 and -1 to the hex value (so that checksum is the same) results in a brick as well for this Turing card = meaning that Turing has more security checks then Pascal and any custom vbios bricks the card (also this was documented on mac rumors).

 

AKA turing custom vbios won't be possible 😞

But could it be possible for the software to sort the Display tables? To know which is A, B, C, D and E?

[JadeRover]

Yes, the display table has tons of info here is a snippet (non parsed data):

 

 

Highlighted is the entire display table, notice this repeating pattern of 6 lines lines 5F10 and 5F60 starting with header "60". These are the DP_X display entries from A to F