JadeRover

Hello, yes I think I know what the problem is. You 8770W with dreamcolor screen connects directly to the GPU in the MXM slot meaning that the GPU must be configured to have eDP output to the dreamcolor screen (dreamcolor LCD uses LVDS but all laptops from that era with DC screen use an internal eDP to LVDS converter -> GPU needs eDP output to be set on the correct lane for it to work) Your 8770w had eDP on lane "D" of the MXM slot *, the signal then goes to the LCD connector, then to the eDP to LVDS converter and finally to the LVDS DC screen. See schematic of your 8770w, eDP are on the last 10 pins of the LCD connector, signal are named DPDx_Dx = DP_D The issue is that the zbook 17 g3 you got the card from uses eDP on lane "C" ! So the card is configured to output eDP on the wrong channel compared to your 8770w = no display. (I know this from my first hand experience getting MXM cards to work on my 17 g3 and getting no display as well because of eDP lane mismatch) The fix is simple, you need to flash a vbios that has the correct display configuration to the card. This dell vbios has eDP on DP_D (as it is from a precision 7710 that has eDP on DP_D): https://www.techpowerup.com/vgabios/221521/221521 They are several ways to flash the correct vbios. I recommend getting a CH341a programmer with 1.8v adapter, it costs 10 dollars max. Good luck and ask away if you have more questions * This is good news as this is the standard for MXM gpus, you could even upgrade to an RTX card by x-vision or other brands that come only with a vbios configured with eDP on DP_D !

BTW what does gpu z show? Because it communicates with the Nvidia driver to get the clock values. Maybe I messed up (again) and have the wrong algorithm to read/write clocks. It would be nice to see if gpu z shows my custom clocks ore the clocks you are seeing in benchmark. Thanks.

OK that is unfortunate. No clue why memory clocks work on p106m but not on p6 as the actual hex values are the same. Same thing for the core clocks on p6. Maybe 2000mhz is too high, we can try 1800 mhz next. Also you can try a custom vbios made with v1.1 on p3200 and p4200 as clock values should now be saved correctly.

Here is an updated version (core clocks are in the correct format). Set to 2000Mhz (again vrel limit before seing this value) You said the memory was good, it boosted to 2000/4000Mhz ? Because checking again my custom memory clock was not in the expected format, strange that it still worked. I change the memory clock in this _1 version. It is in the expected format in version _1. In version _2 it is in the same format as my last p106m vbios. if you can give both a try that would be good. p106m_OC_checked_1.bin p106m_OC_checked_2.bin

Interesting. I might add these IDs but as a read only to see what card is recognized, especially for P6 and other cards that have a non standard clock layout and need different calculations in order to display the correct values.

It should normally. I haven't tested it. When you say 8 bit checksum, you mean the header checksum ? Or the last 8 bits of the 32bit body checksum ?

Yep, base clock is now 1230Mhz and boost is now 2000Mhz (you will hit vrel limit before seing this value) Memory is now at 4000Mhz target power is 100w, limit power is 120w and power slider is enabled. Checksum was fixed as well. You can try this @ssj92 teslap6_OC_power_mod.rom

New version : Release v1.1 | Nvidia-vBIOS-Clock-Power-Tweaker · JadeRover/Nvidia-vBIOS-Clock-Power-Tweaker This one should correctly save the clock values, you can give it a try @ssj92. I made sure it would work for the p3200 and p4200, I tested some roms on techpowerup. (clocks are in the correct 2x2 byte format).

What does the GPU-Z windows show ?

Ok, because the v1.0 will not work i made a mistake for the clock calculations

Ok, only using the power bios ?

Yes, there is a certification issue, might be possible to bypass using OMGvflash by veil for turing cards, any newer cards will not work unfortunately. Pascal works. Even with a hardware flasher it will not work, card will refuse to boot and show error 43.

Ok, I really don't have high hopes for the clock values as I got them by dividing the 4 bytes of hex by 32768. As it turns out you have to substract 16384 and then multiply by 2... on each 2 byte chunk of the 4 byte clock value ! See here : https://rog-forum.asus.com/t5/rog-gaming-notebooks/laptop-pascal-vbios-unlocks-quot-wip-quot/td-p/658321 I'll make a version only with power editing that way you can test that out (as it should work fingers crossed), while I fix the clock editing. Here is this [POWER ONLY] version 1.0 : Release v1.0 | [POWER ONLY] Nvidia-vBIOS-Clock-Power-Tweaker · JadeRover/Nvidia-vBIOS-Clock-Power-Tweaker

Also very important, version 1.0 of my program might be saving the wrong clock values !! I will be making some actual vbios tests on my p3000 in my m6700 this week end. In the meantine no one should try to flash a custom vbios made from my program.

Hello, this is P106m card vbios ? Manual looking at the clock table, it has only one core value of 1290Mhz and all the others are null (FF). For the memory clock it is 1500Mhz (in afterburner clock dual rank mode). Also the power table is a desktop type with 3 values (not supported by my program). Those I read from your vbios are all at 100w. I can make you a custom vbios to try if you want. I made one quickly, boost to 1910Mhz (I changed all the instances of 1290Mhz to 1910Mhz) and mem up to 2000 Mhz you can give it a try, the checksum was fixed as well. You will probably hit a vrel limit and be around the 1850Mhz mark p106m_vbios_checked.rom