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.
Just smashed my previous best in firestrike with my 290x @ 1230/1625.
We are going to release a new driver tomorrow which will fix the black screen problem you've been experiencing.
Thanks for the update, but that's thrown a spanner in the works!
Been looking at a 290, but with the black screen problem, there was no way I was going to risk it as my kid is a hardcore PC nut and I need stability first and foremost for him-the blackscreen issue I 100% will live without.
I was leaning towards a 780 for PhysX and my boy would put shadowplay to good use as he keeps badgering me to upload some vids to his youtube channel.
The downside to Nvidia though is whether the Nvidia 3D hack for my sammy actually works and is viable as I like my 3D and I'm not willing to junk my very good monitor for a higher changeover cost to then be tied to Nvidia.
And last but not least, from what Iv'e read on the forum, Nvidia isn't as stable in BF4 as AMD-as it's been flawless on my 7950's-and that is my main game for the foreseeable future I imagine.
Guys I have a VERY serious question (since amd said its a driver problem..?)
if it's a driver problem, how come:
1) some people who had black screens RMA'd their cards and the new card was rock solid?
2) How come I haven't experienced any black screens? (the only time I ever had one was when overclocking the memory through CCC and after restarting, it applied the oc on startup and blackscreened on desktop after any gpu/scrolling activity--that's when I knew that that type of lockup had to be something related to memory or GPU protection shutdown).. I've even gone to 1150/1500 (90% fan) with +100mv and it ran 3dmark/firestrike like a baws, and heaven is solid with 1125/1500 and +50mv. I didn't see any probs in BF4 either, and one test mentioned on ocuk, running "dark Souls" which caused this one guy to black screen almost instantly, seemed fine too (and MAME emulator was fine).
Sure I'll do more testing to try to trigger it, but why isn't it happening to me?
(and why does it seem the vast majority of cases are those with elpida memory rather than Hynix?).
Thank you.
I can only think that this means memory timings are being set dynamically through the driver and based on performance during initial (possibly light) workloads. Cards with lower performing memory would then fall over under heavy workloads. This would then explain the differences people are seeing due to the different makes of memory and luck of the silicon draw.On rage3d that cavemanJim put that's its something to do with the gddr5 memory training under different workloads.
Guys I have a VERY serious question (since amd said its a driver problem..?)
if it's a driver problem, how come:
1) some people who had black screens RMA'd their cards and the new card was rock solid?
2) How come I haven't experienced any black screens? (the only time I ever had one was when overclocking the memory through CCC and after restarting, it applied the oc on startup and blackscreened on desktop after any gpu/scrolling activity--that's when I knew that that type of lockup had to be something related to memory or GPU protection shutdown).. I've even gone to 1150/1500 (90% fan) with +100mv and it ran 3dmark/firestrike like a baws, and heaven is solid with 1125/1500 and +50mv. I didn't see any probs in BF4 either, and one test mentioned on ocuk, running "dark Souls" which caused this one guy to black screen almost instantly, seemed fine too (and MAME emulator was fine).
Sure I'll do more testing to try to trigger it, but why isn't it happening to me?
(and why does it seem the vast majority of cases are those with elpida memory rather than Hynix?).
Thank you.
I can only think that this means memory timings are being set dynamically through the driver and based on performance during initial (possibly light) workloads. Cards with lower performing memory would then fall over under heavy workloads. This would then explain the differences people are seeing due to the different makes of memory and luck of the silicon draw.
If these drivers do in fact relax timings, it would be interesting to see if this shows up in benchmarks.
Just smashed my previous best in firestrike with my 290x @ 1230/1625.
You're not buying a 290 because you're afraid your kid wont approve it or whatver? lol
What score did you get?
Nice dude nice. What settings and app you using to overclock ? You on air or water aww man more info please lol
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
Understanding is not a requirement in this situation, only that it works is.I simply don't understand how a driver update can fix this - also pretty ****ed off i RMA'ed my card now.
Understanding is not a requirement in this situation, only that is works is.
Nah, they have to give an explanation too. They're not obliged to, but it would be terrible if they didn't.
Well you cant say they have to and then they are not obliged too.