AMD issue / Flickering using multi 1440p monitors and drivers 15.7 and up

[KaRLiToS]

Flickering issue

• Issue going on since June with drivers 15.7 and up.
• Flickering when using 2D and 3D applications
• Use of 2 or more 1440p monitors
• 1 monitor plugged via DisplayPort connection
• R9 290xs cards

2D issue: https://youtu.be/iEDeIxsWroI
3D issue: https://www.youtube.com/watch?v=EgCBw4zgfXQ


Displays and connections / Monitors
1st: CrossOvers 27Q Led-P DVI
2nd:CrossOvers 27Q Led-P DVI
3rd: Samsung U28D590 (4k) native Display Port

Just to explain when the flickering occur with drivers 15.7 and up

• 15.7
• 15.7.1
• 15.8
• 15.9.1
• 15.10
• 15.11
• AMD Crimson Edition
• 15.11.1
• Crimson 15.11.1

Without Eyefinity

Eyefinity Enabled

 

[KaRLiToS]

How can you break a freakin driver 6 months ago and not repair it after all the bug reports?

It is so exhausting to be an AMD customer. You want to have faith but they keep spitting on you.

 

[railven]

How can you break a freakin driver 6 months ago and not repair it after all the bug reports?

It is so exhausting to be an AMD customer. You want to have faith but they keep spitting on you.

As a long time AMD user, I basically reached that point. When their Frame Pacing driver broke a lot of things for me, I basically called it quits.

I never expect AMD to be perfect, but you can only make excuses for so long.

 

[Despoiler]

So in all of your troubleshooting you must have found this right?

http://www.overclock.net/t/1568733/windows-10-flickering-screen/10#post_24290168

 

[KaRLiToS]

So in all of your troubleshooting you must have found this right?

http://www.overclock.net/t/1568733/windows-10-flickering-screen/10#post_24290168

Yes I found it, but since 2014 it worked fine and now out of a sudden it is broken and I need to get a MST hub that will not support my resolution of 7680x1440? No thanks AMD, get your things fixed for god sake. This is not excusable.

MST Hub is plugged in Display Port and a single DP will not be sufficient for 7680x1440 at 60hz

I don't know why Warsam said this.

Keep that in mind: I'm done with AMD.

 

[Actaeon]

Bummer. AMD can't afford to lose its best customers but they make it hard to stay loyal sometimes. It's sad because their hardware and price points are very competitive to Nvidia.

Anyway, you're doing the right thing by voting with your wallet.

 

[KaRLiToS]

I agree, their hardware are very good.

 

[Despoiler]

Yes I found it, but since 2014 it worked fine and now out of a sudden it is broken and I need to get a MST hub that will not support my resolution of 7680x1440? No thanks AMD, get your things fixed for god sake. This is not excusable.

MST Hub is plugged in Display Port and a single DP will not be sufficient for 7680x1440 at 60hz

I don't know why Warsam said this.

Keep that in mind: I'm done with AMD.

Why are you here if you are done? All you are doing is throwing a temper tantrum at that admission.

Did it ever occur to you that they might not be able to "fix" it? They added FRTC and VSR in 15.7. Adding those features might have required that whatever they did before in the code had to be re-done or removed. In other words, perhaps they were band-aiding a limitation that was always supposed to show itself. That band-aid is no longer possible with new feature additions.

 

[KaRLiToS]

Why are you here if you are done? All you are doing is throwing a temper tantrum at that admission.

Did it ever occur to you that they might not be able to "fix" it? They added FRTC and VSR in 15.7. Adding those features might have required that whatever they did before in the code had to be re-done or removed. In other words, perhaps they were band-aiding a limitation that was always supposed to show itself. That band-aid is no longer possible with new feature additions.

Are you even aware of the issue?

Did you read the threads I linked, the issue only happens in 2d mode with idle clocks. If I put the 2d clocks memory at 1250mhz the issue is gone but wasting more power and increasing temperature.

The issue doesn't occur when playing games but as soon as I exit it, the flickers start again. With eyefinity enabled on desktop (2d idle) the flickers starts after several minutes and you see the memory clocks going crazy from 150mhz to 1250mhz.

My workaround works like this.
-Eyefinity disabled
-When I start a game I enable eyefinity and start a game real quick
-When exiting the game I disable eyefinity again

