[Help] DisplayPort Link Failure and Desktop Resets

[zalbard]

Hello everyone,
I am having a bit of a problem here. Hope you can give me a hand.

Setup:

Win7 SP1 64-bit;
Catalyst 11.4 WHQL (the same deal with the beta);
Power Options - High Performance setting;
2x Sapphire Radeon 6970 2GB @ stock for now;
HP ZR30W 30 inch LCD, 2560x1600@60Hz;
ZR30W is connected to the bundled DP-to-DP cable, 2m long;
6970 is connected to the bundled MiniDP-to-DP adapter;
MiniDP-to-DP adapter is connected to the aforementioned DP cable.

At first glance, everything seems to be working perfectly. No lags, blinking, tearing, or anything suspicious.

However, if I leave my PC running and turn off the monitor (by clicking the button on it; I think it completely powers down, no lights, etc) for an extended period of time (over 15-30 mins, not sure), I run into a problem (edit: please see post #4, I think maybe I got it wrong and it doesn't have anything to do with time; still testing, everything mentioned below still applies).

When I turn the monitor back on, I see a small square in the middle of the screen for a second (approximately 640x480 resolution, maybe more, not sure) with my wallpaper on it, everything else around it is black; then my desktop recovers, and all the icons get moved (automatically sorted) into some weird positions. I also get some message about DisplayPort Link failure (I think I actually put a tick at "Don't show me this message again", and it doesn't show up any more... even after driver reinstall). The icon locations basically reset. And not all of them, just those at the edges, so I suspect it tries to fit them onto that tiny square I see for a second, and then it tries to allocate them on the bigger desktop.

I tried a different MiniDP-to-DP adapter, same deal. In CCC > My Digital Flat Panels > Properties, there is a tick at "Enable GPU Scaling", but all the options are greyed out, and "Scale image to full panel size" is picked. Not sure if it has something to do with it. Since I'm using "High Performance" power setting, my screen is never supposed to go to sleep (same goes for PC Sleep and PCI-E Link Power Management, both are disabled), so I am not sure how come this issue is time dependant (if I turn off the monitor just for a few minutes, there is no such problem). S3 is disabled in BIOS, I only have S1 enabled.

Anyway, help, please! I have zero issues with cables and monitor apart from this. Looks like a software problem. I have completely no idea what's going on...

[lowfat]

Same thing happened w/ my HD6870. I would get that error all the time. Couldn't figure out a solution. But it no longer happens w/ my HD6950's.

[zalbard]

Weird. I even tried two different DP ports on this 6970... Same deal. I could try the other card, I guess...
DVI works perfectly fine, by the way.
Wonder if VGA BIOS flash can help...

[zalbard]

Hm, found a way to easily reproduce it. Need to boot up my rig with my monitor turned off. That way I see this happen all the time.
I am having issues reproducing the issue with turning the monitor off and back on after the rig's been booted up. So maybe it only happens on boot up.

Found a related thread, seems to have something to do with DisplayPort and Windows 7 monitor detection. Lots of people with similar problems...
Another thread with complaints, and more links in it...

[WangChung]

Just bought this monitor, and having the same issue. I have two CFed 6950s with unlocked shaders, and it's a brand new monitor connected via DP. Did you ever find a solution?

[photostu]

The solution is to use DVI

[zalbard]

I still use DP. I just turn on my monitor as soon as I start my PC (or at least before Windows starts). No issues then. If you forget, however, you get to rearrange all your icons again.
I believe this may be HP's issue. Old firmware or w/e. But I haven't contacted them because I bought the monitor abroad, so RMA would take forever.
I was also trying to find a more recent BIOS for my 6970, but the reference cards all have the same version. Couldn't find anything more recent...
Anyway, if someone finds a solution or workaround, please post it here.