donta1979
Does the Kingpin have a duel bios if so enable it and do not touch it with precision and see if your issue persists, if not then it may be a firmware update went wrong.

Derren001
Reading all the problems people have had with X1 sure makes me want to install it when I finally get a 30 series card...

Sajin
Give this tool a shot... https://forums.evga.com/R...ate-Tool-m3214879.aspx

Sajin
Sounds like you’ll need to rma then if evga doesn’t have a program that can correct this.

bavor

_Gir_
Did you unplug the PC when powered off, some PCs tolerate/encourage hitting the power switch to discharge as well?
 
Maybe try using a different type of connector e.g. HDMI instead of DP

After I turned off the PC, I unplugged the PC then held down the power button to make sure its fully discharged.  I also tried both Display Port and HDMI in both PCs I used the card in to try to update the firmware.

bavor

Sajin
Sounds like you’ll need to rma then if evga doesn’t have a program that can correct this.

I hope that EVGA has a 3090 kingpin to use for a RMA.  I know they are sort of scarce at the moment.

bavor
EVGA just issued a RMA for my Kingpin Hybrid.  I've had awful luck with EVGA products this generation. I had multiple RMAs for the 3090 FTW3 for the same black screen and 100% fan speed issue in DX11 games until EVGA issues a refund and took the card back.  I had one Kingpin arrive with a dead fan and the pump died within 4 hours of use.  I had a Kingpin Hydro Copper leak and the block was not assembled correctly at the factory, so I couldn't fix it.  Whoever put that block together at the factory stripped the acrylic in the screw hole where one of the screws that holds the terminal on goes.  My other kingpin Hydro Copper block leaked with chilled water until I took the block apart and tightened the screws.  Now this one needs a RMA due to PX1 messing up a firmware update.
 
Also, I'm a bit disappointed because this kingpin Hybrid is one of the better overclocking ones I've had as far as the GPU goes.  It achieved the highest stable speed with the least amount of voltage of the several kingpins I've had due to RMAs.  There is some silicon lottery with the Kingpins.
 

boyleusa
I put my KP Hybrid in an old PC running Win 10 20H2 and PX1 V1.1.8 and the firmware updated first time. The old PC is a 9900k with an Asus Maximus XI Extreme motherboard that doesn't support ReBAR.
 
I only tried versions of PX1 as far back as 1.2.5 on my 5950x Asus Dark Hero, Win 11 where the KP was originally installed.
 
Anyway, glad I don't have to RMA.
 
Looks like this is a PX1 software firmware update issue that EVGA need to review asap to prevent more bricked cards. I was just fortunate I had an older PC that worked... 
 
Further Update
Ok, so I reinstalled the KP in the original 5950x PC, Win 11 21H2, and opened PX1 V1.2.9 and it prompted for a firmware update. I (reluctantly) clicked Start and this time it updated correctly. I'm not a big PX1 user (prefer Afterburner) so doubt I upgraded the KP firmware other than when I first got it 6 months ago? Anyone with similar issues I'd suggest trying an downgrade to PX1 1.1.8 then try 1.2.9 - sorry I can't be more helpful as I didn't really go in to this in troubleshooting mode, I just wanted not have to RMA my card.      

You got lucky, I tried in another PC with Windows 10 and no ReBar support and couldn't get the firmware update to work.

bavor

boyleusa
 
Did you try a much older version of PX1 like 1.8?

My KP is also a good silicon sample so wanted to avoid an RMA as it scores well over 14k on Port Royal with zero overclock.

I first tried an older version that was still on the other computer and it didn't work.  Then I updated PX1 on that computer, rebooted, and it still didn't work.

bavor
 
 
I don't remember what the exact older version was because I didn't write the version down after trying it and it didn't work.  It was from June 2021 or earlier because June 2021 is the last time I used that PC.  I updated Windows 10 on that PC and nothing else because EVGA said I needed Windows 10 21H1 for the update to work properly.
 
Both PCs had the latest version of Windows 10 Pro 2H21. EVGA support specifically said you need 21H1 or newer for the newer versions of PX1 to successfully update the firmware.
 
At this point it doesn't matter because I have the RMA replacement card already shipped my way.

bavor

boyleusa

bavor
I don't remember what the exact older version was because I didn't write the version down after trying it and it didn't work.  It was from June 2021 or earlier because June 2021 is the last time I used that PC.  I updated Windows 10 on that PC and nothing else because EVGA said I needed Windows 10 21H1 for the update to work properly.
 
Both PCs had the latest version of Windows 10 Pro 2H21. EVGA support specifically said you need 21H1 or newer for the newer versions of PX1 to successfully update the firmware.
 
At this point it doesn't matter because I have the RMA replacement card already shipped my way.

It does matter - my sole reason for posting was to help other people and hopefully avoid an RMA. There is zero probability you were using any PX1 version lower than 1.2 from June 2021.
 
1.1.8 was released in March 2021.

 
Again, since you didn't read and comprehend my response, I didn't know the exact version number.  Its a PC I used infrequently.  It may have been many months before June 2021 that I last updated PX1.  However I don't know the exact version number.  You are assuming I said it was last updated in June 2021, which it wasn't.  June 2021 was the last time I used the PC.  I said June 2021 or earlier without giving an exact date or version number.
 

boyleusa
Perhaps if you had followed my suggestion and tried version 1.1.8 of PX1 then 1.2.9 you may have avoided an RMA. We will never know in your case, but let's hope others in a similar situation are able to repeat what worked for me successfully.  

No it doesn't matter because my RMA was approved before you even originally posted a reply in this thread.  My RMA was approved over the weekend before your reply that was post #17 in this thread.