jandarsun8

Hey guys,
I canceled my WoW subscription as I'm getting bored out of my mind and WoW was working just fine. This past weekend I decided to play some of my older games and I'm getting freezes/lock ups in some games with a GPU recovery pop up in the back ground and not sure what the problem is. I was using ver 9.6 drivers before and upgraded to the new 9.8 with same results. Bios is at the latest along with all other drivers from Gigabyte (using an older board so they haven't updated lately).

I'm running two 3870 Sapphire Vaper-X Toxic cards in crossfire, one is OC'd to 830 (max at 840) and the other is OC'd at 875 (found max at 890 but...) using ATI's unlock feature. Both are running at 53 Cel under load (climbs to 60 depending on room temp), 43 idle.

I don't know if it's crossfire that's causing the problem, one of the cards going bad, maybe a slot on the mb that's going out, or just game engines in general as not all games are having problems. I also don't know if I'm disabling crossfire correctly or not. ATI's site states that in order to disable crossfire you have to reset your cables but I've got everything going through the one card that's on the first PCI E slot anyway so I don't know. ATI's site also suggest a reboot after disabling it (which I haven't done yet or know if it's actually needed).

I haven't done too much testing yet but I thought I'd post here for any suggestions ahead of time on what it could be.

Games I've played that have had errors...

Thief 3: sometimes it's with in the first 5 minutes, other times I've played for about 30 minutes.

Roller Coaster Tycoon 3 (daughter loves this game): After 15 minutes just locked whole pc, required a hard boot.

Need for speed Underground: Booted out to Windows with GPU error after 30 minutes.

CoD 2: Game froze for about 2 minutes and then minimized with GPU error in back ground.

Games that have played just fine:

MoH Pacific Assault: 3 hours, no issues. The last Pearl Harbor scene was killing on my old card, this played just fine.

Nascar 4: Very old game, worked just fine with crossfire enabled. Only played for an hour but no problem during that time (was kind of surprised it worked).

Rainbow Six 3 Raven Shield and Athena Sword. Hours and no issues.

Any ideas/ suggestions? Kind of driving me nuts but really not sure where to even look into this at. All games have the most recent patches.

Jand.

__________________

OldBuzzard

Do ya think that maybe, just maybe there is a REASON that they 'suggest' that? Come on...a re-boot would have taken less time to do that it took for you to type all of that. That should be the FIRST thing to do.

Now, AFTER you FOLLOW THE DIRECTIONS, and if you are still having the problems, you might try playing with the CATALYST AI setting in CCC. I know that IL2 1946 (an older game) has issues with some installations if CATALYST AI is even on. So, try changing it from ADVANCED to STANDARD, or STADARD to ADVANCED, depending on how it's set now. If that doesn't help, try unticking the box to turn it off completely.

Something else to try is setting the AA and AF to "Use Applicction settings". Some games don't like it if the GPU is using AA/AF. OR, try setting the IN GAME AA/AF to none, and just allow the GPU to do it. I know that the MS Flight sims work much better with the in game AA/AF setting off.

Another thing that might help is going back to the stock clock settings. It's possible that those games don't like anything OCed.

__________________
When looking for a reason as to why things go wrong, never rule out sheer STUPIDITY

jandarsun8

Well, I was at work last night and why I posted such a long thread and also why I didn't have time to really look into the problem to much. I had posted specific games that I have had issues with in hopes that someone would say "yeah, having the same problems, just a game issue." so that I didn't have to rip into it before finding the problem.

Max Payne had worked before after disabling crossfire with out a reboot in the past so ATI's suggestion was why I mentioned it on if it's actually required to do so in order to actually disable it. This I did not know but I'll test it to find out. Thank you for the other suggestions to look into though, that I do appreciate.

__________________

DJ BIG T

also try going back a few drivers at last resort...

__________________