Computer keeps on rebooting

isthatbbq

Honorable
Apr 13, 2013
4
0
10,510
A little less than a month ago, my computer suddenly crashed on me while I was browsing the web, and when I tried to turn it back on, it got caught in a boot loop. All my fans would start spinning up for a second, and a few LEDs on my motherboard would turn on, but before reaching BIOS, the computer would turn off. Without me having to do anything, it will try to boot up again, and the cycle will keep on going until I unplug the machine.

I didn't have time to try and fix it since then, but today, I tried a few conventional methods and nothing seems to work. Things I have tried:

1. Resetting CMOS by removing battery.
2. Unplugging everything, and reseating motherboard.
3. After that, I tried booting with nothing installed but the CPU, but the problem persisted.
4. I tested my PSU on another computer and it worked.

I looked at my bare motherboard but saw no signs of a burn or burst capacitor. I don't know how to check for any physical signs of CPU failure, do you guys have any hints? Does anybody have a clue as to what's going on?

Specs -
CPU - Core i5 2500K
Mobo - Gigabyte Z68X UD4B3 Rev 1.0
SSD - Intel 520 Series 240GB
HDD - WD Caviar Black 1TB
GPU - Radeon HD 6870 (Asus)
PSU - OCZ Z Series 1000W
Chassis - CM HAF 922
 
It would be helpful if you listed your full configuration.

A quick check you can try is try different memory.

To test your RAM taking out the RAM then put in just 1 stick and see if it boots properly. If it loops again shut it down and move the same RAM stick to the next slot. Start the computer and see if it loops again. If it does shut it down and try the next slot, if you only have 2 then do the same test with the other RAM stick. In this way you test all the RAM and all the sockets.

If you have another CPU that will run on your motherboard you may try that next.
 

isthatbbq

Honorable
Apr 13, 2013
4
0
10,510


Unfortunately I do not have other memory. I have test both my RAM sticks in all the memory sockets and the same boot loop still occurs. I also don't have another CPU that runs in the socket.

Any other ideas?