This model doesn't show a DisplayPort connection during startup until the operating system loads.
This model doesn't show a DisplayPort connection during startup until the operating system loads.
Hello. I updated my monitor and GPU setup: an Asus PG259QNR with a 360Hz Nvidia G-sync chip paired with an Asus TUF 4070ti OC. When powering on, I receive five short beeps, no DisplayPort signal, and a black screen, though the Windows OS loads correctly. This issue occurs during cold boot (over 30 minutes off). After restarting or a brief boot (system off for 1-5 minutes, then back on), everything functions normally. The other hardware includes a Gigabyte Z490 Aorus Master with 32GB 3200 CL14 B-die. These components have worked perfectly since 2020 without any system crashes. The connection uses the original DisplayPort cable from my monitor. The five-beep warning seems misleading; according to Gigabyte’s FAQ, it indicates a CPU error, but this happened after installing new parts. Other users confirm this message appears even without display or GPU signals. I updated the BIOS to version V1 on ASUS’ support site (notes suggest it improves compatibility), but it didn’t fix the problem. I also reverted back to the original BIOS. I changed the PSU to a Seasonic 850W 80+ Titanium due to power needs, though I’m unsure how that affects the display. No overclocking is active. I removed the GPU and reconnected the 12VHPWR adapter and PCIe cables; no improvement was noticed. The adapter uses two separate cables from the PSU (no daisy chain). I have the latest F21 Gigabyte motherboard BIOS, and I attempted an Nvidia firmware update to resolve the DisplayPort signal issue, but it wasn’t necessary since the card is 10xx. Any advice would be appreciated. Thank you.
It’s probably a problem with the firmware on the board and the card not connecting properly during startup. This kind of issue isn’t easily fixed unless you understand how to build your own firmware. It could occur if the manufacturer didn’t notice a conflict between this card and the board. If it bothers you, you might test another 4070 to check compatibility.
Having five beeps at startup isn’t ideal for the long term, especially since I can disable the system speaker if needed. The blank screen is tolerable. Should I file a support ticket with Asus? I’m considering keeping the card and hoping a vBIOS update will resolve the problem. Would it help to return the board before the end of the return window, as I don’t want to waste time trying a new card?
it'll only work if there are sufficient complaints, otherwise they'll repeat the same advice and suggest another card. actually, any organization will do its best to shift responsibility and won't assist, which can be frustrating. your board functions properly, so if I were you, I'd switch to a different brand or model. remember, this firmware issue is just a hypothesis that needs verification—it's my assumption, not confirmed.
Hello. I attempted a different method. I saw online that turning on the monitor before starting the computer might help with the same problem—no DisplayPort signal, but without beeps. So I pressed a button on the screen before powering it up. The steps were: I pressed one button, and the display turned on showing the ASUS logo (with "DisplayPort" instead of the "no DisplayPort signal"). Then I pressed the computer power button; it started up and displayed the BIOS Gigabyte boot logo. No beeps or error sounds appeared, and the system loaded normally. The boot process was smooth, with no audio warnings.
To clarify:
1. If you don’t press any monitor button: the screen turns off, you power on, see "no DisplayPort signal," then hear 5 short beeps, get a blank screen until W10 appears.
2. If you press a button: the monitor lights up with ASUS logo and "DisplayPort" message, power on, see Gigabyte logo right away, then W10 appears—this seems like a standard boot.
I’m not sure what this means for your setup. The monitor model PG259QNR seems to have special features like 360Hz/G-sync, but it doesn’t appear to need a warm-up period. There’s a "Deep sleep" setting on the screen, which keeps it off unless you wake it with a button press. Disabling that might help if it’s stuck in sleep.
In the meantime, I came across several discussions: https://rog.asus.com/forum/showthread.ph...isplayPort Deep Sleep makes the,Deep Sleep on the monitor. https://www.reddit.com/r/buildapc/commen...erm=a11j7y This problem occurs when the monitor takes a long time to power on, causing it to enter Deep Sleep. Once awake, the graphics card may skip the BIOS because it assumes no display is connected. Fixing this usually involves turning off Deep Sleep on the monitor. If you're experiencing similar issues, I'm considering disabling the feature and testing the result. I'll share my findings later.
Hello. I identified the issue: the Asus PG259QNR monitor had its power management setting changed off. Turning it back on resolved the problem. When the feature was active, the monitor would take too long to respond, causing the GPU to assume no display was connected and triggering a "No DisplayPort signal" error. Once that was disabled, pressing the power button worked within seconds, and everything functioned normally. This setting is usually enabled by default, making it tricky to diagnose without outside help. It seems the monitor should stay in a deep sleep mode, but with this option on, it behaves unexpectedly fast. This could point to a firmware issue. If you encounter a blank screen after "No DisplayPort signal" at startup, try disabling the monitor's power management feature and see if it improves the boot process. This might not be unique to Asus—some users have reported similar problems with Samsung monitors as well.