Why is my Asus motherboard insisting on verifying the monitor input settings is accurate?
Why is my Asus motherboard insisting on verifying the monitor input settings is accurate?
After so much time wasted this summer buying/exchanging components and talking to support, I've finally determined the Asus TUF Gaming Z690 and Rog Strix Z790 motherboards I was attempting to use fail to post if I don't have my monitor set to the correct input setting for the PC when I turn on my desktop PC. There appears to be a VGA check on these newer Asus motherboards I have not seen with any other Asus motherboard previously that appears to think something is disastrously wrong if the wrong input setting is selected on my monitor.
I have an Asus ProArt monitor I bought a year ago, and I am taking advantage of the multiple input options by connecting my desktop PC to the Display Port input and a Microsoft Surface Book 2 to HDMI 1. In general, I only bother to switch the input to the correct one after I've turned everything on, this has never been a problem before now to simply select the correct input after everything is on. This has worked fine in the past with multiple monitors and multiple PC's.
This summer I wanted to upgraded motherboards, so purchased the above-mentioned Asus motherboards. Everything would appear to work fine, until suddenly, my desktop PC would intermittently start frantically sounding the one long and 3 short beeps, with the white LED lighting up indicating a VGA issue. All documentation, online support articles and Asus analysts would say was that this indicates the most likely culprit to be the graphics card, with the motherboard and CPU possible culprits if reseating/replacing the graphics card did not resolve the issue. As a result, Asus direction was to buy and try different graphics cards or replace the motherboard due to possibly defective components or try out other components to verify if they were culprits.
After replacing almost all the components, even the Display Port cable, it started looking like I had fixed the issue when I suddenly got the dreaded VGA beeps again and no post. This time though, for some reason I realized I had just used the Microsoft Surface Book 2, and the Asus ProArt monitor was still set to HDMI 1. So, I switched the monitor to the Display Port input, restarted the PC, and lo and behold, the PC booted up with no post errors. Now, I have gotten the error a couple of times, but I've confirmed it's after having used the Surface, so it's definitely when the monitor is set to HDMI 1 instead of Display Port.
I've been looking for a way to turn off this VGA detect option in BIOS on my ROG Strix Z790-H Gaming WiFi motherboard, but I haven't found any documentation on this specific issue or how to fix it. I'm still not sure if I am the only person to ever have encountered this specific issue, other than others complaining about the Asus VGA check stopping their PC from booting, no one has identified the monitor input selection as the culprit. If this is a new "feature" of Asus motherboards, I can only say I am so glad they don't make other audio/video components, can one imagine if all electronics failed to start up if the correct input isn't selected on the TV and the only fix was to select the correct input, then restart the device?!
Anyone have any suggestions?
I had to upgrade my previous 30in Lenovo display to a newer 30in Dell model after finishing a 7950X setup with an RTX 3060 graphics card.
Similar to your experience, I'm connecting the Display Port input on one computer and the HDMI input on another.
The old Lenovo screen would struggle to boot from the RTX 3060 output but worked fine with the RX 580 in my 3800X and an even older GPU in another machine. It might have been the difference between HDMI 1.4 and HDMI 2.0, or a newer DisplayPort version. I’m certain the new Lenovo model didn’t perform well with the 3060.
Swapping the monitor was the simplest choice for me, but I suspect you wouldn’t be pleased with that approach. You might want to explore a reliable KVM switch instead of relying on the monitor controls.
I had to upgrade my previous 30-inch Lenovo display to a newer 30-inch Dell model after finishing a build with a 7950X system equipped with an RTX 3060 graphics card.
Similar to your setup, I'm connecting the Display Port input on one machine and the HDMI input on another.
The older Lenovo screen would struggle to launch from the RTX 3060 output but performed flawlessly with the RX 580 in my 3800X and even an even more outdated GPU in a different PC. It's likely the distinction lay between HDMI 1.4 and HDMI 2.0, or a newer DisplayPort version. All I recall is that the previous Lenovo model didn't handle the new 3060 well.
Swapping the monitor was the simplest choice for me, though I wouldn't recommend it as a long-term fix. You might want to explore a reliable KVM switch instead of relying on monitor controls to manage connections between computers. High-quality KVMs can simulate a functional display, keyboard, and mouse even when switched to another system, usually resulting in a smooth OS boot regardless of the monitor used.
During the POST process, the BIOS checks for a working GPU and monitor. If another PC is using the monitor, it might attempt to boot into Windows (possibly at a lower resolution) or simply freeze due to an invalid resolution and refresh rate.
Some monitors fail to emulate a valid input when another device is actively using a different video output. The issue often lies with the monitor itself or the motherboard, not the components.
I suggest considering Aten KVMs, particularly those with a wired remote button for switching between PC connections. Built-in monitor switches can be inconsistent.
Thank you for the thorough response; it's reassuring to know another person has recognized this concern. I was expecting a 2022 Asus ProArt monitor to work with a 2022/2023 Asus TUF Gaming and ROG Strix motherboard, as mentioned in my earlier comment—I'm relieved that Asus isn't producing other AV parts. While it's understandable that older components and modern tech can clash, this shouldn't be a problem when purchasing new parts during the same setup phase.