57xx and 58xx locking problems with stripes

[Oese]

@roadcone: yes with water comes as well, but only in unstable condition for me..

[HeXploiT]

Pretend your 5870 came at 750/1100. Now overclock it. How are you doing?

[w4tch0]

OK lads,

for Cypress cards (5850, 5870 and 5970) the 10.1 hotfix for GSOD is out:
http://support.amd.com/us/kbarticles...rruptions.aspx

Downloading right now

[HeXploiT]

Fix. http://support.amd.com/us/kbarticles...rruptions.aspx


Won't be able to test mine until tonight. Share your results.

[Darxide]

Damn, I got excited there for a minute...then noticed it's only for 5800 series.
Hope 5700 hotfix comes soon.

[Lokinhow]

Fix. http://support.amd.com/us/kbarticles...rruptions.aspx


Won't be able to test mine until tonight. Share your results.

installed, the problem wasn't fixed, BUT, I tried again to underclock the clock to AMD defaults clock speeds (I have a factory OCed card, XXX edition) and it seems like the problem is fixed, then I tried the GPU clock at the XXX edition (755MHz vs 725Mhz stock) and..no problems, the problem only returns if the memory clock is a bit above 4GHz GDDR5 (XXX clocks are 4.5GHz). remenber, underclocking doesn't fixed the problem with previous drivers.

well, it's not 100% fixed but it's better now.

[w4tch0]

In your case I'd RMA that card. Remember that the GSOD crash is a symptom common to various different isues with the card. The driver hotfix just fixes one of them. Yours has obviously a Hardware problem, not being able to run at XXX "stock" clock.

[zalbard]

There might be more fixes soon out to address the other issues, you never know.

[Lokinhow]

In your case I'd RMA that card. Remember that the GSOD crash is a symptom common to various different isues with the card. The driver hotfix just fixes one of them. Yours has obviously a Hardware problem, not being able to run at XXX "stock" clock.

I doubt it is a hardware problem. Because GSOD only shows here some seconds after login in windows, then I just need to reboot, after reboot I can run ever furmark at xtreme burn mode @ 950MHz core/4.8GHz memory or any other game/benchmark @1GHz/4.8GHz for hours, and let the computer turned on for days...if the card were damaged, it would certainly fail on doing this
but, if I reboot again, *GSOD*, I just need another reboot and everything runs fine ok again.

now, with this drivers and running the memory @ 4GHz there aren't any GSOD, after boot I can even put the clocks at 4.5GHz again, it only can't stay above 4GHz when system is booting.

[HeXploiT]

Well I only had about 20 minutes to test my xfxxxx last night playing L4D2.
Never had a crash but about five times the screen would blink off like it was going to crash and then come right back on. Lasted less than a second each time.
More testing needed.

[BulldogPO]

Cat 10.1 Hotfix :
http://support.amd.com/us/kbarticles...rruptions.aspx

[Philwong]

Anyone noticed the GPU core voltage spike? Idle is 0.95V and can jump up to 1.65V in 3D which fired up the VRM to more than 100 degree celsius even with watercooling.

Phil

[cabbspapp]

I've been having a different issue with my 5770 than you guys. With 9.12, 9.12+hotfix, 10.1, and 10.1+hotfix (thought I might as well) I sometimes get a blurry desktop when I'm done gaming. It's not always the full screen, usually just the middle that's fuzzy. It goes away upon restart. Does this at stock and overclocked speeds. Sometimes clocks jump down to 400/900 core/mem while in game. I've forced 2D clocks to 450/900 with no sign of improvement.

The other issue is that I can't enable multicore rendering in L4D2. It creates a horrendous amount of input lag when pressing keys and trying to aim. Problem is non-existent with it off.

[wez]

I've been having a different issue with my 5770 than you guys. With 9.12, 9.12+hotfix, 10.1, and 10.1+hotfix (thought I might as well) I sometimes get a blurry desktop when I'm done gaming. It's not always the full screen, usually just the middle that's fuzzy. It goes away upon restart. Does this at stock and overclocked speeds. Sometimes clocks jump down to 400/900 core/mem while in game. I've forced 2D clocks to 450/900 with no sign of improvement.

The other issue is that I can't enable multicore rendering in L4D2. It creates a horrendous amount of input lag when pressing keys and trying to aim. Problem is non-existent with it off.

Force the 2D clock to the same as your 3D, eg 850/1200 which I assume is your cards stock 3D clocks, and not 450/900?

Got no idea what might cause the fuzzy desktop... but could try and turn off aero etc in windows..

[Particle]

