Have to turn monitor off after shut down for HDMI to work

danieltech72

Commendable
Sep 2, 2016
21
0
1,510
Hi, I recently got a HDMI cable and it works out fine on everything, besides getting signal when I start my PC up when my monitor is also up,
Let me explain: If I restart my PC and my monitor is on, I won't have any issues whatsoever, the cable recognises my GPU and gets no interruptions once it works for hours on end, however, if I shut down my PC, and my monitor is still on, my monitor will say "HDMI No Signal" as it should be, but if I keep my monitor on for the night and then start my PC later, Monitor won't see any signal from it, however, while the PC is on and presumably at the desktop already, if I turn off and on the monitor, it will get signal.
Basically, I didn't have to turn off my monitor when I had DVI, now I have to turn off my monitor everytime I shut down just so HDMI can be recognised?
is there any way I can work around this?
 
Solution


It really just is up to the cable. I've had it happen with any input really. With costumers coming into the shop and complaining that their monitor doesn't see the pc half the time. A quick new cable usually fixed it.


If it's a cheap hdmi cable I wouldn't be suprised if it isn't transmitting the wake signal to the monitor. However once the monitor is turned on it actively looks for a source and finds the hdmi input.
 

danieltech72

Commendable
Sep 2, 2016
21
0
1,510
So you are saying the cable might not look for a source after it had disconnected when the PC shut down? which just makes it go into a "Yeah there's no input coming around for me" state up until the monitor gets turned on again? Why would a cheap DVI cable work like this and not a HDMI one?
Edit: If this is the case then I should just switch back to DVI and not consider HDMI anymore
 


It really just is up to the cable. I've had it happen with any input really. With costumers coming into the shop and complaining that their monitor doesn't see the pc half the time. A quick new cable usually fixed it.
 
Solution