Running the PC in a loop and illuminating the red indicator for Dram and CPU
Running the PC in a loop and illuminating the red indicator for Dram and CPU
I assembled most of my system around Christmas but I was out of RAM until now. I've been working on this for hours without success. The machine won't boot and I see a red error light and a CPU indicator periodically. I can't reach the BIOS either. My specs are: I7-12700k Kingston 32GB DDR5 5200MHz (2x16), Rtx 3080 (currently not installed but present), Corsair iCUE H100i Pro 750W PSU, Gigabyte Z690 U board. I've tried adding one RAM stick, checked all slots and cables, re-seated the CPU twice, and cleared the CMOS. Anyone have any advice or suggestions? (Apologies for the cable mess, I'm a bit careless)
Confirming your steps: you installed both RAM sticks in the main DIMM slot correctly. There’s one slot that needs to be filled or it won’t boot. Your manual will indicate which one. If it still doesn’t work, it likely points to a faulty CPU. You might also want to remove the boot drive, graphics card, etc., to check. You won’t see an image, but you’ll see at least the boot LED if either component is causing the issue. If you have another CPU, test it too. As a final option, you can re-flash your UEFI BIOS using BIOS flashback.
any way you could test with another set of ram? that would rule out ram issues
They mentioned A2 and B2 slots for initial setup, which was the first attempt. After that, I tried other slots and then used just one stick again. I removed the GPU, took out the RAM and M.2 SSD. The same flashing lights appeared, CPU and DRAM were active. Since I don’t have any other CPU or RAM, I can’t confirm if either is broken.
Unfortunately, I don't have any other DDR5 RAM sets. I tested each stick individually, so unless both are bad, it's probably not the problem.
I recently installed a new motherboard, CPU, RAM, and the PC was functioning fine until I tried reinstalling the CPU fan. The system stopped working, and the problems began. Have you encountered this issue before? If yes, what steps did you take to resolve it?