THANKS NVIDIA! /s Crappy drivers freezing my PC


Recommended Posts

I have dual 9000 series in SLI mode. I often sleep the machine overnight. Since installing above 301.xx I will come down may be once a week in the morning to find the machine completely off. Not in a boot loop, just plain off. Powering it back on suggested a bad shutdown due to the start-up repair timeout appearing.

Disabling hybrid sleep mode reduced it to once in 2 weeks

But ultimately either disabling SLI or regressing the drivers seems to be the answer and I haven't seen the problem for over a month now.

Guys.. there are also reports of newer drivers on older cards causing the GPU to run at 100% which is what causes the freezes and shutdowns/reboots. Not only are they not good for your card at all, but maxing it out in 2d isn't all that fun either.

 

Until there is conclusive proof that the issues have been sorted and a WHQL (or non beta) driver has been released, I'm sticking with what works (in my case 311.06).

 

Last point, Nvidia has claimed a number of times that the issues were fixed in drivers prior to the latest one (beta 331.93)? so yeah, I don't feel like being on a constant beta test either.

I've had 2 NVIDIA cards in the past, both were a nuisance because of 3rd rate drivers. Been using ATI since and while they are also not perfect, they are way better than NVIDIA for me!

 

Yeah,

Luckily for me, I'm not a gamer, so graphics aren't totally important for me, as long they work! Usually just use the windows update site for drivers and haven't ever had an issue. Seems the only time I've ever had an issue is when I try to use the Nvidia site for newest ones! Otherwise, never been a huge fan of Nvidia either.

 

Removing the link to follow this topic now, as no need to follow it anymore.

 

Good luck to you folks having issues here! :)

  • 3 weeks later...

v332.21 has been released.

 

Will try them later after a full system backup just to make sure.

Too early to say yet, but I installed 331.93 yesterday (full install, with all the extra crap) and then updated to the WHQL 332.21 drivers, no freezes yet. 

 

GeForce 560 GTX. (coming from 311.06).

 

Edit: Forgot to mention I selected "clean install" when upgrading to 331.93, but not for 322.21. 

 

 
 

 

Aha! those aren't on WinUpdate yet are they. I will keep an eye on the link in the first post because it looks like that person is also looking out for a fix.

 

 

you use windows update for ya drivers wtf.... get em from nvidias website

you use windows update for ya drivers wtf.... get em from nvidias website

No I don't, but if you have Windows Update set to deliver recommended and non/other Microsoft related updates (for Office etc) then you also get NVidia drivers as well...

 

Not everyone is comfortable installing beta drivers, at least the MS delivered ones are WHQL (and usually the latest too). 

Man, I quit following this topic and have been trying to find it again for a bit now. Sure wish the search function on this site actually worked as it NEVER finds anything even remotely close to what I searched for!

 

Anyway,

All I was trying to find is the name of that Nvidia tool, which I had forgotten, http://www.geforce.com/geforce-experience/download

 

Got here just in time to find it on the front page again! :)

Man, I quit following this topic and have been trying to find it again for a bit now. Sure wish the search function on this site actually worked as it NEVER finds anything even remotely close to what I searched for!

Did you search for nvidia from the Hardware Hangout forum? That will be better than doing a search from the forum index which includes all forums.

Did you search for nvidia from the Hardware Hangout forum? That will be better than doing a search from the forum index which includes all forums.

 

Theres a reason nvidia release so many driver revisions cus some screw up some hardware and some fixes things with certain hardware so have to find the best for you and relying on whql isnt good enough. If i relied on whql drivers for AMD GPU i wouldnt of played BF4 for 2 months cus the beta ones fixed the crashing after beta 8

  • 2 weeks later...

I have a system built by Cyberpower with 2 GTX 460's in SLI. I never experienced a problem except with COD:Ghost. But that's not a driver issue as BF4 runs flawlessly. I have used Nvidia since the middle 1990's and rarely had any issues with drivers. I tried a Ati card back in the day and their drivers are what made me switch back to Nvidia. Hope you sort it out soon.

Wow. I had a GT 520. Never had much driver issues with it. Wanted to get a new AMD but ended up with a GTX 760...

 

And i can't even use it.

 

I can play games as high with graphics as left for dead 2. Even though the card runs BF3 at 60fps with everything ultra. But within 30minutes.... everything freezes.

Same for Skyrim, Simcity... anything.

 

Frowny of death :(

 

Tried all driver versions that support my card, from 324 to 332.21. Same issue on everything. Even worse Windows blames my motioninjoy driver :(. But if I unload it from the system, instead of a frowny of death it just completely freezes. Windows tries to restart the driver a few times, sometimes it works. Mostly everything just hangs.

 

F*(#$&(*#$#(* NVIDIA, last F*(#$*(#$ING TIME I GET ONE.

 

Wow. I had a GT 520. Never had much driver issues with it. Wanted to get a new AMD but ended up with a GTX 760...

 

And i can't even use it.

 

I can play games as high with graphics as left for dead 2. Even though the card runs BF3 at 60fps with everything ultra. But within 30minutes.... everything freezes.

Same for Skyrim, Simcity... anything.

 

Frowny of death  :(

 

Tried all driver versions that support my card, from 324 to 332.21. Same issue on everything. Even worse Windows blames my motioninjoy driver  :(. But if I unload it from the system, instead of a frowny of death it just completely freezes. Windows tries to restart the driver a few times, sometimes it works. Mostly everything just hangs.

 

F*(#$&(*#$#(* NVIDIA, last F*(#$*(#$ING TIME I GET ONE.

 

 

That seems to be a different issue rather than this one about 400 and 500 series of cards with the newer drivers. You should do a search on Google for GTX 760 freezing to see if anyone else is having the same problem.

 

Good luck!

I have 2x 670's in SLI and before that 2 580's and before that 8800's. I've always run the latest beta driver and it has never cause a system problem. Maybe you have something else going on.

The new divers don't crash on me. The ones just released this month. :-) Give it a try. :-)

The only issues I have EVER had with the Forceware drivers (and I went from AMD directly to nVidia) have to do with Flash (mostly browsers or software that use Flash Embedded, such as Google Chrome and some game launchers) - otherwise, every version of Forceware since the original Windows 8.1 WHQL has been flawless.  (GPU hardware - factory-refurb nVidia GTX550Ti.)

The only issues I have EVER had with the Forceware drivers (and I went from AMD directly to nVidia) have to do with Flash (mostly browsers or software that use Flash Embedded, such as Google Chrome and some game launchers) - otherwise, every version of Forceware since the original Windows 8.1 WHQL has been flawless.  (GPU hardware - factory-refurb nVidia GTX550Ti.)

NVidia had issues with the 560ti series cards

NVidia had issues with the 560ti series cards

Really? Mine is still working just fine, and it's factory overclocked. Heck I know 3 of my friends with a 560 Ti, and I haven't heard one of them complain about it. 

A lot of people seem to be blaming drivers in this thread for what are clearly hardware problems.

 

Or a PEBKAC.

NVidia had issues with the 560ti series cards

 

Sweeping statement is sweeping.

This topic is now closed to further replies.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol. The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Most of the stuttering can easily be fixed by generating a PSO cache and compiling every shader before loading the game, it's up to the developer to set it up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!