[Solved] Reset MemOK on P67, but now system won't boot at all

TL;DR - I installed my RAM improperly by having it in slots 1 and 2, rather than 2 and 4. Computer kept crashing, deduced that it was RAM related, tried to "reset MemOK" as recommended elsewhere, and now the machine is dead dead and won't even boot into BIOS on a cmos clear.

--

Hello all,

I recently built my own PC from scratch for the first time by myself. The core components:

- Sabertooth P67
- i5 200K
- Western Digital HDD 120 GB
- XFX GTX250 video card
- Ultra 550W power supply
- 2x 4GB G.Skill Sniper DDR3 RAM


Things were running great for a month. I had no problems at all. Then, randomly this week, the machine instantly shut off, no BSOD.

In my initial research I thought it was my video card over heating. But after downloading some tools to monitor the temps, my CPU never got above 60º and GPU never above 80º.

Then I thought it might be my RAM. After more research, my symptoms were exactly what either faulty RAM or improperly installed RAM will give you. Well, I realized that my RAM was in slots 1 and 2, rather than 2 and 4 as recommended elsewhere. When trying to swap the sticks in different slots to deduce if it was faulty ram or slots, and resetting the MemOK as recommended here (http://www.overclock.net/t/1182093/dram-led-blinking-on-sabertooth-p67), now the machine will not start at all, period. Dead dead.


Does anyone have a recommendation on what I can do?

Thanks.

Check all of your connection and the seating of all of your memory/gpu/etc., including your ATX12V and graphic card additional power connectors. Put in only a single stick of RAM in slot 1, then see if you can POST. If you can POST, run MEMTEST86.

Having ram in slots 1 and 2 as opposed to 2 and 4 won’t do any harm, you may get minor instability symptoms but nothing drastic like what you're experiencing.

I would check your psu, it just might be the problem. Does the psu fan spin when you turn on the computer?

Hello all,

A final follow up: it was indeed my Power Supply. Lesson learned. By replacing it I haven't encountered the error since.

Thanks to all,
Kris

This topic has been closed by Nikorr