Nvidia-vBIOS-Clock-Power-Tweaker - PASCAL TESTING NEEDED !

[JadeRover]

14 hours ago, Khenglish said:

So for all 3 vbios that work, all 3 can OC memory to 8GHz

 

OK, so you set 4004mhz on vram and that allowed the card to oc the ram? 

 

I've done more testing on the downclocking of the card and I noticed that setting lower clocks just on the core clock list results in downclock + only downclocking on the limit clocks found in the vp profiles also results in downclock (both are independent). 

 

So that means that card reads both core clock list + vp profiles to set it's clock value. 

 

On my p4000 if I left the limit clock untouched and OC core clocks in the clock list, card would not OC, I also had to raise vp profile limits clocks. My program does both but it appears that this isn't enough for p5200, there must be another hidden "max" limit clock value, in our case 1708mhz. 

 

Now I will attempt to replace the p5200 vp section with the sections of GTX cards and p4000 to see if that resolves the issue. 

 

EDIT : Well I am starting to fear that the 1708Mhz is baked in deeper into the vbios or the driver as even when using a GTX Virtual P state table or parts of VP table of the MSI P5200 vbios I still hit the 1708Mhz wall...

 

I still have some hope as I am pretty sure the MSI vbios does make the card boost to 1911Mhz (userbenchmark scores) as well as the HP zvr backpack vbios.

 

+ Some guy in china managed to boost the P3200 & P4200 to 1900Mhz & 9Ghz vram : P3200 : Search & P4200 : Search

 

The MSI vbios flat out refuses to boot on my system. Pasting parts from the performance section into the working "dell" vbios results in no boot as well

[Khenglish]

Yeah anything 4004 or higher sets 8GHz ram as long as a I don't touch the base or boost clocks. 6GHz if I touch those.

 

I also tried again to mod the P4000 device ID to be a P5200. That failed again. There seems to be some security check beyond checksums to check the device ID.