PG32UCDM black screen during game sessions!!

[silverbolt81]

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!!

[tardiffbt]

Updated FW to MCM105

Updated Nvidia Driver to 566.36

Updated BIOS to newest version: 3611

BIOS was then restored to factory settings. Memory is no longer overclocked.

Updated AMD chipset to 6.10.17.152

Router moved farther from computer in case of possible interference.

I do not believe this is a signal loss issue (hardware) because when I actually do lose signal, a pop up displays that says "no signal" and then another pop up displays the name of the connected port when signal is restored (ex: HDMI 1), but when I have this issue, no such pop ups ever display.

I removed my GPU and memory modules from my computer today and reinstalled them. I also verified that all cables in and outside the PC ( including power supply connections) were snug, which they were.

I have re-enabled VRR, DDC-CI, and DSC Support to see if the issue returns.

Will provide updates here as they develop.

[rhms]

Awesome

What I mean by hardware issue is not only your PC  but it could be the monitor itself. Since you had your monitor working for at least 3 months without issues.

The goal here is to discard as many potential issues that could be related to your black screen.

What is interesting about the black screens is that you clearly see a white flickers just before the black screen. As if something is struggling to keep it.

It could be multitude of things. You could even try a different HDMI cable, different ports or even try to use the DP cable to see if the black screen also occurs after that distinctive white flicker.

Most users including myself don't have that white flickers before a black screen. It simply goes into a black screen and most of the time we would need to re plug the AC cable.

In your instance it really feels it either the monitor, cable or maybe ports it could be something else. But that white flickers really distinguishes itself from others users black screens.

And well before you got with the whole RMA/Replacement road. Try to troubleshoot as much as you can to pinpoint the issues.

But you to have ask yourself.

Why was it working for the last 3 months and not anymore?

EDIT: Try to keep your windows at 23h2 build 22631(Already is) do not upgrade to 24h2 it has a multitude of compatibility issues including this monitor

[GRTim]

This is a widespread issue that is pointed out in the Blur Buster's post I posted a link to. From what I understand, it is mainly a Freesync problem. Monitors that had the gsync module built in suffer from this to a much lesser degree. Freesync has a default low end of 48hz and when it goes below that, the screen can start to flicker and then go black because LFC (Low Framerate Compensation) isn't being properly utilized by the drivers and/or monitor's firmware. This causes the monitor to essentially crash or black screen. Sometimes this is recoverable, and the screen comes back a few seconds later but other times it is not. Chief Blur Buster recommend setting a new low end to 55-65hz to give a buffer for the LFC to kick in properly. 65hz isn't recommended because it exceeds 60hz required by some consoles.

[Jaynay]

The explanation by Blur Buster makes sense.  It doesn't happen often for me but it does when I'm in an intense scene prob the 1% low is triggered dropping frames below the 48hz threshold.  My monitor does recover it does not go out completely that has only happened to me once where i had to unplug and replug it- i thought my 4090 died!

Is there a way for us to raise the threshold and test?

[GRTim]

There is by editing the EDID with the new limit. Utilities like CRU can do this for you and there are tutorials that can walk you through the process out there. 

[Cornfedturbojoe]

So this issue is really hard to pin ooint. For the longest time i havent had any black screen at all at least for over a month(a month ago i replaced hdmi with the provided dp cable) UNTIL i started playing indiana jones that just got released and yesterday after about 1 hour of playing i got probably 3 black screens back to back within about 20 seconds from eachother, i just paused the game when this would happen. Then i played for another hour and got just 1 black screen, idk if this is a game thing but ivd noticed out of all the games i play; black ops 6, dragon age veilguard, stalker 2, metro exodus, delta force, black myth wukong, and a couple others have not done it. Its only happened on indiana jones so far which is odd

[GRTim]

As Jaynay posited, this behavior probably happens when you hit those 1% lows because some people have said that they can play for hours and then all of sudden it does it. The VRR goes out of range, but LFC doesn't kick in properly and then the monitor crashes (black screen) and then tries to recover. This is something that could be fixed with firmware to compensate for those times when the VRR goes below the threshold, but these manufacturers need to admit that this is an issue and then fix it.

[Cornfedturbojoe]

Hmm interesting, yesh either way its still annoying. I also have vrr turned off alpng with proxy sensor turned off. For the most part it rarely does it now, but asus seriously needs to docsomething about this. There is no reason this should be happening on a $1300 monitor 🤦

[kampi71]

Exactly. It's also hugely disappointing that no one from Asus is responding to this thread anymore. We costumers paid around 1200-1400 bucks for this "premium" monitor and are now left in the dark for weeks and month, with no further information. I guess we all tried a lot of things, swapping cables, tried out different settings and for me the only thing that is preventing the blackout issue is to disable the DSC Support, which of course is one of the MAIN reason why be bought this thing, right? Namely to have the 240 hz support on a 32' OLED monitor. Btw, riight now I'm also playing the new Indiana Jones game and there is indeed a lot of "blackscreening" so I "once again" have to limit the monitor to just 120hz in switching off the DSC Support to get rid of that. I bought 240hz my dear Asus Devs and this is NOT working properly. TALK TO US, please...finally.

[xxdmansurferxx]

This is unfortunately a very much still relevant defect in these monitors. I have the PG32UCDP and it’s doing it to me pretty regularly when I play borderlands 3. I even swapped the first one due to the same issue but the second one still does it. We only have firmware up to version 103 so nothing I can do about that. I really hope something is done about this at some point. 1200 dollar monitor should work flawlessly imo.