I didn't have to do this before. I mean for my Tri 6970 setup, and neither with my Quad 7970 and neither with my Quad 290x until July.

If I'm throwing a temper tantrum it is because the 100 bug reports that I have sent and the 10000 that other users sent seem to be ignored. I'm trying the vocal way now.

 

[Despoiler]

Are you even aware of the issue?

Did you read the threads I linked, the issue only happens in 2d mode with idle clocks. If I put the 2d clocks memory at 1250mhz the issue is gone but wasting more power and increasing temperature.

The issue doesn't occur when playing games but as soon as I exit it, the flickers start again. With eyefinity enabled on desktop (2d idle) the flickers starts after several minutes and you see the memory clocks going crazy from 150mhz to 1250mhz.

My workaround works like this.
-Eyefinity disabled
-When I start a game I enable eyefinity and start a game real quick
-When exiting the game I disable eyefinity again

I didn't have to do this before. I mean for my Tri 6970 setup, and neither with my Quad 7970 and neither with my Quad 290x until July.

What solution do you propose? Ditch my monitors? Ditch triple monitors gaming? Ditch AMD? Ditch PC gaming?

Oh and by the way, if I'm throwing a temper tantrum it is because the 100 bug reports that I have sent and the 10000 that other users sent seem to be ignored. I'm trying the vocal way now.

I was aware of the issue prior to this thread. It's obviously not as widespread an issue as you'd think. It didn't make the Crimson top 10 fix list because your issue isn't in the top 10 reported issues. Simple logic.

I would have flashed my BIOS with new memory base value to 300mhz before I would have come onto a technical forum and written the post you did. That might be too technical for you though. Low 2D memory clocks has actually caused similar issues for non-CF configurations.

Also, pretty sure an MST hub can handle your setup at full bandwidth. "Supported output resolution:up to 2560X1600@60Hz each monitor in DP1.2 MST".

Oh and by the way, if I'm throwing a temper tantrum it is because the 100 bug reports that I have sent and the 10000 that other users sent seem to be ignored. I'm trying the vocal way now.

Again, did it ever occur to you AMD hasn't responded because maybe it's not possible to fix the issue and still have FRTC and VSR work? It's that or the addition of those features makes the required fix very involved.

 

[SimianR]

Hey Karlitos, sorry that you're having this issue, it sounds frustrating. Have you tried making a custom 2D profile in afterburner or another overclocking program and trying memory clockspeeds slightly above the normal idle speeds? Obviously 3D memory speeds will boost power consumption by quite a bit, but perhaps somewhere in between would solve the flickering without wasting too much power.

 

[KaRLiToS]

Thanks SimianR for the respectful reply. The increase of the 2d clocks is an okay workaround but I prefer disabling eyefinity while desktoping.

Despoiler, can you explain why it might be to technical for me and second please link me to this MST hub you are referring to?

 

[KaRLiToS]

Just for your information, AMD aknowledge the bug locking the fan at 20% but people saying it breaks the GPU even with the temp treshold is overreacting.

 

[KaRLiToS]

....

 

[Arachnotronic]

So you gonna sell your current AMD GPUs and put the money towards some NV GPUs or are you going to stick it out this round?

 

[KaRLiToS]

So you gonna sell your current AMD GPUs and put the money towards some NV GPUs or are you going to stick it out this round?

I am waiting for 16nm and HBM2, my workaround is simple but annoying but I can still play my games.

I threaten a lot that I'll switch to green, but I will have to look at what is best for me between NV and AMD next year. It is always a tough choice. I love Quad cards and AMD is best with Quad scaling. Every aspects will be analysed for my next purchase. But 16 nm is a must.

 

[3DVagabond]

Despoiler, please find me a suitable MST hub supporting my resolution at 60hz (7680x1440) which is 11.1 MegaPixels (4k is 8.3 MegaPixels).

And I have two monitors on DVI (native) and one native display port monitor.

Two monitors are 1440p and the DP one is 4k. (I put it in 1440p for multi-monitor use though) In other words, I'm using all native connections.

I expect an answer from you.

I don't think a single MST hub has the bandwidth for 7680*1440. They can do 5120*1440, I believe. What monitors do you have that are 3840*1440?

Also, I thought you had gone all DP a while ago, which solved your issue?

 

