• 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.

Why is AMD quiet about black screens on 290x?

So whats the general concensus here? Are RMA's fixing the issue or is it time to go looking down the Nvidia route...

The card performed great... when it worked...

Know a couple of people who have RMA'd their 290s that were giving the blackscreen/redscreen thing and the replacements work fine but a couple more just changed to a different card rather than take a chance.
 
Last edited:
if it happens at stock you have a faulty card or an unstable overclock (cpu/ram) or bad power supply so you should rma if you have checked everything else
if it happens when you overclock the memory then you have overclocked the memory to much fot your gpu .

so you can rma in the hope to get a card that overclocks better but there is nothing "wrong" with the card as it performs to spec so your rma may be unsuccessful.

my card is stable at 1200/1350(5400) which is not as high as some cards but not a reason for me to rma.
 
Last edited:
RMA for a new one it is then.

I know its not the PSU as I just brought a 1000w Super Flower from here a week ago originally thinking it could be that.

And my CPU clocks are all off at the moment while testing the GPU.

Now for the bigger question of straight up replacement or refund and get a 3rd party cooler in 3 weeks time considering I wont be RMA'ing this til next week.
 
Well so far I've had Win 8 64bit blue screen on me and the drivers have crashed for the card about 5-10 times since I got my MSI 290X on Friday. I'm beginning to get annoyed, do the upgrade of the drivers to the latest set after changing from my 6970 to the 290 do this in you folks opinions?
 
Well so far I've had Win 8 64bit blue screen on me and the drivers have crashed for the card about 5-10 times since I got my MSI 290X on Friday. I'm beginning to get annoyed, do the upgrade of the drivers to the latest set after changing from my 6970 to the 290 do this in you folks opinions?

Pretty much my experience with the Gigabyte Windforce 290x. Ordered 2 cards; both give me random BSODs. I've tried pretty much everything, including reformats, switching from Windows 7 to Windows 8.1, using a different power supply, etc.

Since both cards are doing it, I've made a determination that it's not a fault with the card (other than perhaps a design fault) per se, and is rather an incompatability somewhere with the rest of my system. As such, I'm returning both cards under DSR for a refund, because I'm wary of the cards being tested and deemed not faulty. That would obviously be a nightmare to deal with over Christmas.
 
I have been trying to speak to Sapphire about this problem but their support is useless, they keep telling me to uninstall drivers and install the latest, even when I have tried that and have done a full reinstall of windows. They have no idea what my problem is and at times it is hard to read their english.:(

Opened a RMA ticket with the place I got it from, I hope I get this sorted quickly.
 
While I wait for my RMA to process my ticket at Sapphire is still open, got to love their support.

Dear Sir
Still suggest you test your card on other motherboard and see. Please also take video for your card issue and feedback us. Sorry for your inconvenience.
Regards

I am staying away from Sapphire in the future, the rest of the replys to my ticket are like that. lol
 
IMO AMD should recall all 290s with Eplida memory on it, or at the very least try to add the option for increasing the memory voltage, as unstable memory clock seem to be the highest contributor (if not the sole contributor) to the probability of black screen issue.
 
Last edited:
can you not underclock the memory ?

if you can - could you not run for a few days underclocked and see if black screens persist ? if they do - then less likely to be a hardware issue (although not impossible)
 
Back
Top Bottom