DisplayPort sucks...
DisplayPort sucks...
DisplayPort has consistently been unreliable, and fixing connectivity problems by power cycling the display has worked in the past. I own a 3070 with three DP and one HDMI port, two 1080p60 monitors using only HDMI, and a 1440p165 monitor that supports both DP and HDMI. Over time, I’ve noticed the main monitor (DP) sometimes disappears from view, but a restart always restored it. More often, the software has rearranged itself, showing the display reconnects automatically. One of my HDMI monitors uses a DP-to-HDMI cable, yet still fails to show anything. I’ve tried everything: powering off and on, changing ports, updating drivers, reinstalling them—but nothing helps. Windows 10 detects it (by model) but marks it as disabled and won’t turn it on. I attempted to bypass by connecting via HDMI, which worked. When I unplugged the DP cable, the display stopped responding entirely. Only when both cables were connected did it function properly, using DP at full resolution. Removing the HDMI connection caused DP to fail too. This behavior is strange and seems to defy expectations. DisplayPort is clearly problematic despite its reputation as a superior standard. I’m hoping this issue resolves itself soon, so I won’t forget about it for too long until it happens again.
Looking at the setup at my workplace, I’ve noticed smooth operation with multiple computers supporting DisplayPort, DVI adapters, and even VGA converters. The only hiccup was the unclear nature of USB-C specifications, especially regarding DP compatibility. A recent HDMI problem stood out too—there was a noticeable overscan issue when connecting my laptop to the TV, despite everything functioning fine the day before. I changed the cables, and both devices worked perfectly. It seems it’s time to reconsider using that cable again.