The latest version of Nvidia’s GeForce driver is 355.82, and both the Game Ready and Windows 10 versions have been WHQL certified. Nvidia said that using this driver will deliver the best possible experience in both Metal Gear Solid V: The Phantom Pain and Mad Max.
The driver update comes just in time, as these games are both set to release tomorrow, and with digital downloads being the preferred delivery platform for many gamers, having the driver installed ahead of time means you’ll be up and running as soon as possible.
GeForce Experience will prompt you when the driver is ready, but many people will often ignore the updates. If you’ve ordered a copy of either of these two games, you might want to do yourself a favor and check for updates.
Stay on the Cutting Edge
Join the experts who read Tom's Hardware for the inside track on enthusiast PC tech news — and have for over 25 years. We'll send breaking news and in-depth reviews of CPUs, GPUs, AI, maker hardware and more straight to your inbox.
Kevin Carbotte is a contributing writer for Tom's Hardware who primarily covers VR and AR hardware. He has been writing for us for more than four years.
what about directx12 performance? what about ashes of the singularity fiasco?Reply
I dont think they will give an update for that, their hardware is limited without async shaders.Reply
Does anyone know if this driver update fixes the gtx 970/980 bug when connecting to a monitor via display port?Reply
Up to 6 pages now. Adds a 'debug' mode in control panel for factory overclocked cards that may be having issues. It appears to have the Win 10 x64 SLI memory leak hotfix included from 355.80.
Skimming over it, it appears to be a pretty decent release for more than just the games listed.
16554542 said:Does anyone know if this driver update fixes the gtx 970/980 bug when connecting to a monitor via display port?
Interesting. I've never heard of that one.
Neither have I. I've read and participated in an awful lot of related threads but haven't seen anybody mention that particular issue.Reply
16556426 said:Neither have I. I've read and participated in an awful lot of related threads but haven't seen anybody mention that particular issue.
It took me a while to figure out what was going on and a bit of google searching. There are a few other people having the same issue.
After upgrading to Win10 and getting 355.60 after that, everything was fine at first. When I turned on my computer again - I was able to log in okay, but had my computer mostly freeze once the desktop appeared. It would take multiple manual restarts to be able to use my computer normally (and usually a WDF_Violation). Other times my main monitor wouldn't even turn on. I discovered, after unplugging and replugging my displayport cable, my computer would sometimes work. A few times my main monitor would be locked into a 640x480 resolution.
Long story short, the best solution I found was, when turning on my computer (sleep, hibernate, cold boot), to turn off my displayport (main) connected monitor and leave it off for 10-30 seconds after my computer goes to the log-in screen. No problems since implementing that. It's pretty annoying though. I don't have a spare HDMI or DVI cable lying around so that's what I've got to do.
I have a 580 still until i finish my build on skylake. The new drivers cause overheating. rolled back to .60 and everythings fine again.Reply
16554496 said:I dont think they will give an update for that, their hardware is limited without async shaders.
You are wrong! I checked and nvidia has supported async shaders since 2012 called hyper-q! they are actually faster in shading/compute. Also more recent testing of nvidia's and amd's latest cards have shown both support async shaders though AMD has double that of nvidia's..http://www.pcgamesn.com/relax-nvidias-maxwell-gpus-can-do-dx12-asynchronous-shading-after-all