Second GPU turning itself off?

[powelly]

Ok so, not crossfired in a really long time. howcome my second card turns itself off? i've checked the pci-e slots and swaped the cards round, ran in 1 pci-e but its only the second card, is this a feature that i'm unaware of?

 

[r7slayer]

Do you have MSI afteburner installed? If not download this tool, its a great tool btw.

Go into settings and disable ULPS. If you hover over this setting it should tell you what it does. In short it disables Ultra low power state which stops the secondary crossfire card going into a idle sort of state.
It does warn it can cause instability issues but i think this is something rare but its worth a shot to see if it stops your problem. Also you have to disabled ULPS every time you install the graphics driver i believe.

 

[dholdi]

Yes as slayer says disable ULPS, I haven't experienced any instability issues.

 

[Quartz]

Ok so, not crossfired in a really long time. how come my second card turns itself off?

Because it's supposed to turn itself off when not in use. As the others state, this is ULPS. But don't worry about it. As long as it fires itself back up when you're gaming, that is.

 

[powelly]

Do you have MSI afteburner installed? If not download this tool, its a great tool btw.

Go into settings and disable ULPS. If you hover over this setting it should tell you what it does. In short it disables Ultra low power state which stops the secondary crossfire card going into a idle sort of state.
It does warn it can cause instability issues but i think this is something rare but its worth a shot to see if it stops your problem. Also you have to disabled ULPS every time you install the graphics driver i believe.

yes i use afterburner, which brings me onto my next issue. before i installed the card and when i first installed it it would show my core/mem clocks but now they're all at 0 for both cards which is odd.

 

[dholdi]

I have had AB do this after a driver update, usually a reinstallation ( of AB ) sorts it.

 

[powelly]

I have had AB do this after a driver update, usually a reinstallation ( of AB ) sorts it.

already tried that but no luck this end

 

[Confused Stu]

What two cards are you running Powelly? I've always left ULPS (aka ZeroCore) running on my cards as I like one card going to sleep and hence silent when it's not in use. Never had any issues and it always jumps into life as soon as Crossfire's needed.

Try not running Afterburner at startup, but try manually starting it once CCC has fully loaded and see if that helps at all with the monitoring. I've always run my Afterburner on a delay of 30 seconds after startup as that way my overclock/fan curve settings in AfterBurner are never over-ridden by CCC loading in after and I've never had an issue with monitoring, so might be worth a shot.

 

[powelly]

running an r9 285 with an r9 380 (they really are just re badged) I've not a problem with ULPS now, i just wasn't sure if it was a feature or the cards/mobo playing up. last time i ran crossfire was 2 5830s years ago so yeah i'll try putting after burner on a delay and see what happens.

 

[LoadsaMoney]

As above, its normal, my 2nd card also turns off, its a power saving feature, Afterburner, i had the 0 readings at first with my 2x Furys, found it was the Unofficial Overclocking Mode, as when id reinstalled it after popping the cards in, i just put it straight back to how it was on my 290X, Without Powerplay Support, so i switched it to Disabled, and the clocks appeared fine.