F5F Stay Refreshed Hardware Desktop No output upon awakening from rest.

No output upon awakening from rest.

No output upon awakening from rest.

M
Mannagryn1
Member
122
12-08-2021, 10:10 AM
#1
Recent changes have affected how my desktop operates overnight. After three years, I've managed to put it to sleep and wake it up without problems for weeks. However, in the past two weeks, waking it up caused a DisplayPort error about an incorrect version setting, warning that the screen might appear blank. Adjusting the monitor's version to 1.1 or 1.2 results in a "No Signal" message instead. Remote access via TeamViewer isn't working either. My PC specs are listed in my profile—an LG monitor with a 2560x1440 display and RTX 3060. Switching cables or using HDMI doesn’t help. Resetting the device resolves the issue instantly, but I prefer avoiding that when important work is open. It seems like the system might be forcing DisplayPort version 2, which conflicts with the reset. Could you suggest possible reasons for this behavior?
M
Mannagryn1
12-08-2021, 10:10 AM #1

Recent changes have affected how my desktop operates overnight. After three years, I've managed to put it to sleep and wake it up without problems for weeks. However, in the past two weeks, waking it up caused a DisplayPort error about an incorrect version setting, warning that the screen might appear blank. Adjusting the monitor's version to 1.1 or 1.2 results in a "No Signal" message instead. Remote access via TeamViewer isn't working either. My PC specs are listed in my profile—an LG monitor with a 2560x1440 display and RTX 3060. Switching cables or using HDMI doesn’t help. Resetting the device resolves the issue instantly, but I prefer avoiding that when important work is open. It seems like the system might be forcing DisplayPort version 2, which conflicts with the reset. Could you suggest possible reasons for this behavior?

Y
yalex27
Senior Member
461
12-08-2021, 11:02 AM
#2
It seems the problem might be linked to the Nvidia driver update on December 23rd. The timing matches what you observed. I also saw a Windows notification saying it didn’t ignore the issue even after rebooting. Since I manage my Nvidia drivers myself, I reverted to the previous version (536.something instead of 546.something). I’m hoping this resolves the matter, as it’s the only change I made.
Y
yalex27
12-08-2021, 11:02 AM #2

It seems the problem might be linked to the Nvidia driver update on December 23rd. The timing matches what you observed. I also saw a Windows notification saying it didn’t ignore the issue even after rebooting. Since I manage my Nvidia drivers myself, I reverted to the previous version (536.something instead of 546.something). I’m hoping this resolves the matter, as it’s the only change I made.