2015/10/04 05:08:49
sobika
snow_lightning:
Same here. I experience memory leaking problem with PrecisionX_x64.exe. It use 500 mb of RAM after about 12 hours.
2015/10/04 17:15:15
AndrewKalionzes
I've got a nice memory leak with this version and the two previous versions. Currently at 1.4gb after 6 days up time.
 
 

Attached Image(s)

2015/10/05 17:02:16
Mole3
I just checked mine, it's only using 5 megs and I've had it on for a couple of days. Not sure what could be causing that, but I see that Adobe Photoshop is open... Does Precision X affect it?
2015/10/06 17:32:11
AndrewKalionzes
Mole3
I just checked mine, it's only using 5 megs and I've had it on for a couple of days. Not sure what could be causing that, but I see that Adobe Photoshop is open... Does Precision X affect it?




I just opened it to take a screenshot. The two are not related.
2015/10/07 21:32:51
mikeyuen
Anyone having problems with the FPS counter not showing the correct framerates?  My Precision OSD counter constantly shows false dips down to 1 or 2 fps when the actual framerates are constant 60fps +.  Problem seems to occur in every game I've tried.   
2015/10/08 08:55:01
strongbrew83
Still nothing in regards to the keyboard-only input lag at startup? Seems extra special odd that this hasn't been fixed yet or can't be replicated or whatever. Considering you guys have the source code, could I inquire what could possibly be affecting the keyboard input delay ONLY when precision X start up???? Like other users I think we've determing that it is exclusive, in our cases, to such.
 
Please fix this you guys. I love the fan curve functionality and using K-Boost to eliminate microstutter and hitching in games but don't really wanna go the modified bios route to achieve the same effect because I like having my warranty intact.
2015/10/09 13:41:36
racerx14
Precision is leaking memory. this is about 8 hours of just sitting idle.
h ttp://1drv.ms/1LeupP
 
Remove space between h tt on link above.  it will not let me post a link or file.
After leaking that long when you shut down Precision both the server and server 64 are both still running in the Task Manager so you can not restart without killing the services by hand which is mute because the system will not give back the memory and eventually will crash the display driver. So I have to reboot every couple of hours. This is a fresh install of windows 10 pro x64 not an upgrade. Was having this issue in the upgrade so I went the full install. Still have issues.
 
On a side note; My exclusion list is about long, about three pages or more.
Is there anyway to make it only work for the games and not every app and software on the PC?
 
2015/10/11 12:08:03
RHetherington
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.
 
2015/10/13 12:20:29
strongbrew83
^Interesting. Was using 4.2.1 myself a little while ago because of the startup bug present in all the recent versions and it felt like I had less input lag while gaming but it could easily have been placebo as I didn't measure it. The only reason I don't use that version now is because K-Boost is a little bugged with it and I don't like fiddling with my clock speeds to fix it everytime I switch from work to gaming or vica versa. Does anyone know of another method to force max boost clocks like K-Boost without modifying bios? I'd like to retain the ability to switch back to adaptive mode easily when I'm not gaming considering the energy saving states on these GPUs are nice and green.
2015/10/13 12:41:15
HammerNL
strongbrew83
^Interesting. Was using 4.2.1 myself a little while ago because of the startup bug present in all the recent versions and it felt like I had less input lag while gaming but it could easily have been placebo as I didn't measure it. The only reason I don't use that version now is because K-Boost is a little bugged with it and I don't like fiddling with my clock speeds to fix it everytime I switch from work to gaming or vica versa. Does anyone know of another method to force max boost clocks like K-Boost without modifying bios? I'd like to retain the ability to switch back to adaptive mode easily when I'm not gaming considering the energy saving states on these GPUs are nice and green.




Waiting on the Precision X dev(s) is useless. Custom bios is the way to go. No third party bs, adaptive clockspeeds low load, max boost while gaming. 

Use My Existing Forum Account

Use My Social Media Account