I recently built a new PC but I'm facing a frustrating issue where there's no display, despite the system appearing to boot normally. Here are my specs: I'm using an MSI X370E Gaming Plus WiFi motherboard, an MSI RTX 5080 GPU that I installed myself, and I've got 16GB of RAM (two sticks installed correctly in slots A2 and B2). My monitor is an ASUS TUF VG279QM5A, and I'm connecting via DisplayPort.
When I turn the PC on, the monitor shows the ASUS logo for a moment, then it says 'DisplayPort no signal' and goes to sleep.
The PC seems to be working fine otherwise: all fans are spinning, the RAM RGB lights up, the GPU fans are active, and the keyboard works (I can toggle Caps Lock). However, the motherboard debug light is stuck at 'boot', which I believe indicates it's passed POST and is just waiting for an OS.
So far, I've tried reseating the RAM, confirming they're in the correct slots, trying every DisplayPort on the GPU, changing the DisplayPort version on the monitor, unplugging and re-plugging the DP cable, turning the monitor off and on during boot, and spamming DEL to get into BIOS, but I'm still stuck at the ASUS logo.
I don't have an HDMI cable to test the HDMI output right now, but would it be worth getting one just to troubleshoot this? I'm thinking this might be a DisplayPort handshake issue or possibly related to the GPU output or BIOS settings. Any ideas on what I should try next?
3 Answers
Have you tried enabling Compatibility Support Module (CSM)? Sometimes that helps with certain monitors and GPUs. But I totally understand if you can't see the BIOS to check that setting just yet. You might want to focus on getting a display output first before diving into those options.
If you can’t check BIOS settings, you might also think about Windows updates when you get a different monitor. Sometimes optional updates include drivers that could help with recognition of your monitor. But that would require access to a basic monitor, unfortunately.
Definitely consider getting an HDMI cable to test. Your motherboard has onboard graphics, so you should be able to connect it directly and see if you can reach BIOS or even the OS. That way, you can narrow down the problem to either the GPU or something else with the settings.
Yeah, that makes sense! If CSM is enabled or disabled, it can make a difference, but without being able to see the BIOS, it's a bit tricky. It's good to get the display issue sorted first!