Does anyone still get the AMD 7xxx bug where your monitor doesn't wake up from sleep?

[alexruiz]

The issue is still present on the latest drivers.
Cat 14.7 RC (Aug 2014) still the have the bug.

I just did a fresh install of Win7 on a PC that had a corrupted installation. The PC has a HD7770 and was running cat 12.8. Well, instead of restoring an old ghost image, I went for new, and pow, the issue appears.

Win7 SP1 with all updates + cat 14.7 RC.
Exact same PC, no changes in hardware, no different cable, all the same, cat 12.8 was fine, cat 14.7 is not...

 

[Piotrsama]

The issue is still present on the latest drivers.
Cat 14.7 RC (Aug 2014) still the have the bug.

I just did a fresh install of Win7 on a PC that had a corrupted installation. The PC has a HD7770 and was running cat 12.8. Well, instead of restoring an old ghost image, I went for new, and pow, the issue appears.

Win7 SP1 with all updates + cat 14.7 RC.
Exact same PC, no changes in hardware, no different cable, all the same, cat 12.8 was fine, cat 14.7 is not...

Can't you use a different cable/connector?
I solved the problem by using HDMI (instead of DVI).

 

[inachu]

I have the amd 7xxx and have 4 monitors and this does not happen to me.

 

[Obsoleet]

Those states control the whole pc going to sleep, not just the videocard. If adjusting those states solves anything, you had a different problem than the problem this thread was originally created for.

All I can say is, update drivers first. If that doesn't fix it, try a different monitor cable. If that doesn't fix it either your problem is most likely caused by something else than your AMD card.

There's a repost video upon wake from sleep in the S1/S3 sleep mode section of most bios. I'd try everything, depending on how much this bothered someone.

It bothered me quite a bit, and the solution was either use CCC 12.10, or to stop using DP on the problematic monitor. I chose the latter.

 

[Obsoleet]

I have the amd 7xxx and have 4 monitors and this does not happen to me.

It's probably just a good hardware combination. In my case I use Dell and Asus monitors and only the Asus has this problem with the same videocard and cabling.

 

[Cheesesticksandbeer]

7970 3x monitors no issues

 

[Skolomerija]

Have you tried to set PCI Express Link State Power Management to off in Power Management Options?

 

[SSBrain]

Have you tried to set PCI Express Link State Power Management to off in Power Management Options?

It has no effect on this issue.

 

[spaceman]

these bizarre try til something sticks fixes are patronizing at this point
bios states? cheap cables?cheap monitors?...when all these worked w/o issue on several gens of cards from both vendors
i just dont want to have to hard reset my computer or wonder when next inevitable resume might work.
i dont want to investigate all these weird things
i never had to with a single card that wasnt lemon from voodoo banshee on

 

[mindbomb]

I think it isn't an issue with the cables, but an issue with AMD and the dvi display interface. Switching cables isn't the solution so much as switching to displayport/hdmi. I'm speculating atm though, since I have no displayport monitor to check with.

 

[SSBrain]

I think it isn't an issue with the cables, but an issue with AMD and the dvi display interface. Switching cables isn't the solution so much as switching to displayport/hdmi. I'm speculating atm though, since I have no displayport monitor to check with.

I had it happening with DisplayPort too. Believe me, I tried almost everything I could imagine (and that has been suggested here and elsewhere) and it still happens occasionally.

Since this started happening when I switched to a different display (Dell U2412M), I think it has to do with certain display/GPU incompatibilities. That most of the time, turning physically the display off and then on again restores the video link seems to support this hypothesis.

More than a problem with the display itself it probably is likely a problem with the AMD GPU, however. Or the Catalyst drivers, but I never used old ones (on Windows) or Linux (which uses different drivers) long enough to be able to confirm this. This issue never happened to me with other GPUs like for example the integrated Intel HD2500 one I have, though.

 

[KingFatty]

Disconnecting and then reconnecting the video cable physically from the computer, does that *always* solve the issue? Or are some people still having a blank screen even after doing that trick?

 

[SSBrain]

