Page 1 of 1
7970 Crossfire clock issues
Posted: 14 Jun 2012, 05:06
by BIGGRIMTIM
I just installed my second 7970 for crossfire and everything was great until I rebooted. Now all of the games I try to play run at about 20 fps. The second card will not come out of the 2d clock mode. I tried disabling ULPS, but that did not work. I have tried Afterburner and Trixx to try and set the clock speed but that does not work either. Any help is appreciated.
It seems to be working fine
Posted: 14 Jun 2012, 15:59
by BIGGRIMTIM
It seems to be working fine now. I uninstalled and reinstalled the 12.6 beta driver 3 times and the third time was the charm. Not sure what caused the problem.
BIGGRIMTIM wrote:It seems to
Posted: 15 Jun 2012, 15:21
by BIGGRIMTIM
It seems to be working fine now. I uninstalled and reinstalled the 12.6 beta driver 3 times and the third time was the charm. Not sure what caused the problem.
I spoke too soon. After a fresh boot last night problem is back. Anyone else have this problem?
I have now tried 4 different
Posted: 16 Jun 2012, 06:57
by BIGGRIMTIM
I have now tried 4 different drivers and nothing seems to work. My second card will not come out of low power state. Any help is greatly appreciated. If I can't fix this by Sunday I am selling these and buying some GTX670 FTW cards.
you can easily fix that!
Posted: 16 Jun 2012, 19:12
by Haldi
you can easily fix that!
idle 2D clock means 500mhz/150mhz ? Or 300/150 ?
or UVD Clock aka 501mhz/1375 or 925/1375 ? (Depending on which card, pre OC'ed ?)
(Edit: Actually 2nd Card should be at 0/0mhz in ZCP mode sleeping!)
So if this happens to me i just overclock my Vram from 1425(Pre OC'ed XFX BE) to 1426mhz. That helps Core clock to go back to 1000mhz :)
Thanks for the help, but I
Posted: 17 Jun 2012, 05:53
by BIGGRIMTIM
Thanks for the help, but I have no idea what you are referring to. I have tried to run the cards overclocked and that did not help. I am now running on a clean install of windows 7 x64. I am running the latest beta driver 12.6 beta. it was fine for a little while but I had t reboot for updates and then the problem game back.
aha?So it's just the second
Posted: 17 Jun 2012, 07:10
by Haldi
aha?
So it's just the second Card which is Stuck at 2D Clocks ? (how fast exactly?)
Did you try to change place ( PCI-E Slots) Of Both cards and test again ?
You did overclock Core AND Vram right ?
Haldi wrote:aha?So it's
Posted: 17 Jun 2012, 18:27
by BIGGRIMTIM
aha?
So it's just the second Card which is Stuck at 2D Clocks ? (how fast exactly?)
Did you try to change place ( PCI-E Slots) Of Both cards and test again ?
You did overclock Core AND Vram right ?
I thought I found the issue, but I was wrong. It looked like it may be related to Adobe flash hardware acceleration but it is not. I have tried different slots and overclocking. the second card gets stuck at GPU 500MHz and VRAM 150MHz. If I disable crossfire and then re-enable it it is fine until I reboot.
Thanks
nope, Flash player aka
Posted: 18 Jun 2012, 00:08
by Haldi
nope, Flash player aka Hardware acceleration cant clock to 150mhz Vram.
So, did you try uninstalling MSI Afterburner, Trixx, or any other GPU clock control tool ?
Haldi wrote:nope, Flash
Posted: 18 Jun 2012, 14:34
by BIGGRIMTIM
nope, Flash player aka Hardware acceleration cant clock to 150mhz Vram.
So, did you try uninstalling MSI Afterburner, Trixx, or any other GPU clock control tool ?
I don't have any of those applications installed. I have been monitoring speeds through AMD Vision Center/Catalyst Control Center. I have used GPU-Z but it is just a executable. A friend of mine has 2 680s and I am going to borrow them tonight and see how Nvidia Surround works out. I am going to keep looking for a solution, because I really don't want to go through the hassle of selling these cards. Thanks for the help.
Hope you find a way to fix
Posted: 18 Jun 2012, 20:42
by Haldi
Hope you find a way to fix it.
Oh, and tell more about the 2x GTX680 VS 2x HD7970 after you've tested them troughly !
Just for the sake of testing, do you have an empty HDD somewhere ? Might try to install Windows from scratch and install only GPU drivers. If that works it's definitly a software fault.
Haldi wrote:Hope you find a
Posted: 18 Jun 2012, 20:53
by BIGGRIMTIM
Hope you find a way to fix it.
Oh, and tell more about the 2x GTX680 VS 2x HD7970 after you've tested them troughly !
Just for the sake of testing, do you have an empty HDD somewhere ? Might try to install Windows from scratch and install only GPU drivers. If that works it's definitly a software fault.
I am trying some older drivers while I wait for my 680s to test. 12.4 is not any better, but 12.3 seem to work, but the clock speeds on both cards remain at full speed. I did notice something odd when using Firefox 13.0.1. When I open the browser the second card will come out of low power mode and go to full speed with the 12.6 beta driver. This is of course the few times the card was not locked @500/150MHz. Bf3 performance does not seem quite rite though. I will install Afterburner just to check usage while in game. I will also report back once I get the 680s going.
jup, some (believe it was
Posted: 18 Jun 2012, 22:51
by Haldi
jup, some (believe it was 12.3) drivers are known for bugged idle clock. so they wont clock down.
BTW! Something you have to try.
"C:UsersHaldiAppDataLocalATIACE"
Profiles.xml
There at the end you'll find
Code: Select all
<Groups>
<Group name="Overdrive5">
<Feature name="TimeUnlocked" />
<Feature name="OverclockEnabled">
<Property name="OverclockEnabledProperty" value="False" />
</Feature>
<Feature name="AutoTuneSupport" />
<Feature name="CoreClockTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&11D5388E&0&0018A">
<Property name="Want_0" value="30000" />
<Property name="Want_1" value="100000" />
</Feature>
<Feature name="PowerControl_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&11D5388E&0&0018A">
<Property name="Want" value="0" />
</Feature>
<Feature name="MemoryClockTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&11D5388E&0&0018A">
<Property name="Want_0" value="15000" />
<Property name="Want_1" value="142500" />
</Feature>
<Feature name="CoreVoltageTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&11D5388E&0&0018A">
<Property name="Want_0" value="850" />
<Property name="Want_1" value="1170" />
</Feature>
<Feature name="MemoryVoltageTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&11D5388E&0&0018A">
<Property name="Want_0" value="0" />
<Property name="Want_1" value="0" />
</Feature>
<Feature name="FanSpeedProtocol_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&11D5388E&0&0018A">
<Property name="FanSpeedProtocolProperty" value="Percent" />
</Feature>
<Feature name="FanSpeedAlgorithm_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&11D5388E&0&0018A">
<Property name="FanSpeedAlgorithm" value="Automatic" />
</Feature>
<Feature name="FanSpeedRPMTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&11D5388E&0&0018A">
<Property name="Want" value="1180" />
</Feature>
<Feature name="FanSpeedPercentTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&11D5388E&0&0018A">
<Property name="Want" value="50" />
</Feature>
<Feature name="CoreClockTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&B16BFE2&0&0010A">
<Property name="Want_0" value="30000" />
<Property name="Want_1" value="100000" />
</Feature>
<Feature name="PowerControl_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&B16BFE2&0&0010A">
<Property name="Want" value="0" />
</Feature>
<Feature name="MemoryClockTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&B16BFE2&0&0010A">
<Property name="Want_0" value="15000" />
<Property name="Want_1" value="142500" />
</Feature>
<Feature name="CoreVoltageTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&B16BFE2&0&0010A">
<Property name="Want_0" value="850" />
<Property name="Want_1" value="1170" />
</Feature>
<Feature name="MemoryVoltageTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&B16BFE2&0&0010A">
<Property name="Want_0" value="0" />
<Property name="Want_1" value="0" />
</Feature>
<Feature name="FanSpeedProtocol_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&B16BFE2&0&0010A">
<Property name="FanSpeedProtocolProperty" value="Percent" />
</Feature>
<Feature name="FanSpeedAlgorithm_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&B16BFE2&0&0010A">
<Property name="FanSpeedAlgorithm" value="Automatic" />
</Feature>
<Feature name="FanSpeedRPMTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&B16BFE2&0&0010A">
<Property name="Want" value="0" />
</Feature>
<Feature name="FanSpeedPercentTarget_PCI_VEN_1002&DEV_6798&SUBSYS_32111682&REV_00_4&B16BFE2&0&0010A">
<Property name="Want" value="50" />
</Feature>
</Group>
</Groups>
Want 0 is idle clock ! Try set that to Normal clock speed.
Well i did not have any luck
Posted: 19 Jun 2012, 19:22
by BIGGRIMTIM
Well i did not have any luck with the 680s. I guess my motherboard (ASUS Crosshair V Formula) has a bug where it will not work with surround and SLI. Single display with SLI was great although it is great with crossfire 7970s. There is supposed to be a new bios for AMD 990FX chipset coming out to fix this issue. I am going to try a few more drivers for the 7970s and after I find something acceptable I am going to reformat and stay put for now
OK my reformat is complete.
Posted: 21 Jun 2012, 14:25
by BIGGRIMTIM
OK my reformat is complete. I have only had time to try out BF3 but it is running great. I am running with no AA but everything else is on Ultra plus HSAO. I am pegged at 60 with vsync on. My bezel corrected resolution is 6048x1200. I am using a modded set of drivers that I found (Catalyst 12.6 9.00 BETA June 12 – 7900 MOD). So far no clock issues except the second card does not completely turn off. I can live with it for now. Also I am unable to overclock with these drivers, but I really don't need to at this point.
Ive had a similar problem
Posted: 18 Aug 2012, 17:10
by KJ128
Ive had a similar problem with my Diamond 7970s. I insalled the 2nd one, ran BF3, no issues. Quit the game to do something else and when i played again, whammo- ultra low fps. Afterburner OSD showed low 3D clocks while in game as well.
I forced the clocks via MSI AB and so far so good. I think i also disabled and re-enabled CF. Using 12.6 WHQL, no CAP