Help.. New system build and it wont stay on for more than 4s before reboot

I just finished building a new system specs:

1) ASRock Z68 EXTREME3 GEN3 ATX LGA1155 DDR3 2PCI-E16 2PCI-E SATA3 USB3.0 SLI CrossFireX Motherboard
2) Intel Core i5-3570 Ivy Bridge 3.4GHz (3.8GHz Turbo Boost) LGA 1155 77W Quad-Core Desktop Processor Intel HD Graphics 2500 BX80637i53570
3) EVGA SuperClocked 01G-P3-1463-KR GeForce GTX 560 (Fermi) 1GB 256-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card
4) Microsoft Windows 7 Home Premium SP1 64-bit - OEM
5) NZXT Source 210 Elite White Steel with painted interior ATX Mid Tower Computer Case w/ Black Front Trim
6) G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-8GBXL
7) Corsair GS700 power supply

Now when I hit power the system powers on and on the motherboard the code window in the bottom right starts to count up and reaches 19 then the system turns off and starts again constantly going thru the same process. Any ideas on what to check while I wait for customer support?


My guess is overheating as otherwise the system would stay on while it had some other issue. The processor heat sink might not be on snug enough.

The computer has never been turned on it is a new build and I am trying to boot up so overheating shouldn't be an issue. heatsink was firmly seated after a re-check.
thanks for response.

Also, pull the memory and then test. If it stays on, put one stick in, then the other.

Check your power cables to both motherboard and vid card. Make sure you have all of them plugged in. It's easy to forget one.

Then make sure your motherboard isn't grounding out on an improperly placed standoff or similar. Although that would probably cause faster issues than your 20 second or so issue.

Well, the manual on your motherboard says this:

0x19 Pre-memory South Bridge initialization is started
0x1A Pre-memory South Bridge initialization (South Bridge module specifi c)
0x1B Pre-memory South Bridge initialization (South Bridge module specifi c)
0x1C Pre-memory South Bridge initialization (South Bridge module specifi c)
0x1D – 0x2A OEM pre-memory initialization codes
0x2B Memory initialization. Serial Presence Detect (SPD) data reading

So it's either failing in the South Bridge init, which is very unusual, or something's wrong with the memory, but the board is crashing before you can see the code. I'd check your RAM sticks very carefully to see if you seated them correctly. And try them in the other slots, if you haven't already. Remember you want one stick per channel, so put them in different colored slots.

edit: Oops, I double checked, and all the slots are black. Put them in staggered, instead -- use the slot closest to the CPU, skip slot 2, and put the other chip in slot 3. If that still doesn't work, try slots 2 and 4. Then try individual sticks in each of the first two slots. If NONE of those combinations work, then it may be a bad motherboard instead.

Oh, also, make sure you haven't shorted out the board against the case. If you get one of the standoff screws wrong, it can be going into naked circuitry, instead of a screw hole, causing all kinds of havoc.

The Ram is staggered and firmly seated in the slots with latches clicking them into place.

I did notice that compatable ram VIA ASROCK is: DDR3 1600 4GB G.Skill F3-12800CL9D-8GBSR2
And I bought: G.SKILL Ripjaws X DDR3 G.SKILL 1600 4GG (PC3 12800) F3-12800CL9D-8GBXL

Close but not the same. I guess the ram it not compatable?

thanks for the response

It doesnt boot past 4seconds with 0, 1, or 2 sticks of ram in any of the positions.

Then I'd check for shorts. Try running the board completely out of the case, and make sure any expansion cards you're using are firmly seated.

Removed the Exp Video card and pulled the board out of case and still get the 4sec reboot. ATX power cord and spu power cord are snug and locked in.. looking for a short but nothing seems out of the normal..

Well, if you've got a spare power supply, you could try that, but otherwise, that sounds like it's probably a dead board. Failing on Southbridge initialization means that a chip on the motherboard isn't doing what the CPU expects it to. The Southbridge is usually what drives most of the lower-speed I/O, like USB ports, and old-style PCI slots, so make sure you don't have anything plugged in but power when you test it, but it's probably a dead board.

When you get the replacement, make super-hyper-mega sure that you've matched the standoffs in the case precisely to the holes in the board. If you miss one, and it shorts out against bare circuitry, it will almost always cause problems, and can potentially wreck the motherboard and anything plugged into it.

Thanks for the helping ideas on the problems that it could have been.

Problem is now solved and turned out to be too old of a BIOS version on the Mobo and it didn't support Ivy Bridge intel CPUs until I borrowed my friends Sandy Bridge CPU which alllowed me to update the BIOS and get the rest of the installation going. Now the time consuming task of updating Win7 and installing the nessesary video games.

Pic of New Build

Ohhhh, we've got that old problem back again, eh? Oh Christ, I thought they'd fixed that crap long ago. What the heck are they thinking, shipping Sandy-only BIOSes in freaking August of 2012?

Glad you figured it out, and thanks for letting us know what it actually was.

Man, how the heck are we going to differentiate this issue from a dead motherboard, if we see it again?

edit to add: Out of interest, did you buy that motherboard retail?

I bought the mobo from the US website version.

I found the solution combing thru help section. Just sucks that I had to have access to a Sandy Bridge cpu, cause if I didn't I would have been stuck waiting on an RMA or purchasing a new mobo.

Aside from the BIOS issue I was pleasantly surprised at the ease of the build compared to last time I built a computer well over 10 years ago.