bit-tech.net

AMD confirms grey-screen crash

AMD confirms grey-screen crash

While AMD has confirmed a bug in the Catalyst drivers that results in crashes, it claims it only affects a "small number" of users.

AMD has publicly confirmed reports of crashes with its ATI Radeon HD 5000-series graphics processors, which result in users systems displaying a series of grey or coloured lines.

As reported over on Tom's Hardware, the company has advised customers experiencing the bug that the issue isn't a hardware bug but a software one exacerbated by an update issued by Microsoft for Windows 7.

Despite this explanation, users running other versions of Windows are complaining of the same issue - and in the release notes for the latest version of theATI drivers, Catalyst 10.1, the grey screen crash is noted as an issue which affects all versions of Windows.

Company spokesman Dave Erskine has stated that "only a small number of ATI Radeon HD 5800 series and ATI Radeon HD 5700 series cards are exhibiting the behaviour" and promises that " the [Radeon] team is testing a driver hotfix and initial tests indicate that it resolves the issue."

When pressed on a firm release date, Erskine said only that "we need to test it further but we expect to make the hotfix available shortly."

The driver bug isn't the first software flaw to vex users of AMD's graphics hardware: late last year the PC release of The Saboteur was marred by incompatibilities withATI Radeon graphics cards which resulted in the game crashing on multi-core systems equipped with AMD's graphics processors. While this was later fixed in a patch from Electronic Arts, it left a bad taste in many gamers' mouths - especially as The Saboteur was part of rival graphics chip manufacturerNvidia's "The Way It's Meant To Be Played" programme.

Are you pleased to hear that AMD is fixing they grey screen crash, or are you shocked that such a major software bug ever made it into production drivers? Share your thoughts over in the forums.

36 Comments

Discuss in the forums Reply
mi1ez 1st February 2010, 15:06 Quote
Glad they're admitting it, glad they're working it out.
LeMaltor 1st February 2010, 15:09 Quote
News from Tom's Hardware, a low for bit-tech.
Gunsmith 1st February 2010, 15:17 Quote
Quote:
Originally Posted by LeMaltor
News from Tom's Hardware, a low for bit-tech.

important news is important news regardless the source!
azrael- 1st February 2010, 15:20 Quote
Quote:
Originally Posted by CardJoe
http://www.bit-tech.net/news/gaming/2010/02/01/gta-episodes-from-liberty-city-coming-to-pc/1

AMD has confirmed a driver bug resulting in crashes for "a small number" of ATI Radeon HD 5700 and 5800 users, and promises that a fix is on the way.

:o
Good news, but the link is pointing to the wrong article (when accessing from within the forums).
Horizon 1st February 2010, 15:39 Quote
Affects 4800 series also, Can't play the Mass Effect DLC without it grey screening during dialogue.
wiak 1st February 2010, 15:52 Quote
NVIDIA was crash-o-hotic on vista and they never addmited it so hehe, go AMD!
on sabatur it was EAs fault as it was their update that fixed the issue not AMDs driver or hotfix
theskirrid 1st February 2010, 16:11 Quote
Yep, it was nvidia drivers that gave the majority of early Vista issues. It was IIRC at least 60% of automatic error reporting traffic.

Nevertheless, glad I stayed on 9.12 :-)
crazyceo 1st February 2010, 16:56 Quote
You're kidding me? How can you all start pointing fingers elsewhere when AMD first said it was just Windows7 then "oops!" it's completely knackered on everything!

Another sign that AMD rushed out the recent software updates without any thought. This company has it's head completely up it's own ass!

Give us an honest explanation and we'll give you the benefit of the doubt. However, AMD cannot do this and have to point fingers and cry that everyones picking on them. Well I'm telling my mommy!
Cobalt 1st February 2010, 17:13 Quote
Quote:
Originally Posted by crazyceo
You're kidding me? How can you all start pointing fingers elsewhere when AMD first said it was just Windows7 then "oops!" it's completely knackered on everything!

Another sign that AMD rushed out the recent software updates without any thought. This company has it's head completely up it's own ass!

Give us an honest explanation and we'll give you the benefit of the doubt. However, AMD cannot do this and have to point fingers and cry that everyones picking on them. Well I'm telling my mommy!

