I just noticed potential issues with the PrecisionX install created scheduled start up task configuration:
Stop the task if it runs for longer than: 3 days (checked)
Note: The task to run PrecisionX is triggered by user log in.
If a user does not "log in" but lets their system "sleep" couldn't this result in the task being stopped after 3 days after their initial log in?
I also noticed:
Start the task only if the computer is on AC power. (checked)
Stop if the computer switches to battery power. (checked)
If a laptop users system gets unplugged (switches to battery) and then gets plugged back in there is no method to restart the task that was shut down by this tasks configuration setting...
People may begin to wonder why their video cards are getting hot... IE: I use PrecisionX Primarily for the auto fan curve/control myself.
Just noticed something else... PrecisionX GDI objects = 1800 Which seems rather high given the functionality.
Note: There is a limit of 16,384 GDI object handles per user session in Windows.
You just used over 10% loading PrecisionX (not counting the servers)
----
Note: 3 Hours after the above post the GDI Objects now over 2000. (this is also part of the memory leak reported by others above)
I uninstalled and went all the way back to the best version I have used so far 4.2.1... GDI Objects = 142 vs the 1800+ in 5.3.8 ummm hello?
The 4.2.1 version also has neither server running (both the 32 and 64 bit server processes were running on the 5.3.8 release even with the same exact settings)
Also the 5.3.8 task configuration settings noted above were NOT checked in the 4.2.1 installed task configuration settings.