JacobKlein

eruntalon
Why am I not seeing anyone else who has recently clean installed Windows 10 using Precision getting this error. Still the same as before with 5.3.7 now still with 5.3.8. Everything works albeit the error message at startup:

...
In order to troubleshoot a program/OS, you need to think like a program/OS.
Once you figure it out, don't forget to chime back in here, to describe what the problem was, so others can benefit.

Removing either (one must remain at any time) the file PrecisionXServer or PrecisionXServer_64 from the directory will result in no error message and the program functions normally / confirmed as overclocking:
 

Toms Hardware article
"there may be multiple reasons as to why you might receive 0xc00007b error when trying to run an application on a windows machine. 0xc000007b error usually comes from mixing up 32bit environment with 64bit one. For example 32bit application loads a 64bit dll causing 0xc000007b error."

 
I am still experimenting with this though.

How do you set your profile to start with Precision? And I don't have it start with Windows just because is causes my Zoom Player to crash when ever I watch a video.
 
 

NordicJedi

Airbrushkid
Anybody tell me why it doesn't save the setting I apply?

Have you created a profile for your settings, set PrecisionX to start with Windows, and set your profile to start with Precision?

Scarlet-Tech

strongbrew83
Still getting the slow start of Precision X and keyboard lag for about 15-25 seconds after boot. System itself boots in about 6 seconds only thing lagging are the two afformentioned. Tried it without Precision X and no slow input on keyboard. Any fix for this?

That may be hard to replicate for some, as I personally have not experienced this since I use the steam version of Px

Could you post your system components so that they will be able to see what you are using and if there is another program that may be causing the lag/fighting with Precision X, and then possibly make a fix?

If your full system specs are in your signature, I can't see sigs, so I apologize.

4790k @4.7ghz
980 @1500mhz and stock mem speed
16gb 2400mhz DDR3
Win 10 x64
system timer resolution set to manually tick @.5ms
 
tested to the point of obsession, completely stable in all games, apps, and stress testing software.
 
I run a highly minimalist windows 10, all the bloat uninstalled and literally no other software running at startup. tried deleting the font hook DLLs and the server DLLs along with the .exe and that didn't work. Only a problem with latest versions of precision X as 4.2.1 and other software like Afterburner doesnt have this problem, and again only affecting the keyboard input for about 15-25 seconds after boot, entire system including mouse, and my 360 controller work fine with no lag and i can start any other application manually with no delay. just recently tried switching keyboards to see if my old logitech one was the cause of the issue like the program was trying to hook itself into the LCD on it or something but with my new basic microsoft keyboard im still experiencing it.

With this release i reinstalled Precision X again on the Windows 10 OS here. I've been testing it for a few days and it seems to function as intended for the most part. I'm not using any information from Precision X to display on a G15.
The only issue i'm still having that the Precision X startup is slow on OS boot and manual start. It takes for about a minute and something is going on in the background when looking at CPU usage on loading. 
 
In previous versions nothing really worked or the program caused excessive GPU and VRAM usage on regular programs like browsers and such. Apparently some of the problems where caused by the precision X OSD server and needing exclusions. Perhaps it's a good idea to have everything excluded by default by this server and list programs yourself in this list when you want the server to work with it. This might solve allot of problems in the future. Creating a standard exclusion list that comes by default might become long as time progresses.
 
Thx for 5.3.8 it fixed allot of issues for me.
 

Media Player Classic not freezing/crashing anymore so far! Heroes of the Storm not getting stuck mouse, so far!
 
I have yet to find issues!

Yup, VLC and other media players should be fixed also.

Thank you, new version doesn't crash video players anymore. Also EA Origin's in-game overlay works again.
 
*edit* In 5.3.8, memory clock shows 0mhz in Mass Effect 3 and GTA V, both in OSD and in monitoring graphs in the app... Everything seems to be fine though, no oddities. <--*edit* After a loading screen or alt-tabbing is when the memory clock seems to drop to zero in both OSD and monitoring graph. Reloading a save in ME3 fixes it, until the next loading screen or alt-tab. I seriously doubt the memory clock is actually dropping to zero, it would definitely cause a problem.
 
