Download: GeForce 385.69 WHQL driver

#5474154

Klementh

2017-09-21 19:10

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

#5474158

khanmein

2017-09-21 19:18

Klementh:

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.

#5474181

khanmein

2017-09-21 19:54

Alberto:

@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

#5474270

dr_rus

2017-09-21 22:49

nevcairiel:

But the release date is already known? Its definitely in October. For that matter, 1703 (ie. Creators Update) didn't release until April either.

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.

Emille:

Nvidia can't keep blaming windows....they had an update to fix hdr compatibility and before and after than windows patch the old drivers still have perfect hdr when the new ones do not.

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.

#5474288

BuildeR2

2017-09-21 23:42

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.

#5474292

nevcairiel

2017-09-21 23:55

dr_rus:

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.

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)

#5474299

dr_rus

2017-09-22 00:00

nevcairiel:

Anything else is mostly coincedence.

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.

#5474303

-Tj-

2017-09-22 00:17

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.

#5474307

robertmor52

2017-09-22 00:21

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.

#5474325

volkov956

2017-09-22 02:01

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

#5474330

cricket bones

2017-09-22 02:49

ESlik:

Hey all..When reporting driver results, issues etc. would you please indicate what version of Windows? Win. 7, etc. Some of are still with Win. 7. In my case, I intend to stay with it for a while. Thanks all..

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

#5474351

X7007

2017-09-22 05:00

is the 3D wizard works now ?

#5474353

elite69

2017-09-22 05:41

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

#5474440

khanmein

2017-09-22 11:41

Alberto:

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.

#5474441

alanm

2017-09-22 11:41

Alberto:

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?

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

#5474447

Spax1171

2017-09-22 11:56

robertmor52:

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!!

No problem here. Work fine.

#5474454

robertmor52

2017-09-22 12:25

Spax1171:

No problem here. Work fine.

Thanks mate, after repairing it works fine, even much faster than before but at the same time, it looks like BF1 graphics are a bit downgraded? or its just me?...now I can run the game at 260x1080+130% scaling no problems, before only at 120%...are graphics the same? thanks!!

#5474456

Cave Waverider

2017-09-22 12:30

dr_rus:

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.

They can, but they could just as well add an option to use their working HDR solution that works perfectly fine with previous drivers and override the trash Windows solution instead to give users a choice what they use. Perhaps @ManuelG could poke the driver devs to add that option.

#5474468

khanmein

2017-09-22 12:42

Alberto:

My monitor is the LG 27UD68 if is you useful to help me 🙂

http://4k.com/monitor/lg-27ud68-review-4k-uhd-ips-monitor-with-freesync-lg-27ud68-w-lg-27ud68-p/ http://www.tftcentral.co.uk/icc_profiles/lg_27ud68_user.icm http://www.lg.com/us/support-product/lg-27UD68-P FreeSync monitor?

#5474483

dr_rus

2017-09-22 13:35

Cave Waverider:

they could just as well add an option to use their working HDR solution

This will likely prevent them from receiving WHQL certification. Such option would actually break WDDM 2.2 driver design rules. So again, while possible in theory, it's up to MS to allow it.