Sean1976
.....it's been 4 days and still no reply from Evga....

I'm starting to think the forums aren't the place for this stuff. The replies are too sporadic and unreliable. If I have time later, I'm going to call EVGA customer support and explain what's going on. Maybe there's a better way for us to submit bug reports, but I thought a stickied forum post by an EVGA employee was something they'd see and reply to. (referring to my post from early June)

EVGATech_ErinW
While we can't always reply to a post, the programming team does track bug reports that are posted here. If you've experienced a bug, please post it!
 
If you don't have your system info in your sig, then post it in your bug report. Also, include the driver version that you're running. 

Erin, thank you for the quick reply. I've been doing bug reporting for a long time, on the receiving end as well, and there is definitely a psychology to it. If you don't acknowledge bugs, it creates a problem. Saying "don't worry, we watch the forums" doesn't really reassure us that we're not wasting our time. We don't need an ETA, or even a deep dive analysis that minute. What you did by replying with a single line is a huge step.
 
Just saying "Thank you for your bug report. It has been forwarded to our development team" can turn a hostile situation into a positive experience. If there's a better, more official way to submit bug reports I'll gladly do it, but we need some kind of acknowledgement, otherwise it seems like we're being ignored, even if we're not. We're taking time out of our day to work with you to solve a problem, so it kind of stings when we don't even get a reply.
 
I get that you guys have other duties, and monitoring the forum isn't a 24/7 thing. Trust me, I understand more than you may think. Alright, I'll go ahead and get off my high horse and post system specs. I've tested on a couple builds of Windows, so I'll list each that I've tested, and the corresponding version.
 
Affected versions:
 
Precision X 6.02 tested with:
OS Name: Microsoft Windows 10 Pro Insider Preview
OS Version: 10.0.14372 N/A Build 14372
EVGA GTX 1080 SC
Nvidia driver: 368.69
 
Precision X 16 5.3.11 tested with:
OS Name: Microsoft Windows 10 Pro Insider Preview
OS Version: 10.0.14372 N/A Build 14372
EVGA GTX 1080 SC
Nvidia driver: 368.25 and several versions prior
 
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.10586 N/A Build 10586
EVGA GTX 680 SC
Nvidia driver: 368.25 
 
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.10586 N/A Build 10586
EVGA GTX 680 SC
 
Unaffected versions:
 
Precision X 16 5.3.10 tested with:
 
OS Name: Microsoft Windows 10 Pro Insider Preview
OS Version: 10.0.14372 N/A Build 14372
EVGA GTX 1080 SC
Nvidia driver: 368.69
 
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.10586 N/A Build 10586
EVGA GTX 680 SC
Nvidia driver: 368.25 
 
While I have not tested Precision X OC with a non-Insider Preview version of Windows, I think we have enough data points here to conclude that it would also be affected, mostly since Precision X 16 was affecting previous versions and has the same bug.

I said it years ago.....when Evga switched their development company(4.2.1 legacy was the last decent working tuner Evga distributed) things spiraled down hill from there. Their still having issues today......
Should of let Sidewinder do the work, at least he knew what he was doing.

Sean1976
I said it years ago.....when Evga switched their development company(4.2.1 legacy was the last decent working tuner Evga distributed) things spiraled down hill from there. Their still having issues today......
Should of let Sidewinder do the work, at least he knew what he was doing.

 
Its taken a long time. Its finally getting there. If they can address these few bugs remaining. I think it will finally be there and solid. They just have a QC problem. Every release has a problem. It should not be like that. 

I keep getting prompted there is the 602 update even though I have a 980 Ti. When I tried installing it tells me I must have a 1070/1080 etc., so I put the regular Precision X 16 back but still get prompted about the 602 update every boot or restart of Precision X. Is there any way to stop the prompting for software that is not compatible with my 980 Ti Classified?

Sean1976
and still no 6.0.3 update......weeks later.......

Anybody have a twitter update for us? Any news?

makes me kind of glad, evga downloads are such a pain in the neck

Does this include support for 3440 x 1440 now?

Please add brightness slider for led control.
Please add position adjustment for OSD.

fettouhi
anyone else having problems with GPU clock offset not remembers when you reboot the system ? I get mine to 120 and reboot and it sets to 100+ instead.
 
windows 10 pro 64bit
EVGA 1080 FTW
EVGA Precision X 6.0.2

I noticed the same thing. Here is a quote from my earlier post (post #6): "If I set my clock offset to +38, when I close precision and reopen, the offset is shown as +25, so not remembering the exact setting."

GTX 1080 FTW SLI - I have +75 set on my core clock, but when I load up a benchmark, the secondary card is not getting the same clkfreq as the primary GPU - anyone else see this? This is with 6.0.2

EVGA Precision X OC is only for Pascal?
 
Now I use Framerate Target for controlling fps in old games.
Not Vsync, if no tearing and many games not tearing at all I lock on 100-120fps and on that way fps is not so high and in same time GPU not work always on full speed. Example games where card don't need to boost on full speed, why to play with 250 fps and 70-80C when you can play 100-120fps in 60C, even in monitor support only 60. And my card work on 1071MHz instead 1215MHz for max fps. Nice setting...

https://twitter.com/EVGA_JacobF/status/755076818307166208
He tweeted that.

6.0.3 is out now.

Why do I have to enter the serial number of my card before the program will run?  This seems rather odd you need the serial number of a card I registered over a year ago and can't extract that info automatically.