Personal computing discussed
Moderators: renee, morphine, SecretSquirrel
thegleek wrote:For months I was hating on my Nvidia video card (GeForce GTS 450) and the current and/or older drivers (v260.89) that were installed/re-installed on my Windows 7 x64 OS...
It was my MONITOR the entire time! When I finally got the motivation itch to change the blown capacitors in my other Samsung SyncMaster 226BW monitor, no driver issues ever came up again! In fact, it's been running flawlessly 24/7 for the past month without a crash. Previous to that it was almost a daily occurrence!
I am running nvidia's driver v285.62 flawlessly now! So happy!
Jon wrote:The issue cannot be pinned on bad hardware because by simply reverting to the 275.xx series of drivers gamers no longer experience TDR issues.
P5-133XL wrote:I really must be missing something for it seems that in the first post of the thread Jon outright told all of you having problems what the solution is...Jon wrote:The issue cannot be pinned on bad hardware because by simply reverting to the 275.xx series of drivers gamers no longer experience TDR issues.
So why is everyone trying to be so complex? If you have this problem, do the solution immediately and wait till Nvidia solves the driver issue at some future time. Generally, there isn't that much functionality added with each new driver released that it is worth chasing driver releases. Let others frustrate themselves and save yourselves the headaches.
Complexity, should only occur if the given solution doesn't fix the problem. Further, if it doesn't fix the problem then you can no longer exclude HW as the issue since this solution is given as the proof that it isn't HW.
just brew it! wrote:Ding ding ding!About half the time, it's an incompatibility between the installer and the version of the .NET libraries you've got installed.
JustAnEngineer wrote:just brew it! wrote:About half the time, it's an incompatibility between the installer and the version of the .NET libraries you've got installed.
Ding ding ding!
That's been my experience, too. That's why I try to keep .NET up to date.
P5-133XL wrote:I really must be missing something for it seems that in the first post of the thread Jon outright told all of you having problems what the solution is...Jon wrote:The issue cannot be pinned on bad hardware because by simply reverting to the 275.xx series of drivers gamers no longer experience TDR issues.
So why is everyone trying to be so complex? If you have this problem, do the solution immediately and wait till Nvidia solves the driver issue at some future time. Generally, there isn't that much functionality added with each new driver released that it is worth chasing driver releases.
thegleek wrote:I've had v260.89 installed previously and still experienced these bsod's...
Are you telling me they (nvidia) fixed something between 260.x and 275.x and then re-broke it again from 275.x to 285.x? not.
thegleek wrote:I've had v260.89 installed previously and still experienced these bsod's...
Are you telling me they (nvidia) fixed something between 260.x and 275.x and then re-broke it again from 275.x to 285.x? not.
Ryu Connor wrote:I believe you have a damaged video card, not a driver issue.
morphine wrote:Civilization V in DX11 mode triggered this, nearly every time a leader popped up, with my GTX 460. Haven't tried with my new 570 yet.
This issue seems to effect everyone. Myself and my friend with a 6950. It's annoying, run into it a lot in combination with gawker blogs and embedded youtube vids.
Silicondoc wrote:AMD drivers do not work as well as Nvidia drivers in many situations and overall, even considering this terrible issue. One error does not balance unending years of the same and worse.
morphine wrote:Silicondoc wrote:AMD drivers do not work as well as Nvidia drivers in many situations and overall, even considering this terrible issue. One error does not balance unending years of the same and worse.
As someone who's been back and forth between AMD and Nvidia in these past few years, I think you're off the mark. I've found significant issues with both vendors.
Nvida issues I've come across: as mentioned, with my previous GTX 460, Civ V crashed on leader screens. Then my gamma settings weren't applied on boot half the times. Right now with my 570, if the monitors go into power-saving mode running a fullscreen app, my gamma resets, and it resets *again* if I alt-tab out. A friend has major issues with BF3 crashes. Flat panel scaling was outright broken for a few years, thankfully it's fixed. There's this TDR issue, etc.
Although AMD had pretty poor driver quality in the early 2000s, that's not really the case anymore.
Silicondoc wrote:morphine wrote:[...]AMD still has terrible drivers and whole classes of cards that crash. Worse yet, often there are no fixes. The system must be rebooted, and it happens again, and again, and again... for YEARS literally people try to find a fix and there isn't one. [...]
You can think I'm off all you want, but I'm not anywhere near off. Nvidia solves their issues 99 times out of 100 in sohrt order, while AMD has an endless, and continuing, and ever expanding list.
They did solve CRAPPY CF scaling, but that was present for YEARS and YEARS and YEARS before they finally came up to Nvidia levels...
You mention a single crash issue, but YOU KNOW in what area and game it crashed - unlike AMDATI cards, where ANY CRASH in ANY GAME at ANY TIME goes.
You won't EVER convince anyone who has a clue.
r00t61 wrote:Since I had to reinstall Windows 7 anyway, I updated to 285.79, which seems to have solved the TDRs. 285.79 is a beta driver, but I have to use it because the WHQL driver listed on NVIDIA's page - 285.62 (dated 10/24/2011) - has a known issue, breaking Windows Media Center (http://forums.nvidia.com/index.php?showtopic=213923).
Ryu Connor wrote:I've been following this particular drama on the NVIDIA forums since it kicked off with the 280.26 release. As with most broad driver problem the issue has begun to have problems attached to it that are not related to the actual issue.
If 275.33 or older are giving you TDR issues then your problem isn't related to what spawned this thread and potentially isn't a driver problem.
Using 275.33 or older will allow for use of Direct2D in Chrome, IE9, and FireFox under Vista or 7 without TDRs. The moment you upgrade past 275.33 TDRs will begin occuring in 2D, but not in 3D. Downgrading to 275.33 resolves the issue.
Issues before 275.33, with 275.33, or involving 3D (e.g. game) related TDR events or BSOD are not a known NVIDIA issue. It's more likely it is a SMD issue with your card or a quirk specific your exact set of hardware and software.
290.53 & 295.51 each have 2D TDR fixes that have helped some people, others are still stuck on 275.33 to avoid TDRs.