AMD confirms grey-screen crash

**anticupidon** · 02-01-2010 07:23 AM

bit-tech.net | AMD confirms grey-screen crash

At least they admit it and they will try to fix it.
Anyone remembers Nvidia's driver issues on Vista?

**SirRobin4ever** · 02-01-2010 08:14 AM

I wondered why this happened to me a few times now.

**logain** · 02-01-2010 08:31 AM

Guess I will be holding off on 5xxx cards for a little while.

**SirRobin4ever** · 02-01-2010 08:40 AM

Originally Posted by logain

Guess I will be holding off on 5xxx cards for a little while.

Well at least it doesn't sound like it's going to be very long before the issue is resolved.

**logain** · 02-01-2010 08:42 AM

Originally Posted by SirRobin4ever

Well at least it doesn't sound like it's going to be very long before the issue is resolved.

I am kinda waiting for the supposed 5830 anyway. 5850 is nice but still to pricey for me.

**MagicLess** · 02-01-2010 08:43 AM

**beerandcandy** · 02-01-2010 09:56 AM

what the hell is a grey screen crash?

**CapnBFG** · 02-01-2010 02:20 PM

Interesting, have not seen this. I've had occasional lockups and reboots while running F@H GPU2, but no gray screen so far.

**anticupidon** · 02-01-2010 02:35 PM

This is nothing new.Owners of 5xxx series faced this and ATI is now working around the clock to fix it.
Looks that i have to wait for the new refresh of ATI's 5xxx and more mature drives.
Like i'm in a hurry.Usually i wait 6 months after a product release.

**SMU_Pony** · 02-01-2010 02:46 PM

Hopefully I'm not jinxing myself here, but I haven't had any problems yet (5870 + Win7 64-bit)

**arisythila** · 02-01-2010 05:15 PM

You know. When I had my GTX280 in there, IT would always blue screen me when the drivers would crash.. with the ATI. I get a screen blink, but no blue screen. I'm pretty impressed I dont have to reboot my machine when it happens.

Kudos!

**randomizer** · 02-01-2010 05:30 PM

I wouldn't be impressed about having screen blinks. I get them myself when using 3DS Max and they waste 15 seconds of my life. Sure they're not blue screens, but they take almost as long to recover from. I sometimes wonder what exactly driver developers get paid to do. Bugs might not be as bad as they were pre-2000 but this is 2010 now and we still have major bugs.

**SirRobin4ever** · 02-01-2010 06:24 PM

Originally Posted by arisythila

You know. When I had my GTX280 in there, IT would always blue screen me when the drivers would crash.. with the ATI. I get a screen blink, but no blue screen. I'm pretty impressed I dont have to reboot my machine when it happens.

Kudos!

I think you're talking about something else. This crash is just that, a crash. It does not recover, at least not in my experience. The computer, however continues to work fine- music continues playing, and in fact I can change songs and adjust the volume, etc...just no display. It's pretty annoying.

**SuperFly03** · 02-02-2010 10:06 AM

I experience this on a regular basis in WoW. By regular I mean every 2 hours or so. The screen goes green/grey. It will have vertical alternating color bars.

It never happened before I updated Win 7. No biggie... just wait for a hot fix and roll on. Nothing to see here folks.

**arisythila** · 02-02-2010 10:13 AM

Windows says the drivers crash out, but have been recovered. I'm pretty happy they recover. I mean yeah sure. I have two SSD's in Raid 0, and windows takes about 30 seconds to boot anyways. HOWEVER. When I'm in the middle of this or that, while i'm gaming, I dont want to deal with a full BSOD. I'd much rather it just recover the drivers like I've notied it does with my ATI 5850, over my old GTX280.

I don't loose SSH sessions or anything.

~Michael

**logain** · 02-02-2010 10:35 AM

Hope this gets fixed soon. I have a friend interested in getting a new system and I want to get him a 5850 for his build.

**billdcat4** · 02-02-2010 12:11 PM

Ive been having video driver problems with the IGP in my netbook. The screen will freeze and then turn on and off with a message that the video driver had to reboot.

beer, do you have any custom super-drivers for me?

**beerandcandy** · 02-02-2010 12:20 PM

that sounds like a hardware problem
what os and how do you make it happen?
when it says it recovered its really a BSOD that they dont show you
for XP its a 0xEA on vista and newer its a 0x117 or something like that
they also call it a TDR
if you change the timeout value to a longer value you may not see the issue anymore
it might just be that the os thinks the hardware is hung when its just slow

you might have to create the DWORD in the registry to mess with these settings if it isnt there

The TDR-related registry keys are located under
HKLM\System\CurrentControlSet\Control\GraphicsDriv ers
TdrLevel?: REG_DWORD. The initial level of recovery. The possible values are:
TdrLevelOff? (0). – Detection disabled.
TdrDebugMode?: REG_DWORD: The debugging-related behavior of the TDR process.
TDR_DEBUG_MODE_IGNORE_TIMEOUT (1) ignores any timeout.

or on XP do a search for earecovery and change the value to 0 and it should actually do a BSOD
but there are multiple instances of earecovery in the registry so you would want to change all of them to 0 just to make sure you change the right one

**randomizer** · 02-02-2010 04:53 PM

Originally Posted by arisythila

Windows says the drivers crash out, but have been recovered. I'm pretty happy they recover. I mean yeah sure. I have two SSD's in Raid 0, and windows takes about 30 seconds to boot anyways. HOWEVER. When I'm in the middle of this or that, while i'm gaming, I dont want to deal with a full BSOD. I'd much rather it just recover the drivers like I've notied it does with my ATI 5850, over my old GTX280.

I don't loose SSH sessions or anything.

~Michael

It's driver dependent, and probably dependent on alot of other things too. My NVIDIA drivers never BSOD (visibly) and never require reboots to recover, they just blank the screen several times and then allow me to continue. I'm still not happy that it happens though.

**billdcat4** · 02-02-2010 05:28 PM

Originally Posted by beerandcandy

that sounds like a hardware problem
what os and how do you make it happen?
when it says it recovered its really a BSOD that they dont show you
for XP its a 0xEA on vista and newer its a 0x117 or something like that
they also call it a TDR
if you change the timeout value to a longer value you may not see the issue anymore
it might just be that the os thinks the hardware is hung when its just slow

you might have to create the DWORD in the registry to mess with these settings if it isnt there

The TDR-related registry keys are located under
HKLM\System\CurrentControlSet\Control\GraphicsDriv ers
TdrLevel?: REG_DWORD. The initial level of recovery. The possible values are:
TdrLevelOff? (0). – Detection disabled.
TdrDebugMode?: REG_DWORD: The debugging-related behavior of the TDR process.
TDR_DEBUG_MODE_IGNORE_TIMEOUT (1) ignores any timeout.

or on XP do a search for earecovery and change the value to 0 and it should actually do a BSOD
but there are multiple instances of earecovery in the registry so you would want to change all of them to 0 just to make sure you change the right one

Its on Win7 RC 32bit. I havent had the issue for a couple of days, and the RC is going to end soon, so im not going to mess with it. After the RC runs out, I might use XP or Ubuntu Netbook Remix

Thread: AMD confirms grey-screen crash

LinkBack

Thread Tools

Display

AMD confirms grey-screen crash

Posting Permissions