Anyone else still getting the no video when waking monitor from sleep?

E

EnhancedInterrogator

New member
Man, I've had this bug for like a year now. Is anybody else still having this problem? Monitor wakes, but the screen is blank. I have to put the whole computer to sleep and wake it to get video back.

The weird thing is that sometimes it doesn't happen. And with some beta drivers it happened less than others. Pretty much happens every time with the new WHQL driver.
 
Yeah, I've been having it with my Gigabyte 7970ghz. I'm currently using the newest whql drivers and have the same symptoms.
 
dirty fix

dirty fix

I had this and then I swapped to HDMI cable (or was it the other way round to DVI-I). I think you loose the zero core but atleast it wakes correctly.

Sad that this bug is still around. AMD can't you please correct this???
 
No, i've never had this.

From none of the three posters any info about their system specs.... :bleh:

At least make sure you have enough free RAM, enough free disk space, and that your paging file and hyberfil aren't fragmented.
 
Yeah, same problem here with 13.12 on Win 8.1. Going back to 13.09, no problem there...


Gigabyte HD7870OC on a Asus P8Z77-V with Core i5 3470 and 16 gig of ram and plenty of free disk space.
 
I've been having this happening since updating to my 280x. prev. card was a 6950 and didn't have this issue.

@Dyre Straits

I use DVI and have this issue. only way I was able to get around it was to disable windows' putting monitor in standby on idle :/

running cat 13.12 driver.
 
bwat47 said:
I've been having this happening since updating to my 280x. prev. card was a 6950 and didn't have this issue.

@Dyre Straits

I use DVI and have this issue. only way I was able to get around it was to disable windows' putting monitor in standby on idle :/

running cat 13.12 driver.
Click to expand...

I know at one time...a year or so ago...I had to enable the Screensaver to avoid the problem and did the same as you: Disabled Sleep/Standby.

Interestingly, the cards I had then are now in use by my two sons and neither of them have mentioned this problem. But, I'm not sure how often they bother with driver updates, either.
 
I have this issue I think when the monitor turns off. When I try to turn it back on the screen is green. Un plugging/replugging my hdmi cable fixes it.
 
I have this at work.
Radeon 7770, latest Catalysts, HDMI connection, the screen remains black with the monitor's activity led still red/orange instead of green, so it doesn't receive any signal. A reboot is required in this case.
Doesn't happen on DVI, though.
 
a friend was just telling me about this problem :lol:, he has been having it for a while, he's on an APU (forgot which one) but he has given up and thought it off as one of those "hardware mysteries"
 
I also suffer from the same problem. In my case with a R9 280X using Catalyst 13.12 WHQL under Windows 8.1 and with the card connected to the monitor through DVI. I didn't notice it when my previous driver set 13.11 beta 8, but, just like the rest of you, it doesn't occur all the time. Hope AMD will fix this soon enough.

Sent from my GT-I9505 using Tapatalk
 
Oh yeah, I forgot to mention I'm running multi monitor at work as well.
Haven't tested to see if it happens with just one monitor connected, but it would seem that it might be required to reproduce the issue.
 
I have same problem with dvi using Windows 8.1. Also happens if monitor goes to sleep (not computer), sometimes monitor doesn't wake up.
 
for those with the monitor "not waking up" you may want to double check something.. I have the same "issue", where the displays are "off" or "sleeping",.. BUT .. if I log in remotely (using RDP) the displays wake up. The system is "awake" but for some reason the displays are not getting a "hey wake the f(*& up" signal. Use RDP (run mstsc.exe), from another pc, a tablet or a phone/mobile device.
 
@md_Guy said:
for those with the monitor "not waking up" you may want to double check something.. I have the same "issue", where the displays are "off" or "sleeping",.. BUT .. if I log in remotely (using RDP) the displays wake up. The system is "awake" but for some reason the displays are not getting a "hey wake the f(*& up" signal. Use RDP (run mstsc.exe), from another pc, a tablet or a phone/mobile device.
Click to expand...

RDP Clients use their MS's own special RDP video drivers, they do not use the local video drivers.
 
The Mac said:
RDP Clients use their MS's own special RDP video drivers, they do not use the local video drivers.
Click to expand...

I understand that, however connecting via RDP forces the video card drivers to either resync or are sent a signal from the host OS for a status check and respond back thus "waking"..

I simply added a shortcut on my tablet to my desktop, if the screens refuse to "wake", I hold down icon "Connect using Remote Desktop".. and as soon as the RDP client connects (not even checking for credentials) the displays all come out of their "S0" state.
 
@md_Guy said:
I understand that, however connecting via RDP forces the video card drivers to either resync or are sent a signal from the host OS for a status check and respond back thus "waking"..

I simply added a shortcut on my tablet to my desktop, if the screens refuse to "wake", I hold down icon "Connect using Remote Desktop".. and as soon as the RDP client connects (not even checking for credentials) the displays all come out of their "S0" state.
Click to expand...

gotcha, problobly the swich from RDP to local drivers when you log back in locally.
 
You must log in or register to reply here.
Back
Top