THANKS NVIDIA! /s Crappy drivers freezing my PC

By Steven P.
in Hardware Hangout

 Share

Recommended Posts

Mentor

jesseinsf

Posted
Posted

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. 

How long has it been since you used your 560ti card? You're specs sat 770. There were issues starting spring of last year up until Beta driver 331.82. Anything after that driver had no problems. Crashes usually happened when browsing the internet by going to intensive sites like facebook, maximum PC, ext. But you also have to have other sites open like outlook.com. Some games would crash the driver too if these websites were running in the background.

Proficient

AStaUK

Posted
Posted

OFT, but seeing this thread reminds me I need to put my 670 up on ebay.

 

Probably just placebo but the latest drivers seem to have better image quality on my 780.  BF4 seems to look a lot sharper.

Mentor

jesseinsf

Posted
Posted

Or a PEBKAC.

 

Sweeping statement is sweeping.

They were no hardware problems because the issues were fixed after driver 331.82 beta. It's not really good to assume that it's a hardware issue unless you are the one writing the driver code and are 100% certain that it's a hardware issue..

Proficient

ndoggfromhell

Posted
Posted

I had an issue with Java 6 Update 32 (the newest version we can use at my business to be compatible with General Motors and Kia Motors)  The Java windows would crash and peg the CPU @ 100%.  I would have to end the process to close it.  Using older drivers seemed to fix the problem.  

Grand Master

tsupersonic

Posted
Posted

How long has it been since you used your 560ti card? You're specs sat 770. There were issues starting spring of last year up until Beta driver 331.82. Anything after that driver had no problems. Crashes usually happened when browsing the internet by going to intensive sites like facebook, maximum PC, ext. But you also have to have other sites open like outlook.com. Some games would crash the driver too if these websites were running in the background.

February 2011, so roughly 3 years of rock solid performance, and still going. My main desktop is running GTX 770, which I just bought recently. I transferred the GTX 560 Ti to the backup computer. I've run Beta drivers on my main desktop, and haven't had a single issue. I haven't heard of any mass problems with the 560 Ti, it might just be you. 

Mentor

jesseinsf

Posted
Posted

February 2011, so roughly 3 years of rock solid performance, and still going. My main desktop is running GTX 770, which I just bought recently. I transferred the GTX 560 Ti to the backup computer. I've run Beta drivers on my main desktop, and haven't had a single issue. I haven't heard of any mass problems with the 560 Ti, it might just be you. 

Just an FYI, do you use the internet? Obviously when it doesn't pertain to you then no one else shouldn't have the problem. And if they do, then it is the assumption that it is a 100% hardware failure. another FYI, not only did NVidia as me but they also made a post on their website to ask the owners of the 560ti cards to send in their cards while they give loaner cards. The problem was difficult to reproduce because there was no real evidence in the dump files for them to locate the source of the error. Obviously it "Was" wide spread or they would not have wasted money doing this. I highly suggest you do a bit of research before commenting. It would definitely help you gain more knowledge before posting comments.Again, since the problem has been fixed, it was not a hardware issue. It just took them a long time to fix the issue.

Grand Master

tsupersonic

Posted
Posted

Just an FYI, do you use the internet? Obviously when it doesn't pertain to you then no one else shouldn't have the problem. And if they do, then it is the assumption that it is a 100% hardware failure. another FYI, not only did NVidia as me but they also made a post on their website to ask the owners of the 560ti cards to send in their cards while they give loaner cards. The problem was difficult to reproduce because there was no real evidence in the dump files for them to locate the source of the error. Obviously it "Was" wide spread or they would not have wasted money doing this. I highly suggest you do a bit of research before commenting. It would definitely help you gain more knowledge before posting comments.Again, since the problem has been fixed, it was not a hardware issue. It just took them a long time to fix the issue.