[KaRLiToS]

I don't think a single MST hub has the bandwidth for 7680*1440. They can do 5120*1440, I believe. What monitors do you have that are 3840*1440?

Also, I thought you had gone all DP a while ago, which solved your issue?

I have two that are 2560x1440 and one is 3840x2160 but when I set eyefinity I prefer to put it in 2560x1440. For triple monitors at 7680x1440.

My issue was never solved, I had to sell one of the three CrossOvers 27Q Led-P (DVI) and I had to buy a native DisplayPort monitor instead and I decided to settle on a 4k one so I could still play my games in eyefinity and sometime 4k but I never play 4k much, only eyefinity.

When using my three CrossOvers, I had to use one with a DVI to DP adapter USB powered. But they broke it and I didn't want to wait for months for their fix, which I don't even know if they fix it, I did it myself this time around.

AMD even sent me the Bizlink one to try to solve my issue but they sent the same adapter but different brand.

The issue was discussed here (somewhere) http://forums.anandtech.com/showthread.php?t=2353407&page=18

 

[3DVagabond]

So, I'm confused. Are you trying to hook all 3 monitors to a single DP on the card? AFAIK a single DP using an MST won't supply the bandwidth. Even if it could I don't think that will solve your issue. It seems like it's purely VRAM 2D clocks. Is that correct?

 

[KaRLiToS]

So, I'm confused. Are you trying to hook all 3 monitors to a single DP on the card? AFAIK a single DP won't supply the bandwidth. Even if it could I don't think that will solve your issue. It seems like it's purely VRAM 2D clocks. Is that correct?

No, its despoiler that proposed the use of MST Hub. What I'm trying to do is used my setup like I always used to... but AMD broke it since driver 15.7 (You see the many links in the OP :thumbsup: )

It is the same issue as in the video here https://youtu.be/JYoNTXetOtw

My monitors were like this in 2011 (Tri 6970 and Quad 7970)
1st: CrossOvers 27Q Led-P DVI
2nd: CrossOvers 27Q Led-P DVI to DP adapter
3rd:CrossOvers 27Q Led-P DVI to DP adapter

In 2013 Quad R9 290x
1st: CrossOvers 27Q Led-P DVI
2nd: CrossOvers 27Q Led-P DVI
3rd:CrossOvers 27Q Led-P DVI to DP adapter

In 2014 they broke something in drivers for so long and had to sell and buy another monitor (same setup)
1st: CrossOvers 27Q Led-P DVI
2nd:CrossOvers 27Q Led-P DVI
3rd: Samsung U28D590 (4k) native Display Port


And now, another issue going forever

 

[3DVagabond]

OK. Well he might not be aware of the bandwidth limits of a single DP?

Well, sometimes you have to roll back if a new driver breaks things. This is a fact of life. The more exotic the setup the more chances there are of something slipping through the QC checks. There won't be as many people playtesting a setup like yours.

I had one where when I turned on Soft shadows in Cinema 4D it crashed. Rolled back to the prior drivers and it was fine. The next driver it was still broken. The one after that fixed it.
I was using a Radeon card and when I first filed the bug report I got the standard "We don't guarantee Radeon with Pro Aps, like C4D. I replied that's fine, I'm assuming since something in your new driver broke the OGL soft shadow function you might want to see what it is because it's likely nothing to do with the ap. They agreed and said they would look into it, and apparently did. It just took a while for it to get fixed.

That said, have you tried upping your 2D memory clocks to see if that works?

 

[KaRLiToS]

OK. Well he might not be aware of the bandwidth limits of a single DP?

Well, sometimes you have to roll back if a new driver breaks things. This is a fact of life. The more exotic the setup the more chances there are of something slipping through the QC checks. There won't be as many people playtesting a setup like yours.

I had one where when I turned on Soft shadows in Cinema 4D it crashed. Rolled back to the prior drivers and it was fine. The next driver it was still broken. The one after that fixed it.
I was using a Radeon card and when I first filed the bug report I got the standard "We don't guarantee Radeon with Pro Aps, like C4D. I replied that's fine, I'm assuming since something in your new driver broke the OGL soft shadow function you might want to see what it is because it's likely nothing to do with the ap. They agreed and said they would look into it, and apparently did. It just took a while for it to get fixed.

