rusTORK
I have no problem with my current graphic driver and XOC, only X1 act like it's not working. I see starting logo, but i don't see main menu. Software crash before that. How NVIDIA power Targer problem connected to Precision X1 start?
 
Which NVIDIA driver version i may use with X1?
 
I deleted EVGA folders in diffirent locations before X1 installation and result always was same - X1 don't even start after logo.
 
All i want is working G.P.M. LED of iCX at windows boot, but it's not working in XOC and not working in X1. What the hell? =)
 
P.S. One more thing - normal user must stay away from RegEdit as far as possible. Since one wrong deleted key and you have to reinstall windows. In another topic was few folders names without full address. It's not how things are done with RegEdit fix.

I use PXOC on all my GTX Cards so I do see any issues.
I only use PX1 on my RTX Cards and really do not have any issues.

O.K., i will try 430.53 tomorrow with complete fresh install (all delete, DDU, all install).

rusTORK
O.K., i will try 430.53 tomorrow with complete fresh install (all delete, DDU, all install).

It’s a pain in the ass I’ve been there. If all else fails you can try contacting evga support they only sometimes respond to people on the forums it’s mostly users helping users.

Their was a weird bug awhile back in PXOC where if osd wasn’t highlighted for temp, power temp, memory temp in hardware monitor then it wouldn’t change colours when the tempatures change it’s possible it needs it checked to be able to load previous setting on startup. Doing your step is essentially the same but might not save.

I’m not exactly sure however. It’s been awhile since I had g.p.m issues thought they fixed it in the latest pxoc updates.

rusTORK
I installed NVIDIA Driver v430.39, installed Precision X1 and it's finally runned well. I configured G.P.M. LED and tested it in Valley Benchmark (closed X1, run Valley, card was hot, but LED didn' show it, i run X1 after Valley Benchmark and it's updated them instantly).
 
 
Bad effect only one - NVIDIA driver disabled my dGPU (GeForce 650M). Look's like i need to re-install driver again. Because i saw how windows installed v376, then 388 and after all that i installed 430...

If you find later your also having issues with high cpu usage on 430.39 install the hotfix 430.53

This Hotfix driver addresses the following:
Fixes higher CPU usage by NVDisplay.Container.exe introduced in 430.39 driver
3DMark Time Spy: Flickering observed when benchmark is launched
BeamNG: Application crashes when game is launched
Shadow of the Tomb Raider: Freezes when launched in SLI mode
Desktop flickers when videos are played back on a secondary monitor

https://nvidia.custhelp.c...-driver-version-430.53

rchiwawa
Looks like i am going to be the guinea pig for driver 430.64...

Aren't we all.

rchiwawa
Looks like i am going to be the guinea pig for driver 430.64...

Have to hack it to get support of my GT 650M. Didn't tested yet with GTX 1080 Ti and X1...

My PX1 0.3.16 problems with power target saving and GPU clock offset not displaying but being actually implemented are fixed.
 
My Nvidia driver problem of having my Gsync displays power their back light on after being asleep for ≈5 minutes has seemingly been resolved... so it seems they actually made some improvements and I am satisfied.  I won't be bothering with updating my driver for a while now as this 430.39 really pissed me off. :) 
 
If I come up with a problem as I use the machine I'll be back to inform but I am going to say this (430.64) is a good one so far as 15 minutes of testing is concerned.

Void65231
Nvidia driver 430.64 is basically the 430.53 hotfix relabeled for public release as far as I can tell from the changelog.

the hotfix left me with PX1 power target saving and even implementing not functional, .64 doesn't have any of the issues I have been GeForce Experiencing with .39 and .53 fwiw

Void65231
Glad to hear your issue is resolved and 430.64 works for you. I’ll be updating to that version from 430.53 shortly. I’m sure they likely patched some other things in .64 compared to the the hotfix, but the main points in the 430.64 changelog still highlighted the stuff from the last patch.

Hey, just so we're clear, I am appreciate you went through the change logs and shared what you found.  I am pleased that the fix for me was part of the minutiae that didn't get documented... like the little detail of borking increased power limits.

