F5F Stay Refreshed Hardware Desktop New build features DRAM lighting.

New build features DRAM lighting.

New build features DRAM lighting.

S
stevie_123
Junior Member
2
02-12-2021, 11:05 PM
#1
New build details available. Parts saved here: https://pcpartpicker.com/user/schaefstev...iew=f99FXL. On startup, fans spin up on the case and PSU, but not the graphics card. The CPU light turns red briefly before the DRAM light also lights red and stays active. I've experimented with different RAM configurations—two sticks in two slots, one in each slot, another in a single slot—but no improvement. No RAM detected. Tried reseating the CPU, booting without the cooler, checking for bent pins, removing the GPU and trying again, clearing CMOS, and leaving it for 5-10 minutes. I haven't tested any other DDR5 systems or components. The manual suggests a RAM issue, but I suspect another problem. One memory of early boot issues was a loose GPU power connector.
S
stevie_123
02-12-2021, 11:05 PM #1

New build details available. Parts saved here: https://pcpartpicker.com/user/schaefstev...iew=f99FXL. On startup, fans spin up on the case and PSU, but not the graphics card. The CPU light turns red briefly before the DRAM light also lights red and stays active. I've experimented with different RAM configurations—two sticks in two slots, one in each slot, another in a single slot—but no improvement. No RAM detected. Tried reseating the CPU, booting without the cooler, checking for bent pins, removing the GPU and trying again, clearing CMOS, and leaving it for 5-10 minutes. I haven't tested any other DDR5 systems or components. The manual suggests a RAM issue, but I suspect another problem. One memory of early boot issues was a loose GPU power connector.

S
SanayZockt
Junior Member
5
02-14-2021, 08:37 AM
#2
I’d take the opposite route, as finding two dead sticks in the same kit is uncommon. That wouldn’t impact the situation right now. What I’d follow next is a BIOS Flashback to check if the BIOS was damaged during setup. Detailed steps can be found in the motherboard manual.
S
SanayZockt
02-14-2021, 08:37 AM #2

I’d take the opposite route, as finding two dead sticks in the same kit is uncommon. That wouldn’t impact the situation right now. What I’d follow next is a BIOS Flashback to check if the BIOS was damaged during setup. Detailed steps can be found in the motherboard manual.

B
Buns_of_Steel
Member
217
02-15-2021, 11:32 AM
#3
Great suggestion! However, it didn't work before. Please try again.
B
Buns_of_Steel
02-15-2021, 11:32 AM #3

Great suggestion! However, it didn't work before. Please try again.

L
Luis1234
Member
62
02-19-2021, 10:31 AM
#4
You'll likely have to replace the motherboard instead of reaching out to Gigabyte.
L
Luis1234
02-19-2021, 10:31 AM #4

You'll likely have to replace the motherboard instead of reaching out to Gigabyte.

8
8IIIIIIIIIIIID
Junior Member
19
02-20-2021, 01:40 PM
#5
You're checking your setup carefully. The DRAM light indicates the system is recognizing memory, but it doesn't confirm proper functionality. If you're unsure about compatibility, testing the GPU connection might help determine if it's starting up at all. Consider replacing the RAM to rule out a faulty stick.
8
8IIIIIIIIIIIID
02-20-2021, 01:40 PM #5

You're checking your setup carefully. The DRAM light indicates the system is recognizing memory, but it doesn't confirm proper functionality. If you're unsure about compatibility, testing the GPU connection might help determine if it's starting up at all. Consider replacing the RAM to rule out a faulty stick.

M
MiniYBallY
Junior Member
30
02-22-2021, 04:08 AM
#6
The setup is finally functioning properly. As mentioned earlier, replacing the motherboard didn’t resolve the problem. I received a different model or RAM—Corsair Vengeance. This time I verified that the new RAM appeared on the motherboard’s qualified vendor list, whereas the original wasn’t. At first, both performed similarly. My main guess is that the problem stemmed from the RAM slots I was using combined with needing to restart after training. I inserted a stick of the new RAM into slot B2, attempted to boot, saw the DRAM light, waited about three minutes, then restarted with the same slot and it finally worked. After that, I still couldn’t boot with only RAM in slots A1 or B1, but it functioned correctly when both A2 and B2 were used. There’s no documentation on the motherboard indicating single sticks must go into specific slots, though I suspect it should work if all four are filled. In my earlier tests, I tried RAM in each slot only once, not twice. If anyone encounters this issue later, try placing a RAM stick in each slot individually, wait a few minutes, then reboot. I believe the original RAM would have worked even if it wasn’t on the QVL, but I didn’t test that. Now my system is operational and I’m ready to conclude the troubleshooting.
M
MiniYBallY
02-22-2021, 04:08 AM #6

The setup is finally functioning properly. As mentioned earlier, replacing the motherboard didn’t resolve the problem. I received a different model or RAM—Corsair Vengeance. This time I verified that the new RAM appeared on the motherboard’s qualified vendor list, whereas the original wasn’t. At first, both performed similarly. My main guess is that the problem stemmed from the RAM slots I was using combined with needing to restart after training. I inserted a stick of the new RAM into slot B2, attempted to boot, saw the DRAM light, waited about three minutes, then restarted with the same slot and it finally worked. After that, I still couldn’t boot with only RAM in slots A1 or B1, but it functioned correctly when both A2 and B2 were used. There’s no documentation on the motherboard indicating single sticks must go into specific slots, though I suspect it should work if all four are filled. In my earlier tests, I tried RAM in each slot only once, not twice. If anyone encounters this issue later, try placing a RAM stick in each slot individually, wait a few minutes, then reboot. I believe the original RAM would have worked even if it wasn’t on the QVL, but I didn’t test that. Now my system is operational and I’m ready to conclude the troubleshooting.