AMD said an update for Win 7 made it worse, not that the problem only affected Win 7 or that it was MS's fault.

I wish people would actually read.
shanky887614 1st February 2010, 17:18 Quote
its a funny little error (sabotuer one)
when i was on xp i installed a new cpu e7600 and new gpu 4670 and installed latest drivers then i could play the game no problem then i fresh installed x64 win7 and installed drivers and it didnt work it was a wierd but so i just ran in it win xp mode and it worked flawlessly till they released patch
Casefan 1st February 2010, 17:41 Quote
I got this on my 5850 first time I ran MW2, it hung for about 6 six seconds then went back to my desktop, since then no problems. Running Windows 7.
crazyceo 1st February 2010, 17:43 Quote
"As reported over on Tom's Hardware, the company has advised customers experiencing the bug that the issue isn't a hardware bug but a software one exacerbated by an update issued by Microsoft for Windows 7.

Despite this explanation, users running other versions of Windows are complaining of the same issue - and in the release notes for the latest version of theATI drivers, Catalyst 10.1, the grey screen crash is noted as an issue which affects all versions of Windows."

Read it yourself! AMD said it was an update on Windows7 then their own release notes say it affect ALL versions of Windows.

Anything else or is your defence dead?
Tokukachi 1st February 2010, 17:52 Quote
Bloody Idiots on here I tell you...

http://www.thefreedictionary.com/exacerbated
Scootiep 1st February 2010, 18:06 Quote
Quote:
Originally Posted by crazyceo
"As reported over on Tom's Hardware, the company has advised customers experiencing the bug that the issue isn't a hardware bug but a software one exacerbated by an update issued by Microsoft for Windows 7.

Despite this explanation, users running other versions of Windows are complaining of the same issue - and in the release notes for the latest version of theATI drivers, Catalyst 10.1, the grey screen crash is noted as an issue which affects all versions of Windows."

Read it yourself! AMD said it was an update on Windows7 then their own release notes say it affect ALL versions of Windows.

Anything else or is your defence dead?

Holy cow, seriously, read what you post CAREFULLY before you post it. The first part is the quote from AMD. It states "the issue isn't a hardware bug but a software one exacerbated by..." EXACERBATED by means made worse. The SECOND part states "Despite this explanation, users running other versions of Windows are complaining of the same issue..." This is where the writer at Tom's hardware pops in and is adding his own observations and interpretations. The problem is that you're interpreting his addition of the problems on other OS's to say somehow that AMD was originally saying that it didn't affect those other OS's. BUT THAT WAS NEVER STATED BY AMD. They said that the Windows 7 update made it WORSE. The bug was already there and on other systems. For the love of God man, learn to read above a grammar school level. :(:(:(:(:(

edit: I should have said "the writer from Bit-Tech" and not "the writer from Tom's hardware" so sorry about that inaccuracy.
Taros 1st February 2010, 18:27 Quote
Quote:
Originally Posted by Scootiep
Holy cow, seriously, read what you post CAREFULLY before you post it. The first part is the quote from AMD. It states "the issue isn't a hardware bug but a software one exacerbated by..." EXACERBATED by means made worse. The SECOND part states "Despite this explanation, users running other versions of Windows are complaining of the same issue..." This is where the writer at Tom's hardware pops in and is adding his own observations and interpretations. The problem is that you're interpreting his addition of the problems on other OS's to say somehow that AMD was originally saying that it didn't affect those other OS's. BUT THAT WAS NEVER STATED BY AMD. They said that the Windows 7 update made it WORSE. The bug was already there and on other systems. For the love of God man, learn to read above a grammar school level. :(:(:(:(:(

edit: I should have said "the writer from Bit-Tech" and not "the writer from Tom's hardware" so sorry about that inaccuracy.

Here Here!

Can only assume Crazyceo is an AMD fanboy! :P *Wooosh Sparks Fly!*

AMD and Nvidia have both had their issues with drivers but after using both types of graphics cards il be keeping my money with AMD for now.

