slovak_killer
Anyone that flashed KP bios and also update to KP firmware through PX1 firmware update ?

Just asking if this won't brick the BIOS on my card slovak did you see the boost? it's 1920 ours are 1800...mine is Stock Air and not modded, maybe after flashing it will not give image and i don't recall if there's a way of reverting this situation, i think that connecting another card...but not sure.

Did u update the firmware? I testing the 480w now without the update... And doesnt pull near what the strix does... Ill test the 520w

Then will try with the firmware updated

slovak_killer
Anyone that flashed KP bios and also update to KP firmware through PX1 firmware update ?

PX1 did not prompt me to update the firmware.  
 

andressergio
 
Awesome man the first one to try congrats 
 
Did you try anything else than furmark?
 
Cheers, Sergio!

I played Doom Eternal for a couple of minutes and saw a bit lower consumption, but still above 450W. 

If your card can normally hold the stock boost clocks that the Kingpin has (1920 according to the product page), you will be able to at least boot this vbios - with bugs
Stock w/ boost lock enable sends mine to 2010 mhz @ 1075 mv, so it may be a good idea to see if your card can do that before flashing.
 
edit:

• The voltage control is broken, I've moved it around but it doesn't seem to change. However, it seems that if you touch the power target, the voltage slider won't do anything, but the card behaves like you've given it the full voltage slider. 
• fans is broke af 
• power reporting in PX1 (the W readout next to power %) always shows 0w

 

andressergio
I just asked for it and they told me it's garbage, we need to see if the RTX 3090 KINGPIN BIOS works but kinda scared to brick my card, my FTW3 has a BOOST of 1395/1800 and the KPE has 1395/1920, I know I benched mine till 1950 but not sure if flashing these new BIOS will make any difference or just brick it.
 
Cheers, Sergio!

Doesn't brick the FTW3. Still power limited shown with Afterburner at 400W.

kvswim
 
I played Doom Eternal for a couple of minutes and saw a bit lower consumption, but still above 450W. 

If your card can normally hold the stock boost clocks that the Kingpin has (1920 according to the product page), you will be able to at least boot this vbios - with the bugs I've listed already.
Stock w/ boost lock enable sends mine to 2010 mhz @ 1075 mv, so it may be a good idea to see if your card can do that before flashing.
The voltage control is broken, I've moved it around but it doesn't seem to change. However, it seems that if you touch the power target, the voltage slider won't do anything, but the card behaves like you've given it the full voltage slider. 

Thanks for your tests, yes mine can handle STABLE XC3 +85/ +1000 and STABLE XOC +150/ +1250 (with the ups and downs you know already) but if all controls are so screwed and fans don't work like they should it's just asking for problems inmo.
 
Cheers, Sergio.
 
 

so updating firmware, on px1, when completed and u hit close, it opens again
 
i have no idea if it's trying to flash 3 different bios' that originated with the kingpin
 
i did 2 anyway, cancelling the third popup and rebooting now

What’s the deal with updating firmware? I wasn’t even aware that was something you could do.

andressergio

kvswim
 
I played Doom Eternal for a couple of minutes and saw a bit lower consumption, but still above 450W. 

If your card can normally hold the stock boost clocks that the Kingpin has (1920 according to the product page), you will be able to at least boot this vbios - with the bugs I've listed already.
Stock w/ boost lock enable sends mine to 2010 mhz @ 1075 mv, so it may be a good idea to see if your card can do that before flashing.
The voltage control is broken, I've moved it around but it doesn't seem to change. However, it seems that if you touch the power target, the voltage slider won't do anything, but the card behaves like you've given it the full voltage slider. 

Thanks for your tests, yes mine can handle STABLE XC3 +85/ +1000 and STABLE XOC +150/ +1250 (with the ups and downs you know already) but if all controls are so screwed and fans don't work like they should it's just asking for problems inmo.
 
Cheers, Sergio.
 
 

