Originally posted by: Genx87
I cant handle the half ass drivers from ATI anymore. I tried them twice and both times ended in flaming defeat. This latest round with a 4850.
Bad ATI drivers 2
Me 0
Back to Nvidia but would wait to make a purchase if the refresh cycle is close.
Originally posted by: Genx87
I may have came off as flaming, for that I apologize. I was a bit pissed that I just sat in a 30 min queue for WoW to have the ATI driver BSOD me when I hit #20 in line. But it is typical for this thing and I had enough.
Originally posted by: toattett
Originally posted by: Genx87
I may have came off as flaming, for that I apologize. I was a bit pissed that I just sat in a 30 min queue for WoW to have the ATI driver BSOD me when I hit #20 in line. But it is typical for this thing and I had enough.
If such a popular card (4850) w/ ATI Catalyst drivers indeed causes BSOD in such a popular game (WoW), the whole WoW/ATI community (guess how large the user base would be?) would be actively rioting all over the Internet.
In this case, it's so obvious that you are the only one with this problem, so this leads me to believe either you have software problem (bad windows/drivers install) or simply defective hardware (bad PSU/video card etc.
There are only so much time and resource availability that any company has to do QA on drivers. No one can do everything, and neither NVIDIA nor AMD do.
I think they both have issues and neither one is really overall "better" than the other (though I do think AMD has the appearance of being better due to their schedule).
...
Here's the thing --
In order to get the gamer what he or she wants, a company would need to test all of their hardware to make sure things simply work and regression test all games from the past couple years with that hardware. This is never going to happen.
Both AMD and NVIDIA cut major corners.
AMD has multiple driver trunks, and a rotating schedule of only about 2 dozen titles for regression testing that do not repeat within something like 6 months to a year. If one driver breaks something, it will be at least two months until it gets "fixed" for real (as the next month might not exhibit the same problem, but it also won't necessarily be based on the same code). If one game is dropped from the regression testing schedule, it could break in one driver and not be caught for a very long time (or until reviewers start to complain about it).
We run into the problem a lot, especially with crossfire scaling, of things that used to work not working and then when we point it out, all of a sudden we've got a beta driver with a fix. It's just because AMD dropped that title from their regression testing. Over time they hit a lot of titles, but this is an optimization that does cause issues.
Because you can't have monthly WHQL drivers with the latest features on the latest hardware all regression tested on everything everyone could want to play. There isn't enough time there to do all the necessary QA. All the driver has to do is pass Microsoft's WHQL testing ... which is easier than actually working in all relevant games.
NVIDIA does something else --
They don't always test all their hardware every cycle. We'll see beta drivers tested completely first on high end hardware or newly released hardware. Older stuff is left out of testing, so we have divergent driver versions necessary for different classes of hardware. Since NVIDIA uses a unified model (at the moment), all drivers should work on all hardware, but if it hasn't been released to support a specific card then that means it hasn't been QA'd on that card.
NVIDIA regression tests with many more titles per WHQL release, but at the same time, there is much more time between WHQL releases. This gives them a longer period to look at more things, but at the same time stuff can stay broken for longer.
If all this stuff is really interesting, I could take some time and talk to AMD and NVIDIA again (we've had this discussion with them before) and I could do a write up about it explaining the pros and cons of both approaches.
Frankly, from my perspective, monthly WHQL is just a marketing tool ... it makes people feel better. But NVIDIA's approach isn't necessarily better -- it's just different.
Originally posted by: thilan29
Maybe your card is bad? Does it BSOD when you stress it?
its your OS thats corrupted or hardware as thilan29 has said.
Are you running everything at stock? I do. If you OC your ATI may be more sensitive to it than your nv card was.
If such a popular card (4850) w/ ATI Catalyst drivers indeed causes BSOD in such a popular game (WoW), the whole WoW/ATI community (guess how large the user base would be?) would be actively rioting all over the Internet.
In this case, it's so obvious that you are the only one with this problem, so this leads me to believe either you have software problem (bad windows/drivers install) or simply defective hardware (bad PSU/video card etc.
Originally posted by: Genx87
I understand many have great success with ATI. I have not. The exact same system that ran with an 8800GTS 640 without a single Blue Screen gets regular BSOD and driver failures with this card. When i got this I reinstalled from the ground up. No conflicts with Nvidia drivers from the old card.
I may have came off as flaming, for that I apologize. I was a bit pissed that I just sat in a 30 min queue for WoW to have the ATI driver BSOD me when I hit #20 in line. But it is typical for this thing and I had enough.
And it really irritates me because when my 8800 died I had a decision to make. Nvidia or ATI. My past experience with a 9600 Pro AIW was a nightmare driverwise. Their control panel software spiked the CPU with an apparent high priority. Which meant if you couldnt kill it before it spiked, you couldnt do a damed thing. So when I went with this 4850 I knew I was taking a gamble and apparently lost.
Originally posted by: apoppin
Originally posted by: Genx87
I understand many have great success with ATI. I have not. The exact same system that ran with an 8800GTS 640 without a single Blue Screen gets regular BSOD and driver failures with this card. When i got this I reinstalled from the ground up. No conflicts with Nvidia drivers from the old card.
I may have came off as flaming, for that I apologize. I was a bit pissed that I just sat in a 30 min queue for WoW to have the ATI driver BSOD me when I hit #20 in line. But it is typical for this thing and I had enough.
And it really irritates me because when my 8800 died I had a decision to make. Nvidia or ATI. My past experience with a 9600 Pro AIW was a nightmare driverwise. Their control panel software spiked the CPU with an apparent high priority. Which meant if you couldnt kill it before it spiked, you couldnt do a damed thing. So when I went with this 4850 I knew I was taking a gamble and apparently lost.
i think it is metaphysical
some people just have bad luck with one vendor and naturally gravitate to the other vendor which somehow works well for them
Maybe you do not have enough patience with AMD; perhaps you should choose Nvidia from now on
![]()
Originally posted by: SSChevy2001
So you didn't do any troubleshooting, and decided your just going to bash on the ATi driver team.
1) Check forums for know problems with this combination ( wow / 4850 )
3) Test with other applications for problems.
4) Test the card underclocked to see if that helps. ( RMA might be needed )
5) Try older drivers.
6) Redo windows
It looks like you bought this card with crossed fingers just waiting for something to go wrong. Bad karma
Look here's a GTX260 user having BSOD problems with WOW, maybe he should only buy ATi. What you think?
You can only help someone if they want help. He thinks the grass is greener on the other side, which is not always the case as I pointed out.Originally posted by: keysplayr2003
This doesn't help Chevy.
Originally posted by: apoppini think it is metaphysical
some people just have bad luck with one vendor and naturally gravitate to the other vendor which somehow works well for them
Maybe you do not have enough patience with AMD; perhaps you should choose Nvidia from now on
![]()
Originally posted by: SSChevy2001
So you didn't do any troubleshooting, and decided your just going to bash on the ATi driver team.
1) Check forums for know problems with this combination ( wow / 4850 )
3) Test with other applications for problems.
4) Test the card underclocked to see if that helps. ( RMA might be needed )
5) Try older drivers.
6) Redo windows
It looks like you bought this card with crossed fingers just waiting for something to go wrong. Bad karma
Look here's a GTX260 user having BSOD problems with WOW, maybe he should only buy ATi. What you think?
Originally posted by: SSChevy2001
You can only help someone if they want help. He thinks the grass is greener on the other side, which is not always the case as I pointed out.Originally posted by: keysplayr2003
This doesn't help Chevy.
Originally posted by: SSChevy2001
So you didn't do any troubleshooting, and decided your just going to bash on the ATi driver team.
It looks like you bought this card with crossed fingers just waiting for something to go wrong. Bad karma