System Specs First:
GPU: Powercolor RX 480 8 GB
CPU: AMD FX-8350
Motherboard: Gigabyte GA-970A-UD3 AMD 970
RAM: 16gb G.Skill RipjawsX
PSU: 650 Watt Corsair RM650x Modular 80+ Gold
OS: Windows 8.1 64bit
Driver: Catalyst 17.6.1 (Problem is the same with 17.4.4)
Two displays connected:
BenQ GW2255 Full HD connected directly per DVI 60hz
LG LH 3010 TV, connected via HDMI, connected via Sony HTP BD 36 surround system
(The BenQ is my main Monitor and the TV is usually turned off, with power off)
I've been gaming with this setup for 5 months without any problems. Then, all of a sudden during playing Overwatch, my BenQ display turned black and showed "no signal". It turned back on a couple of times before staying black and showing "no signal". However, the system did not freeze and I could hear the game and music playing in the background. When resetting, the Display (BenQ) turns on, shows the boot-up and "windows loading" screen. However, when the system logs into Windows, the display turns black and shows "no signal". The system is running, however, and when I turn on my secondary display/TV (hdmi), the system is working and I can use it with the secondare display. When I look up the display resolution menu, the BenQ display is not displayed, as if it was not connected. This error has been happening for about two days and nothing could really fix it: When I boot in safe mode, both displays work just fine. I uninstalled the driver with DDU, and reinstalled Catalyst 17.4.4, 17.6.1 and 17.5.2 (after uninstalling each time, of course). There doesn't really seem to be a difference between the driver versions.
Strangely, as soon as the driver install is completed, my BenQ display turns black and loses signal. So right now I assume this is a software-sided error? The strange thing is that the signal losses happened quite irregularly: On the first day it happened the monitor used to turn back on a few seconds, then off, and so on. For two days then, it was always like this: Monitor working just fine when booting, signal loss when logging into windows, second display (HDMI/ TV) works always. Of course, I tried unplugging the HDMI cable, still no signal on my main display. I tried system recovery because I thought I might have installed something that could have caused the issue, but without success. THEN AFTER TWO DAYS, the problem disappeared: Everything working just fine.
Everything has been working just fine for about two weeks now, until yesterday evening. I was playing Fallout 4 (ultra settings), as I have been the last couple of days, and then my monitor turns black and shows "no signal" again. Again, this time, the system didn't freeze and I could here the ingame sounds. The display then turned off and on a coule of times (not really "off" and "on", but rather "receiving signal" and "no signal"). This was really really strange and I couldn't really figure out what made the monitor lose signal. I was able to tab out of the game and bring up the task manager and wattman: Nothing special, no spikes in GPU or CPU load. What I noticed, however, is that whenever the dispay turned on again, the steam ingame FPS counter would show 1 or 2 fps for a second before going up to 50-60 again. I tabbed in again, played for 3 seconds, "no signal" again. I tabbed out again, and I see that Windows explorer seems to have crashed and that the system is unresponsive. What? I turned off the system and called it a day.
When I booted the system today, I was presented with the same issues as before: Primary Display working fine during boot-up, losing signal when logged in into windows, TV connected via hdmi working just fine. However, there were two more errors today. The TV (secondary display) went black too randomly and I had to reboot. Then, it went black for 2 seconds, but as of now it is working fine.
I think that the display which is connected via DVI is working just fine and that the cable isn't the problem either.
However, I have got absolutely no idea why a system would work for 5 months, then decide to not recognise a display anymore and show this strange behaviour.
One side note that could be of interest: It was a really hot day when the issue occured for the first time. It was, however, not really hot when the error occured again yesterday.
I found that there are quite a number of people that face issues similar to the ones described above, but none of the solutions to each of the other threads seem to apply to my case. The only "solution" I think could apply in my case.... faulty card. But still, why would a GPU work pefectly fine and then randomly cut off the dvi port?
Hope you guys can help, thank you!