05-31-2024 12:18 PM
I discovered a bug that seems to be related to the automatic input/source detection on the PG32UCDM monitor. In my setup, I have two monitors connected to my PC: the PG32UCDM and one other. They are both connected with HDMI. However, I often only enable one monitor at a time depending on what I'm working on (or gaming). Both screens are powered on, but the one disabled in Windows enters standby. When I'm only using the other monitor, the PG32UCDM seems to periodically scan for other active sources. When it does this, it must break the HDMI connection. When the PC detects that an HDMI connection was changed, it follows its normal process of detecting the new monitor configuration, setting window positions, scaling, etc. This causes the screen I'm using to go blank and then come back. However, since the PG32UCDM quickly switches back and forth between HDMI-1 and other potential inputs, the other monitor's HDMI signal is rapidly interrupted and restored. If this happens too much, the other monitor sees this as an input error and it will shut down until manually power cycled. This doesn't happen every time the PG32UCDM attempts to detect inputs, but it is very frequent. After the process completes, "HDMI-1 No Input" is briefly displayed on the PG32UCDM, even when it's still in standby and disabled from the PC.
Turning off the PG32UCDM entirely instead of letting it go to standby fixes the problem. Disabling the "auto-detect input" setting also resolves it, but the screen still seems to keep trying HDMI-1 and displaying the "No Input" message over and over. I'm worried this could eventually cause burn-in.
Before I figured out the cause of the problem, I tried the following to rule out other potential issues:
Below are my relevant system specs:
06-04-2024 11:51 PM
Hi @klaxian ,
thank you for contacting us.
Based on your issue, we would like to confirm if your current problem is related to using the HDMI connection on both displays of the PG32UCDM. Specifically, is one of the displays set to standby mode, causing the PG32UCDM to continuously detect other input sources, resulting in a black screen on the active display and displaying the message "HDMI-1 No Input"?
Could you please let us know if both displays are PG32UCDM models?
Additionally, have you enabled the Auto KVM function? Did the issue occur with previous firmware versions?
To further investigate your issue, could you please provide a video showing the problem occurring?
We kindly request that you record the video in MP4 format, ensuring that both displays and wiring status are clearly visible.
Thank you.
06-10-2024 09:14 AM
Thanks for looking into this. I'll do my best to answer your questions.
It seems to me that the PG32UCDM is potentially breaking the HDMI connection when scanning for other inputs. Windows behaves as if the cable is unplugged and then plugged back in quickly. This does not happen every time, but it happens at least once per hour. Sometimes it will cause problems requiring a system reboot to correct. It makes the computer unusable. As I mentioned, disabling "Auto-detect Input" on the PG32UCDM resolves the issue, but it still seems to constantly hunt for a signal and display the message shown in my video. Turning off the PG32UCDM fixes both issues. However, I would like to be able to let it run in standby when I'm using the other screen so I can easily switch between them when needed.
PG32UCDM
MSI MPG 271QRX
06-11-2024 01:45 AM - edited 06-11-2024 02:41 AM
Hi @klaxian ,
thank you for providing the information.
Regarding the video, could you please zoom out the camera and capture the entire monitor (including the power indicator) displaying "HDMI-1 NO SIGNAL"? Could you also provide the video file in MP4 format for our reference?
You mentioned that the two monitors are placed at a distance from each other.
Could you please provide a detailed description of how you have connected the two monitors?
Did you use any docking stations or other devices for the connection?
Additionally, may I ask if you encountered this issue right after purchasing the monitor, or did it occur after making any changes?
Thank you.
06-11-2024 08:15 AM
The power indicator is solid ORANGE (standby) when the screen is flashing "HDMI-1 NO SIGNAL". The only way to attach a video seems to be with an external link (ie. YouTube). If there is a way to attach an MP4 file to a post that I'm missing, please let me know.
The monitors are connected directly to my video card with HDMI 2.1 certified cables. No, I am not using any docking station, adapter, or anything between the video card and the screens. As I mentioned, I tried several different known working HDMI cables as well as DP, but it did not fix the problem. Each screen works fine when connected by itself, and I can work around the issue with the PG32UCDM by disabling "auto-detect input" (but the screen still flashes "HDMI-1 NO SIGNAL").
The issue has always been present, ever since I purchased the screen, but it took some time to figure out the cause.
You should be able to replicate the behavior on your end with a test. Connect a PG32UCDM and another screen to a computer with HDMI. Set the PG32UCDM to disabled using the nvidia control panel. The problem is more prevalent when using high-bandwidth features like 360Hz, HDR, and DSC, but it also happens at lower refresh rates with these disabled. Launch a game that will utilize HDR and high HDMI bandwidth. It should happen within an hour or so, and then repeatedly. To reiterate, using features like high refresh, HDR, DSC, VRR, and running a game seem to make the issue happen more often, but it also happens with all these disabled, even in the BIOS before Windows is loaded. I suspect that the connection is more sensitive to momentary resets when it's at the edge of it's capabilities.
Please let me know if there's anything else I can do to help. I suspect this will need to be fixed in a future firmware update.
06-11-2024 08:15 PM
Hi @klaxian ,
thank you for the information.
Regarding the MP4 video, when you post a message, you can attach a file in the red box.
Please kindly provide the complete video of the issue occurring at the time.
Thank you.
06-17-2024 06:30 PM
Hi @klaxian ,
according to our backend team's testing, using a 3080 graphics card, setting PG32UCDM to "do not display" in the OS, and testing with two HDMI 2.1 connections to PG32UCDM (FW version 103) and PA32UCG, we did not replicate the issue you described.
Since you mentioned that there is no issue when using PG32UCDM alone and the distance between the two monitors is relatively far, we kindly request you to provide a video to confirm the connection method (based on the photo you provided, it appears that you have multiple cables connected to PG32UCDM) and the monitor's settings in order to replicate the issue.
Please shoot a clear video documenting how the two monitors are connected, then proceed with the following three steps:
These videos will assist our backend team in confirming the issue. Thank you.
06-18-2024 08:34 AM
Thanks for testing it. Please note that the problem does not happen right away. If you follow my reproduction steps above and let the setup run for some time, you should see it.
As I mentioned previously, both screens are connected with HDMI 2.1 (certified cables). The other cables connected to the PG32UCDM are USB-B, USB-A, and optical audio.
I will try to get a better video for you, but it might take some time to set up. Unfortunately, I don't see the section to attach files to posts on this computer. I will try a different PC next time.
06-18-2024 05:45 PM
Hi @klaxian ,
based on your suggestion, we recommend that you first test using the cable provided by the original manufacturer and remove any other USB-B, USB-A, and optical audio cables to further diagnose the issue.
If you are unable to attach the MP4 video file, you can place the file in a Google Cloud storage and share the link with me via private message.
Please note that when recording the video, please try to remove any other external devices (such as USB-B, USB-A, and optical audio) and only keep the signal cable, then proceed to record the steps to replicate the issue.
Thank you very much for your cooperation and understanding.