New build, p8p67 deluxe not booting

showb1z

Senior member
Dec 30, 2010
462
53
91
Just assembled a new build and it won't boot.
Asus p8p67 Deluxe, i7 2600k, Corsair hx850, Corsair Vengeance 1600mhz 1.5V C8, POV GTX 570.
When I turn it on the mobo, fans, videocard start working, but nothing else happens. The DRAM led on the mobo is lit and the q-code led says "30". In the manual it says reserved for ASL about this, but it's never mentioned so i don't know if that's anything significant.
When I boot w/o ram the DRAM led is lit and it gives code "22".

I've tried using one stick in all memory banks and clearing cmos. I've taken the mobo out of the case, reseated the cpu and tried only booting with cpu + ram but results are identical.

I'm out of ideas here, any input greatly appreciated.
 

mlc

Senior member
Jan 22, 2005
445
0
0
its a new board..

1) did you try downloading the latest BIOS to see if that get's you past the problem ?

2) are you running with AUTO settings? Someetime you have to go in and manual set the ram voltage and latency setttings.. particularly with Corsair....


In addition.. that board has a jumper to clear the RAM.. . So you may need to power off, pull the cord, etc. .and then flip the jumper over to the other 2 pins for a few seconds, and back.. and then try rebooting
 
Last edited:

Ausm

Lifer
Oct 9, 1999
25,213
14
81
With the machine powered down, hold the MemOK button on the motherboard until it powers up. Wait for a bit and see if it boots. If it does, get into the BIOS and manually verifiy your memory's voltage (DRAM) and the timings. It may power up and down repeatedly a few times
 

00Aron

Junior Member
Jan 18, 2011
9
0
0
With the machine powered down, hold the MemOK button on the motherboard until it powers up. Wait for a bit and see if it boots. If it does, get into the BIOS and manually verifiy your memory's voltage (DRAM) and the timings. It may power up and down repeatedly a few times

This... except that I believe you'll need to turn the computer on first. Even if nothing appears, you can hold the MemOK! button until it starts flashing and then let go. It should restart on it's own. Also, before holding the MemOK! button, check to see if any other red LEDs stay lit during the boot. It indicates a problem in that area.

You could also try a CMOS clearing again (CLRTC jumper swap & battery removal per the manual?) after trying MemOK!
- double check that your RAM DIMMs are fully seated (and everything else for that matter) in the recommended socket (A2 + B2 for the P8P67 Pro... probaby the same on the deluxe... don't know if it really matters, either, but it's what they recommend!)

If you do get a successful boot, BIOS is going to set your memory to 1333mhz by default. I left my 1600mhz g.skill at whatever BIOS set it while installing OS & drivers before making any changes to avoid any crashes during initial set up. Since then I have had my memory set to 1600mhz and BIOS automatically detected the 7-8-7-24 timings. CPU-z reflects the correct timings as well.

Try another set of RAM... if the DRAM LED still stays lit... bad RAM? Either that or bad board.... RMA time either way I guess
 
Last edited:

Mattman90

Junior Member
Jan 21, 2011
1
0
0
I had the exact same issue. I have the g.skill ripjaws 8GB kit installed in my rig. What you need to try is to reseat the RAM sticks. The motherboard does not have two DIMM clips like you are used to with other motherboards. This is the first time I encountered memory slots with only one lockdown clip. Make sure you push all the way down on the unclipped end first then while holding that side down, push the other side of the DIMM down until the clip engages and locks the DIMM in place. If you are able to pull up on the unlocked side of the DIMM then it is installed wrong. It will come out easily if not all the way in the slot.

Before I figured this out, I tried different RAM slots in the MB, different RAM, and it gave the same error "30" code. With the RAM out it would give the "22" like you are getting. I then put the original RAM back in and made sure it was all the way seated in the slots and like magic it booted right up. This is most likely happening to you as well.
 

Tlords

Junior Member
May 11, 2011
1
0
0
Mattman90 you rock... I just found the same problem - seating those memory sticks did the trick!