Simply because of the fan problems, I'm going back to the FTW3 XOC bios after I'm done playing around; I may flash back to it once I get a block for my card. But I had to test, for science! I'll be playing around with 3dmark for a little while, see if I can get some PBs with the extra current.

slovak_killer

drunknfoo
I dunno after reboot its aaking to update firmware, testing now with AB

so your firmware didnt update and u cant open px1 ?

Says complete and rebooted, tried again rebooting and same

Ill reinstall px1, toggle drivers on n off n see what happens... Either way it is safe to attempt on ur end from what i can see

andressergio

arestavo
Doesn't brick the FTW3. Still power limited shown with Afterburner at 400W.

Thanks for your reply arestavo! So it's worse than any of the BIOS we tried?

I'd say it's about on par with the XOC. The baseclock is higher, but the overall power draw is the same and I still get Power Limit. I see it at 400W (not all the time) all the way to 450W, which seems to be the max average of this card.
 
The first fan seems to be capped at 2000 RPM, likely because that one is supposed to be for the pump? Two and three show 3000 (or so) RPM when at 100% though.

slovak_killer
ok tested KP bios and firmware, Please dont use most recent PX1 when u have flashed any KP bios, it will prompt u to update firmware which will "brick" your card (theres way to recover though). So in short if u have flashed any KP bios use PX1 version 1.1.1 not the newest one.

Wonder why yours brick and mine didnt.... ****

slovak_killer
ok tested KP bios and firmware, Please dont use most recent PX1 when u have flashed any KP bios, it will prompt u to update firmware which will "brick" your card (theres way to recover though). So in short if u have flashed any KP bios use PX1 version 1.1.1 not the newest one.

Out of curiosity i went back to the beta updated that firmware (which i assume was the 2nd original) reinstalled 520w and trying this over again...


But the firmware updated 520w does appear to be functioing for my ftw and not incorrectly throttling the power based on tdp flags... Reapplying firmware and rebooting.... Again just to confirm

slovak_killer

drunknfoo

slovak_killer
ok tested KP bios and firmware, Please dont use most recent PX1 when u have flashed any KP bios, it will prompt u to update firmware which will "brick" your card (theres way to recover though). So in short if u have flashed any KP bios use PX1 version 1.1.1 not the newest one.

Wonder why yours brick and mine didnt.... ****

check if your 8pin leds are red or if your fans are at 100% nonstop, if yes u have bricked firmware
update : well if you already flashed back XOC bios and updated firmware with that bios u "unbricked" your card

Yup second time brick mode... this is wierd...
cause the first flash was from the strix bios and firmware x2 applied before reboot and no brick

Now flashing from beta to 520 and 1 firmware update attemp reboot brick

Kylearan

slovak_killer

Kylearan
I think I figured out what's going on with the power balancing on these cards.  
This may have absolutely nothing to do with the current Bios issues, or perhaps it does have something to do with it, but here is what I can work out so far.
 
The Current Sense chip controls all of the power regulation between the wattage rails, including from itself.  This is called PP Source Input Power, where PP stands for Power Plane.  It is NOT "PCI Express Slot power".
 
If any power rail has a higher resistance shunt value than the Current Sense shunt, that power rail, or the one with the highest resistance, will control via its shunt, the total amount of TDP allowed with respect to that power rail's absolute maximum limit.  The easiest example here is PCI Express.  Founder's Edition cards have an absolute 79.9W cap on the PCIE slot.  eVGA seems to either have 75W or 85W cap.  The FE card will never use a value this high---at 400W TDP and 114% power limit (from 350W To 400W), the PCIE slot is around 65 to 68W.  But it's master power limit is 79W.
If the Slot has the highest shunt resistance, the total board power cap will be reached when PCIE Slot reaches its maximum allowed Vbios value.  For example, on a FE, you would probably see 160W/160W/80W in GPU-Z (this may vary depending on how the 8 pins are shunted, but you get the picture).  A 15 mOhm stacked shunt (3.75 mOhms total shunt resistance) on PCIE slot and 10 mOhms stacked shunt on all other shunts, will allow you 466 watts of GPU power before PCIE Slot reaches 79 watts, in this case.
 
