Author

Topic: Dual card setup help (Read 1198 times)

sr. member
Activity: 266
Merit: 250
March 08, 2013, 04:49:15 PM
#2
Now that the card is mining properly I've messed around with OCing a bit and am running at 1050/300MHz core/mem, with +20% power (see above) and at stock voltage. Will run over weekend to check stability.

Edit: Just to help anyone in the future following this, I used the tricks here to manage to get the clocks down to 300.

I would like some advice on temps though. Setting fans to 100% gives a reasonable core temp of 78C but I'm worried about one of the VRM temps. One is down at 67C but the other is up at 97C which seems a little worrying to me. Any comments on whether VRMs can handle this kind of temp for a long time would be appreciated, and if not what can be done about it.

Also, suggestions of best settings to run would be great, though this is secondary. Am currently running OpenCL miner on GUIMiner with "-v 2 -w 256" switches and am getting ~520MH/s with the above settings
sr. member
Activity: 266
Merit: 250
March 08, 2013, 04:37:30 PM
#1
Hi,

Long time miner, long time reader of this forum, first time posting here (thread reposted here from here)

I used to have 2x6950 rig, just swapped one of the 6950s for a 7950 and am having some problems getting it running right.

Problems are as follows: when all 3 monitors are plugged into the old 6950 the new card appears as "Disabled Adapter" in Catalyst Control Centre and is therefore automatically down-clocked to 500MHz and hashrate drops to ~250MH/s. I can get around this by connecting a monitor to it so that it appears as an "Enabled Adapter" but this is not ideal as it means that I need to run the memory at a more reasonable speed in order to avoid visual artefacts.

I have been in the registry and disabled ULPS for the card but this didn't fix the "disabling" of the card, the only way I can find to get around this is to connect a screen to the card. I didn't have to do this with my old dual 6950 setup so this is quite frustrating. I have updated CCC which might be causing the problem, but I had to do this to get the new card seen by the system at all so I don't think a rollback is viable.

I'm sure other people have had this problem but couldn't find anything after quite a bit of googling and forum searching so I thought I would just admit defeat and ask for some help!


System details are:
OS = Win7x64
Miner = GUIminer (using OpenCL)
Display Driver = 9.012
OpenCL(tm) Driver ver. 10.0.1084.4
Catalyst Control Center ver = 13.1 (2012.1219.1520.27485)

If there's any other relevant information I've forgotten then please ask!

PS Just noticed that even when running the new 7950 with stock settings (core clock and mem) that I am a) still getting visual artefacts on the screen connected to that card and b) GPU-Z shows that it is is spending some time at 880MHz and some at 500MHz so av. hashrate is only ~350. (880MHz is its stock clock rate as it is a VTX3D X-edition card, and 500MHz is it's idle/disabled clock rate).

Any help with any of these problems would be greatly appreciated!

Edit: 500MHz is not the idle state clock speed, that's 300MH so I have no idea why it's cycling between 880 and 500MHz.

Edit 2: Also, what overclocking utility would people recommend? I used to use Sapphire Trixx as the 6950 is a Sapphire card, but for the new card, as soon as I close Trixx it forgets the fan profile I created and the fan speed drops so my guess is it isn't able to write to the card. And recommendations on this as well?

Part solution: The clocking up and down between 880MHz and 500MHz was solved by upping the power to +20% (without touching the voltage). Apparently normal power limit doesn't allow running at 100% load even at stock clocks (found on this thread).
Part solution : Needing to have a monitor plugged in to enable the card can be solved by plugging on in temporarily and then moving it back to the other card. However, this has to be done each time the computer is rebooted and is a very ugly workaround so would still be interested in hearing a proper solution to this problem.
Jump to: