Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
He already knows - thats why I went back to 1.3.0. He's a dick head anyways, I'd rather just use 1.3 than deal with him.
Dick head wishes empty head boy Merry XMas. Hope Santa will make you present and give some brains.
Strange 1.41 works for me.. only thing I seem to have to do is disable ATI HDMI Audio driver and im back running stable again twice now on two different systems. Personally I love afterburner. Not so much for the overclocking part but for the fan control. Anyone can OC in CCC just fine... but you cant build a fan profile like you can in Afterburner.
Dick head wishes empty head boy Merry XMas. Hope Santa will make you present and give some brains.
I just installed my brand new XFX HD 5870 and loaded up L4D2. Within 2 minutes I got this famous gray screen crash with sound looping.
I have nothing overclocked and am just running the ATI 9.12 drivers with hotfix. No Afterburner or any other special apps.
I switched back to my previous XFX HD 5770 card. I'll be sending the HD 5870 card back to the retailer Monday unless ATI releases a fix before then...
Here are my system specs:
Seasonic X-650, Gigabyte EP45-UD3P, Intel Core 2 Quad Q9550S, A-DATA 8GB PC2-6400, XFX HD5870, Intel 160GB G2 SSD, Western Digital WD20EADS 2TB, LG GGW-H20L, Samsung SH-S223Q, Windows 7 Ultimate x64
He should ask for his money back... oh yah that right, he codes that program and offers it for free.
He should ask for his money back... oh yah that right, he codes that program and offers it for free.
Is this happening with all brands of 5870's? Any brand I should avoid? Sapphire? XFX? Or is it a problem with all the cards in general? Luck of the draw type of deal..?
Well its not the over clocking part that isn't working, but the voltage control that seems to be the issue. You do still need to unlock overdrive in the CCC for the overclock to take effect from AB.
I need 1.187mv for mine to be stable @ 1Ghz core, AB 1.4.0 and 1.4.1 were crashing with the core at 1Ghz but 1.3.0 its perfectly fine. Found it to be AB voltage control to not work properly.
Make sure you use two separate power cables from the PSU. Maybe it's not enough power from a single power cable.
The weird thing is, most people were saying that the card ran fine for playing 3D games but would crash in Windows during basic 2D stuff. If it was a case of the card not getting enough power, you would think that it would be stable doing 2D as the card wouldn't be taxed nearly as heavily and then crash when put under load during 3D apps.
Not true, legal owners of MSI cards purchasing it with Afterburner CD pay me 0.01 EURODean can get his 0.01 if he wish.
What do you mean unlock CCC for OC to take effect? My overdrive is still locked and grayed out but overclocking fine with AB.
Benchmark before and after and see...
Try using this:
Make sure you use two separate power cables from the PSU. Maybe it's not enough power from a single power cable.
Also not the problem in my case. I have a Corsair HX1000 PSU. That has a total of 6 dedicated 8-pin PCIe connections, of which I'm using two. It is perhaps 30% loaded at maximum load on my system.
well i moved my ddr2 1141mhz to the other slots last night and guess what i greyscreened with sound loop and vert stripes. Quickly i put ram back in other slots. Ive been rock stable since i flashed to asus bios and oc via smart dr.
so what does this mean ? drivers ? 58xx sniffs out weak memory or hardware oc ?
I know sometimes some hardware doesnt play well with other hardware. 5870's not very hardware friendly ?
do you guys ever get some long pauses in l4d2 with sound loops but then game plays fine like it was a 3-8 sec pause ? looks and sounds like a crash but then plays fine.
Could anyone else with these crashes do me a favor and test this out?:
Connect a second screen and add it in extended mode (not group it in Eyefinity). Use Catalyst 9.12 hotfix.
You'll notice that the idle temps are now much higher and the clocks are fluctuating between higher clocks. Load temps should be around the same.
Run games/benchmarks where it normally crashes on one of the screens .![]()
The cards are set to clock up higher at idle when running dual monitors. This is normal. For those having crashes you should be knocking your video cards back to stock clock and not using any aftermarket overclocker. You should also set your system back to stock settings. If your crashes go away after this then you know there is a problem with either your system stabilty, your video OC, or the third party OC application you may be using. Also for me disable ATI HDMI fixed me up all over again. It also fixed a coworker having the same problem. The Gray screen is so generic.. its no one thing that causes it.
The initial implementation of WHEA focuses on platform hardware devices, including processor, memory, cache, and system interconnects such as PCI, PCI-X, and PCI Express. Peripheral device errors remain under the control of their respective device drivers.
Higher idle clocks might help with this problem, which is why I would prefer if someone else with the crashes could test this too The grey screen issue isn't about a general instalbility in the system. If so, it wouldn't occur in my system which was 100% stable with a 4870x2 for a year and didn't have crashes before the 5870.
However, I do belive that the problem is related to ACPI power management vs. Powerplay and that they changed something in the 5000 series power management that causes instability on some systems.
I have logs from way back on my system and the first occurance of WHEA-logger error came after installing the 5870. It happens after some crashes (not all) and can be found in the event log upon restart after the crash:
http://www.microsoft.com/whdc/system/pnppwr/whea/default.mspx
The generic nature of the grey screen error and the randomness of when it crashes might be explained, if its a powerplay/acpi issue. If you check the link of WHEA above, you can see that it relates to more then just the GFX card.
So, other things might trigger this, but if the 5000 series are more sensitive to it, it might crash from this. Even though WHEA doesn't log an error in event manager after each crash, it still is active before each crash and might cause a crash in conjunction with the 5870.
Again, could anyone please test their system with a second screen as shown in link above?
I agree with some of that but your like the 15th person to tell me ..."My system was 100% stable with my old card and now crashes with my new card" After eventually talking these ppl into going bakc to stock clocks and re-checking thier ram wtih memtest most of them found either ram issues or that going bakc to stock clock fixed thier crashes. This card is notorious for taking a completely stable OC in a system and makign it unstable. Not that this is your problem but its kinda getting old hearing someone say how stable thier system is and then finally they go back to stock clock and thier problems go away. Good luck with your issue though.
well i moved my ddr2 1141mhz to the other slots last night and guess what i greyscreened with sound loop and vert stripes. Quickly i put ram back in other slots. Ive been rock stable since i flashed to asus bios and oc via smart dr.
so what does this mean ? drivers ? 58xx sniffs out weak memory or hardware oc ?
I know sometimes some hardware doesnt play well with other hardware. 5870's not very hardware friendly ?
do you guys ever get some long pauses in l4d2 with sound loops but then game plays fine like it was a 3-8 sec pause ? looks and sounds like a crash but then plays fine.