• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Monitor problem with displayport cable

Joined
Apr 30, 2011
Messages
2,773 (0.54/day)
Location
Greece
Processor AMD Ryzen 5 5600@80W
Motherboard MSI B550 Tomahawk
Cooling ZALMAN CNPS9X OPTIMA
Memory 2*8GB PATRIOT PVS416G400C9K@3733MT_C16
Video Card(s) Sapphire Radeon RX 6750 XT Pulse 12GB
Storage Sandisk SSD 128GB, Kingston A2000 NVMe 1TB, Samsung F1 1TB, WD Black 10TB
Display(s) AOC 27G2U/BK IPS 144Hz
Case SHARKOON M25-W 7.1 BLACK
Audio Device(s) Realtek 7.1 onboard
Power Supply Seasonic Core GC 500W
Mouse Sharkoon SHARK Force Black
Keyboard Trust GXT280
Software Win 7 Ultimate 64bit/Win 10 pro 64bit/Manjaro Linux
Since I got an ASUS TUF GAMING VG249Q1R 24'' LED FULL HD IPS 165HZ monitor it doesn't switch on to display anything until it gets to the login screen of windows. I returned it and in the service they told me that it is natural for most monitors to turn on only when windows drivers load when connected by DP cable, while with HDMI it turns on immediately. I already have another monitor connected on DP cable (AOC 27G2U/BK IPS Monitor 27" FHD 144Hz) and it turns on instanlty when PC boots. What is your experience with that? I strongly suspect they lie to me since I have never seen any such problem being normal. And ASUS doesn't say so even if the DP cable was the only one shipped with the monitor.

Thanks in advance for any help!
 
All the monitors I have had switch on when a signal is detected... How, else, would you get a Bios screen?

Edit: I use DP... also, press the power button to check if the monitor is in the ON mode.
 
Last edited:
Garbage, they’re lying to you. Like your other monitor and this one on HDMI, mine shows the BIOS startup messages. Might be worth returning it if you can.
 
They are either lying or don't know their their a$$ from a hole in the ground. I suspect the latter - at least from the Level 1 techs because they tend to be under-trained, under-paid, and forced to follow some troubleshooting checklist, forbidden to deviate from that list even if they know the correct answer.

As 95Viper notes, if the monitor (any monitor) could not detect basic VGA signals, how could users access the BIOS Setup Menu or even install Windows (or Linux) in a new build?

I would swap DP cables, just to make sure that's not the problem. And I would do a power reset with the monitor too. There might be some setting in there that is remembering the Windows resolutions when the monitor just goes into stand-by mode. And note like many electronics today, they are in some form of standby even when turned off. They have to be unplugged from the wall, or if equipped, a master power switch on back is set to off.
 
Thanks a lot all of you! :toast: I know all of what you wrote and had already tested with another cable. Monitor is faulty and I have returned it already but they try to force their BS on me. I told them what you wrote about BIOS access and they told me that whoever needs that is forced to connect the monitor to HDMI cable and that rang bells of hearing bs again.
 
Thanks a lot all of you! :toast: I know all of what you wrote and had already tested with another cable. Monitor is faulty and I have returned it already but they try to force their BS on me. I told them what you wrote about BIOS access and they told me that whoever needs that is forced to connect the monitor to HDMI cable and that rang bells of hearing bs again.
They're not all right.

My Samsung G9 does this from a reboot. It looks like its defective till ya realize what's happening. On reboots, the panel doesn't light till it finally gets to the login screen. Thus if I wanna get to bios I have to shutdown first then upon initial boot I get the bios screen. I suppose I could try to pinpoint it down since its not tied to fastboot but it's not a big deal for me at least. And before any goes etc etc DP, you can't get 240hz on a G9 w/o DP with DSC, so yea its using DP.
 
they told me that whoever needs that is forced to connect the monitor to HDMI cable and that rang bells of hearing bs again.
Well, that, to me, would suggest the issue is with the card and how it prioritizes protocols and not the monitor itself. It is the cards responsibility to sync with the monitor. But the monitor should be saying "here I am, sync with me on DP".

I have an old Viewsonic that has a similar issue, only it is between HDMI and VGA. I cannot get into Safe Mode or the BIOS Setup Menu with HDMI. So I have both cables connected and when I need to access Safe Mode or the BIOS, I flip the monitor's input selector to VGA. And I believe that is needed because the default mode for the card is VGA and it does not switch to HDMI until the card's drivers are loaded. And of course, that does not happen until after the POST and the boot drive is touched, and Safe Mode works with limited basic drivers.
 
Well, that, to me, would suggest the issue is with the card and how it prioritizes protocols and not the monitor itself. It is the cards responsibility to sync with the monitor. But the monitor should be saying "here I am, sync with me on DP".

I have an old Viewsonic that has a similar issue, only it is between HDMI and VGA. I cannot get into Safe Mode or the BIOS Setup Menu with HDMI. So I have both cables connected and when I need to access Safe Mode or the BIOS, I flip the monitor's input selector to VGA. And I believe that is needed because the default mode for the card is VGA and it does not switch to HDMI until the card's drivers are loaded. And of course, that does not happen until after the POST and the boot drive is touched, and Safe Mode works with limited basic drivers.
I get what you mean but this PC is working properly with another monitor and DP cable, so its GPU (RX480 Nitro) doesn't cause that issue at all. However, thanks a lot for sharing your experience.
 
Well, Asus is talking shit, as this is not a default behaviour of monitors.
However, I have had this problem in the past and it seems to be a combination of the graphics cards, the DP port you're using and the display in question.
I have had this issue with various older graphics cards and I have had to swap DP port to make it work. Some cards that had only one DP port seemed to have had a weird preset where the DVI or HDMI port was the "boot" port. This meant I had to reboot to get into the BIOS/UEFI at times.
Not having this problem with my current setup though, which is an Asus screen that technically only has one useful port, which is DP, as the HDMI port is limited to 24Hz...
It doesn't mean the monitor is faulty though, it just mean the combination of hardware you have doesn't behave the way the display is expecting in terms of the display signal going to the monitor on boot and that Asus was too cheap to go with a solution that doesn't have this issue. It's all really down to what controller board/hardware is used in the display, some is better, some is cheaper...
 
Well, Asus is talking shit, as this is not a default behaviour of monitors.
However, I have had this problem in the past and it seems to be a combination of the graphics cards, the DP port you're using and the display in question.
I have had this issue with various older graphics cards and I have had to swap DP port to make it work. Some cards that had only one DP port seemed to have had a weird preset where the DVI or HDMI port was the "boot" port. This meant I had to reboot to get into the BIOS/UEFI at times.
Not having this problem with my current setup though, which is an Asus screen that technically only has one useful port, which is DP, as the HDMI port is limited to 24Hz...
It doesn't mean the monitor is faulty though, it just mean the combination of hardware you have doesn't behave the way the display is expecting in terms of the display signal going to the monitor on boot and that Asus was too cheap to go with a solution that doesn't have this issue. It's all really down to what controller board/hardware is used in the display, some is better, some is cheaper...
Thanks for the suggestions. The RX480 has 1 HDMI and 2 DPs so I tried with both of the latter ones with the same symptoms on the faulty monitor and without any of those in my old 60Hz LG monitor.
 
It's a comedy if errors tbh. If I read your post before I would've suggested to turn off Freesync from the monitor OSD if ypu want to access boot screen. But since you returned it I hope it was just a monitor issue.
 
Back
Top