Home / Software & Gaming / Drivers / Nvidia rolls out beta driver 364.51 following widespread issues

Nvidia rolls out beta driver 364.51 following widespread issues

Yesterday, Nvidia launched a new ‘Game Ready' driver for Tom Clancy's The Division, Hitman, and Need for Speed, all of which come out this month. Unfortunately, those who were quick to install it started facing some serious issues including crashes, boot loops, blue screens, black screens, basically every problem you don't want to run into after updating your drivers.

After sifting through feedback yesterday, Nvidia's engineers seem to have identified the issue, which caused a fault with the install process while performing an ‘Express Installation' rather than a completely clean install.

game-ready-drivers-e1446731499478

Following on from that, today Nvidia launched beta driver 364.51, which should solve the issues. However, it is waiting for WHQL approval at the time of writing.

So if you installed driver 364.47 yesterday and have been having severe issues since, then this beta driver should help. Since it isn't WHQL certified, you will need to grab it from the GeForce website manually rather than from the GeForce Experience. You can find the driver, HERE. 

KitGuru Says: It is always a shame when this sort of thing happens, especially when there are big game releases that people want to play. Did any of you install driver 364.47 yesterday? Has the new beta release fixed things for you?  

Become a Patron!

Check Also

Nvidia driver update fixes crucial security vulnerabilities

Nvidia GeForce, RTX, Quadro, NVS and Tesla GPU users will want to update their drivers soon. Nvidia has pushed out a hotfix with a number of critical security fixes that if left unfixed, could allow for unauthorised access to systems. 

6 comments

  1. I installed 364.47, it was fine for me. The problem came when I went to uninstall it, got a bsod followed by a restart loop. Ended up needing to jump through safemode hoops to get it cleaned out properly with DDU.

    So fat 364.51 seems alright, though performance is questionable. Doesn’t seem as good as the 35x.xx releases for most games.

    The one nice thing these drivers offer is the ability to use SLI, G-Sync and DSR all simultaneously, something that couldn’t be done before (on a g-sync monitor, DSR was locked out completely with sli enabled for some reason). So that’s nice.

  2. Stretford End Gaz

    Yep got me this morning, been having no end of problems, that have without too long a story involved no less than 8 full system repairs , complete reinstall in end found that for some reason when i repaired my OS ( windows 10) as soon as installed bit defender it will then reboot and stick in a loop of “operating system requires repair”, in end i had to give up ghost and completly flatten my C: and reinstall from scratch

    But I installed this driver this monring and suddenly bang black screen with flashing lines, so just went and plugged monitor into MB and took power out of GPU that give me the time to then install an older driver, so no major ball-ache (well not considering other problems i have had today)

  3. José Fernandes

    Just want to point Out that if this was a amd problem All hell would break lose

  4. I’m having issues with the 364.51 release. I’ll wait till the next one. Installed 362.00 without issue. Can’t afford downtime.

  5. I installed 364.47 non-express. It was my first Nvidia update after initial install on a recently rebuilt computer that has been running AMD/Radeon for the last decade. Had only had Windows installed maybe 10 days, and apparently I had improperly configured Windows Restore. This drier put me into a boot loop that would not even let me access Safe Mode. Long story short, I tried every single option available to me until finally resorting to reinstalling Windows. The only saving grace in this fiasco was that I had thankfully configured almost all of my data to run on a non-OS drive, so while I had to reinstall every program, I lost very little data of significance. Was still a lost day of business (this is my home-work machine) and a lot of stress, but it didn’t cost me too much in the end.

  6. went through literally the same exact things
    i have just enough time to comment while i’m deleting my windows.old folder