GeForce 385.69 - WHQL driver Download & Discussion

Ive had problems installing these ,3 failed attempts where as the installer can't find any compatible graphics adapter so ive ran DDU in safe mode and after two more reboots it has installed and seems to be working normally now , this is on Windows 10 64bit so i don't know if it was a problem with the driver or my O/S or just a bug either way i can't find anything in Windows Event Viewer relating to the failed installs attempts .

 

Shadow mode? What is? If I perform a clean install of Windows , Vulkan api don't install on my pc?

 

Worked fine for me, tho i used DDU and installed the driver after. But i'm on 8.1

 

Fixes a bunch of vulnerabilities: http://nvidia.custhelp.com/app/answers/detail/a_id/4544

 

I suggest don't skip this driver & please kindly update the latest Windows updates too.

 

@khanmein in this driver release there is vulkan api?

 

Yeah, but you can't find the the uninstaller under the Control Panel > All Control Panel Items > Programs and Features but actually is installed.

The files are located in C:\Program Files (x86)\VulkanRT\1.0.54.1

Try running CMD by typing vulkaninfo

 

1703 RTM (the build which eventually went into update system) was released on 20th of March and the Windows 10 ISO/update tool was switched to 1703 on 29th of March.
I expect a similar schedule with 1709 too which means that the RTM build should release between now and the end of September.

That's because the old drivers simply don't support Windows 1703 HDR and use the old NV's HDR solution instead. So, yeah, in fact - they can keep blaming Windows.

 

Anybody able to test out Gears 4? I'm still playing it with a friend and have been forced to stay on 382.xx drivers. Any driver beyond that and I get crashes/freezes/hard locks in under an hour, sometimes ~10 minutes.

 

The official end-user release was on April 11th, which is the date that really matters anyway. Anything else is mostly coincedence. In fact on March 30 they only started testing the "RTM" build in the Release Preview ring, and between then and final "consumer" release, it did actually still change, even if the release number didn't (or it probably even did, appending a digit at the end)

 

Nope. You could've installed 1703 quite officially on 29th of March. 11th was the day they started pushing it into updater but this is tiered so some users got it only in May - does it mean that it was released in May? The fact is, the RTM build was available in March which is what is expected from a version which has "03" in it. Same is expected from 1709.

 

Thanks, 385.41 was ok so far, not completely perfect, had 2 Firefox crashes ,but still ok I guess. Hope this one fixes it for good.

 

After several weeks out of BF1 now I updated the game to the latest version and updated to this drivers (mandatory according to BF1) and now BF1 crashes inmediately after launching it...WTH?¿?¿? any idea why?...thanks!!

EDIT:Looks like it was a problem with BF1, after repairing it works fine.

 

well thats a first for me Driver Not Responding and has to reload driver well thats a first while web browsing

 

Why don't you click a few things and do it yourself?

 

is the 3D wizard works now ?

 

still with 385.41 they are good for me but i will save this ones for later.Thanks for the driver man.

 

I've installed the latest driver on a clean install of Windows but the colors of desktop are slightly washed out... With previous driver release all was fine.
I've got the latest build of Windows 10 CU.
Solutions?

 

Did you install your monitor driver? Did you apply any ICC profiles? Did you set the dynamic range to Full (0-255)?

I installed my Dell driver & use the custom ICC profile from TFTCentral so far so good.

Regarding the color issue, Microsoft fixed the problem.

• The addressed issue where the color profiles do not revert to the user-specified settings after playing a full-screen game.

 

(If high res monitor) check NVCP (resolution tab) Output color = RGB and output dynamic range = FULL. And in windows display settings turn off HDR.