No video playing during startup.
No video playing during startup.
My 5900X build has generally worked well—except for one persistent problem that changes with time. It occasionally boots without video. At first I believed the system was freezing before loading, but after disconnecting and reconnecting the cable, it started booting into Windows without showing any video. Re-seating the GPU, RAM, or cable, adjusting the cable layout, using a support wire to fix GPU sag, and confirming the connection to the main HDMI port all failed to resolve the issue again this morning. I’m feeling quite frustrated. My main question now is whether a PCIe3 M.2 drive could affect GPU video display during startup? I suspect the WD Blue SN570 M.2, being a PCIe3 device, might sometimes block the GPU from showing video when it powers on. I’ve also read some discussions suggesting USB devices can be the culprit, so perhaps the x16 USB riser I have is causing the problem. It wasn’t critical, just installed to protect the system board from physical stress. Removing the card triggered a freeze while loading in Device Manager. I spent hours trying to identify and disable the right device, but couldn’t find a solution. This situation has become quite annoying. I’ve backed up all my data to an external drive and plan to try a fresh Windows install without the riser. If that doesn’t work, I might switch to a non-M.2 SSD or simply remove it entirely and start over. Do you have any other ideas? I also noticed that even though I’ve set Asus Aura to dark on the motherboard via Armoury Crate, it displays a rainbow effect when not in use. It seems unnecessary for idle operation. Could the system be going into sleep mode instead of shutting down when prompted? Specs: Ryzen R9-5900X, Asus Tuf Gaming B550-PLUS 2x16, Crucial Ballistix CL16 (3200 OC with stock timings), WD Blue SN570 1TB M.2, WD Black 6TB HDD, Corsair iCUE Commander Core XT (six 120mm fans), Scythe Mugen 5 Black Edition cooler, Inantek 20GBps (10GBps per 3A/1C), USB 3.2 x16 riser, Corsair 4000X RGB case. Updated July 13, 2022 by An0maly_76
I've experienced similar problems before with my 980ti, where it wouldn't show up in DP until after posting and the BIOS splash screen appeared. Once resolved, it would always recover afterward. Likely the issue was with my Corsair K70 RGB featuring two USB 2.0 ports, which caused the output to redirect when connected to any USB 2.0+ device. I recommend checking the BIOS for a display PCIE option. Set it to show only from the PCIE slot where your GPU is located to avoid conflicts with other slots or onboard graphics. Also, try running DDU and reinstalling your drivers.
I don't appear to have the choice you're looking for, or an alternative I was recommended. This isn't the only case, but it creates a difficult situation for me. The issue stems from several factors: threads suggest the main problem is either the board itself or an overload of USB hubs, ports, or devices, plus a PCIe conflict (potential interference between the USB riser and GPU, especially since the riser uses an x8 port in an x16 slot, worsened by the M.2). Any of these could fit my concern. But is it a matter of two or just one? Unfortunately, the board isn't a fix, as it's one of only three available (all from ASUS) that can manage the heat from the 5900X. It seems this would be more common and troublesome if the board were the cause. Even with a BIOS update, ASUS' site doesn't clearly guide users on obtaining or updating firmware. The USB riser isn't a deal-breaker—it was added just to protect the mainboard's USB ports. I suspect the M.2 might be the culprit, too. It's possible it's designed specifically for compact setups like iGPU or mini-ITX builds where space is limited, leaving no room for a dedicated GPU or traditional SSD/HDD. Whether it uses SATA bandwidth or not, it still relies on PCIe lanes. An article I found points to the M.2 possibly blocking the GPU during boot: https://bit-tech.net/blogs/tech/storage/...nfusion/1/. I'm considering reinstalling Windows without the riser, keeping the M.2, but it seems the M.2 itself might be the issue. Removing it and switching to a 2.5" SATA drive could help. Alternatively, moving the M.2 to the lower slot—since only that position near the CPU causes trouble—might resolve the problem. I plan to test this tonight. Any advice? Edited July 14, 2022 by An0maly_76 Updated with more details
Well, it's been a bit of a puzzle lately. After about four months of repeated issues, I've tried reseating the drives and still faced problems. The Rig was positioned behind my monitor, making it hard to spot the issue until now. I ran MemTest86, and both drives passed without errors. Could this combination actually cause trouble? Why does it seem so inconsistent when the system boots? Updated July 16, 2022 by An0maly_76 Added more details
Latest update: Talked too early... It seems there might be a motherboard problem, as the system works well except for the mentioned issues. Edited July 17, 2022 by An0maly_76 Updated further