Just wish my order of Vapor-X 5870 would hurry up and be in stock again! :D
HourBeforeDawn 1st February 2010, 18:59 Quote
Either way at least ATI takes charge in actually getting problems fixed, I have seen where nVidia had issues that they didnt resolve for over a year.
TWeaK 1st February 2010, 19:18 Quote
I think it's a bit cheek throwing in Saboteur at the end of the article. That had nothing to do with AMD, and as I understood it, when the problem came up AMD jumped into action and helped EA fix it.
Farfalho 1st February 2010, 19:25 Quote
[QUOTE=Taros

Here Here!

Can only assume Crazyceo is an AMD fanboy! :P *Wooosh Sparks Fly!*

AMD and Nvidia have both had their issues with drivers but after using both types of graphics cards il be keeping my money with AMD for now.

Just wish my order of Vapor-X 5870 would hurry up and be in stock again! :D[/QUOTE]

Taros, crazyceo is more of an anti-AMD than of an AMD fanboy. Well, I guess misinterpretation is getting more common this days
Aracos 1st February 2010, 19:55 Quote
Quote:
Originally Posted by TWeaK
I think it's a bit cheek throwing in Saboteur at the end of the article. That had nothing to do with AMD, and as I understood it, when the problem came up AMD jumped into action and helped EA fix it.

But it did have something to do with AMD did it not? They even admit to it.
Quote:
Originally Posted by AMD interview
It was a mess of timing. The developer put in a change at the very last moment which unfortunately relied on a particular behaviour of the driver. Two changes in our driver and [this change] in the game took place at the same time and we didn't catch that - we should have done, and that's a straight forward failing on our part.
Scootiep 1st February 2010, 20:07 Quote
Quote:
Originally Posted by Farfalho
Taros, crazyceo is more of an anti-AMD than of an AMD fanboy. Well, I guess misinterpretation is getting more common this days

psst, actually Farfalho, he put that in there to see if he could get a rise out of crazyceo. Sarcasm f t w . :D
fantastic dan 1st February 2010, 20:34 Quote
I've had a lot of problems with Dragon Age on my 5770. I actually thought it was Dragon Age.

At least they're admitting it, if it's out in the public domain then there is a better chance they'll do something about it.
frontline 1st February 2010, 20:42 Quote
I saw this mentioned quite a lot on the Rage 3D forums and wasn't sure whether it was a common issue, as i haven't experienced it to date. Looks like they were right. At least they have recognised it is partly a driver issue and that it is their responsibility to fix it.
crazyceo 2nd February 2010, 00:04 Quote
LMFAO @ the AMD fanboys coming in for the rescue.

They dropped the ball bigtime and are scurrying as quickly as their little feet can carry them.
Elton 2nd February 2010, 00:53 Quote
Good for AMD, really they are at least brave enough to admit to a mistake..

With that said...how exactly did they get away with this?
wiak 2nd February 2010, 04:13 Quote
i have NO problems with my HD 5870 with Catalyst 10.1 and Windows 7 64-bit
so it has to be a user error ;)
Ross1 2nd February 2010, 04:27 Quote
my 5850 has been full of fail. okay, since ive updated to beta drivers i havent had the grey screen, however i still continue to get video playback glitches (mainly in fullscreen), and screen tearing issues in firefox and a few other windowed programs (despite 'forcing' v-sync')
Ross1 2nd February 2010, 04:28 Quote
Quote:
Originally Posted by wiak
i have NO problems with my HD 5870 with Catalyst 10.1 and Windows 7 64-bit
so it has to be a user error ;)

absolute bollocks
kenco_uk 2nd February 2010, 12:54 Quote
Quote:
Originally Posted by Scootiep
Holy cow, seriously, read what you post CAREFULLY before you post it. The first part is the quote from AMD. It states "the issue isn't a hardware bug but a software one exacerbated by..." EXACERBATED by means made worse. The SECOND part states "Despite this explanation, users running other versions of Windows are complaining of the same issue..." This is where the writer at Tom's hardware pops in and is adding his own observations and interpretations. The problem is that you're interpreting his addition of the problems on other OS's to say somehow that AMD was originally saying that it didn't affect those other OS's. BUT THAT WAS NEVER STATED BY AMD. They said that the Windows 7 update made it WORSE. The bug was already there and on other systems. For the love of God man, learn to read above a grammar school level. :(:(:(:(:(

edit: I should have said "the writer from Bit-Tech" and not "the writer from Tom's hardware" so sorry about that inaccuracy.


