Some users, myself included, are experiencing display corruption when using multiple monitors on R9 290 VGAs running Windows 8/8.1 and Windows 10 with Catalyst 15.8 beta or Catalyst 15.7.1 (the problem did not occur with Catalyst 15.6).
The following references show some discussions on the matter on other forums, including videos showing exactly how the problem appears:
It seems, so far, that there is not a specific trigger cause, since it randomly starts even when the computer is showing only the desktop. Some users have found that this problem may be related to memory idle clocks being set to low for multiple monitors, which is partially confirmed by the fact that the display corruption never happens while gaming (except when some games, like GTA V, are paused). Also, it seems the problem is happening only with R9 290.
I have reported this bug to ATI using the "AMD Issue Reporting Form" (AMD Issue Reporting Form ) since Catalyst 15.7.1 was released. Now that Catalyst 15.8 beta is available, unfortunately, not only the problem persists, but also, it is not listed on the "known issues" section of the "beta release notes", which seems to indicate that AMD has not acknowledged the issue. This is very worrying, because this bug is ruining our experience with R9 290, Catalyst and Windows 10.
Has anyone found a solution for this problem? Reverting to Catalyst 15.6 solves the issue, however, we lose WDDM 2.0 and DirectX 12 support, which is very undesirable. Any help is highly appreciated.
Additional information about my setup that might be useful:
- The three U3014 are always used together (either as individual displays or as a single display using eyefinity), but never together with the TV. When the TV is used, the U3014s are powered off. Whenever the three U3014 are used together (either as individual displays or combined with eyefinity), the issue happens. Using only the TV (U3014s powered off) the problem does not happen.
- Enabling/disabling eyefinity display group temporarily solves the problem (setting it to the opposite state that was set when the problem starts).
- The problem seems to be uncorrelated with Crossfire settings, since, after disabling crossfire, it also randomly starts.
So far I have only seen this happen for users that have a native resolution higher than 1080p. I have yet to see a report from anyone with multiple 1080p monitors which may be why this isn't as wide spread
Thank your for reporting this in the correct forum. Hopefully AMD will pick up on this and fix this asap.
Summary of our findings in our thread on a different part of the forums are that this is related to driver 15.7.x and 15.8 beta. It has worked with all previous versions of the driver. Most importantly, it is linked to DisplayPort. It seems like the display connected with DP is key. If i turn of and on my monitor connected with DP the issue is temporarily resolved. I f I turn of my monitor connected with DVI(leaving DP display on) the flickering continues even on one monitor.
Resolution is not the key, some users has trouble with 1080p monitors, but most of us run higher resolution monitors
My gear: Asus R290X, dual screens (Dell U2713H) connected with DVI and Displayport. Resolution 2560x1440 on both screens. Windows 10 64bit (experienced the same issue first on 8.1 after i installed 15.7 before upgrade of windows to v 10)
The other thread detailing this:
Hello, I'd like to state that I'm having this issue with 15.7.1 on a Fury X, stock speeds, brand new HDMI cable connection, Windows 10 x64 Pro. Single monitor, 1920x1080 @ 60hz.
This occurs on the desktop/browsing the internet sporadically for me, I'd say the average is once per three weeks. I found a very recent youtube video that shows the exact kind of corruption I'm describing:
Per the reddit thread you linked in your original post, I'm going to try completely disabling Overdrive for a few weeks, since I haven't been using any overclocking while gaming anyway.
Just wanted to throw my hat in the ring and state that this appears to be a driver wide issue, regardless of Windows version, resolution, multiple or single monitors, or gpu.
Flard, thank you for your update. Maybe now that the problem is affecting ATI's top of the line product, it will get some attention. I'll send ATI a new driver bug report linking this discussion.
Previous thread about this here Flickering
The Trigger is when the display changes from 3D to 2D. EG; exiting most games and going back to the windows desktop causing this to start
I have been further testing this, running some games in window mode eg(Diablo 3) on the middle monitor will stop the flickering from happening (also works if i put the d3 window on the other monitors as well), but this is annoying - i shouldn't have to run a game in window mode to stop the flickering happening.
It can be really bad at times if running youtube on 1 monitor and working other items in the other 2 monitors...
my temp fix is putting a game up in window mode, restart the PC, changing refresh rate to whatever then returning it to 60 Hz, entering a game and playing for 5 mins then exiting...
Happened with all the 15.XX drivers - the last known working driver for me is 14.12
Funny thing is - i haven't noticed it in any game as yet when running full screen across all 3 monitors (Eyefinity)
this is very annoying indeed. and whats more frustrating is that now im running windows 10 - it seems to be doing something to the AMD drivers because my raptr app keeps advising me to install 15.7.1 even when i have done a clean wipe and install of these 3 times..
Issue occurred in windows 7 as well with the same 15.xx drivers - 14.12 was working fine...
I was actually running two 1920x1080 monitors on this r9-290 card since the card first came out. Never had any issue. Changed to two 2560x1440 monitors today and it was having problems within 10 minutes. The "fix" I am currently using is to that I am running a 3 hour high res mp4 file in windows media player minimized to the taskbar. This video running causes the GPU clock to move a bit, but it causes the memory clock to stay maxed out.
You simply have to put some load on it to prevent idling. I was able to stop it using a high res youtube video, but every time the youtube video went to a commercial the screen would flicker and act up till the high res video put the load back on. Was funny.
Has anyone tried driver 15.9 Beta?
I was eagerly waiting for this release, but, as our problem is not listed neither under the "Fixed Issues" nor under the "Known Issues" sections of the beta release notes, I am reticent about uninstalling 15.6 (which works fine) to install 15.9.
After spending an entire day trying to figure out why low load caused this issue. I decided to try re-wiring some stuff. I had one monitor connected to the HDMI port and one to the Display Port. I re-wired it leaving the one in the Display port, but then daisy chaining from the MST output on that monitor over to the second screen. It hasn't flickered since. The driver shows the display port output as 7.42 Gbps and 35% load on each screen. Total load 70%. Total Bandwidth 21.26 Gbps.
Maybe it has something to do with using the mixed connection. With my old 1080p screens I had one in HDMI and one in a DVI port and it worked fine. Or, perhaps the HDMI cable just didn't handle the extra bandwidth going from 1080 to 1440. But so long as I kept something running to put load on it there was never a flicker, so I do not think it was a bandwidth issue.
At this point it has been stable for days, so something in that port change made a difference.
Great outcome for you.
however for some of us running greater than 1440 i dont think this will help much (yes i know it will be even the more so minority of this issue)
still frustrating that no one in AMD wants to even say a peep about this....