There is an unusual issue where the new system fails to boot into the BIOS.
There is an unusual issue where the new system fails to boot into the BIOS.
This situation continued as an ongoing discussion nearly four months in the making. I paused on this task for a while because it became increasingly annoying, but then consulted a specialist and believed I had resolved the issue twice before. Still, it didn’t work.
The trouble began when I upgraded all my hardware—new motherboard, processor, power supply, case, NVMe SSD, and cooler. Despite these improvements, I ended up salvaging components from my previous setup to fit into the new one. The problem emerged during assembly: when trying to install everything on the new motherboard, the system failed to boot. The monitor would display a no input screen for a brief moment before entering sleep mode, which would only resume if an input was present.
I attempted to reset the CMOS, reinserted RAM, and reconfigured the GPU. Still, nothing resolved the issue. I considered returning the CPU and motherboard, but decided to keep testing. After reassembling everything, it worked again.
Then I removed the 24-pin connector from the motherboard and realized I should boot into BIOS to verify functionality. When I reconnected, it failed completely regardless of my attempts. Eventually, I gave up and brought it to a local repair shop.
I initially brought only the new parts—motherboard, PSU, CPU, NVMe SSD, and cooler—since I trusted the other components in my current system. The technician checked the same problems with a multimeter on the PSU and confirmed that the GPU and RAM were working. Upon receiving the new hardware, I followed his instructions to boot into BIOS, but it still didn’t work.
I experimented by moving the graphics card between slots, removing RAM sticks one at a time, and even using only one stick, but nothing resolved the issue. Later, when he swapped out two incompatible RAM modules (16 GB Ballistix DDR4), the card booted into BIOS successfully. He also mentioned that turning off and restarting the system resolved the problem multiple times.
I tried relocating the card between slots, disassembling it, and testing with just one RAM stick, but nothing changed. Eventually, I returned to the shop with my graphics card, and within 15 minutes it booted into BIOS. He explained that two of my RAM sticks weren’t compatible due to their size (16 GB Ballistix DDR4), while the other two worked fine. He showed me the BIOS update helped, and after a reboot, it functioned properly.
However, when I tried again at home without the anti-static bag, the same problem occurred. I kept the bag under the board to test, but it resolved once I waited a few seconds after removing it. I also checked the power supply connections carefully—no changes made.
I’ve been monitoring the situation closely, keeping the anti-static bag in place, and following the recommended steps. Still, I’m puzzled by this recurring issue and unsure what might be causing it. Any advice would be greatly appreciated.
It was a lengthy read, but my suggestion: contact the repair professional at your location and attempt to resolve the problems at home. Perhaps even hire them to assemble the setup fully at your place once the initial testing succeeds.
When the PC is powered on and you're in BIOS, allow it to remain active for some time. Avoid shutting it down abruptly. (I even went through several exit BIOS, POST cycles, and returned to BIOS before powering off during breadboarding.)
After turning off the PC (switching the PSU), do not immediately restart the build. Let it rest for at least a minute. <- This approach worked well with older hardware (PATA/IDE era), where waiting until you powered it back on was necessary. I haven't tested it with modern components, but it still holds true today. For electronics in general, it's undesirable to keep devices constantly on and off, especially without allowing small capacitors in the motherboard or power supply to discharge properly.
Alright so I tried what you said. I took all my parts out of their boxes, set it all up, and first time I start it up, it works. I sit in bios and exit the bios a good 5-10 times, and I let it sit for like 10 mins minimum. I then powered it off, and let it sit for around 8 minutes. I powered it on and still the same issue occured. I then unplugged the PSU and jumped the starter pins for about 20 seconds to drain the capacitors and tried to power it on but still, same problem. Then I unplugged all PSU connectors from the board, and took out the GPU, and pulled out the cmos battery, and waited about 8 minutes. I put the battery in and start it all up, but still nothing. For whatever reason, it seems to want to work when I pull everything out for the night, and wait about 8 hours before I try anything again? Idk tbh this just brings up more questions than it answers.
This symptom suggests replacing the PSU. While the EVGA SuperNova GT is of good quality, there are still potential issues. Even if you use a high-quality, reliable PSU (such as top models from Seasonic PRIME, Corsair AXi or Super Flower Leadex Titanium), it's possible the problem lies elsewhere. It might also help to use a different power socket at home, just in case the issue is related to the main power supply.
I'm not sure if Amazon will exchange it after four months since purchase. I've already tested it with a multimeter and another device, but that's one of the few parts I haven't replaced. I'm wondering what else I might do in the meantime. Thank you for your assistance with all this.
To make the PC function properly, you need four parts: CPU, motherboard, RAM, and power supply. However, because your CPU has an F-suffix, without an integrated graphics card, you’ll also require a separate dedicated GPU. The display is there to observe what the PC is doing, while keyboard and mouse handle input. Therefore, your problems mainly relate to these five components.
Using a multimeter won’t help much, as there’s no load on the power supply during testing. To confirm the PSU works correctly, you need specialized equipment that applies load while monitoring its outputs.
When setting up a breadboard, stick to one RAM module only—switching it might reveal if it’s the issue.
In summary, it’s hard to pinpoint exactly why your build is behaving this way.
Additionally, the fact that your CPU is F-suffix makes things more complicated, because it forces you to include a separate GPU. This is essentially the main reason I wouldn’t recommend getting an F-suffix CPU unless you’re certain it won’t be needed. Sure, in most cases the integrated graphics are unused and don’t help, but for those rare instances where problems arise, removing the GPU and checking with the motherboard and monitor can be very useful.
Alright, I finally got the new PSU, tried it out about an hour ago and still have the same problem. I plan to call the repair guy and bring my stuff over so he can check everything and see if it’s a user error. My other thought is that when I brought back either the board or the CPU, they sent me another DATA one, but I don’t think that’s very likely.
About that; i've seen countless of cases where people have gotten DOA as 2nd or even 3rd replacement. Both on PSUs and MoBos. So, for my eyes, this isn't that unheard of. Of course, there's also the fact that i'm on the tech support side of things and all cases i see, are to do with PC acting up. Those PCs that operate fine, i won't get to see, since there's nothing to report about.
So, while my experience would suggest some foul play on the hardware replacement part and it's more like hit or miss, i have to remind myself that this is actually very small percentage of all returns ever made.
Sometimes, even my morale gets low, since all what i see, are PC failures. While there are actually far more success stories out there. It's like where doctor may think that all people in the world are sick, since he only sees sick people. Or car mechanic thinking that all cars out there are broken, since he only sees broken cars.
But yeah, get the repair guy out and go over the PC on-site.