http://www.nvidia.com/download/driverResults.aspx/109256/en-us
DriverVer = 10/21/2016, 21.21.13.7563
-The start menu freeze while moving apps is fixed
Release Notes
Game Ready Drivers provide the best possible gaming experience![]()
![]()
for all major new releases, including Virtual Reality games. Prior to a new title launching, our driver team is working up until the last minute to ensure every performance tweak and bug fix is included for the best gameplay on day-1.
Game Ready
Provides the optimal experience for Battlefield 1, Civilization VI, and Titanfall 2
Game Ready VR
Provides the optimal VR experience for Eagle Flight and Serious Sam VR: The Last Hope
-
Spartan@HIDevolution Company Representative
-
Spartan@HIDevolution Company Representative
i_pk_pjers_i, Papusan, killkenny1 and 3 others like this. -
i dont think they forgot i think now you have to download it yourself no more gfe in drivers
-
-
killkenny1 Too weird to live, too rare to die.
i_pk_pjers_i, sasuke256, Papusan and 4 others like this. -
-
giving these drivers a try cos i am getting BSODs in BF1.
i_pk_pjers_i likes this. -
saturnotaku Notebook Nobel Laureate
-
Unusual OS GUI glitches that weren't occurring with 372.54 but performance seems to be decent, still testing further.
i_pk_pjers_i likes this. -
i_pk_pjers_i Even the ppl who never frown eventually break down
This is going to be a long post, so buckle in and enjoy the ride on i_pk_pjers_i's wild adventure.
It all started at 10:38PM on a Tuesday. I had just woken up from a slumber, and went on my desktop computer as usual. However, something was wrong, something was different... I had noticed that my NVIDIA Control Panel was gone from the right click menu on my desktop, and I thought that was weird. The only time I have ever had that happen was when I had a hardware issue on one of my old laptops. I tried opening up NVIDIA Control Panel from the start menu, but it was no good - it crashed with nvcpl.dll being the faulting module.
I rebooted my computer, and I was greeted with... nothing. My computer had its regular 1 post beep (because I forgot where on my motherboard the BIOS speaker is, and I was too lazy to remove the BIOS speaker), followed by a blank screen. I thought to myself that this may be quite a long night, and I wasn't entirely wrong. I powered off my computer for 30 seconds with the power supply turned off, and tried again. No good, the blank screen happened again. I tried flicking the vBIOS switch on my GPU since it had two, no good. I tried plugging my GPU into a different PCI-E port on my motherboard, but it was still no good. I still had a blank screen after the 1 post beep. I also randomly experienced multiple post beeps and a D6 POST code which had indicated "NO VGA" as per my motherboard manual.
I tried a different graphics card that I knew was working and good in both the main and alternate PCI-E port, and it did not work. "Uh oh", I thought to myself. I tried a CMOS reset, and it did not help. I wasn't entirely sure what to do next, and I believed it to be my motherboard. I sat down in a panic, and tried to gather my thoughts.
I decided that I would not use DisplayPort for my monitors, and I would try HDMI instead. Success!! I managed to get output on one of my monitors using HDMI, and also the other monitor when I individually tried both of them since I only had one HDMI cable. I tried using only DisplayPort cables again, and it did not work. This was unlike anything I had ever seen before.
I decided to try booting into Windows using an HDMI AND DisplayPort cable, and lo and behold it did actually manage to work for both monitors. I decided that it was time to uninstall my driver 375.63 and try going back to my known good working driver 373.06. I tried a clean install, and rebooted. Uh oh. NVIDIA Control Panel was gone once again. I rebooted, and tried another clean install. Still no good. I needed a different approach.
I had decided to try and give DDU a shot, I hadn't used DDU to install 375.57, or 375.63, or 373.06. I used DDU to uninstall my potentially corrupt driver, and then installed 373.06 after DDU had done its job. I then switched out the HDMI cable with a DisplayPort cable. "Yes, it works!!!", I shouted (I actually did). I switched my GPU back to the primary PCI-E slot, and it worked yet again. That was the end of my adventure... or was it? I started up Battle.net launcher because I wanted to play Overwatch with a friend (no, not Dovydas for you RuneScape players) and I was greeted with yet another blank screen. I screamed a little bit, but then I quickly realized it was just UAC asking if I wanted to give administrative privileges to Battle.net launcher for the update. I clicked yes, and Overwatch ran just fine. I had no issues after that. Everything was fully working exactly two hours after this nightmare began.
Well, that's the end of my story. The moral of the story is don't do NVIDIA drivers newer than 373.06, kids. Not even once.Last edited: Oct 26, 2016tribaljet likes this. -
-
i_pk_pjers_i Even the ppl who never frown eventually break down
-
i_pk_pjers_i likes this.
-
I've had these installed on my 2013 Alienware 17 with a 970m in it, modded driver inf myself with no issues so far for a couple days. Played Overwatch, Battlefield 1, and WoW for several hours.
nVIDIA GeForce Drivers v375.63 Findings & Fixes
Discussion in 'Gaming (Software and Graphics Cards)' started by Spartan@HIDevolution, Oct 23, 2016.