07-30-2024 05:41 AM
PG32UCDM has a Pixel Cleaning function to prevent the burn-in. Something it works and appears "Pixel Cleaning Successful"... others times nope and appears this error message. Why does this happen? Is there a way to fix it?
Thanks!
07-30-2024 06:03 AM - edited 07-30-2024 06:03 AM
Hello Luca23
Are you letting the pixel cleaning finish?
Normally, you'd get this message if the pixel cleaning is interrupted.
07-30-2024 02:24 PM
Hi! Yep!
07-30-2024 07:21 PM - edited 07-30-2024 07:21 PM
Have you updated to the latest firmware MCM105? - ROG Swift OLED PG32UCDM | Gaming monitors|ROG - Republic of Gamers|ROG USA (asus.com)
It says the update includes several bug fixes.
07-31-2024 05:18 AM
I have the MCM103. I'm going to install the 105 and I'll update you. Thanks
07-31-2024 07:03 AM
Still nothing. Could it depend on the Proximity Sensor function which, not detecting any person in front of the screen during the Pixel Cleaning (I don't stay in front of a black screen for 6 minutes doing nothing), activates the stand-by and this stops the cleaning?
If so, it would be a problem, because I would have to disable (and reactivate) the Prox Sensor each time or I would be forced to stay at the PC for the entire 6 minutes
07-31-2024 11:22 PM
Hi @Luca23 ,
Thank you for contacting us.
We understand that you are experiencing issues with the pixel refresh function on your PG32UCDM monitor.
Based on your description, we suggest you check the following:
Regarding the Proximity sensor function, if the function is enabled and no activity is detected, the monitor gradually reduces brightness when displaying power-saving information. The monitor resumes normal brightness when human activity is detected again. Please check if your power settings are in power-saving mode. If so, please assist in setting it to standard mode and verify if the issue persists.
If the issue still persists after trying the above methods, we kindly request your assistance in further troubleshooting.
Please record the process of the issue occurring in a video format, preferably in MP4, and provide it to us. Additionally, please provide more detailed information about your computer configuration and the environment in which you are using it, such as the operating system version, graphics card model, and display settings. This information will help us accurately diagnose the cause of the problem.
Thank you again for your cooperation.
08-02-2024 07:03 AM
Hi!
- I checked the four points and it's all ok
- About Prox Sensor, the monitor has always been in Standard Mode. In any way, the Prox Sensor makes the screen totally black (I guess in stand-by?)... so it doesn't gradually reduce the brightness. It goes from standard brightness to total black, like the monitor was off
The issue still persists
About the video, what would be possible to see more than the posted image? Simply, when the Pixel Cleaning finishes, appears the error message I posted in this thread
About the info: Win 11, GeForce RTX 4080, MB Z790 AORUS ELITE, i713700k, Corsair RM850x. Driver and OS updated
But please consider this: I don't know if it's a coincidence, but I noticed that such error appears when, during Pixel Cleaning, the Prox Sensor gets activated... on the other hand, if I stay at the pc and/or move the mouse, the Pixel Cleaning finishes successfully (at least for what I am testing now)
08-01-2024 09:47 AM
I also know that error message very well, so war I could not track down when it exactly appears. I could not be bothered for extensive analysis though. It's not unit related, as I already have my 2nd 32UCDM (first ran into the screen-test-endless-loop, see my forum post here). But both monitors sometimes show this message.
My suspicion is, that it is related to HDR switched on in windows. I only activate it for some games, and my feeling is it only appeared when I left HDR enabled and started the manual pixel refresh.
08-02-2024 07:05 AM
Do you have the Prox Sensor function ON or did you set that your pc/monitor goes in stand-by after few minutes?