Got a new OLED monitor, and my PC wouldn’t start anymore. It’d power on - all the lights came on etc. - but nothing would happen and the monitor would go into standby after a few seconds, saying there was no signal. I have a program I use for remote access via my phone, so I’d check that to see if the PC actually made it into Windows or not, but it didn’t. Plus tapping the power button would switch off the PC again instantly, as opposed to having to hold it down like normal, so it seems it didn’t get past stage 1 of bootsville.
After MANY hours of futile fiddling, I discovered that it was as simple as starting the PC with the monitor off, and after the first few seconds, to turn on the monitor. Everything’s fine after that, until I need to start my PC again the next day. I need to turn off the monitor, press my PC power button, then after a few seconds turn on the monitor.
What the hell is going on here?
Specs:
- GPU: NVIDIA GeForce RTX 5070 Ti
- CPU: Intel Core i9 9900K
- RAM: 32GB Corsair DDR4 (rockin’ a small country’s GDP these days)
- Monitor: Samsung Odyssey G81SF
- Motherboard: Gigabyte Z390 AORUS PRO WIFI-CF
My previous monitor was connected with a display port cable, and the new one is with a fancypants HDMI one.
It’s obviously a minor issue to have to turn off the monitor before booting, but I’m curious as to why it’s happening in the first place. If there’s something I can do to fix it, all the better. But it’s so bizarre.
Cheers!
Some charge leak somewhere? I’ve had a case in which, if you touched the blend with the connector (sometimes also the finger, static charge), it would turn video off until reboot.
Now see I have the opposite problem after transferring to Linux lol If the laptop is connected to my thunderbolt 4 dock, the second it turns off… it turns right back on. I have to unplug the dock to keep it off.
I’ve seen this problem before and it was fixed with a BIOS update. Consider checking for an update.
I would also suggest trying a different cable or connecting your monitor using a different display standard if it supports this.
Some newer monitors can support stuff like HDMI-CEC, HDCP (aka DRM to prevent copying video feeds), and EDID handshakes. Your motherboard, especially if it’s older, is probably getting hung up trying to resolve these during boot.
You can go into the monitor’s settings and try disabling extra features like HDMI-CEC, upgrade your motherboard bios, switch to display port (or display port->HDMI cable), or try disabiling legacy boot. There’s probably some other stuff to try, but that should give you somewhere to start.
You can also gather more info, like if it happens with other HDMI monitors (specifically newer monitors only or all HDMI).
I’d try:
-
Powering up the system and monitor without the HDMI connection in place, on the off chance that it’s somehow related to power draw the moment that the things are coming on rather than the data connection. If that’s the issue, there are fancy power strips (PMUs) designed for server racks that can be set up to power on each successive device with a delay to avoid having large instanteous load.
-
Using DisplayPort rather than HDMI (DisplayPort presently can do higher throughput than HDMI, FWIW, IIRC).
-
Inserting some device that talks HDMI between the two.
EDIT:
- Try putting both the monitor and computer on the same power circuit if they aren’t currently so that you’re sure that they have a common ground.
higher throughput than HDMI, FWIW, IIRC
Holy mother of acronyms
-
Weird. Is the monitor connected via USB as well?
I’m the BIOS, there’ll be an option for which device to use as primary display, it’s usually labelled as PCI or something. Switch that.
Also why hdmi and not displayport?
Video BIOS.
You’ll probably find it works when you set the Odyssey to a lower refresh rate too (effectively a lower bandwidth device), but obv that’s not a fix. So flash the latest video BIOS from the card manufacturer.
If that doesn’t work, do the motherboard BIOS for good measure. And any firmware on the Odyssey if it has it.
It’s almost certainly not a hardware issue and cannot be a driver issue.
Try setting a lower version of displayport on your monitor. I have the 57" Mini LED Odyssey and Kubutnu refused to start if I had it on DP 2.1 (i think its 2.1) but dropping it to 1.4 fixed it despite my card supporting 2.1.
isn’t this the type of thing that the monitor is supposed to change and auto do usually?
Yes but monitors have become so complicated now that there could be a bug. Or the cable might not support it properly.
I was gonna ask if you had tried a few different cables. I ended up having to buy a brand new display port cable when I got a new monitor. But it’s not even leaving Bootsville? Now that is interesting. What about what the other person said: Do you have a connected via USB as well? If so try booting without that. Did you try the old DisplayPort cable?
