Black Screen after installing newest AMD drivers on R7 370

[koolman179]

Hello, I have had this problem for over a week now. Recently while I was playing GTA V, my screen on my first monitor suddenly went black, and my second monitor got a bunch of yellow and red stripes on it. I had to do a hard reboot, and when I opened another game, the same thing happened again. The only problem is that this time when i restarted my computer, after going past the windows splash screen, the entire computer screen was black. I have tried literally everything to fix this issue, including fully uninstalling drivers, cleaning dust out of my computer, reinstalling my OS, and even switching from windows 10 to windows 7, which is what I am currently running. The only slight workaround I have found is not installing the AMD drivers at all, which allows my screen to work and I can use my computer, except games don't work at all and video plays back at low frames when I am using the Microsoft basic video card driver. Is their anything I can do, or is my card on its last legs? I have read threads on AMDs forums with people claiming that they have the same problem and haven't found a fix yet. The card I have is here: https://www.amazon.com/MSI-R7-370-2GD5T-OC/dp/B00ZGF0TNM

 

[Small_Tarzan]

I probably do know what's happening. Your drivers have installed to a different port.
I have my monitor plugged in the HDMI port and I get black screen when I boot up my PC.
So, I took a DVI cable and plugged it into my GPU and the issue was gone.

I'm not really sure what causes the issue there.
Do you have two monitors?

 

[kiwinadians]

Your problem is identical to one a number of us over on the AMD forums are having. We've tried all of the same solutions to no avail, and it seems like it is a common issue with the older architecture AMD cards and recent windows updates. The strange thing is that once it starts happening, nothing software related seems to be able to make the issue go away. Our worry is that we are experiencing another wave of card culling from AMD with another bad driver issue causing card death. It's fine if you are running a Vega card, they'll replace that on RMA, but our older cards might be done for.

In my case I have an HD 7870, which won't get past a driver install, but works fine in safe mode or with the windows basic driver. My old HD 5750 still works like a charm, but its hardly a backup anymore. I have no issues with stability or power from my psu, and everything else has been tested and is stable in my build. Seems like this is a systemic issue, and I hope for all of our sakes that it gets resolved soon. Most of the cards affected are no longer able to be RMA'd, so hopefully something good can come of it. If not, I guess I'm baking a gpu as a last resort.

 

[koolman179]

Your problem is identical to one a number of us over on the AMD forums are having. We've tried all of the same solutions to no avail, and it seems like it is a common issue with the older architecture AMD cards and recent windows updates. The strange thing is that once it starts happening, nothing software related seems to be able to make the issue go away. Our worry is that we are experiencing another wave of card culling from AMD with another bad driver issue causing card death. It's fine if you are running a Vega card, they'll replace that on RMA, but our older cards might be done for.

In my case I have an HD 7870, which won't get past a driver install, but works fine in safe mode or with the windows basic driver. My old HD 5750 still works like a charm, but its hardly a backup anymore. I have no issues with stability or power from my psu, and everything else has been tested and is stable in my build. Seems like this is a systemic issue, and I hope for all of our sakes that it gets resolved soon. Most of the cards affected are no longer able to be RMA'd, so hopefully something good can come of it. If not, I guess I'm baking a gpu as a last resort.

I saw that, MSI took my card for RMA and now it is working. Just try getting it fixed.

 

[koolman179]

Never mind, the problem is back even after an RMA.