Black screening and artifacts despite upgraded video card (R9 290)

spoonycoot

Distinguished
Feb 1, 2011
33
0
18,540
I have been having this problem for quite some time intermittently after I upgraded my card back in September 2012. I went from a problem free asus 6950(I think) to a gigabyte 7950. This was in windows 7. I started having issues with card black screening and artifacts coming in the screen. It would happen with any type of flash or YouTube video more than in game. It would also cause my pc to not be able to come out of sleep. When I would try to resume the fans would kick but I would have no display out put and it wouldn't respond to any key strokes. I then noticed that some things were still seeing it as a 6950 and I tried everything to uninstall it to no avail. I ended up jacking up some registry keys and had to reformat. I did a clean install on windows 8, but the problems persisted. The one occurring most frequently was it locking up coming out of sleep. I would still randomly get black screens. Fed up I sent the card to gigabyte this winter. Everything seemed to working correctly for a couple of months. Then I moved and my computer had packed up for 3 months. I got it all set up and updated it to the latest drivers. It works for about a week then bam. I tried playing some avi files and it back to it's old ways of black screening and artifacts in the video. It was also hanging up coming out if sleep again which I think it may have done before the driver update. I'm super pissed at this point and I end up getting my money back.

So I order a fancy new Sapphire R9 290 and install it yesterday. I check for driver updates, but the current driver is the latest. I don't have internet I just had to tether my phone. Anyway everything is fine and dandy except for some crazy loud coil whine in the startup of Rome 2(in game coil whine stopped with vsync enabled).

So today my fiancée's watching some avi's in windows media player and f-me it starts black screening and artifacting to the point that it was unwatchable.

To me this seems like it could be a driver issue, but I'm wondering how could this be a problem for almost 2 years. I have yet to try the 6950 this time around, but when I sent the 7950 off this winter the 6950 worked perfectly.

Anybody have any idea what is going on?

Sorry for the long story, thanks in advance.