Host down after attempting RAM upgrade

[Nercules]

Hello,

I have a simple desktop that I switched into an homeserver with Proxmox virtualisation. Recently I tried to upgrade my RAM from 16GB to 32GB. I bought 2dn hand memory sticks of which I assume they work fine. The sticks have the same brand, capacity, speed and timings. But a different heatsink.

So the original RAM was installed in slot 2 and 4. I shut down the machine and simply pluggin in the other two sticks in slot 1 and 3. When I booted the machine back up, it started making beeping noices and the RAM led started blinking, as also the 4 led above the ram slots started lighting up. Also the CPU led blinked a few times. After a little while I shut down the machine again and I removed the new sticks from the machine. But now it is not even booting on the old configuration. No mather what combination I try, the machine keeps beeping and leds keep blinking. I am really confused on why this is, I always thought that RAM upgrades where plug and play.

Specs:
all 4 RAM sticks: Balistix sport ddr4 2400MHz | BLS8G4D240FSB.16FARG
CPU: i7 7700
Proxmox is installed on a single 64GB ssd, all the VM's and data are on seperate disks.

 

[leesteken]

Hope you realize this has nothing to do with Proxmox. Maybe look in the motherboard manual (or manufacturer support site) what the various beeps and LEDs mean? It could be something else that you bumped lose or damaged unwillingly.

 

[Nercules]

So I can exclude the idea that proxmox has anything to do with this?

 

[Felix.]

So I can exclude the idea that proxmox has anything to do with this?

Yep.

Most likely a BIOS issue - ram timings / speeds, maybe OC profiles misconfigured.
Or simply a hardware issue, depending on the beep codes.

Google those beep codes for your board, that should give you a clear hint what is wrong.

When your system gets bootable again, like beside being able to enter the BIOS/EFI, run memtest86 to make sure your hardware is fine.

 

[Neobin]

In addition to what was already said, you could try with a cleared CMOS.

 

[cwt]

As @Neobin already mentioned, try clearing your CMOS. Most boards have a jumper for this, but to be sure read the manual of your board. You could also remove the CR2032 battery. Disconnect the power cord, after that hold down the power button a few seconds to discharge any remaining capacity, ground yourself and remove the battery. Wait a few seconds and put it back in.

 

[Nercules]

Thanks @cwt @Neobin, clearing the CMOS helped, I just had to jump two pins for a few seconds, while power was disconnected. Everything booted and seems to be working with the new RAM configuration.