Hello!
I have an R9 290x crossfire setup and as per usual it isn't working, only this time it is different, if you fancy yourself a bit of a challenge, I'll run through some details to save some time:
Power?
1300w EVGA G2 PSU, single 100Amp 12v rail so no issues here.
Cards?
The first 290x is a gigabyte, currently it is fitted with a G10 and Kraken x40
The second 290x is a reference, currently fitted with a G10 and a Corsair H90
VRM Cooling?
Both have more than adequate VRM cooling with gelid enhancement kits all round (don't reach beyond 80c in regular games)
Drivers?
I've tried 16.7.3, 16.8.2 and 16.8.3 crimson.
I will note down now that I've tested both cards, I put them both in at the same time, disabled xfire and fired up heaven on monitor 1, switched main displays and fired up heaven again on monitor 2.
I checked with GPU-z and Crimson and both cards were being 99/100% utilised. So tested separately but at the same time if that makes sense?
Ok, so I ensure crossfire is enabled in crimson, fire up Furmark, 240fps, clearly crossfire is working, flawlessly in fact! After 10minutes of Furmark I close it and load up Heaven.
I will describe the process that occurs, I'm thinking motherboard but others might disagree.
Heaven loads on monitor 1 and within 5 seconds the picture completely freezes, the other monitor however works fine and I can see GPU-z updating temps (I've tried with and without any monitoring software open btw) I can alt-tab and move the cursor on monitor 2 I can even use chrome if it happens to be open on monitor 2. However, if I try to attempt to close the benchmark/game on the taskbar then after 10 seconds both screens lock up and I can't do anything, sound still continues to play but the image is completely locked, the same happens if UAC appears, same happens if I use CTRL + ALT + DELETE.
I couldn't do too much to figure out what was wrong with crossfire lastnight though, think I might have flicked the switch on the Gigabyte 290x because I couldn't even get it to boot into windows for 15 seconds before it black screened. For some reason, there is a switch on the gigabyte 290x that breaks the card 0___0.
I believe the motherboard could be to blame;
I have been perfectly able to run crossfire before now with 2x 7950's (use bridges)
Whenever I make a BIOS change, the system shuts off after saving changes, then I hear it's usual boot routine but the monitors don't receive a signal, it's like the graphics card hasn't been detected properly or something.
This happens with any graphics card and results in me standing up, flicking the power switch on the PSU, waiting till it's completely drained the cap, then flicking the switch again, going to the breaker box to flick the breaker, then returning and pushing the power button. Only then will it turn on again as normal.
This process which I went through 15-20 times lastnight has driven me a little bit insane so I do apologise if this post seems too to the point.
I only recently bought the reference 290x, I did test it with furmark on it's own for 15minutes or so.
The seller wants to know if I am ok with it and that it works etc, should I cut my losses and just send it back?
Or is it likely that something else is to blame? Such as the motherboard?
thanks to anyone who has spent the time to read this
thanks more to those who have any ideas
I have an R9 290x crossfire setup and as per usual it isn't working, only this time it is different, if you fancy yourself a bit of a challenge, I'll run through some details to save some time:
Power?
1300w EVGA G2 PSU, single 100Amp 12v rail so no issues here.
Cards?
The first 290x is a gigabyte, currently it is fitted with a G10 and Kraken x40
The second 290x is a reference, currently fitted with a G10 and a Corsair H90
VRM Cooling?
Both have more than adequate VRM cooling with gelid enhancement kits all round (don't reach beyond 80c in regular games)
Drivers?
I've tried 16.7.3, 16.8.2 and 16.8.3 crimson.
I will note down now that I've tested both cards, I put them both in at the same time, disabled xfire and fired up heaven on monitor 1, switched main displays and fired up heaven again on monitor 2.
I checked with GPU-z and Crimson and both cards were being 99/100% utilised. So tested separately but at the same time if that makes sense?
Ok, so I ensure crossfire is enabled in crimson, fire up Furmark, 240fps, clearly crossfire is working, flawlessly in fact! After 10minutes of Furmark I close it and load up Heaven.
I will describe the process that occurs, I'm thinking motherboard but others might disagree.
Heaven loads on monitor 1 and within 5 seconds the picture completely freezes, the other monitor however works fine and I can see GPU-z updating temps (I've tried with and without any monitoring software open btw) I can alt-tab and move the cursor on monitor 2 I can even use chrome if it happens to be open on monitor 2. However, if I try to attempt to close the benchmark/game on the taskbar then after 10 seconds both screens lock up and I can't do anything, sound still continues to play but the image is completely locked, the same happens if UAC appears, same happens if I use CTRL + ALT + DELETE.
I couldn't do too much to figure out what was wrong with crossfire lastnight though, think I might have flicked the switch on the Gigabyte 290x because I couldn't even get it to boot into windows for 15 seconds before it black screened. For some reason, there is a switch on the gigabyte 290x that breaks the card 0___0.
I believe the motherboard could be to blame;
I have been perfectly able to run crossfire before now with 2x 7950's (use bridges)
Whenever I make a BIOS change, the system shuts off after saving changes, then I hear it's usual boot routine but the monitors don't receive a signal, it's like the graphics card hasn't been detected properly or something.
This happens with any graphics card and results in me standing up, flicking the power switch on the PSU, waiting till it's completely drained the cap, then flicking the switch again, going to the breaker box to flick the breaker, then returning and pushing the power button. Only then will it turn on again as normal.
This process which I went through 15-20 times lastnight has driven me a little bit insane so I do apologise if this post seems too to the point.
I only recently bought the reference 290x, I did test it with furmark on it's own for 15minutes or so.
The seller wants to know if I am ok with it and that it works etc, should I cut my losses and just send it back?
Or is it likely that something else is to blame? Such as the motherboard?
thanks to anyone who has spent the time to read this
thanks more to those who have any ideas
