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

Sapphire accounts for over 75% of our sales on R9 290 series.

We've seen black screen on Asus, MSI and sapphire, but all three only when over clocked quite far.

It seems to be an OC / software issue, though it's a little harder for us to test as we can't sit and play games for hours.

Mine was sent back today. Never been overclocked.

For most of the people it happens at stock, and you can trigger it with Haven or Metro benchmarks, always within 20-30 minutes from a cold boot.
 
I asked last night about the black screen people are getting in BF4 including myself. It would seem a friend of mine also has this issue though he's on a much older gpu, 6870. So I'm happy now knowing it's a game issue rather than a driver/gpu issue. Thought I'd just share my findings with you.

I've filed a bug report with someone I know who is on the Dev Team at DICE. It will be passed onto the right guys but being a random bug, might take a while to work out what's up. Then again it might not so who knows !
 
Its a shame your friend is having issues too but it is very unlikely its the same issue. I wouldn't take any comfort thinking its a dice/battlefield problem its an AMD problem and almost certainly an AMD r9 series problem, its either a coincidence or a black screen crash unrelated. The black screen we are getting is very specific it requires a full hard reset to recover, I've had the screens go black with other cards but not at stock clocks and not in the same way as this one.

Yes the game is screwed and crashes but the black screens the 290 cards are getting is not just in battlefield its just that's the game of the moment so people are playing it a lot.
 
Originally I put these reports down to typical buggy release code in BF4, but this is now sounding more serious. It does sound a lot like components running right at the limit of their stability threshold. So that slight variances in power or temperature together with under-performing memory result in black-out. I can't help but think that the last minute tweaks to the driver and the fan profile are also a factor here for certain cards in certain environments.

I nearly went for the 290X myself but held off at the last minute; which is now looking like a good decision. However I can appreciate how frustrating and disappointing this will be. I really hope AMD get their finger out and sort this for you guys.
 
Originally I put these reports down to typical buggy release code in BF4, but this is now sounding more serious. It does sound a lot like components running right at the limit of their stability threshold. So that slight variances in power or temperature together with under-performing memory result in black-out. I can't help but think that the last minute tweaks to the driver and the fan profile are also a factor here for certain cards in certain environments.

I nearly went for the 290X myself but held off at the last minute; which is now looking like a good decision. However I can appreciate how frustrating and disappointing this will be. I really hope AMD get their finger out and sort this for you guys.

Until your house burns down lol
 
New driver on its way

Hello everyone,

Our Customer Support and Driver Teams have been aware of this problem and been working on it; they collected lots of feedback from our Support Forums, which has been very helpful.

I'd also like to thank those of you who have reached out to me directly via PM (i.e. weldon855) to provide more details about the issue.

We are going to release a new driver tomorrow which will fix the black screen problem you've been experiencing.

Thank you very much for your patience
 
Hello everyone,

Our Customer Support and Driver Teams have been aware of this problem and been working on it; they collected lots of feedback from our Support Forums, which has been very helpful.

I'd also like to thank those of you who have reached out to me directly via PM (i.e. weldon855) to provide more details about the issue.

We are going to release a new driver tomorrow which will fix the black screen problem you've been experiencing.

Thank you very much for your patience

Sounds good.
 
Good new s from caveman Jim, driver update coming this week to fix black screen issue

http://www.rage3d.com/board/showthread.php?t=34006026

Hello everyone,

Our Customer Support and Driver Teams have been aware of this problem and been working on it; they collected lots of feedback from our Support Forums, which has been very helpful.

I'd also like to thank those of you who have reached out to me directly via PM (i.e. weldon855) to provide more details about the issue.

We are going to release a new driver tomorrow which will fix the black screen problem you've been experiencing.

Thank you very much for your patience

THANK YOU.

Sidenote:

Ordered some goodies for my 290x :D.

L0xMQ3Nv.jpeg
 
Last edited:
Hello everyone,

Our Customer Support and Driver Teams have been aware of this problem and been working on it; they collected lots of feedback from our Support Forums, which has been very helpful.

I'd also like to thank those of you who have reached out to me directly via PM (i.e. weldon855) to provide more details about the issue.

We are going to release a new driver tomorrow which will fix the black screen problem you've been experiencing.

Thank you very much for your patience

Really nice guy,
looking forward to the new driver and hopefully finally being able to put my new waterblock on my 290x.
 
Hardware is useless without the software, so if it is a driver bug, AMD have got no one to blame but themselves for all the RMAs. It's taken them a long time to even acknowledge the problem. If they'd come out and said they were aware and working on a fix, a lot of people would have hung onto their cards instead of sending them back.
 
Mine went back yesterday but I will be buying another one, glad to see we finally have some news on the issue though hopefully the fix works, thanks for the updates.

On rage3d that cavemanJim put that's its something to do with the gddr5 memory training under different workloads.
 
Last edited:
Back
Top Bottom