Disconnecting and then reconnecting the video cable physically from the computer, does that *always* solve the issue? Or are some people still having a blank screen even after doing that trick?

Most of the time it does / not *always*; occasionally the screen will remain black with only the mouse pointer showing which likely means that the issue caused some kind of internal Windows crash, requiring a hard system reset.

I tend disconnecting physically the cable from the PC as a last resort when turning the display off doesn't help. However, if it's not something that switching multimonitor configuration with Win+P (ie making the display driver forcibly switch output) helps, then it generally means that a hard system reset is pretty much required to be able to take control again anyway.

 

[alexruiz]

Can't you use a different cable/connector?
I solved the problem by using HDMI (instead of DVI).

I can try, but as I mentioned, old install wirth cat 12.8 had no issues, new install with cat 14.7 has them.

 

[coffeejunkee]

This issue never happened to me with other GPUs like for example the integrated Intel HD2500 one I have, though.

That's only logical, Nvidia and Intel gpu's don't turn themselves off when the monitor goes to sleep.

Disconnecting and then reconnecting the video cable physically from the computer, does that *always* solve the issue? Or are some people still having a blank screen even after doing that trick?

No, when I had this issue I had to reconnect my monitor to the other dvi connector to get my image back.

I can try, but as I mentioned, old install wirth cat 12.8 had no issues, new install with cat 14.7 has them.

Try 14.4. 14.7 is beta so might have issues.

 

[mindbomb]

I had it happening with DisplayPort too. Believe me, I tried almost everything I could imagine (and that has been suggested here and elsewhere) and it still happens occasionally.

Were you using a displayport to dvi cable? cause that still counts as dvi.

 

[SSBrain]

Were you using a displayport to dvi cable? cause that still counts as dvi.

No, that was (is) a normal DisplayPort cable.

 

[CHADBOGA]

I have occasionally had this issue, but only occasionally.

But what I am experiencing lately, without me having made any changes to the monitor or system powering down, is that my monitor doesn't want to go into sleep mode.

I have an AMD HD7850 video card.

 

[nopanopa]

Disconnecting and then reconnecting the video cable physically from the computer, does that *always* solve the issue? Or are some people still having a blank screen even after doing that trick?

That trick never worked for me (my connection is DVI->VGA anyway). I haven't had the problem since the last time I posted here. If that happens again, I'm gonna use the windows key again, see if it still works.

 

[VirtualLarry]

Well, 14.9 WHQL Cats still don't fix this problem, on Win8.1 64-bit.

I got a few AMD BSODs when doing DC (BOINC, Einstein@home). So I stopped doing DC (no more WUs), and let the PC go into monitor sleep mode.

Well, it never woke up. Hitting the power button didn't shut it down either.

AMD drivers SUCK.

 

[godihatework]

HD7870. Win 8.1. WHQL 14.9. Still get SOD.

 

[Rhezuss]

I still have it on the 7950 with 14.4 WHQL but it's really random. What worked for me most f the time was turning the monitor off and on again. 90% of the time it worked and everything was back to normal.

It didn't happened in a month or so now. But I will have my GTX 970 tonight so I guess it's solved now

 

[RussianSensation]

Well, 14.9 WHQL Cats still don't fix this problem, on Win8.1 64-bit.

I got a few AMD BSODs when doing DC (BOINC, Einstein@home). So I stopped doing DC (no more WUs), and let the PC go into monitor sleep mode.

Well, it never woke up. Hitting the power button didn't shut it down either.

AMD drivers SUCK.

It's either your Windows, your unstable overclock, poor electrical delivery (PSU / outlet) or faulty cards. I've been running DC work since HD4890 (August 2009) and in 5 years despite overclocked NV/AMD cards doing DC, I haven't had 1 blue screen with any of the driver versions when doing DC work. My system pretty much ran DC 24/7 when not gaming, other than electrical timeouts due to power outages.

 

[SSBrain]

I wonder if the black screen/wake up issue has something to do with the AMD drivers and Windows itself. Perhaps Windows 10 could bring fixes to this.

 

[Makaveli]

I installed the newest cats yesterday and this is still working for me. As it was on my previous post with the 14.4 drivers.