Not even a week has passed and we have another driver update from NVIDIA. Despite the quick turnaround this is not a rushed released. Indeed, we have some heavy hitters found in a good number of fixes, a relatively large number of game ready updates, and even official Vulkan support.

This driver update introduces the 364 driver branch and NVIDIA has issued several bug fixes this time around. Among them including a crash in Assassin’s Creed Syndicate when ShadowPlay is enabled, a system hang during installation, crashing in Adobe Illustrator CC 2015, and a problem with the Twitch broadcast game title not matching Twitch’s game library. With all these fixes though, it is important to note that some users are reporting this driver update crashing their systems. Due to this issue a clean install is recommended even more so than it usually is.

Update: 03/08: NVIDIA has posted a new beta driver, 364.51, that is reported to resolve the earlier driver's installation issues.

Meanwhile for game-specific updates, this driver brings performance and compatibility updates to Tom Clancy’s The Division, Hitman, Need for Speed, Ashes of the Singularity, and Rise of the Tomb Raider. Alongside the list game ready updates NVIDIA has provided SLI profiles for Hitman, The Technomancer, and Zui Shong Bing Qi (Ultimate Weapon).

Lastly, but possibly the biggest news of this update is that with the switch to a new driver branch, Vulkan support has moved out of beta and is now in NVIDIA's mainstream drivers. We looked at Vulkan just last month as implemented in The Talos Principle, and though it's merely proof of concept at this point, it represents significant progress in Vulkan development. However while we're talking about API support, this latest driver branch still doesn't have DirectX 12 support for NVIDIA's Fermi architectre, though as we've seen it working in developer drivers it should still be on its way.

Anyone interested can download the updated drivers through GeForce Experience or on the NVIDIA driver download page.

Comments Locked


View All Comments

  • archon810 - Tuesday, March 8, 2016 - link

    I'd recommend either staying away or getting your safe mode ready for this build

    The best strategy seems to be a full uninstall first, then a clean reinstall.

    I was afflicted myself
  • DabuXian - Tuesday, March 8, 2016 - link

  • Gigaplex - Tuesday, March 8, 2016 - link

    My brother was affected too, and it refused to enter safe mode.
  • hechacker1 - Tuesday, March 8, 2016 - link

    Um yeah, stay away from this driver. I have 2 monitors, and now i'm getting TDR driver crashes while just browsing the web. Might be related to youtube/video acceleration.
  • Breit - Tuesday, March 8, 2016 - link

    "Despite the quick turnaround this is not a rushed released."

    I'm not so sure about that. A lot of people have severe problems installing this, including me. I can't get my head around the fact that this even passed WHQL?! Is this WHQL merely a label you have to pay for these days without any further testing involved?
  • bikal adhikari - Tuesday, March 8, 2016 - link

    It seems to be exactly that! I am happy with my 353 drivers. Most stable I have found yet.
  • jasonelmore - Tuesday, March 8, 2016 - link

    It's a dual monitor bug that only happens when installed though GFE. Nvidia has since pulled the driver from GFE, and has fixed the problem, and submitted the fixed driver to microsoft for WHQL Certification.. We are now just waiting for microsoft to certify.

    If you don't want to wait, Nvidia has posted a Beta driver on, that is the exact same driver waiting for certification.
  • Khenglish - Tuesday, March 8, 2016 - link

    That's what WHQL has been for a decade. All it means is MS did some basic testing for memory leaks and some other possible OS issues. The only difference WHQL makes to nvidia is if they paid for the testing or not. For video drivers always ignore whql and just get the latests beta. There is no stability differnece on average
  • bug77 - Wednesday, March 9, 2016 - link

    I didn't have a chance to look at 364.47, but 364.51 that replaces it is actually marked as beta...

    Either way, it's been posted to death that WHQL is merely a verification that the driver conforms to some APIs, not a verification of functionality (remember how many WHQLed drivers used to wreak havoc on VIsta?).
  • testbug00 - Wednesday, March 9, 2016 - link

    WHQL means of is it compatibly with The Windows versions it says it is and Microsoft backs that claim up.

    It means absolutely nothing for stability.

Log in

Don't have an account? Sign up now