I uninstalled 5.3.2 of precision x16 and installed 5.3.3. However, their is no clean uninstall checkbox. Can anyone confirm this?

As I stated in the other thread a few moments ago, FYI, I used version 4.2.1.2143 [compiled on 15-05-2013] with my 590 classified since its release, until just yesterday when I replaced the 590 with a newer card.
Every version of Precision after this version 4.2.1.2143 resulted in frustration such as is related many times here and elsewhere in these forums. I too tried every method of verifying the culprit was the newer version of Precision, hoping it was not. Usually I would end up completely removing the newer version or restoring an older image without the newer version present so as to verify that no version after this older one from 2013 was useful to me without conflict.
I mean to say that for me over a period of at least 23 month the v 4.2.1.2143 is stable compared to any newer version. Limited to my experience I know, but just to say... I will not be installing a newer version even with my new card until I do not hear any more wailing and gnashing of teeth over the newest version of Precision in these forums. It is heartening to hear from those for whom the new version is working.

Aporking
Guys, no joking .. EVGA Precision X 4.2.1 is not comparable to these latest versions. Only PROBLEMS. 4.2.1 irreplaceable for me.

 
replaceable for me. The 5.3.2 working perfectly well. 

DBurlison
For the freak'n love of god, **** with small text on G15 keyboards already, quit freak'n saying next release and fix the damn thing already.

For real! I have a g510 and the "small font" is no smaller than the "medium font"... I can't see any useful info on my cards because the font is outrageous! As a side note, it also thinks my top card is GPU-2...

metal_god69
How does one change the OSD location?  I looked in Precision Server and dont see anything regarding it either....?

It is easy. In the Precision X server all you need to do is input a number where you see OSD X 0 and OSD Y 0 and click on set and the OSD will move.

Disclaimer - this is just my view from what i have noticed and not any scientific yada yada yada.  
 
I don't think it is wrong in my assessment. I think PrecisionX reports what the GPU is putting out rather than what the screen is doing. In MW3 multiplayer i get exactly double what fraps puts out but in MW3 co-op i get any thing from 370 - 490 fps and in fraps i get like 125 - 250 fps. I prefer PrecisionX to fraps and Nvidis's Shadow play.

My monitor is 60hz and bot fraps and shadow play give me 91 in both MW3 and Ghosts but in PrecisionX i the same as i stated for MW3 in the earlier post and 91- 160 fps and this is on max settings.
 
I think precisionX is reporting what the GPU is doing and not what the monitor is doing.

This version of Precision appears to be crashing Skype, the FPS counter on my G510 LCD seems to show 3-4fps during Skype calls and Skype will crash within 5 mins of a call beginning, I guess this means the skype call window is gpu accelerated... If I close precision, open skype, then open precision again - the fps counter doesn't show that same 3-4fps value, nor does skype crash. Skype doesn't crash if Precision is left closed either. This close/open/close method is working as a clunky work-around for now but yeah, it'd be nice to see Precision return to former glory.

JacobKlein
Try this

 
Good idea! Giving it a test run, tried and failed to just add *.exe to the list, I wonder if it's stored in raw text somewhere...

Edit: It is (precisionxserver.cfg) - added *.exe to the list, fingers crossed! :P
 

JacobKlein
 
I did not recommend a wildcard.

I have no intention of ever using the OSD, all that really matters is that my fan curve loads and Skype stops crashing. I can test it without the wildcard over the weekend if spare time permits, though.

Hi.
 
I'm using Precision X version 5.3.3
 
Does the Fan Curve function only work when this software runs on the background? Every time I close Precision X it ignores my predefined settings. 

Follow up: Unfortunately the *.exe wildcard doesn't work, but adding skype.exe to the blacklist worked a treat, no more crashes.

bcavnaugh

camstatic
Follow up: Unfortunately the *.exe wildcard doesn't work, but adding skype.exe to the blacklist worked a treat, no more crashes.

You can also exit from Skype when not in use.

What an unhelpful reply. The problem happens when Skype is running, so a workaround needs to work while Skype is running. "Don't use it" is not a workaround.
 
I really hope EVGA fixes the real problem. The OSD functionality, when set to OFF, should NOT be interfering with processes!

In your image where is it showing 1.250 ?
Click on Image to view larger view.

pickoff
The software isn't reporting the right voltage.
The one on the general control panel isn't the same as the one in the graph !


 
1.262 vs 1.250 V ...

The voltage being displayed inside the main control panel is showing the voltage of GPU2. The voltage inside the hardware monitor graph is showing voltage of GPU1.