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:
- VGAs: Sapphiretech R9 290 Tri-X OC (dual, in Crossfire)
- Monitors: Three Dell U3014 (one on DVI, two daisy chained on DP, all 2560x1600) and a 1080p TV on HDMI.
- 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.