The Chip Master power limit is 300 watts.  At 400W TDP, it will never pull this limit.
 
MVDDC (FBVDD) is unknown.
 
The Current Sense shunt itself is a special case.  It seems that if the current sensing shunt is a higher resistance than all other shunts (or at least the 8 pin plugs and PCIE Slot shunts!), the resistance of the Current Sense resistor is used for "Normalized TDP" and the 8 pins and PCIE slot power draw is completely rearranged, by having the 8 pin#1 rise up to its max internal TDP value (170W on FE cards), which will be the limiting factor, and reducing the power draw of 8 pin#2 and PCIE slot, in such a way so that 8 pin#1 + 8 pin#2 + PCIE will total up to 350 watts.  If your power TDP slider is at 114%, and you are pulling 400W Total Board Power in GPU-Z (even if you're drawing more via shunt mods), the "Normalized" TDP will show up as 114%, but base TDP will be around 100%.  A shunt modded card will still of course draw more power, but will be limited in TDP To the current sense shunt (Normalized TDP!) rather than the TDP of the 8 pin power plugs and PCIE slot (regular TDP!!!)
 
If the current sense shunt is equal to or lower in resistance than the 8 pins, then the 8 pins will report balanced power, and any shunt with higher resistance will get recalculated to its max limit when total board power TDP gets reached.  For example if PCIE Slot and Current Sense have a 3.5 mOhm total shunt resistance and Chip Power has a 3.75 mOhm total shunt resistance, Chip power will reach 300 watts and signal power limit throttling when total board power approaches 400 Watts in GPU-Z.
 
Obviously this makes full sense if shunt modding and trying to use shunts with slightly different resistances and wondering why your TDP% and Normalized % are not matching, but with a stock board with the normal 5 mOhm shunts, everything should be perfectly in sync and balanced.
 
Tl;dr: i have absolutely no idea what's going on with the eVGA boards and the PCIE Slot (or MVDDC) or any other limits going on.

Your theory has multiple loop holes, "The Chip Master power limit is 300 watts" this statement is not true as I was able to draw multiple times above 300W.
Also this power balancing doesnt make much sense as if u input -64mhz offset on core clock, nothing in terms of power delivery specs changes but your power draw will shoot up significantly as the card is now boosting to 1043mV. I had no problem sustaining around 470-480W.

This is tested on the Founder's Edition.  You guys need to test this on the eVGA for yourselves with your own shunt mods.  Of course chip limit should exceed 300W since your TDP can go up to 500W, unlike FE which is capped at 400W.
 
Every power rail has its own internal power limit not directly related to TDP.  TDP is simply all the 8 pins and slot power combined.  TDP "Normalized" will calibrate around this if any of the power rails goes out of phase with TDP%.  There is hardly any discussion about TDP Normalized, and even Martin at HWinfo64 doesn't know much about it, except that NVAPI uses it somehow. 
 
TDP% is the only one everyone is aware of and PCIE Slot limit is less well known.  There is also MVDDC limit, Current Sense source, GPU Chip Limit, and PCIE 8 pin limit.

 hmm looking back at your statement I think youre right, from what I saw rn with 520W KP bios, Im hitting normalized power limit 120% however Total power limit is barely above 105%. I think youre theory is on point and it makes a lot of sense now to me, what I dont understand is why some ftw3s have this "issue" and others dont ? I also saw Martins explaination on this issue, can u maybe help us further with investigation ?

kvswim
seems like it's safest to use v1.1.1 and to start from the factory vbios then? also, a couple of tries on port royal and I'm -1000 points from my previous best, but the average clock is higher and it was using up 475w-ish. what gives? https://www.3dmark.com/compare/pr/496839/pr/579772#
tried another pull, same thing https://www.3dmark.com/pr/579986 ???

if u benched your previous best few days ago it may be because 3Dmark had major update and all newer scores are significantly worse score wise, please rebench again.