02-06-2025 11:46 PM
Hi guys.
Sorry for the clickbaity title.
So, yesterday I set up my new PG27UCDM. I hadn't had a lot of time to get comfortable with the new monitor and I am coming from FHD gaming.
In Windows 11 Pro, I set the resolution to UHD, set the refresh rate to 240Hz and enabled HDR (not Auto-HDR).
Ran a few Bechmarks in 3DMark, everything was fine. I shut down Win11 and went to bed.
Today I boot the PC and the screen stays black. The red LED is lit, so the monitor gets a signal from the PC. I can even type my PIN into Win11 and hear the start-up sound. So the PC is there, I am in Win11, but the screen stays black.
Tried a few things (turning it off and on again, un- and replugged the DP cable, hard-reset of the PC, un- and replugged the power cable) but the screen stays black.
I even can't get the On-Screen Display (OSD) to show and to my understanding, the OSD should pop up regardless of if the monitor gets a working signal or not.
Well, I then switched back from the OLED to my old LED FHD monitor to see if it might be the GPU, but as soon as I connected the old monitor via HDMI, I had a picture.
So it is not my GPU or the PC in general.
Win11, because of the old monitor, is now set back to FHD resolution, 60Hz, no HDR (since the old display is not capable of HDR).
And now I am wondering: Did I get a faulty unit?
Or what could be the culprit? DP-Port on the monitor bad? DP-cable bad? Problem with 240Hz? Problem with HDR? Problem with 4K?
I can only continue testing in a few hours, but if you have any idea, I'm all ears. Well, eyes...
02-07-2025 03:13 AM
Update: Had time to test some more.
Tried two other DP 2.1 UHBR20 cables, screen stays black.
Tried those with all three DP 2.1 connectors of the GPU, screen stays black.
Tried it with an HDMI cable, screen stays black.
Connected both monitors at the same time, the old monitor via HDMI.
Win11 recognizes the new OLED. I can change screen resolution, successfully identify it, disable and enable it in Device Manager and/or Nvidia App, but the screen stays black.
ASUS own "Display Widget Center" also recognizes the monitor. I can change settings, but whatever I do, the screen stays black.
At this moment I am out of ideas and to me, it looks as a) either the proximity sensor is broken, so that the Display stays black because it "thinks" there is nobody in front of it and it has to stay black to prevent Burn-In or b) the panel itself is broken, since it doesn't even display the OSD menu and the power device, obviously, works (I can turn the display on and off).
I guess I will have to return it.
02-07-2025 03:40 AM
Have you tried to completely uninstall the drivers using DDU?
02-07-2025 04:37 AM - edited 02-07-2025 05:36 AM
-
02-07-2025 05:36 AM
A few minutes ago, I connected the OLED via HDMI to a Laptop, so a second PC. Driver got installed, screen stays black, OSD doesn't show.
As of now, I am pretty sure the panel is dead. I just started the return process.
02-07-2025 10:12 AM
Hi,
Do you have Windows 11 24h2 installed? If so, did you try the new monitor without hdr? Windows 24h2 has a problem with hdr. If I can find where I read about it I'll paste it here. They actually put a block in windows update so that it will not offer the 24h2 update to computers that have auto HDR installed until they can fix the problem, but if you have it, obviously you installed it before getting the monitor and turning on hdr. For now they suggest turning off hdr. If you've done that already though, then perhaps it may be broken.
02-07-2025 10:16 AM
https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2
Here's the link. If you scroll down to known issues you'll find it.
02-07-2025 10:47 AM
Actually after re-reading it, it specifically mentions auto hdr and apparently they did fix it. HOWEVER, these are known issues and who knows what unknown issues there may still be where problems are being blamed elsewhere.
In my experience and from what I've been reading, there are quite a few issues with windows 24h2 and asus products. I just built a new pc with an asus motherboard and trying to install windows was agony. I thought some part of my pc must be damaged. I finally got windows installed after 2 full days of troubleshooting. Installing windows 10 instead of 11 helped.
Once installed, the offer to upgrade to windows 11 came up. I upgraded. Then windows update offered 11 24h2. I installed it and immediately regretted my decision because things got buggy again. That is how I came across the information I gave you. So all that to say, if you have 24h2, you may want to investigate windows being the culprit when you have issues with new additions to your pc.
02-07-2025 10:58 AM
Yes, I am on 24H2. No, I did not enable "Auto HDR". Yes, I used the monitor in sRGB and in HDR, both worked fine the first evening. The problems arose when the monitor, after a full night of sleep and being on Standby aka "Turned Off", got a signal from the PC again to display something on screen. The monitor at that moment was set to 240Hz and had HDR enabled. I have no idea what happened internally, but from that time on, the panel was incapable to display anything on screen.
02-07-2025 01:14 PM
That's another thing about windows I read about, just FYI. Issues don't appear at first, but after a day or two problems pop up. I just thought it might be a possibility. If you haven't returned it yet try turning all hdr off not just auto.
If it doesn't work and you go ahead with the return and get another one, I really hope you post here whether you have better luck with the replacement because I'm waiting to get this monitor also.