Second monitor shows intermittent issues after power-off.
Second monitor shows intermittent issues after power-off.
In general, for as long as I can remember, my second monitor's screen on my main display keeps flashing on and off. Online reports suggest similar problems but with a key difference: the monitor shuts down completely and loops repeatedly, displaying its logo before restarting again. On the other hand, my own experience is that the display turns black and stays on for several moments after I move the mouse or type, even though it remains functional. If I don’t mind using it in that state, it still works—mouse input is registered but it’s very bothersome. This behavior only appears after the computer has powered down. My previous solution was to fully power off and on again (sometimes a restart helps), and now I’ve switched to keeping the PC awake with a screen saver. There seems to be no permanent fix beyond that workaround. I’m currently using Windows 10 version 22H2, an AMD Ryzen 9 5900X with 12 cores, a Mag X570 graphics card, and a Tomahawk monitor (24.5 inches, 1920x1080, 144 Hz). I’ve updated the BIOS and driver software, but the issue persists with this specific monitor. This problem has already occurred after several Windows updates, so it doesn’t appear to be resolved by those changes.
I'm working with a recent Windows PC featuring a dedicated GPU. Waking the machine from sleep can be tricky, involving many potential issues. I recommend updating the BIOS/UEFI firmware first, since the UEFI plays a key role in exiting sleep. After that, ensure your Windows is current and your graphics drivers are refreshed. Then observe its performance.
I understand the situation. I'm using Windows 10 version 22H2, an AMD Ryzen 9 5900x with 12 cores, Mag X570 Tomahawk Wi-Fi, a GeForce GTX 1660 Super, and two Acer XF250Q Bbmiiprx 24.5" monitors at 1920 x 1080 with 144 Hz. I've updated the BIOS and drivers, but the same issue persists with these displays. It's been a problem since a couple of Windows updates, so it seems unlikely this will resolve things right now.