GeForce 388.59 WHQL driver download
Click here to post a comment for GeForce 388.59 WHQL driver download on our message forum
X7007
Any BF1 Dolby Vision and HDR10 works fine with this drivers ? I can't get Dolby vision to work. It says black screen and I can hear the game music. HDR10 worked before but now it doesn't work after trying the Dolby Vision.... don't understand what is going on. COD WWII works fine with HDR10, Movies also works HDR10. for my friend Dolby Vision works. I'm not sure if it's Windows, the game, TV firmware. he has LG OLED B6 5.30 version , I have LG OLED C6 4.31.0 . Same windows for both of us 1709.
Cave Waverider
I've noticed some noticeable performance degredation in some games (-20 FPS) as well as blue screens (IRQ less than equal, oddly enough there are no crash dumps/logs so I can't analyze what exactly caused it) on all four Systems in the household which we haven't had any before (Titan X (Pascal), GTX 1080 (Notebook), GTX Titan X (Maxwell), GTX 1060 6GB) on Windows 10 64 bit 1709 since installing these drivers. They seem to happen after playing various games for a couple of hours. Could be that the latest Windows Update is to blame, too, but the drivers and that was the only thing that got installed, thus one of them is likely the culprit. I've now moved back to 388.43 which have been stable before, so we'll see.
X7007
Anyone BF1 works with HDR10 and Dolby Vision ? because for some reason it worked with HDR10 , and after trying Dolby Vision which got me black screen but music on the background, alt + tab worked , when trying again now both aren't working, TV signal doesn't get HDR or Dolby vision . I think the drivers are screwed or something , cause there is no other reason it will stop working
Webhiker
dr_rus
Today's patch fixed performance issues which ROTTR had since the previous one.
TheDeeGee
Seems like a fine driver, no issues.
(running 1703)
Susahamat
Amigafan35
Chastity
How many fps does the NV h265 convert at vs Handbrake?
X7007
No one is using 388.59 or 388.43 with laptop 9xx series or 1000x series ? with 388.31 everything is fine but with the others I have artifacts in movies MKV 1080p and also in youtube. all with hardware acceleration . using Potplayer + MadVR Renderer so it's like using the GPU for gaming but for Videos best quality . Using other Renderer doesn't have the issue , but still youtube has the issue.
It happens in youtube when you pause the video in many places there are colourful dots everywhere like memory artifacts . but games runs fine, but not the best also , it feels like it has reduced fps and higher lag input then 388.31 .. so something is screwed with those drivers... so hate nvidia, how can they not test laptops with youtube videos ??
Also my friend with laptop ASUS ROG G752VS 1070m series have the same issue in Youtube, he doesn't use MadVR but I'm sure it will happen to him there too.
I have Asus ROG G751JT Series 970m
it is visible more or only on HD quality and not 4K . so make sure to check those kind of videos
for example
[youtube=NUjMO_k9IF8]
No one notice it for the both drivers ??! nvidia just doesn't know about this ???
Mufflore
Cave Waverider
Exostenza
Dragondale13
X7007
Xtreme512
latest is not the greatest. 388.43 is still the king so far after 385.69. i can find lot of people agreeing on this.
Rolacka
Oculus are telling people to use this driver for the rift as newer ones are causing issues.
https://forums.oculusvr.com/community/discussion/62069/black-screen-on-rift-be-sure-to-use-nvidia-driver-388-59
"We are currently investigating an issue affecting Nvidia card users on newer driver versions and the latest Oculus app. If you have an Nvidia GPU, please be sure to install Nvidia driver 388.59 or you may experience black screens or other compatibility issue. Thanks."
Quick update on this issue, ManuelG has said on the nvidia forums that this bug has been found now & fixed & it will be in the next driver release.
https://forums.geforce.com/default/topic/1039358/geforce-drivers/requesting-end-user-assistance-with-vr-black-screen-issue-after-pc-has-been-on-for-extended-period-/post/5306456/#5306456
This issue is now fixed in the 391.24 drivers 🙂