Link to this? How does this work? I am going to go out on a limb and say most gamers will purchase non-reference cards (aka branded video cards like MSI, Gigabyte, EVGA, etc.). Did it affect one brand more than another - and if so did they extend warranty on affected 560 Ti's? Furthermore, there is the 384 core and 448 core, which one did it affect, or both? I tried a quick Google for "560 Ti Recall" and "560 Ti Failure" and nothing out of the ordinary except the usual unlucky people who have failed cards due to some in a bad batch. As with any product, the ones that do fail or have issues, people have strong voices on the internet...

Mentor

jesseinsf

Posted
Posted

Link to this? How does this work? I am going to go out on a limb and say most gamers will purchase non-reference cards (aka branded video cards like MSI, Gigabyte, EVGA, etc.). Did it affect one brand more than another - and if so did they extend warranty on affected 560 Ti's? Furthermore, there is the 384 core and 448 core, which one did it affect, or both? I tried a quick Google for "560 Ti Recall" and "560 Ti Failure" and nothing out of the ordinary except the usual unlucky people who have failed cards due to some in a bad batch. As with any product, the ones that do fail or have issues, people have strong voices on the internet...

Dude, I'm not going to sift through all the issues that are related to the 560ti during that time. What I will do is give you a link to the NVidia forums which will display all of the discussions about the 560ti crash issues.I have an Asus card which is built extremly sturdy. Oh and you are using the wrong words. There were no failures to the cards. The "Driver crashed". So when doing a search you need to be more spacific. search: "560 Ti driver failure".

https://forums.geforce.com/search/more/sitecommentsearch/560ti%20crash%20problems/

Mentor

snaphat (Myles Landwehr) Member

Posted
  • Member
Posted

Dude, I'm not going to sift through all the issues that are related to the 560ti during that time. What I will do is give you a link to the NVidia forums which will display all of the discussions about the 560ti crash issues.I have an Asus card which is built extremly sturdy. Oh and you are using the wrong words. There were no failures to the cards. The "Driver crashed". So when doing a search you need to be more spacific. search: "560 Ti driver failure".

https://forums.geforce.com/search/more/sitecommentsearch/560ti%20crash%20problems/

 

Here's the thread you are talking about:

https://forums.geforce.com/default/topic/621899/geforce-drivers/desktop-internet-browser-freeze-thread-w-geforce-460-560-gpus-updated-for-nb-12-5-13-page79-/

 

EDIT: ehh that looks too late in date to be what you are talking about actually...

Grand Master

Steven P. Administrators

Posted
  • Author
  • Administrators
Posted

Link to this? How does this work? I am going to go out on a limb and say most gamers will purchase non-reference cards (aka branded video cards like MSI, Gigabyte, EVGA, etc.). Did it affect one brand more than another - and if so did they extend warranty on affected 560 Ti's? Furthermore, there is the 384 core and 448 core, which one did it affect, or both? I tried a quick Google for "560 Ti Recall" and "560 Ti Failure" and nothing out of the ordinary except the usual unlucky people who have failed cards due to some in a bad batch. As with any product, the ones that do fail or have issues, people have strong voices on the internet...

There are many topics on this (now seemingly fixed) issue, one of which is linked in my opening post by a unsatisfied customer.

 

The only drivers that didn't crash for me where in the 311 series, considering we're now on 332 (fixed in 331.93 beta) that's quite a number of drivers in between before it got fixed.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Posts

    • DWARF mini review: the world's smallest smart telescope for night and day sky captures

      By Nick H. · Posted

      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.
    • Halo: Campaign Evolved is out next month with new prequel missions

      By +pmrd · Posted

      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. Just because Nanite can render meshes with millions of polygons doesn't mean you should use it like that, in fact, Epic recommends you avoid doing that. Most of the stuttering can easily be fixed by cutting down on unique shaders by using master materials and generating a PSO cache and compiling every shader before loading the game and managing what must be loaded and unloaded at runtime, it's up to the developer to set all that up properly.
    • DWARF mini review: the world's smallest smart telescope for night and day sky captures

      By Malisk · Posted

      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.
    • Microsoft confirms a new, useful Teams' app is coming very soon

      By Malisk · Posted

      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 hellowalkman · Posted

      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
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!