Windows 8 and Nvidia driver 310.70 problem


Recommended Posts

Installed Windows 8 Pro and everything was fine until I downloaded and installed Nvidia Drivers v310.70 and now everything turned into crap. The PC booted and the screen is black. Had to re-install Windows 8 again but this time I did not update the drivers.

Anybody else experienced this?

My video card is the Nvidia GTX 570.

I see others seem to have this issue as well:

http://www.tomshardware.com/forum/2745-73-windows-nvidia-driver-problem

http://www.google.com/search?client=ubuntu&channel=fs&q=Nvidia+Windows+8+driver+issues&ie=utf-8&oe=utf-8

http://nvidia.custhe...display-drivers Either reboot the computer a few times after installing Windows 8 before installing the latest nVidia drivers or don't have your computer connected to the network so it can't grab drivers from Windows Update.

Interesting. Thanks!

Just ran in to this last night (long story on why I rebuilt, it was my fault). I was able to boot to Safe Mode, install the drivers again (PhysX is not available in Safe Mode). To get to Safe Mode on Win8 hold Shift and hit F8 a bunch of times, when you get to the menu it's option 4 for Safe Mode w/o Networking.

Today I ran the installer again and was able to install PhysX stuff.

  • 3 weeks later...

I am also having similar issues with ASUS GTX 660 Ti-OC. I have done multiple re-installs for refreshing & resetting of Windows 8, both with internet turned off/on. But everytime I re-installed nVidia drivers, before & after Windows Updates, never during, Windows 8 will fail to load.

There are 3 lots of Microsoft Updates to date, and after each Update I was able re-start my PC perfectly. These are all excluding the Microsoft nVidia update. When there are no more Updates, I restart the PC again just to be sure before installing nVidia drivers. Every version of the drivers makes Windows 8 hang at the loading screen. Sometimes I can move my mouse around, sometimes it is just a blank and or flickering screen.

So I tried installing nVidia drivers before any Windows Update (internet off), nVidia Drivers v306.23, v306.97, v310.70) worked fine. These are the first re-starts after installation. If I try to re-start a second time, or attempt to install v310.90, the blank screens comes back.

Also note that v310.70 & v310.90 seem to "crash" during installation. The screen would flicker and show my desktop. All I can see is the task bar, but none of the windows pop up when I click on the icons even though I can see them in the preview panes. Windows button does nothing, I can only move my mouse around, and closse the power-off / restart option.

CPU: Core i5-3570K

GPU: Asus GTX660 TI-DC2O-2GD5

MoBo: Asus P8Z77-V

Memory: 8GB DDR3 1333

HDD: Seagate 2TB SATA3

SSD: Samsung SATA3 120G SSD

ATX: Coolmaster RC-371

PSU: Corsair CMPSU-500CXV3 500W

I have Windows 8 Pro installed in bootcamp on my 2010 MacBook Pro (only system I have it on at the moment, also the only one with a nVidia GPU), and 310.70 caused my system to crash pretty much repeatedly within a minute or so of booting up (sometimes it wouldn't even boot fully). Once I was able to get into safe mode, I uninstalled them and went back to 310.64 for a little bit, but those became unstable as well. I installed 310.90 the other day, and so far have had good luck with them. They're stable now for the most part. Can't really comment on performance (I still need Apple to update bootcamp drivers, so a lot of things don't work correctly).

I suggest going into bios and changing the PCI default from Auto to Gen3. If it's a newish motherboard, leaving it at default can cause the incorrect voltage therefore giving the black screen as it (The graphics card) doesn't have enough power to output the display.

This topic is now closed to further replies.
  • Posts

    • Server Summit had a heap of announcements, ADCS changes are baller.
    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
    • Windows 11 KB5094126 BSODing, freezing, forcing BitLocker lockout, breaks OneDrive, and more by Sayan Sen Microsoft released Windows 11 KB5094126 and KB5093998 last week as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. While Microsoft has so far not acknowledged any major problems with the release, some users online are running into problems. These range from OneDrive and Dropbox access issues, BitLocker recovery lockouts, to blue screens and BSODs. The most common one seems to be happening with HP systems wherein affected users say they hit 0xc0430001 BSOD (blue screen of death) error code after the KB5094126 update. We wonder if this could be related to the recent bug we covered on HP devices wherein the ongoing Secure Boot certificate updates are leading to similar issues. While we are not certain, users affected by this issue likely need to ensure that the boot.stl file is included on the installation media (such as a USB installer or ISO), if the above-mentioned dynamic updates are deployed. If this file is missing, computers may fail to boot from the installation media and could display the error 0xc0430001. This STL file is used by Secure Boot to verify that the boot files are trusted, so it must match the same Windows version and system architecture. To ensure the file is included, Microsoft recommends using the Update WinPE script, which automatically updates the image and handles the required files. Alternatively, you can manually copy the boot.stl file from the Windows\Boot\EFI folder on a Windows device and place it in the matching folder on your installation media before deploying the updated image. Aside from blue screening some users also note their systems have been freezing following the update. This could be happening to Lenovo PCs specifically. In the case of the OneDrive and Dropbox access issues, a user figured out that there could be a conflict with UAC. He explained: "Okay, so I did some digging, and in our environment KB5094126 breaks OneDrive and Dropbox in Explorer. I went through all our GPOs and found out that the combination of disabling UAC and having my user being a local admin breaks OneDrive in Explorer. ... If I enable UAC again, then it works, even with KB5094126 still installed." Hopefully, Microsoft will look into these issues. Source: Microsoft forum (link1, link2, link3, link4), Reddit (link1, link2, link3, link4)
    • It is when it's a desktop in my house though for a PC that's lightly used and not really important when it is. If it was a laptop, it would be a different story. The real solution is varied and begins starting at post #22 in that thread.
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!