Nvidia GeForce driver 364.47 causing errors

Multiple users across the internet are reporting that GeForce drivers version 364.47 are causing serious issues, from black screens during gameplay to BSOD on Windows. It seems that the issue is related to express installation only. Nvidia have since pulled the guilty driver and have released 364.51. It is highly recommended that you upgrade to this driver immediately if you're running 364.47.

​Nvidia released this information on their forum:

---

UPDATE: After finding a critical installation issue, the team has replaced yesterday’s driver (364.47) with today’s new driver (364.51). 

This driver has been submitted to Microsoft for WHQL-approval and we will update the driver package online as soon as we have the certified package.

We had received reports of some users having issues installing driver version 364.47.  Initial investigation suggests the issue was related to doing an "Express" installation.  If you happen to have a pending installation of 364.47, we recommend that you do not install it and either use the new 364.51 beta version or wait for the WHQL certified version.

Issues and Updates

7:30AM 3/8/16
After finding a critical installation issue, the team has replaced yesterday’s driver (364.47) with today’s new driver (364.51). This driver has been submitted to Microsoft for WHQL-approval and we will update the driver package online as soon as we have the certified package.

4:00PM PST
We have reproduced the issue and our engineers continue to debug it. Initial investigation suggests the issue is related to doing an "Express" installation. We suggest those willing to try this driver use a Custom -> Clean Install installation.

9:30AM PST
We have received reports of some users having issues installing today’s Game Ready Driver. Initial investigation suggests the issue is isolated to multiple-monitor configurations. 
Should you experience issues, you can either disconnect one monitor during the driver installation (and reconnect once completed) or you can uninstall the driver through Windows Safe-Mode and revert to a previous version. Our driver team is actively investigating the issue and we will have more information shortly.