04-18-2024 09:36 AM
So i am having this issue since the day i bought the monitor.
At first it was happening during a certain game,the callisto protocol.
Now it is happening also in Destiny 2.
As i am playing these games with HDR on,after some time the screen goes black and i have to manually turn the monitor off and on again in order for the image to appear again.
I had at the beggining the factory firmware,after i updated to MCM102 and now i have the 103.
This issue seems to be consistent on all firmwares.
I know it is not related to my windows setup because on the same pc with a different monitor this does not happen.
I have my pg32ucdm connected via dp.
Any suggestion would be much appreciated!!
11-25-2024 06:56 PM - edited 11-25-2024 07:03 PM
Well reached last page (no black screen, phew!) and no word/hint that ASUS have found the issue and working on a fix so I guess my only option now is contact where I bought to inform of the issue and this thread and hopefully I can return without paying for sending back and get all my money back. I would be pissed if that adventure would cost me a dime.
First time I was trying OLED and wow, 4K WOLED looks nice coming from 1440p PG27VQ but I will have to endure it for a few more weeks/months with the visual glitch which plagued many units after warranty was over.
I like the curve of the PG27VQ so I may look for a curved one again next time. I wish this WOLED gen have a curved one. All I see is a QD-OLED from Dell but I don't want QD.
11-25-2024 07:23 PM - edited 11-25-2024 07:25 PM
Did a little bit of research and it looks like this issue is not relegated to this brand. It looks like OLEDs released this year suffer from this problem some more so than others. If you are going to return the monitor, I would do some research first before making a decision on getting another monitor.
11-25-2024 07:29 PM
Thanks for the info. Do you have any links you can share?
11-25-2024 07:46 PM
Some Reddit posts:
Alienware AW3225QF
https://www.reddit.com/r/OLED_Gaming/comments/1b2pu10/has_anyone_experienced_the_aw3225qf_going_blan...
https://www.reddit.com/r/OLED_Gaming/comments/1brylet/aw3225qf_4090_black_screen_issue/
MSI 321URX
https://www.reddit.com/r/OLED_Gaming/comments/1d5zze0/msi_321urx_screen_going_black/
https://www.reddit.com/r/OLED_Gaming/comments/1avngyj/msi_mpg_321urx_qdoled_screen_going_black/
Gigabyte FO32U2
https://www.reddit.com/r/OLED_Gaming/comments/1ctp7nn/fo32u2fo32u2p_issue_with_screen_randomly_blank...
https://www.reddit.com/r/OLED_Gaming/comments/1cjlzxk/random_black_screens_on_the_fo32u2p/
LG 32GS95UE
https://www.reddit.com/r/OLED_Gaming/comments/1ewek9l/lg_32gs95ueb_flickering_then_black_screen/
11-26-2024 10:55 AM - edited 11-26-2024 05:39 PM
The PG32UCDM uses the Gen 3 Samsung QD-OLED :
Dell Alienware AW3225QF
MSI MPG 321URX
Asus ROG Swift PG32UCDM
The PG32UCDP uses the LG Third Generation WOLED
Here is a link to give you guys ammo or nightmares :s
(NA users are on that thread due to thread volume)
11-25-2024 08:05 PM
Since my last post a hour ago, no issue. I was also able to play Apex a full hour. So strange. I really wish I wake up tomorrow and read a post from ASUS saying HEY GUYS WE FOUND THE ISSUE AND A DEFINITIVE FIX IS HERE. I like the monitor, it's no comparison with my PG27VQ.
Anyway, time to go sleep.
11-26-2024 09:50 AM
Would an RMA just provide replacement? I still have the issue. I don't believe a different monitor will fix this at this stage. It seems to be an issue with the firmware and according to others it's present on this current OLED tech across several brands. Some of these brands use the same panels obviously. Perhaps we should all start an RMA to press the matter and get an official response from Asus.
11-26-2024 10:17 AM
yeah from reading the thread i think all RMAing will do is escalate the issue since it costs Asus money to deal with RMAs. but at $1300, i'll just keep RMAing until the issue is fixed or I get a refund if they don't fix it.
11-30-2024 10:41 AM
Have the exact same problem with my PS5. Mine got delivered with firmwire 1.03. I'm hesitating to send mine back. Does anyone know if every monitor have this problem? Or does returning it for a new monitor fixes the problem?