Computer turns on, off, on again without booting

Krackit

Reputable
Oct 21, 2014
1
0
4,510
Today I decided to insert 2 sticks of Corsair 2GB ram (cm3x2g1333c9nx) to supplement my 2 sticks of Corsair (Vengence cmz8gx3m2a1866c9) 4GB ram without really looking into if this is something I could/should do.

I definitely found out when I turned it on and there was a quick puff of smoke. After a 4 second panic I flipped off the power supply. I removed the added RAM and gave the inside a look, but I couldn't see any damage, so i turned it on again.

Now it only turns on for a split second, stays off for 5 or so seconds, and turns back on. I don't hear any beeps, and there is no display at all.

I've tried a few different things without any change:

I tried only one stick of RAM, as well as trying one of the other 2 sticks of the 2GB RAM (I had 4 total but only used two with my 4GB ram) that I hadn't used as well - same result.

I tried switching out my GPU (from my GeForce GTX 680 to my older but functional GeForce GTS 450) in case it was an issue there, same result. I'm fairly confident that the GPUs are fine.

I forget the exact processor information, but I'm quite sure it is an Intel i7. The motherboard is an ASUS P8P67-M (rev 3).

Everything in this computer was purchased in 2009 with the exception of an SSD and the GPU, so it's getting up there in age.

Any insight as to what the issue I've created is would be much appreciated.
 
Solution
Hate to say it but It's probable you messed up the memory socket on the motherboard itself. A bad socket would cause the board to go into a continuous boot loop with the memory installed. Experiment at your own risk but you could try putting just one known good stick into each socket and see if you can get the system to boot and figure out which socket is bad. Problem is if the socket is bad you could potentially ruin the memory stick as well. I had an MSI mobo with a bad socket that would do the boot loop with memory installed in the bad socket but booted fine with sticks in the other slots leaving the bad slot empty.

Navman72

Reputable
Oct 13, 2014
7
0
4,520
Hate to say it but It's probable you messed up the memory socket on the motherboard itself. A bad socket would cause the board to go into a continuous boot loop with the memory installed. Experiment at your own risk but you could try putting just one known good stick into each socket and see if you can get the system to boot and figure out which socket is bad. Problem is if the socket is bad you could potentially ruin the memory stick as well. I had an MSI mobo with a bad socket that would do the boot loop with memory installed in the bad socket but booted fine with sticks in the other slots leaving the bad slot empty.
 
Solution