[SIZE=7]UNLEASH THE CAPSLOCK FURY! ;) j/k

Hope this doesn't affect their mobile/laptop gpu's.
[USRF]Obiwan 2nd February 2010, 14:58 Quote
What is "only a few" if every mayor tech site forum in every country is full of people complaining about the Grey/blue/red/green stripes or grey/blue/black/green etc screens? on the 4 and 5 series of ATI cards.

Tell me!
Cyberpower-UK 2nd February 2010, 18:30 Quote
Observations from the frontline:
I spend my days chained to rack full of gaming PCs so I've seen a few GSODs.

Many failures due to an OC will be put down to the cards as a GSOD may also occur on 124 (AKA insufficient CPU voltage) and memory related errors. So check you event log first 116 or 117 is Graphics. In my experience this is far more likely to be the problem even in stock clocked systems poor RAM/settings can cause crashes.

I have a system under testing at the moment that will run Prime95 and Furmark simultaneously but has intermittent crashes (Display Device Stopped Working...) on the desktop and in Direct3D. i.e. the CPU and Graphics are rock solid but the error still occurs. Unigene Heaven is a good tool to use as it can test in OpenGL and DX9,10 & 11 which can help isolate the problem. This is the first system I have seen with the exact issue so it is fairly rare. Changing the 5850 for a different brand did not solve it. I changed the RAM from GSKill to OCZ and it hasn't GSODed yet we'll see if it's still running in the morning.

Forcing Windows Vista/7 to run in Basic mode can stop the desktop freezes.

Something else I've noticed is that the systems that end up doing this often get the wrong Windows Index Score typically 6.0.

Sometimes the 9.12 driver will eliminate the issue, sometimes 10.1 will.

The problem is similar to one seen with the 4870x2 and 3870x2 shortly after launch.

8800 GTX/Ultra nvdklm problem has a similar failure mode in 3DMark06 was sometimes fixed by changing memory brand/type despite Memetest/Prime/IntelBurn stable memory.
frontline 2nd February 2010, 19:36 Quote
Hmm, i don't dispute it is an issue for a fair number of people, but i can only say what my own experience is, and that is running a Sapphire 5870 24/7 on Windows 7 since around the launch date. I've run furmark, vantage, heaven benchmark multiple times, with maximum settings and have played numerous games for hours on end, including demanding DX10/DX11 titles and not had a single crash. Lately i've been playing the BF:BC2 beta for several hours a night and still no problems.

I can only assume that it is either specific combinations of software and/or hardware or something that will occur randomly at some point in the indeterminate future...
TheHalfWit 2nd February 2010, 21:00 Quote
Personally I have a 5770 and can attest to this problem, I thought it was my PSU so I replaced that, and I still have this issue, albeit less frequently with the 10.1 drivers. I thought it was because I was OC my cpu too hard, e8400.

Note: The PSU replacement was planned anyway for a crossfire setup I'm planning, (CM Storm Scout, too small for a 58xx or 5970.) It was just rushed because of this.
Cyberpower-UK 3rd February 2010, 10:29 Quote
OK, the system in my above post has responded positively to the memory change.

So despite the memory passing Memtest and Prime95 Blend testing the memory appears to have caused the problem.

I'll try and repeat the fix, for verification, next time the bug crops up.
samuelmorris 4th February 2010, 05:34 Quote
Having owned a 4870X2 from the get go it's dissapointing to see the HD5s get off to a more rocky start with software (given for example the inflated cursor bug), but saying that, CF scaling seems a little bit better from the off this time.
HourBeforeDawn 4th February 2010, 21:53 Quote
is there any new word on a release date for this fix? we have stopped selling ATI cards at least the generation effected as we have already had to much backlash from customer complaints so we are hoping this fix comes out soon like this month soon ^^
HourBeforeDawn 8th February 2010, 17:48 Quote
Since no one has posted, I shall in case someone comes across this thread again, there has been a fix released for the 5870 and 5870 series of cards
http://support.amd.com/us/kbarticles/Pages/Grey-screen-and-vertical-line-corruptions.aspx

A fix for the 5770 and others should be coming out soon.
Log in

You are not logged in, please login with your forum account below. If you don't already have an account please register to start contributing.



Discuss in the forums