That said, have you tried upping your 2D memory clocks to see if that works?

I agree with you. It's complex setup, but still, it sucks when they break something. It is not like I'm using ancient hardware, it's some 290x.

Yes man I have tried upping the 2d clocks. :thumbsup: Working but not the workaround I prefer for it.

The thing that is getting me mad is all the money I throw at them, yet they always break the drivers rendering my experience miserable, the worst of the worst were the hard lock I had with the 7970s in 2012. It took them 12 months to fix the issue, glad I only bought them 7 months after release so I had to wait only 5 months, but imagine 5 months without being able to use your gear.

Check the first VID in the OP and let me know how you would react for 5 months with that.

http://www.overclock.net/t/1295809/...rash-hang-freeze-galore-what-to-do-fixed/0_30

Check the vid at 0:39
It's my vid
https://www.youtube.com/watch?v=ZNE0qyyiZE8

 

[3DVagabond]

I agree with you. It's complex setup, but still, it sucks when they break something. It is not like I'm using ancient hardware, it's some 290x.

Yes man I have tried upping the 2d clocks. :thumbsup: Working but not the workaround I prefer for it.

The thing that is getting me mad is all the money I throw at them, yet they always break the drivers rendering my experience miserable, the worst of the worst were the hard lock I had with the 7970s in 2012. It took them 12 months to fix the issue, glad I only bought them 7 months after release so I had to wait only 5 months, but imagine 5 months without being able to use your gear.

Check the first VID in the OP and let me know how you would react for 5 months with that.

http://www.overclock.net/t/1295809/...rash-hang-freeze-galore-what-to-do-fixed/0_30

Check the vid at 0:39
It's my vid
https://www.youtube.com/watch?v=ZNE0qyyiZE8

Sorry for your experiences, but that's not pertinent now really. So you upped the 2D mem clocks and it fixed it, but you want it fixed some other way? Am I understanding you correctly?

If so, it makes sense that a system with as many pixels as yours might require a higher than stock setting. For 99% of the users out there it would do nothing but increase their power target for no benefit. If that fixes it, then just do it and go back to gaming, would be my advice.

 

[KaRLiToS]

Sorry for your experiences, but that's not pertinent now really. So you upped the 2D mem clocks and it fixed it, but you want it fixed some other way? Am I understanding you correctly?

If so, it makes sense that a system with as many pixels as yours might require a higher than stock setting. For 99% of the users out there it would do nothing but increase their power target for no benefit. If that fixes it, then just do it and go back to gaming, would be my advice.

It is doing it to people with triple 1080p monitors. And I don't want 4 cards with memory running at 1000mhz all the time. ( And when you say that to me, it's like saying, but why don't you disable all your 3 other cards and play on one single monitor and set the resolution at 1080p so you don't get any drivers issues.)

It's like the lock fan issue we see right now with Crimson drivers... do you expect every user to go everytime in AMD overdrive to set the fan curve and speed correctly? No you don't expect that, AMD already got their hotfixfix 3 hours ago... Explain to me how come they wait 5 MONTHS to repair the issueI get. Do you think I don't feel ripped off like a freaking jerk. This is what makes me mad with AMD.

Please go read the threads I linked in the OP, and please notice how every people are tired of this... like very tired, me including.

 

[3DVagabond]

It is doing it to people with triple 1080p monitors. And I don't want 4 cards with memory running at 1000mhz all the time. ( And when you say that to me, it's like saying, but why don't you disable all your 3 other cards and play on one single monitor and set the resolution at 1080p so you don't get any drivers issues.)

It's like the lock fan issue we see right now with Crimson drivers... do you expect every user to go everytime in AMD overdrive to set the fan curve and speed correctly? No you don't expect that, AMD already got their hotfixfix 3 hours ago... Explain to me how come they wait 5 MONTHS to repair the issues I get. Do you think I don't feel ripped off like a freaking jerk. PLEASE.

Thank you to support and understand me. Please go read the threads I linked in the OP, and please notice how every people are tired of this... like very tired, me including.

I don't need to go elsewhere. I've seen your threads here. I'm just trying to address your current problem.

It seems for now you have two options 1) revert to the last drivers that worked 2) up the memory clocks. The current drivers are broken for you as is. None of us can address that, unfortunately.