ATI 5xxx Grey Screen of Death

Supersonic64

Senior member
Jun 9, 2010
372
2
0
Is it back? I am running the latest 10.6 Cat's on W7 x64 with a 5870 and I just got the infamous grey screen of death while playing NFS Shift.

Wasn't this fixed back in the 10.1 Cat's? I am running a very "mild" OC as far as CCC Overdrive lets me which is about 50MHz on the core and 100MHz on the mem.
 
Last edited:

Hardlin

Senior member
Aug 27, 2004
226
0
71
I have personally never seen it but I only run a single card on a single monitor. Do you think it will happen with the Shift demo? I will download and test it on my 5870 under Win7 Ultimate 64 and let you know if I see the issue.

I have the same motherboard and memory that you do so it may be a valid test to try.
 

Supersonic64

Senior member
Jun 9, 2010
372
2
0
Well it's only happened this one time although I have checked the event log and have a repeating event apparently related to the ATI drivers, it repeats every 15s or so which is odd and has made my event log very long. I wonder if this had something to do with the crash. In any case, I did a registry tweak (Google "5870 DVD_OV") to stop the recurring event.

I've also read that this recurrent event can cause crashes while gaming, so we'll see now that it has been stopped.

Log Name: System
Source: amdkmdag
Date: 7/4/2010 11:06:32 AM
Event ID: 62464
Task Category: DVD_OV
Level: Information
Keywords: Classic
User: N/A
Computer: KrisDesktop-PC
Description:
UVD Information
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="amdkmdag" />
<EventID Qualifiers="16384">62464</EventID>
<Level>4</Level>
<Task>61</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-07-04T15:06:32.076491300Z" />
<EventRecordID>14337</EventRecordID>
<Channel>System</Channel>
<Computer>KrisDesktop-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>00006000010000003D00000000F40040000000000000000000000000000000000000000000000000FFFFFFFF010406580300000000000000000000000FFF7D0000803E003C000000000000000300000003000000000000000300000003000000000000000300000003000000000000000300000000000000000000000024040000803E003C000000</Binary>
</EventData>
</Event>
 
Last edited:

Meghan54

Lifer
Oct 18, 2009
11,684
5,228
136
You sure you didn't let those bad old Shell Lube guys put your car keys on it? Or maybe you didn't torque your mounting screws to their proper "recommended" torque?
 

Supersonic64

Senior member
Jun 9, 2010
372
2
0
You sure you didn't let those bad old Shell Lube guys put your car keys on it? Or maybe you didn't torque your mounting screws to their proper "recommended" torque?

Rule Refresher!

In an effort to maintain a friendly and productive Video Cards & Graphics forum, the moderators here at Anandtech would like to continue a proactive approach to forum conduct.

We know that it gets exciting around launch time for new products, however we would ask that all members remain civil to one another and keep the discussions on topic.

By being civil, we observe the following:

First things first: All members, especially new ones, should familairize themselves with the following.

AT Forums TOS:
http://forums.anandtech.com/me...=2147026&enterthread=y

Anandtech Forums Guidelines:
http://forums.anandtech.com/me...=2070583&enterthread=y

Emphasis on the following:

Zero personal attacks (no matter the degree).

No baiting other members into an altercation.

Keep the threads ON TOPIC. Do not derail threads. It would seem the biggest reason for
thread derailment is a member getting personal about the opinion of another member.
Discuss the topic, not what you think of a member for having an opinion.


Learn when to say, "When". Agree to disagree. No need for 15 pages of getting nowhere.


This forum has come a long way, and there is no point in turning back now. :thumbsup:

Thank you very much,

Anandtech Moderators
 

BD231

Lifer
Feb 26, 2001
10,568
138
106
Grey Screen = Overclock Fail, equally true for the 4xxx series. It's already obvious some driver sets do better than others on overclocked cards so there's going to be some variability.

Chance's are your memory is just not up to the task of running 100mhz over stock. Sadly, being that your card is overclocked you have absolutely zero evidence the driver is at fault.

Rinse and repeat with non-overclocked settings and *maybe* I'll consider your claim.
 
Last edited:

CurseTheSky

Diamond Member
Oct 21, 2006
5,401
2
0
Grey Screen = Overclock Fail, equally true for the 4xxx series. It's already obvious some driver sets do better than others on overclocked cards so there's going to be some variability.

Chance's are your memory is just not up to the task of running 100mhz over stock. Sadly, being that you're card is overclocked you have absolutely zero evidence the driver is at fault.

Rinse and repeat with non-overclocked settings and *maybe* I'll consider your claim.

Agreed. The first step to diagnosing a computer problem like this is to reset all settings to stock. Yes, that means your CPU / memory / etc. clock speeds and voltages as well.
 

BD231

Lifer
Feb 26, 2001
10,568
138
106
Agreed. The first step to diagnosing a computer problem like this is to reset all settings to stock. Yes, that means your CPU / memory / etc. clock speeds and voltages as well.

Didn't notice his system specs good catch. Op's entire system is suspect.
 

Boobs McGee

Senior member
Feb 6, 2006
405
0
76
I have had this problem since I put my machine together.

My Specs:
Gigabyte 890 GPA UD3H
1055T w no /oc
G.Skill Ripjaws 2x2GB DDR3 (F3-12800CL9D-4GBRL)
XFX 5850
Corsair 620HX
CM HAF 932

I have ran everything at stock settings. I have run memtest86+ with a ton of passes and no errors. That is with each stick individually and with both installed. I have underclocked my video card on both the core and the mem. I still get the errors. I see it the most with TF2. I was able to play STALKER Clear Sky for a good hour before getting the crash, but TF2 will usually crash within a few minutes of playing. Sometimes it just flashes for a few minutes and lets me play again for a few, but usually the screen has artifacts afterwards even in 2d mode.

One thing I have noticed is that i can get a little more time before it crashes running only one stick of my memory. That made me think something was wrong with my ram, but like I said, memtest comes up clean. I have also tried running 10.5 drivers, but that did not seem to change anything at all. So at least in my case I can say that it is definitely not overclock related.
 

Supersonic64

Senior member
Jun 9, 2010
372
2
0
Overclock has been reset although it passed stress testing for quite some time. The first time I got this error though my card wasn't OC'ed.
 

Hardlin

Senior member
Aug 27, 2004
226
0
71
I'm still unable to reproduce it on my system running any of the listed games. I did speak with a friend who had the problem on his 5850 dual screen setup until he went to the 10.2 drivers. Before that, he could make the problem go away by upping his voltage to 1.2
 

lopri

Elite Member
Jul 27, 2002
13,329
709
126
For me, it would occur when playing games while GPU-accelerated video was played. It disappeared after Catalyst updates some months ago, so I thought it's resolved. Now I'm getting it again when attempting to play 4K video (4096x2304) using MPC-HC.
 

kosh.iii

Junior Member
Jul 22, 2010
1
0
0
I upgraded the CCC on my brand-new Asus G73JH (5870M) from the pre-installed version to 10.6 recently and recognized GSODs in S.T.A.L.K.E.R and Dead Space after ~2-3min of playing since then.

The only thing that solved the issue was installing 9.12 instead. But I supoose now I won't ever see Tesselation in action...

I ran the games w/o Turbo mode by the way, so overclocking cannot be the only issue here.