Sometimes a worst case scenario test can be enlightening. I have noticed the same stuttering caused by EVGA software many of you have, and wondered to myself... how terrible would be the stuttering be if px18.exe had its priority elevated?
 
Run this command in an elevated (administrator) cmd window to set px18.exe to realtime priority:
wmic process where name="PX18.exe" CALL setpriority "256"
 
Be prepared to be amazed, and not in a good way. Although this is a worst case scenario it will become obvious just exactly how poorly the program is optimized. These are the scenarios that programmers should be using to test px18.exe and it fails in the worst way.
 
Precision X is not fit for its intended purpose- gaming. Instead of improving gaming it makes it objectively worse. If you can handle/don't notice/don't have the stuttering while the program is realtime priority you should be good to go gaming with precision running- otherwise use it to set a manual fan speed before you game and "end task" (it will be labeled as Precision X1) using task manager. That is my advice until they can (or perhaps it is better said- choose to) optimize this thing.

I have a 10 yr old computer with a i7 990x oc to 4.14, running monitor at 144hz, limiting fps to 120, BFV a ultra, fps 60~95 and a bit higher for short periods, and no stuttering with PX1.
 
I can how ever get it to stutter by changing settings to higher performance settings on the PX1 and certain settings on BFV.
 
 
Current BFV set up:
monitor 144hz
limit frame rate to 120
don't restrict card memory
ultra fidelity
future rendering on
 
PX1 settings:
Memory Clock 1200
GPU Clock 160
Voltage 90
Target Power 120 (max is 135)
 
I get bad stuttering with BFV if I:
limit frame rate to 60
turn future frame rate off
and at times if I restrict memory to video card only
 
I also get stuttering and crashes at times by:
Increasing the Memory clock higher than 1200 and definitely above 1300
Increasing the GPU clock to 170
all in combination with gpu voltage above 90 and target power above 120
 
Then of course there is the CPU oc above 4.14 since the original Alienware MB is not the best.
 
If you are pushing settings to the higher limits it will usually result in poorer performance overall. It is a bit of a balancing act between components and programs being used. Higher settings do not guarantee better performance. Try different settings within game and PX1 to find he best performance.
 
Then there will be the inevitable driver update that will screw everything up.  

ee11vv22gg33aa44
Your advice is appreciated, dc8fliyer! I am guessing your computer is not quite 10 years old, being that the i7 990x was released in February 2011. You must have dropped about a grand on that bad boy back in 2011! :)
 
However, PX1 is the cause of nearly all of the stuttering in the games I play (occasionally windows will peg the cpu doing who knows what with photos or some other unruly windows 10 app). The solution is simple- set the fan speed to manual and kill the program = no stuttering issues.
 
Did you set PX1 to realtime priority to check for stuttering?

The computer is a 2009 Alienware with an original i7 950 chip. I replaced the chip later at, yep 1G.
 
I'll take your word about the PX1 running at priority with the associated stuttering. Like I said, it doesn't take much to get a game to stutter with so many combinations of settings and different components.
 
I'm not sure exactly what continues to work once PX1 is closed. I have observed that with a custom fan setting I can minimize PX1 and the card will follow the settings. If I close PX1 and open it back up a few minutes later, the card is several degrees warmer but comes back down as the custom fan curve takes back control. I suspect if PX1 is closed other settings may not be working also, don't know for sure but am sure the custom fan settings don't work once the PX1 is closed.
 
 

Yes, dc8 that has been my experience as well. Manual fan settings will persist after PX1 is closed- custom fan curves will not. Don't know about the rest of the options (overclocking/etc.) because I never use them.