FAQ
TL;DR: GTX 1060 users report Nvidia driver 397.31 install issues; four board partners were named. "Mine from Gigabyte works fine." [Elektroda, andrzej55, post #17190043]
Why it matters: This FAQ helps GTX 10‑series owners fix 397.31 install loops, Code 43, missing Control Panel, and GFE issues.
Quick Facts
- Common symptom: Code 43 and a post-restart prompt to reinstall 397.31 on GTX 1060 systems. [Elektroda, rzymo, post #17189982]
- Reported affected AIBs: PNY, Palit, Gainward, Zotac; one Gigabyte card worked fine. [Elektroda, andrzej55, post #17190043]
- Clean fix path: Use Display Driver Uninstaller (DDU), remove all "NVIDIA", restart, then reinstall drivers. [Elektroda, rtj71, post #17189050]
- GeForce Experience can push the newest driver, blocking rollbacks to older versions. [Elektroda, stalker2000pl, post #17189131]
- Not just 1060: a GTX 1080 user also hit issues; wait a few days before updating. [Elektroda, rzymo, post #17190064]
What’s going on with Nvidia driver 397.31 on GTX 1060 3GB?
Users reported failed installs on GTX 1060, showing Code 43 and a reinstall loop after reboot. The advice was clear: "Users of GeForce GTX 1060 should wait for the hotfix." These symptoms indicate the driver package fails to initialize the GPU properly. [Elektroda, rzymo, post #17189982]
How do I cleanly remove and reinstall Nvidia drivers?
Use DDU and reinstall.
- Run Display Driver Uninstaller and remove all entries named “NVIDIA”.
- Restart the computer when prompted.
- Reinstall the Nvidia drivers cleanly from your chosen package. [Elektroda, rtj71, post #17189050]
Why does Device Manager show Code 43 after installing 397.31?
Code 43 appears when the device is suspended due to a failed driver initialization. After reboot, a dialog may ask you to force a driver reinstall. This loop matches the 397.31 issue pattern on GTX 1060 systems. [Elektroda, rzymo, post #17189982]
GeForce Experience keeps forcing the latest driver. How can I stop that?
A participant put it simply: don’t install GeForce Experience during troubleshooting. Skipping GFE stops the auto-push to the latest package and reduces reinstall prompts. Revisit it only after stabilizing your driver. [Elektroda, sylweksylwina, post #17189167]
Does GeForce Experience force 397.31 over older drivers?
Yes. The thread author noted GeForce Experience imposes the newest driver, hindering tests of older packages. Avoid launching or installing GFE when you want to hold an older, stable driver. [Elektroda, stalker2000pl, post #17189131]
Which board partners were reported affected?
PNY, Palit, Gainward, and Zotac were named. One user’s Gigabyte card worked fine. That’s four vendors implicated, highlighting AIB variance with 397.31. This helps scope troubleshooting expectations by brand. [Elektroda, andrzej55, post #17190043]
Is a GTX 1080 also affected by 397.31 issues?
A user reported a broken setup on a GTX 1080 as well. Their takeaway: "do not install everything new as it goes, just wait a few days." Delay updates until feedback confirms stability. [Elektroda, rzymo, post #17190064]
My fans ramp at idle after trying 397.31. Is that related?
A user observed fans running hard at zero load, like a 4K benchmark. They suspected a transient condition during the problematic driver attempt. Treat it as a symptom while you stabilize drivers. [Elektroda, stalker2000pl, post #17189878]
Should I try older drivers instead of 397.31?
Yes. Install an older, stable package while waiting for a hotfix. One helper suggested using an earlier driver when the latest appears broken. Test stability before updating again. [Elektroda, rtj71, post #17189126]
Should I mix old and new driver components?
No. A participant considered combining versions but questioned the value: it likely lacks benefit. Focus on fully testing a known-good older package instead. [Elektroda, rtj71, post #17189190]
Do I need to reinstall Windows to fix this?
One user formatted and then used their board’s older drivers. They reported the problem matched the known symptoms and was resolved afterward. This is a heavier, last-resort path. [Elektroda, stalker2000pl, post #17190261]
Why is the Nvidia Control Panel missing or unusable during this issue?
The thread author removed everything "to zero," including the Control Panel, while chasing the install loop. The loop prevented proper configuration afterward. Stabilize drivers first, then restore the Control Panel. [Elektroda, stalker2000pl, post #17189022]
Why does it say “restart required” but nothing changes after reboot?
This is part of the loop: after reboot, a dialog demands reinstalling the drivers again. It aligns with the 397.31 failure pattern documented for GTX 1060 systems. [Elektroda, rzymo, post #17189982]
Are all Gigabyte GTX 1060 cards unaffected?
Not guaranteed. One user’s Gigabyte card worked fine, but others reported issues on different brands. Treat that as a single data point, not a rule. [Elektroda, andrzej55, post #17190043]
Should I install new Nvidia drivers immediately on release?
A user advised caution after hitting issues: "do not install everything new as it goes, just wait a few days." Waiting helps avoid regressions. [Elektroda, rzymo, post #17190064]
