Thursday, April 26th 2018

NVIDIA GeForce 397.31 WHQL Drivers Put GTX 1060-Powered Systems Into Endless Restart Loop

NVIDIA released their latest GeForce 397.31 WHQL drivers yesterday. The new 397.31 drivers came game-ready for recently released titles BattleTech and Frostpunk while also provided support for features like NVIDIA RTX and Vulkan 1.1. However, numerous GTX 1060 owners have reported on the official NVIDIA forums that they were unable to complete the installation of the 397.31 drivers. Users were prompted to restart their systems to complete the installation process, but once they have done so, they were presented with the exact screen over and over again putting their systems into an endless restart loop. While NVIDIA is investigating the bug, GTX 1060 owners are encouraged to roll back to a previous version of the drivers as a stop-gap solution. The workaround consists of rebooting the affected system in safe mode and running Display Driver Uninstaller (DDU) to completely remove the 397.31 drivers. Users can then proceed to install the previous 391.35 drivers normally.
Source: NVIDIA Forums
Add your own comment

43 Comments on NVIDIA GeForce 397.31 WHQL Drivers Put GTX 1060-Powered Systems Into Endless Restart Loop

#1
Gasaraki
Nice... Weird that it only affects the 1060 when the "whole" 10xx line is using the same architecture.
Posted on Reply
#2
ironwolf
There were mentions of at least one 1080 user having issues, not sure how true/confirmed that was.
Posted on Reply
#3
Dave65
Nvidia to busy counting money to put out good drivers, sheesh, get real folks.:laugh:
Posted on Reply
#4
ironwolf
Dave65Nvidia to busy counting money to put out good drivers, sheesh, get real folks.:laugh:
That or they are too busy nuking the GPP haters. :laugh:
Posted on Reply
#5
T4C Fantasy
CPU & GPU DB Maintainer
GasarakiNice... Weird that it only affects the 1060 when the "whole" 10xx line is using the same architecture.
they all have different device IDs

very easy to screw them up xD opps 1c03 was stringed wrong... (1060 6GB)
Posted on Reply
#6
ASOT
Reasons why wait 1-2 week after release...is to make sure all OK!
Posted on Reply
#8
mcraygsx
This should've been reported during Beta. I would love for nVidia to refresh/redesign UI for Control Panel. Hoping to see something new with Version 400 drivers for VOLTA based GPU's soon.
Posted on Reply
#9
MasterInvader
Running my 2º system with a Asus 1060 Dual OC and 0 problems on the installation and games...
Posted on Reply
#10
FreedomEclipse
~Technological Technocrat~
I mean its not like AMD havent had their fair share of borked drivers. Lets not forget the bigger picture here. Both camps have been guilty of letting bugs slip through QC at one point or another.
Posted on Reply
#11
silentbogo
GTX1060 6GB, Windows 10 no issues.
ChinoUsers were prompted to restart their systems to complete the installation process, but once they have done so, they were presented with the exact screen over and over again putting their systems into an endless restart loop.
I'm always selecting a checkbox "Perform Clean Install" in GFE, and was never asked to reboot my PC to complete the installation process. I can make an educated guess that the above issues were observed only Windows 7 PCs.
Posted on Reply
#12
ssdpro
Things like this expose what small operations some of our tech comes from. We all envision complicated labs with armies of engineers. Sometimes it is just a couple guys with a couple cards and it's hanging by a thread. I mean seriously, not one 1060 was tested with this new package? At this point I am curious if the bug is on the NVIDIA side or the MS side. Seems fishy that only 1060s would be affected by the same driver package. My 1070 is fine.
Posted on Reply
#13
Sp33d Junki3
Have 2 GTX1060 on Win without driver install or restart issues.
Same goes with GTX1070 system.
Nvidia likely tested this, but it is end user most times in their system that would cause this.
Posted on Reply
#15
springs113
This is why I always wait to install updates...glad I didn't cause that is my daily driver.
Posted on Reply
#16
trog100
i dont bother with the "must install the latest drivers as soon as they come out ritual" if the ones you have installed are working fine why bother..

trog
Posted on Reply
#17
Arctucas
It warms the cockles of my heart to see nVIDIA adopting Microsoft's policy of 'If it ain't broke, fix it 'til it is'.
Posted on Reply
#18
CandymanGR
I would guess this affects only Win7 systems?
I have also noticed several strange behaviours in some of my clients Win7 systems recently. Maybe some new Win7 update is conflicting with something else, i dont know..
Maybe the drivers are not the real culprit here, if that is the case.

P.S. Win10, GTX 1060, zero problems so far.
Posted on Reply
#19
John Naylor
Is the problem what happens after you install the driver from the nVidia website ... or is it like we have seen so many times in the past, when Windows update reinstalls it ? Have to ask me son if he had any issues.
Posted on Reply
#20
Tomgang
I been on nvidia since gtx 285 where the card to get and since 5 different nvidia gen cards and yes a very few drivers had give me some problems but that is maybe like 5-6 driver over a period of 9-10 years and that is not in my opinion so bad.

For the most nvidia drivers works great for me. Havent tryed the latest driver yet throw.
Posted on Reply
#21
eidairaman1
The Exiled Airman
FreedomEclipseI mean its not like AMD havent had their fair share of borked drivers. Lets not forget the bigger picture here. Both camps have been guilty of letting bugs slip through QC at one point or another.
Yet is strange people in here try to minimize the impact these drivers are causing problems but everyone loses their friggin mind when AMD has a goof.
TomgangI been on nvidia since gtx 285 where the card to get and since 5 different nvidia gen cards and yes a very few drivers had give me some problems but that is maybe like 5-6 driver over a period of 9-10 years and that is not in my opinion so bad.

For the most nvidia drivers works great for me. Havent tryed the latest driver yet throw.
It's been that way for me Except i use Mint Green Arrow=now the Red Arrow
Posted on Reply
#22
Valantar
Fun that these are WHQL certified.


Also, I thought AMD was the only one that ever screwed up a driver. Hm. Almost as if these companies are pretty equal in some aspects. How odd.
Posted on Reply
#23
R-T-B
eidairaman1Yet is strange people in here try to minimize the impact these drivers are causing problems but everyone loses their friggin mind when AMD has a goof.
Don't kid yourself. Certain people lose their mind everytime anyone has a goof.
Posted on Reply
#24
eidairaman1
The Exiled Airman
R-T-BDon't kid yourself. Certain people lose their mind everytime anyone has a goof.
I only try to help users anymore, no matter if they use the Chartreuse Green Eye or Mint Green/Red Arrow, or the Blue Oval.
Posted on Reply
#25
rtwjunkie
PC Gaming Enthusiast
eidairaman1Yet is strange people in here try to minimize the impact these drivers are causing problems but everyone loses their friggin mind when AMD has a goof.
What I find strange are the number of people minimizing Nvidia driver mistakes. I, however, know I have run out of fingers to count the number of bad drivers this organization has put out in the last 3-4 years. There are people in this thread that will remember I have remarked numerous times that Nvidia seems to be trying to give MS a run for their money with releasing bad updates....like they hired some ex-MS employees. Yet today, here we are with minimizing....
Posted on Reply
Add your own comment
May 1st, 2024 21:30 EDT change timezone

New Forum Posts

Popular Reviews

Controversial News Posts