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

[Crasje]

Mac too? Hmm there goes the Windows update theory some had. Would be nice to have another Macbook confirmation.

[dradams]

It happens for me with Windows 10,11 and MacBook.

[Xaxxus1]

I've heard a theory that its related to having USB-B peripherals plugged in.

Im gonna test later tonight with all usb devices unplugged. Gonna be sad if that's the cause. The whole reason I bought this display was the built in KVM switch.

EDIT: Confirmed its not specifically the usb-b port

going to try going completely without USB peripherals plugged into the monitor to see if its just the KVM switch in general.

[GRTim]

At this point, with as many different systems this issue is happening on, it has to be something firmware related. It can't be drivers or the OS because it has been reported to happen on Windows, Linux, Mac, PlayStation and maybe more. Something is causing the monitor to crash when certain conditions are met. I cannot believe Asus have not been able to replicate this issue. Seems to me they could take 10 random monitors and stress test them over a time period to see if a few have this issue. That is not including the amount of people that have returned their monitors that could be used to troubleshoot the issue too! It is just baffling. I have actually written Gamers Nexus about this issue. I doubt I will get a response, but it was worth a try.  If anyone is interested, feel free to write them at tips@gamersnexus.net. Maybe if they get quite of bit of mail on this, they will do something about it. They did such a good job with their other Asus support investigation.

[Xaxxus1]

I sent an email to GN about it. Hopefully they can light a fire under Asus' feet and get some movement on this. Because it Seema Asus doesn't want to do anything about it.

[dradams]

Yes, or hardware. My own pet theory is that a hardware component is intermittently failing due to charge accumulation, heat or some other factor. I don't have test data to verify this, but it isn't one OS/driver version/cable, etc. etc..

[Xaxxus1]

So I have an update on what I think MIGHT be a solution (figures I find this out AFTER I ordered the new MSI MPG 322).

So the original reason I went with this display over competitors was the KVM switch. Which allowed me to free up a ton of cables on my desk.

So in preparation for my new monitor, I removed all USB devices I had connected through the pg32ucdm's KVM switch, and hooked them up to my old KVM switch instead.

I had the following hooked up through the monitor:

1. a web cam

2. a wireless dongle for my HyperX cloud alpha headset

3. A USB 3.0 cable that splits off into 3 USB 2.0 female cables (I had my mouse + keyboard plugged in there)

So far I have been able to use my monitor without any issues for the past hour or two. Previously, I would have no issues for about an hour, and then id start to see it happen in increasing frequency the longer I use the display.

I'll report back tomorrow evening after a full day of work + gaming in the evening.

I also swapped out the provided display port cable with one of my own display port 1.4 cables, but I don't think that was the issue, as im using the same USB-C cable as before for my Mac, and I have not seen any issues with it either.

I would definitely be interested to see if anyone else here had a setup similar to mine, and experienced these issues. And if removing all USB devices solved it.

[yukich]

That is definitely not the solution.. I have 0 USB and it still happens. It's simply a BW OCP issue..

People there is no solution other then Asus FW fix.. sadly.

[Aureliannn_ROG]

Hi @Xaxxus1 ,

Thank you for your inquiry. To better assist you in this issue, we require the following information:

1. Device Information:

   • Device model (MB/GPU/CPU...)
   • Operating System (OS) version
   • BIOS version(Please confirm already update to the latest version)
   • Driver versions (Please confirm already update to the latest version)
   • Firmware version(Please confirm already update to the latest version)

2. Problem Confirmation:

   • Is the human sensor enabled?
   • Are all original manufacturer cables being used?
   • Are there any other Sources or displays available for cross-testing to determine if it is a Source issue?
   • At the time of the issue, was the Source only connected to the PG32UCDM? If not, does connecting it alone still show the problem?
   • Was HDR enabled or disabled when the issue occurred? What was the timing?

Please provide the above information in as much detail as possible so that we can analyze the issue more throughly.

Thank you.

[Xaxxus1]

1. Device Information:

   • Device model (MB/GPU/CPU...)
     • MacBook Pro 13 inch 2025 (M4 Pro)
     • Desktop
       • Gigabyte Aorus X670 Elite
       • AMD Ryzen 9 7950X
       • Nvidia 4090 Founders Edition
   • Operating System (OS) version
     • MacOS (latest)
     • Windows 11
   • BIOS version(Please confirm already update to the latest version)
     • are you referring to my MB's bios? or the monitor? The monitor is MDM 108
   • Driver versions (Please confirm already update to the latest version)
     • updated to the latest version a few days ago
   • Firmware version(Please confirm already update to the latest version)
     • MDM 108

2. Problem Confirmation:

   • Is the human sensor enabled?
     • Tried with it enabled and disabled
   • Are all original manufacturer cables being used?
     • Yes, also tried with my own cables
   • Are there any other Sources or displays available for cross-testing to determine if it is a Source issue?
     • There are other displays available, they do not have the issue
   • At the time of the issue, was the Source only connected to the PG32UCDM? If not, does connecting it alone still show the problem?
     • I have tried with only one device connected, and with two devices connected. Both experienced the issue
   • Was HDR enabled or disabled when the issue occurred? What was the timing?
     • happens enabled or disabled