PG32UCDM – Firmware MCM108 – Monitor doesn't wake up after no signal (serious bug!)

[GameKiller168]

Hi everyone,

I wanted to report a persistent and very frustrating issue with my PG32UCDM monitor running the latest firmware (MCM108). Despite the update, the monitor is still plagued with a serious bug.

When Windows (latest version: 24H2, with the latest Nvidia drivers) turns off the display after a period of inactivity, and I later move the mouse, the monitor doesn't wake up. The PC itself is still running – for example, music continues to play in the background – so it's clear the system is not in sleep mode. It's just that the monitor doesn't respond to the signal.

I’ve tried everything:

HDMI CEC options on/off

Auto input detection on/off

All OLED care features disabled
Still the same issue.

The only way to bring the monitor back is to power cycle it. Sometimes even that’s not enough – I have to turn it off and on multiple times, and in some cases, I need to unplug it entirely to get it out of this soft lock state.

This happens every single time Windows turns off the screen (i.e., stops sending HDMI signal). It’s not a rare glitch – it’s fully reproducible.

I’ve seen similar reports on Reddit, so I know I’m not the only one. I really hope ASUS takes this seriously and issues a fix soon – it’s incredibly annoying for a monitor in this price range.

If you’re affected too, please drop a kudo so we can get ASUS’s attention and get this resolved.

Thanks!

[GameKiller168]

Here's a video, showing the bug in action:

https://youtu.be/ug8nS_Va9go?si=lVhOtRaTfX9ok8l4 

[DessyG]

When I start my PC from a cold boot, my monitor turns on, I see the red logo and I see the Displayport input message and I see the splash screen of my Asus Mobo, enter bios ect. Once I get to windows I can hear windows logging in but my monitor no longer displays an image, its stays black. I have to either 1) turn the monitor on and off to get it to display anything or unplug and replug my display port. Really annoying and its been happening for the last 1-2 months on and off but now it happens everytime I do a cold boot.  FW: MCM105

[PoisonedBrick]

Hi, I have similar issue. Basically until your display is turned on, the monitor USB hub will not connect to that PC (when using KVM, it is acctually still connected to previous input) so moving a mouse connected to monitor USB hub doesn't turn on the display. My solution is moving my other mouse connected to that PC via different USB hub. It turns on the display and monitor USB hub connects. Maybe it will work for you as well. It's bad workaround, but it's still faster than power cycle the monitor.

I hope next firmware update will fix that or I will try to find a way how to rollback the firmware to previous version.

EDIT: Oh, just watched your video, sorry, not the same issue.