*edit* OK it's happening in GTA V if I alt-tab out of the game. Running in borderless window mode, that might be relevant. After exiting the game, memory clock still shows 0mhz until I clear history on the monitoring graphs. *edit* Just tried this further... Now I'm seeing in ME3, walking to areas where there's very little graphics to load, the memory clockspeed being monitored shows 0mhz, then it goes to 810mhz and then back up to 3005mhz. In GTA V, it'll stay stuck on 0mhz, though there seems to be nothing wrong, as the game continues to run perfectly. That's where I have to go to clear history on the graphs and it shows 3005mhz again. I also see the 3005mhz to 0mhz to 810mhz if I open and close my browser. Not sure if this is normal or not, but everything seems to be working fine. GTA V reaches 79C under full load, but this card's always run very hot with the reference cooler.
 
Also in GTA V with OSD, sometimes the framerate incorrectly shows 29 fps. There's a noticeable smoothness only at 60+ fps, and when it shows 29 fps it still looks like 60fps.
 
Also if I have the Fan Curve graph open, after closing it it won't open again, unless I pick a different fan profile or back out of the fan options. <--This issue was in 5.3.7 version as well.

Scarlet-Tech

strongbrew83
Still getting the slow start of Precision X and keyboard lag for about 15-25 seconds after boot. System itself boots in about 6 seconds only thing lagging are the two afformentioned. Tried it without Precision X and no slow input on keyboard. Any fix for this?

That may be hard to replicate for some, as I personally have not experienced this since I use the steam version of Px

Could you post your system components so that they will be able to see what you are using and if there is another program that may be causing the lag/fighting with Precision X, and then possibly make a fix?

If your full system specs are in your signature, I can't see sigs, so I apologize.

There is a topic about this problem. It's not like people don't want to help or give information making it easier to find the cause of this problem, but until now Evga showed no interest in investigating/fixing this bug.
 
 
 

HammerNL
There is a topic about this problem. It's not like people don't want to help or give information making it easier to find the cause of this problem, but until now Evga showed no interest in investigating/fixing this bug.

Unfortunately for everyone having the issue, it isn't a wife spread problem. I read a lot of threads, and have never seen the one you refer to, and since this is a user based forum, that means EVGA may not have been directed to the specific thread you are referring to that I can remember. If I did see it, I have forgotten about it.

Posting the information and issues on the release thread means all items are centralized instead of being spread across multiple threads, making them exceedingly difficult to distinguish from any other thread. That makes it especially hard when the thread isn't pertaining directly to the latest release.

I requested the information posted here because it seems to get noticed the most when the issues are on the release threads, which the user above was nice enough to do. If you are having this specific issue, could you post your information on this thread to see if there may be something linking the two issues into one?


Does you keyboard have specific drivers for it? If so, did you try removing those specific drivers from the company and just try the standard Windows drivers? I ask that, because me Roccat board has Roccat drivers, but will work with standard drivers from Windows. If the drivers are taking longer to load for the keyboard because of some resource in Precision, then that may help evga pinpoint the issue.

I have 

Scarlet-Tech

HammerNL
There is a topic about this problem. It's not like people don't want to help or give information making it easier to find the cause of this problem, but until now Evga showed no interest in investigating/fixing this bug.

I requested the information posted here because it seems to get noticed the most when the issues are on the release threads, which the user above was nice enough to do. If you are having this specific issue, could you post your information on this thread to see if there may be something linking the two issues into one?

Does you keyboard have specific drivers for it? If so, did you try removing those specific drivers from the company and just try the standard Windows drivers? I ask that, because me Roccat board has Roccat drivers, but will work with standard drivers from Windows. If the drivers are taking longer to load for the keyboard because of some resource in Precision, then that may help evga pinpoint the issue.

I can, my system: 
 
i5 2500k @4.8GHz
ASUS P8Z68-V Pro 
8GB DDR3
MSI GTX780Ti @1250Mhz
Samsung 850 EVO 500GB
Creative Soundblaster Z
Keyboard Corsair k60 no specific driver installed/not needed
Windows 10
 
I also had this problem on Windows 8.1, then i switched to windows 10 but the problem remained. Clean install, only installed the basic driver for each component in my system:
-Chipset drivers
-Basic display driver
-Intel lan adapter
 
So no Samsung magician, or soundblaster drivers, geforce experience and more of that BS. 
 
I'm now running Precision X (5.2.4) if I install a newer version I get the very noticeable ~30 second delay in input. With the 5.2.4 version, the delay is still there, but almost non existent.
This is of course with Precision X enabled on startup.