Monitor screen goes blank when accessing/changing fullscreen applications

[Steven7]

Hello,

I got a new computer packaged with the HP Envy 32 inch monitor. I am running into an issue which is simply irrating and I am not sure how to go about resolving it.

Basically, the screen goes blank. It isn't a hard lock or anything, it just decides when initialising most full-screen applications (ie, a game) or even post Win10 log in, when computers do that 'flickering' during change over, the screen just likes go blank. This can be resolved by switching the input channel on the monitor, or putting monitor on standby and off again. During these occassions, I am getting sound through the monitor.

So from appearances, the monitor is still recieving input from the computer, and the fact switching monitor off and back on, makes it display picture as intended. It is a case where the monitor is simply deciding it doesn't want to show the picture for unknown reasons. Like energy saving or such.

I have updated graphics card, ensured I got most up to date display driver, double checked the connection... it just occurs.

It feels like there some really annoying setting somewhere which is making the monitor do this, and I would really like to change it. At the moment, it is a rate of having to switch the monitor on and off two times just to get to the start menu, then if I load up a game, it does it again, when I exit the game, it does it again. It doesn't occur when a game which supports borderless-windowed mode is loaded (I presume because it is not 'real fullscreen').

So it seems to occur during that fullscreen initilisation process.

[Steven7]

I recorded an example of what I am talking about with my phone and put it upon youtube.

https://youtu.be/n_JYNwn0iXI

I hope that helps make what I said make sense?

[Steven7 · Accepted solution]

Well, there was another cable I was unfamiliar with in the box called "DisplayPort".

So I changed my HDMI cable to using that one. The monitor is working perfectly now... so as a workaround, this solved it.

But the question remains, why was the monitor acting so weird when using HDMI? Maybe it could be flagged up as a potential issue.