I decided I'd had enough and modified the BIOS to just lock to 800/1150 for all powerplay states. It's relatively safe and is definitely easy for anyone else who wants to just be done with it. No more messing with software tools. Just use this:

http://www.techpowerup.com/rbe/

[BulldogPO]

Haha, I upgraded to Catalyst 10.1 hotfix at HD 5970 machine which were doing just fine with catalyst v9.12(non hofix) as 9.12 hotfix and 10.1 were not working properly or making almost instant tripes after boot, just under minute from logging in to Win7 X64.
Same thing happened with hotfix so I backed down to 9.12 drivers.

[zalbard]

Haha, I upgraded to Catalyst 10.1 hotfix at HD 5970 machine which were doing just fine with catalyst v9.12(non hofix) as 9.12 hotfix and 10.1 were not working properly or making almost instant tripes after boot, just under minute from logging in to Win7 X64.
Same thing happened with hotfix so I backed down to 9.12 drivers.

Oh god, these HD5970s are really messed up, wonder what's wrong.

[cabbspapp]

Reinstalled my drivers without HDMI audio and registration and so far so good. No more blurry desktop after gaming. I can also enable multicore rendering in L4D2 without issue now.

[Lokinhow]

Selecting "high performance" in Windows's power options seems to help a lot...

[BulldogPO]

Really weird issues with these cards indeed.

[Musho]

I'm REALLY getting fed up by this problem. Has happened for me at stock clocks _and_ overclocked clocks (which passed 30 LinX loops, 1 hour of OCCT and 24 hours of prime blend) on 2 different 5870s, no matter what driver (even the so-called hotfix). If the problem's still here when Fermi hits the shelves, I'm selling my ATI cards and I'll go to the green team. I'm no fanboy by any means. I've used a 8800gtx > 4870x2 > 2x 5870. But this problem is simply ridiculous.

Specs:
Q9650
Maximus II Formula (p45)
4x1gb Kingston 1066mhz 5-5-5-15 RAM
Corsair HX1000

[Biker]

Hi guys.

Just wanted to say i have solved most of my 2D problems with a 5870 by partially disabling hardware acceleration....

More details here

There is a very interesting article over at Toms hardware that sheds a lot of light our 2D issues (read especially page 4 and then from 8 onwards).

[w4tch0]

Well, it's been a few weeks so it's time to sumarize for me.

Ever since 10.1hotfix release I had no GSOD. Non, Nada, Nichts.
10.1 catalyst and earlier versions + original bios (113-C00201-100) = occasional GSOD at random occasions.
10.1 catalyst and earlier versions + ASUS unlocked 1200/1400 bios = occasional GSOD at random occasions.
10.1 hotfix + ASUS unlocked 1200/1400 bios = no more GSOD's for a week
10.1 hotfix + new Sapphire bios (113-C00201-103) = no GSOD's another week
10.2 catalyst + new Sapphire bios (113-C00201-103) = no GSOD's as of yet either.

Big relieve here.

//edit:
ASUS m2f with Q9550 @ 3.825GHz
2x2GB Patriot DDR2 1080MHz 5-5-5-15 2T
Sapphire 5850
Win7 64bit

[BulldogPO]

There is my version of summarize with HD 5970:

Catalyst 9.12 = everything works fine (GSOD about one a week).
Catalyst 9.12 hotfix = GSOD straight after logging in to Windows 7 X64, or within one minute.
Catalyst 10.1 = GSOD straight after logging in to Windows 7 X64, or within one minute.
Catalyst 10.1 hotfix = GSOD straight after logging in to Windows 7 X64, or within one minute.
Catalyst 10.2 = no GSOD but machine instantly freezes after logging in windows.
Catalyst 10.3 beta = no GSOD but machine instantly freezes after logging in windows

So, WTF???

[ml2517]

There is my version of summarize with HD 5970:

Catalyst 9.12 = everything works fine (GSOD about one a week).
Catalyst 9.12 hotfix = GSOD straight after logging in to Windows 7 X64, or within one minute.
Catalyst 10.1 = GSOD straight after logging in to Windows 7 X64, or within one minute.
Catalyst 10.1 hotfix = GSOD straight after logging in to Windows 7 X64, or within one minute.
Catalyst 10.2 = no GSOD but machine instantly freezes after logging in windows.
Catalyst 10.3 beta = no GSOD but machine instantly freezes after logging in windows

So, WTF???

This is after uninstalling + driver sweeper and then fresh install? Are you using Afterburner with the unofficial overclocking or something else like that?

I had zero issues with my 5970's after doing the complete uninstall + driver sweeper and then freshly installing 10.3 beta + that profiles thing. I don't use the unofficial overclocking stuff in Afterburner though.