2x XFX 7950 crossfireX uneven gpu usage and custom fan curves

[Destro521]

Hey everyone I just thought I might ask a few questions about crossfire and other such related questions

I am wondering if it is normal to have one gpu do 100% of the work while the other hovers around 30-60% ?

also my temps are quite high and was wondering if setting the fan curve in MSI AB to above 60% for each stage would be sufficient and if I would come into any problems with it?

At load my gpu 1 card has 85+ Celsius while my gpu 2 only reaches around 75-80 degrees. This is in games such as sleeping dogs with high res textures and War-game European escalation with its full range of DX 11 features.

I wont have any money for quite a while as I am focusing on my Tafe course so im wondering what I can do at the moment. My case is a cm storm stryker with its front 120's facing sideways. Should I change that?

I have also noticed that going from my OC'ed speed of 1200Mhz on both cards cores down to 950MHz doesn't affect temps at all so would this come down to a temperature probe problem or just the high room temps of 35-45 celcius ?

The computer itself is 3 days old and I have focused on trying to find the "sweet spot" for my speeds even though 1200MHz and 1575 memory clock is still stable at stock volts

 

[SavageCupcake]

That's a really high ambient temp mate so its doing well to stay under 90 degrees . Is there any way you could have a fan blowing at the cards for a bit more airflow? Whats the slot spacing between the cards?

 

[Deejeta]

I suggest getting as much exhaust as you can in your build. Two cards that dump their heat into the case like those DD models can heat up a case pretty quick.
Face the front intake fans onto the cards as well.

 

[Destro521]

Theres 1 expansion slot of space between the cards so around an inch of space.
Ive been receiving errors today in games such as battlefield and hitman absolution saying: "DirectX Function "GetDeviceRemovedReason"
and something about no memory or capped memory. but I have 3gb Vram so im practically clueless on what to do these cards are less than 2 weeks old (in my desktop that is) and it literally appeared over night. It might have occurred after I installed 3DS MAX

Update: someone said that uninstalling MSI AB can fix it but its my only way of seeing the temps in real time as I don't know other software that can do the same thing

 

[MrKambo]

Theres 1 expansion slot of space between the cards so around an inch of space.
Ive been receiving errors today in games such as battlefield and hitman absolution saying: "DirectX Function "GetDeviceRemovedReason"
and something about no memory or capped memory. but I have 3gb Vram so im practically clueless on what to do these cards are less than 2 weeks old (in my desktop that is) and it literally appeared over night. It might have occurred after I installed 3DS MAX

Which version drivers are you using at the moment, also are the cards overclocked at all?

 

[Destro521]

Im using 13.1 drivers with a 1100 MHz core on both cards and a 1350 MHz mem clock on both. I have had these cards at this level for the past 2 weeks with no problems. Im beginning to think its a crossfire X error, CS:S doesn't use CFX but Hitman and BF3 Use CFX. I also have the latest CFX profiles and ULPS disabled

 

[MrKambo]

ok right.....

Install the 13.2 beta drivers from here

The 13.2 drivers are so much better than all the other drivers ive played with, also disable ULPS for both cards, it seems flakey at best to be honest and ive had trouble with crossfire not working correctly because the card shuts off etc etc

Use stock clocks, and play games and stuff and see how it goes, the "device removed" error you get, is the driver crashing due to unstable overclocks, because you're running Xfire your overclocks will only be as good as your worst card.

 

[Destro521]

ahh ok I was just wondering if it was unstable but it has been fine at that level until today as I was able to play bf3 and hitman yesterday at the same clocks so I am quite confused

For 13.2 im getting application install package failure

Update: thanks! the 13.2 fixed it