Download: Nvidia GeForce 387.92 WHQL driver

Published by

Click here to post a comment for Download: Nvidia GeForce 387.92 WHQL driver on our message forum
https://forums.guru3d.com/data/avatars/m/227/227994.jpg
thesebastian:

I hope they fix the issue I have with the NVCP, sometimes it disappears until I reboot the PC. Already tried to clean all gpu drivers in safemode, etc.
Sounds like your OS is messed up. NVCP works just fine.
https://forums.guru3d.com/data/avatars/m/260/260048.jpg
All works nice and smooth. Nothing to report.
https://forums.guru3d.com/data/avatars/m/269/269416.jpg
Why is there never a mention about the drivers being for 800 notebook series?
https://forums.guru3d.com/data/avatars/m/174/174022.jpg
Memorian:

GPU-z reports SM 5.1, not 6.0
GPU-Z reads data from its own database which is updated manually. D3D12CheckFeatureSupport tool (above) reads the info from D3D interfaces, like any game would.
https://forums.guru3d.com/data/avatars/m/252/252171.jpg
madvr is not working for me with this driver.
https://forums.guru3d.com/data/avatars/m/238/238369.jpg
sayem57:

madvr is not working for me with this driver.
madVR 0.92.5 updated today, try it.
https://forums.guru3d.com/data/avatars/m/252/252171.jpg
LocoDiceGR:

madVR 0.92.5 updated today, try it.
Updating doesnt solve the problem. Found the solution. deselecting "use Direct3D 11 for presentation" solved the crash issue for me.
https://forums.guru3d.com/data/avatars/m/238/238599.jpg
Memorian:

Creator's Update doesn't support WDDM 2.3. You need to install the new version of Win10(Fall Creator's Update) build 16299.15
Yeah, I know right, but I thought @skizzo using v1703.
https://forums.guru3d.com/data/avatars/m/238/238599.jpg
sayem57:

madvr is not working for me with this driver.
Read
https://forums.guru3d.com/data/avatars/m/174/174022.jpg
So far the driver seems to be slower than R384 releases (on 1703). In fact, it's the slowest one in Gears4 benchmark here since the game's release.
data/avatar/default/avatar28.webp
Finally (and this time I double-checked) the color issues in fullscreen exclusive mode in some DX11 titles have been fixed with this new driver (I am on Windows 10 16299.15). Also the colors on the desktop are as expected. MSI mode does work as well, hence it seems to be the first WDDM 2.3 driver which I am quite happy with so far.
https://forums.guru3d.com/data/avatars/m/238/238599.jpg
ms178:

Finally (and this time I double-checked) the color issues in fullscreen exclusive mode in some DX11 titles have been fixed with this new driver (I am on Windows 10 16299.15). Also the colors on the desktop are as expected. MSI mode does work as well, hence it seems to be the first WDDM 2.3 driver which I am quite happy with so far.
The color issue is related to Microsoft.
data/avatar/default/avatar10.webp
In my case with previus 385.41 temps in idle stay in 40/41 gradius with this version up 43/44. Greetings.
https://forums.guru3d.com/data/avatars/m/174/174022.jpg
Some gains in The Division DX12 renderer, DX11 is the same. Could be due to the 1.7.1 patch though. Edit: Scratch that, no gains in either DX12 or DX11, likely made some minor mistake with in-game's settings. It also looks like these drivers are disabling 1703 exclusive fullscreen optimizations for all games, even compatible ones. I don't see Game Bar appearing in any of the titles I've launched.
data/avatar/default/avatar04.webp
With 387.92 I have much worse input lag than with 387.78.
data/avatar/default/avatar20.webp
khanmein:

The color issue is related to Microsoft.
Well, you might be right but these issues were not present with older NVidia WDDM 2.2 drivers on the same Windows 10 build. But as long as it is fixed, I really don't care who the responsible party was.
data/avatar/default/avatar27.webp
Things will become more interesting with SM 6.1... (you can try query the related interfaces under experimental mode with the fall creators update sdk).