Some might say that most releases from AMD in recent memory were "broken releases". Granted, this break could be considered more critical. Nonetheless, I have to agree with D. Lister that they did well dealing with this one quickly rather than the more typical pull the release and delay it a month or three to deal with the issues.
Sign of things to come? Would be nice, but the skeptic in me doubts it. Still, I'll give credit where credit is due. Good job AMD.
It's not that they DGAF, but rather after the several layoffs* they sadly Do Not Have Enough Testers, and beta testing is almost entirely left to the end users.
Because nVidia have never released a buggy driver... No. Never. They were only a cause of a large fraction of Vista's blue screens and other issues since then.
These drivers are getting stupidly complex and costly for both camps, they already eclipsed the NT Kernel years ago in regards to how many lines of code they have, stuff like this will happen, regardless of the company you go with.
These (the former) drivers caused consistent crashes in Diablo 3. Not unexpected that they would jump into damage control when very popular current titles blow up in your face after a release.
Hard to believe AMD had a bug in 15.8 that killed something as basic as Photoshop & Lightroom GPU acceleration for more than a month. They just didn't seem to care about it. No info. No patch (even though it proved to be a simple typo in their code per one poster who made his own patch). I've built a new machine with an Nvidia, card. They seems to have finally leapfrogged AMD. Good riddance to AMD & wonky driver bugs and PITA updates!
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
Facebook
Twitter
RSS
11 Comments
Back to Article
D. Lister - Friday, October 2, 2015 - link
AMD was actually uncharacteristically quick in dealing with this one, good job.Chaser - Friday, October 2, 2015 - link
Considering it was a fix to a broken release I would certainly hope so.BurntMyBacon - Friday, October 2, 2015 - link
Some might say that most releases from AMD in recent memory were "broken releases". Granted, this break could be considered more critical. Nonetheless, I have to agree with D. Lister that they did well dealing with this one quickly rather than the more typical pull the release and delay it a month or three to deal with the issues.Sign of things to come? Would be nice, but the skeptic in me doubts it. Still, I'll give credit where credit is due. Good job AMD.
Communism - Friday, October 2, 2015 - link
This was a blatant bug that almost instantly causes buffer overflow in 100% of cases.The fact that the blatently buggy release was even sent out to the public is the sign that AMD DGAF about proper testing.
D. Lister - Friday, October 2, 2015 - link
It's not that they DGAF, but rather after the several layoffs* they sadly Do Not Have Enough Testers, and beta testing is almost entirely left to the end users.* https://www.google.com/search?q=amd+layoffs&oq...
DiHydro - Wednesday, October 7, 2015 - link
Beta testing on a Beta driver! I don't believe it!StevoLincolnite - Sunday, October 4, 2015 - link
Because nVidia have never released a buggy driver... No. Never. They were only a cause of a large fraction of Vista's blue screens and other issues since then.These drivers are getting stupidly complex and costly for both camps, they already eclipsed the NT Kernel years ago in regards to how many lines of code they have, stuff like this will happen, regardless of the company you go with.
Strunf - Tuesday, October 6, 2015 - link
They are becoming complex cause they are now using per game optimisations, not to mention they install many non driver related "options".HiroshiTrinn - Friday, October 2, 2015 - link
These (the former) drivers caused consistent crashes in Diablo 3. Not unexpected that they would jump into damage control when very popular current titles blow up in your face after a release.rochlin - Friday, October 2, 2015 - link
Hard to believe AMD had a bug in 15.8 that killed something as basic as Photoshop & Lightroom GPU acceleration for more than a month. They just didn't seem to care about it. No info. No patch (even though it proved to be a simple typo in their code per one poster who made his own patch). I've built a new machine with an Nvidia, card. They seems to have finally leapfrogged AMD. Good riddance to AMD & wonky driver bugs and PITA updates!Gigaplex - Sunday, October 4, 2015 - link
There's nothing particularly basic regarding GPU acceleration in those applications.