rusTORK
Here is my test of Precision X1 with NVIDIA Display Driver v430.64 (Modded, installed in special Windows mode). I added in driver lines for my dGPU (GeForce GT 650M).
 
1. Precision X1 is loading, i see logo and it's crash without reaching main menu - just like it was before;
2. If i turn ON developer settings in NVIDIA Control Panel and then allow access for all users to GPU performance counters - same problem like in #1;
3. If i disable in device manager dGPU (GeForce GT 650M) and keep developer settings (and everything else) - Precision X1 is starting normally.
 
So, Precision X1 don't like my dGPU and can't be run without developers settings ON + access to GPU performance counters.

And what happened when you ran PX1 as an administrator?
Do you still need to turn ON developer?
This is a Laptop you resting this on GeForce GT 650M?
PX1 is not meant to be run a Mobile Graphics Card and is not really even supported.
 
I am running as administrator and not having any issues.

Precision X1 was rebuilt and not a reskin of Precision XOC and because of that the only supported cards are 10 series, 16 series, 20 series cards. You pretty much said it yourself once you disabled your older internal graphics everything worked as normal, so their is clearly a incompatibility in px1. It’s unfortunately not as simple as pxoc because they try to incorporate gpu specific ui components to each supported card which could be what’s crashing the application.

I don’t imagine EVGA fixing this issue because it’s somewhat outside of their scope of support.

I think we just overestimate how big evga actually is as a company. I don’t want to actually defend them because “software” has always been a weak area, and need some serious work.

Evga is primarily a hardware company, and most likely their hardware isn’t manufactured in house but instead contracted out to factories like Foxconn. I’d be happy be to corrected by them.

Software on the otherhand I believe is likely QA tested in house by a small software team, likely forum mods or people internally. But the actual software is likely produced by another company which evga contracts to, and purchases “time” for that software company to work on reported bug fixes and produce new product software. And likely they don’t work on every software evga has. This is all just speculation, but would explain why we don’t see Evga’s software products patched more frequently.

That or they do produce their own software in house, but just have a really small team that are overworked, and are stretched thin between multiple software projects.

I installed 3.16.0 running NVidia 419.67.
PX1 won't save fan profiles. It nearly baked my card; I set fan profiles, set to auto, and then the fans never ran. I have to force them into 100% or they just sit there.
 
PX1 has been dumpster fire since release, and we're now 6+ months into it.
 
EVGA has been my go to for years, but this ridiculous software BS is beginning to test my patience. $7k+ into EVGA products, I'd only expect this BS from ZOTAC or the like.
 
-N.

bcavnaugh

nathanielhatten
I installed 3.16.0 running NVidia 419.67.
PX1 won't save fan profiles. It nearly baked my card; I set fan profiles, set to auto, and then the fans never ran. I have to force them into 100% or they just sit there.
 
PX1 has been dumpster fire since release, and we're now 6+ months into it.
 
EVGA has been my go to for years, but this ridiculous software BS is beginning to test my patience. $7k+ into EVGA products, I'd only expect this BS from ZOTAC or the like.
 
-N.

Did you click Apply and Save on Each Change that you made?
Under Settings Did you click Apply and Save on Each Change and Select Apply previous settings on load?
 

*Edit*
@bcavnaugh: Thank you for trying to help. Not frustrated with you. Just really tired of dealing with broke-*** software and wasting my time rooting around to figure out "workarounds" for something that should work out of the box since it's integral to the function of the hardware.
 
*Original*
I did. This isn't my first rodeo with the software. I've had a 2080 Ti FTW3 since they were released; same for the Precision X1 software. I've found a workaround for my problem; still a load of hooey IMO to deal with this 6+ months into it.
 
And for those who are tired of having to do the right-click, run as Admin, you can schedule a task to execute in Windows 10 and it should handle for you instead.
 
See here for high; just make sure to set it to run at highest possible privileges.

I am seeing PX1 0.3.17.0 Lockups when making changes on the OLED Panel.
Requires a Forced Computer Reboot to Clear End PX1.
Clicking on one of the Fans (Tacho) and then clicking it off and clicking on the other one Locks PX1.
I did this 3 times in a row.