• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Advice : MSI R9 280x Crossfire

I must admit I forgot to check this thread after my original reply.

What Vcore are you cards showing at Tat? I notice Abitar reported his at 0.850 which sounds really low to me so that could have been the cause, or contributing factor, to his problem(s).
 
Thanx for the reply...
I'm running the cards at stock speed or rather the one that has been installed will have been running fine solo (everything stock/default and no OC), then when I add a second card, upon starting up, Windows throws the BSOD and error before I get fully into the OS and thus it isn't a problem I get from doing an OC on the CPU or GPU. I have tried to OC the clock speeds a bit on each card, but that didn't result in this BSOD 3b error - only starting up with two cards did this . . .
I could perhaps lower the core and memory clock of the card already in the computer, but I fail to see how that would help.
I also thought of lowering the CPU voltage, but it's at default - should be stable...
The ASUS I got in the machine now, runs at 0.850 when idle and 1.200 when on full load.
 
Hi Tat

I did fix my issue in the end by replacing my motherboard to a gigabyte z77ud4 from b grade stock. The asus board I did have worked fine with different card in crossfire for year, in fact its still working now with a single card but the asus board just didn't like the 280x's for some reason.

I only had issues playing games (BF4) mainly, it was solid at the desktop or running gpu benchmarks but gaming was causing lockups and BSOD.

With the gigabyte board I have oc'ed my 2500K to 4.8 and the 280x's to 1100/1600 with no issues so far.
 
Last edited:
.Griff. said:
I must admit I forgot to check this thread after my original reply.

What Vcore are you cards showing at Tat? I notice Abitar reported his at 0.850 which sounds really low to me so that could have been the cause, or contributing factor, to his problem(s).
Click to expand...

Hi Griff

What is the default vcore on your cards showing as in afterburner?
 
Abitar said:
Cheers LtMatt that's what I'm getting unless I oc my monitor to 96hz or 120hz then it sticks at 500 / 1500 on 2nd card for some reason.
Click to expand...

Yes once the hz goes past a certain point the card moves up to the next clock state.
 
Abitar said:
Just odd how it only happens on GPU 2 not the one connected to the monitor.
Click to expand...

That is odd. From memory i think 120hz should be at normal idle clocks of 300/150. Above 120hz on gpu 1 idle should be 500/1500. (or whatever your memory speed is) THat is strange that gpu 2 is clocking up though if nothing is plugged into it. Probably worth droppping Thracks a trust message and see what he says.
 
You must log in or register to reply here.
Back
Top Bottom