"Can't run 5.3.5 in Windows 10 64-bit (Builds tested on 10131-10162) and OSD enabled."

Enabling OSD renders Precision X useless as it crashes all of my games straight away from initial loading. So with all this excitement over DirectX 12 support  all for naught lol

Core System Specifications:

Asus Rampage V Extreme
Intel Core i-7-5960x @ 4.2Ghz
ADATA DDR4 @2500Mhz 11-11-12-14 1T
EVGA GTX 980 (1)
EVGA GTX 980 (2)
(Yes SLI is enabled & using the latest nvidia drivers: "353.30-desktop-win10-64bit-international-whql" )
Sound Blaster X-Fi Fatality Professional Series PCIe Using Daniel K's Support Pack 3.3 (Waiting to put my Blaster Z in later this month when Creative puts out official drivers)
System Drive: Consists of x3 Intel 530's in RAID 0 Array configuration
Windows 10 Professional Technical Preview, Build release candidate 10162
EVGA SuperNova G2 1300w

Before someone asks:

Yes I have the latest Nvidia drivers as stated above, and yes it's a clean install of them. Every driver update I tare down the display drivers to the "Microsoft Generic Display Adapter" level with all driver files properly removed from directories to registry entries.
Tried a clean install of Precision X as well, results are consistent. (Games Crash)
Yes results are the same regardless if I'm running reference speeds or overclocked.

Solution to Date:

Simple install previous version in my case 5.3.3 , only issue I'm experiencing is Precision unable to save screenshots or better put will not acknowledge hot keys for taking a screen shot. This seems to be an isolated issue pertaining to Far Cry 4 only, as multiple key assignments prove successful in other games with no issues even from the same Developer/Publisher. As an example Assassin's Creed Unity I'm able to take screens with no exceptions via Precision.

Scarlet-Tech
Try using the 353.49 hotfix driver, since driver 353.30 is known to cause crashing.  353.30 is not technically the latest driver, since the hot fix came out. The 353.49 addresses windows 10 Crashes that 353.30 were causing.. conveniently, you are having crashes on the same driver everyone else is.
 
 < is the forum thread that tells you where to go and how to load it.  

Son of *beep*, I just looked last night for an updated driver so much for google fail lol If I saw these definetly would have tried before posting. Either way thanks for the heads up on the drivers. I noticed they put it out for a Sony laptop. Ironically when I tried other drivers from nvidia not listed for windows 10 but addressed the TDR crashes similar to windows 10 wouldn't take them. Which is odd because in the past were able to get away using Windows 8/8.1 , which tells me they've been adding a lot to the OS in terms of tightening up for release. I know version build 10158 rolled out with 300+ Bug fixes.
When it comes to windows and drivers it's always a roller coaster of fun lol I rarely post on the forums because 99.9% of the time I interdependently deal with the issues & I'm not one to whine either. You see this by my join date and the number of posts lol

Thanks again, lets see how these drivers work, first I have to do a few reboots as I tare down anything to do with Nvidia drivers especially in Windows 10 it really forces things on you which is why to save time I just disable my Ethernet adapters to keep Windows from doing things on the sly. (Yea even changing the hardware setting in the advanced options setting the options "Never install updates from windows update" doesn't fully keep it from meddling lol

Precision X Conflict.
I have recently purchased a Sound Blaster Z audio card. There seem to be a conflict in software. If install the Extra suit from the SB-z drivers then the EVGA Precision X will not load, on boot or by manually. It show to be running in the task manager and the task bar but will not display on screen and the OSD server is intermittent, start and stops randomly.
Had to remove sound drivers and precision X and had to remove the Precision X CFG files by hand as they were corrupted some how. It took me a couple of try's to narrow it down to the Extras pack in the Sound Blaster Driver.
Now that I have that straightened out there is a problem that EVGA Precision X is very slow to start. I will get the GPU temps in the tray but the interface takes up to one minute to show in the tray icon to click. If you kill the running app and start it from the desktop it can take two minutes or longer for the EVGA Precision to appear on the desktop. Remove the Sound  Blaster Z driver and all is well.
I loaded the back up of my Windows 8.1 I made before installing the Audio card and reconfirmed the issue.
Creative Labs have not made a driver in 19 months so I doubt they will address this. Their tech support answer was to not run Precision X.
I was hoping that you all (EVGA) might take a look into the issue.
 
Thank you.
RacerX14

Can not see Precision X on Windows but can see on Taskbar... help. There is no extra monitor where it is... so Im confused. If I install a earlier 4.0 version I can see it but if I hover over the taskbar it says PrecisionX is open.. so please help.

Hi, why is precision x not showind the direct x version thats being used? Am i the only one with this problem?
I tried everything but still nothing! Am i missing something?
 
Please reply, thanks in advance!

ViperInfinity
I no longer have the OCD and something else option. I cannot remember what that something else was.

^ This was good

Why is my precisionx osd not showing on any directx12 based game or benchmark ? It work perfectly fine on directx11. It also wont show in doom with opengl or vulkan.
 
I'm using the lastest version 5.3.11.