Just finished a build - computer restarts in a loop

[Aristotelian]

Hi.

So I just finished my build.

I press the power button, the fans start spinning, and after a few seconds the computer powers down by itself and restarts. Nothing is displayed on my screen. I don't hear any error beeps either.

Build:
HAF-X
2600K
NH-D14
Gigabyte p67 ud7
2x C300 256gb
2x EVGA 580 superclocked
Seasonic x850
2x4GB Patriot Extreme DDR3
U2711 monitor

I took my time to carefully plug in all the power plugs and so on, and am at a loss here.

Edit: I opened the case and on the motherboard "C 1" shows in red on the bottom right corner - if this helps. All the fans are spinning for sure, and the NH-D14 is quite tightly screwed on there with about..half a pea of paste on there.

 

[gorcorps]

Are all the fans for certain spining? I had a PC do this when the CPU overheated. Make sure the fan's plugged in, the HSF is seated correctly with the right abount of thermal paste.

 

[Krynj]

Try the RAM sticks one at a time in the first DIMM, which will either be the first or second slot from the left. You have to look at the board.

Can you get into BIOS? Is the CPU overclocked? What do you have for a power supply?

 

[Aristotelian]

Try the RAM sticks one at a time in the first DIMM, which will either be the first or second slot from the left. You have to look at the board.

Can you get into BIOS? Is the CPU overclocked? What do you have for a power supply?

Power supply is listed - Seasonic X850. I just tried it with one card, and the problem persists. The ram is under the heatsink/fan, so it'll take me a bit to test the RAM - will do that now and update.

Oh, this is the first boot - I can't get into bios, cpu is therefore not overclocked.

 

[gorcorps]

Are BIOS/CMOS setting still reset by moving the little jumper thing to the "reset" position? If so, the jumper may be on reset for some reason and you need to move it.

I don't have a modern motherboard so I dont' know if it's still done this way.

 

[Aristotelian]

I tried both ram sticks in slot 1, the issue persisted. There is no cmos reset switch 'position', it's a button on this board that you press any time you want to do it. There are no error beeps.

I took out both gpus and tried either as well in the first pci e slot, and nothing. I reseated the heatsink, it's still not working. By the way, the fins on the nh-d14 are both sharp and delicate, heh. I must be the first person to cut himself in a case as big as the haf-x.

 

[Patrick Wolf]

Did you build a boot outside of the case first?

 

[BTRY B 529th FA BN]

Are the ram sticks tightly installed?

If so, your volts might not be right somewhere

 

[mfenn]

It's God telling you that you spent way too much money on that thing.

Seriously though, it sounds like your mobo has a POST code LCD by your description (it's the thing showing C1). Your manual should have a list of what the codes mean.

EDIT: The POST code table starts on page 117 of the English manual. C1 means "Detect memory", so it sounds like you've got a problem with your memory config. Most likely, they're just installed wrong, but DOA is always a possibility.

 

[Aristotelian]

Is it even possible to install memory incorrectly? Regarding the volts - everything is stock, I haven't changed anything as it doesn't even reach the bios. I don't normally build a boot outside of the case, as this is the first time (ever!) that a pc I've built has had a problem like this. It has been one of those weeks, to be frank, so this isn't surprising. Thanks for your help guys.

Also thanks for doing what I should have done already myself, mfenn. I was just burned out at the time of posting. I'll exchange the memory.

 

[BoomerD]

The best way (but not the fastest) is the "build & boot" method. Start with only CPU, cooler & fan, ONE stick of RAM, and your video card. See if you can boot to BIOS.

If so, add your boot drive...try again.
If the drive is recognized in BIOS, add more RAM, (2nd stick in appropriate slot for dual channel)
Try again.

As long as you can keep booting to the BIOS, keep adding your hardware.
IF you get everything loaded and can still get into the BIOS, load to windows.

Make sure you double check and triple check all connections from the PSU and to the various components.


Personally, I'd start with the motherboard OUTSIDE the case and sitting on cardboard or some other non-conductive surface, just to eliminate the possibility of ground issues with the board/case.

 

[Aristotelian]

This is so odd. I tried it the way described above (with the motherboard out of the case).

I have one stick in slot one, cpu/heatsink/fan, and one graphics card in the motherboard. It posted. Time to isolate the issue...

 

[mnewsham]

Could have been a standoff in the case.

 

[Krynj]

Could have been a standoff in the case.

That's what I was thinking.

 

[BoomerD]

Could have been a standoff in the case.

Which is exactly why it's best to start any new build in such a way...

OP, double check each stand-off to be sure it's in the correct place and that there are no extras in the case.

I know several people who use "paper washers" in between the stand-offs and case to eliminate any possible grounding issue. I never have...and have never had a problem.
It's also quite possible that one stick of RAM wasn't seated properly...

 

[mfenn]

I know several people who use "paper washers" in between the stand-offs and case to eliminate any possible grounding issue. I never have...and have never had a problem.

That's actually a terrible idea. If you look at your motherboard, you'll notice that there are solder pads around some of the standoffs. Those are for grounding. While the mobo should be grounded by the PSU, a little extra insurance never hurt.

It's also quite possible that one stick of RAM wasn't seated properly...

That's what I'm thinking.

 

[Aristotelian]

I installed and reinstalled the RAM repeatedly, so it wasn't that. With the way the sticks lock in I'm not sure how RAM could be seated improperly.

It turns out that I had placed an extra standoff where I thought it was needed, and that was apparently causing the issue. This'll teach me to pay a bit more attention. Thanks for your help guys. :thumbsup:

 

[BTRY B 529th FA BN]

It turns out that I had placed an extra standoff where I thought it was needed, and that was apparently causing the issue. This'll teach me to pay a bit more attention. Thanks for your help guys. :thumbsup:

That would of never occurred to me. I always check the placement of the standoffs atleast two or three times before I install the board.

Good to hear you solved the problem

 

[BoomerD]

I installed and reinstalled the RAM repeatedly, so it wasn't that. With the way the sticks lock in I'm not sure how RAM could be seated improperly.

It turns out that I had placed an extra standoff where I thought it was needed, and that was apparently causing the issue. This'll teach me to pay a bit more attention. Thanks for your help guys. :thumbsup:

:thumbsup:

 

[Patrick Wolf]

I wonder if that can damage the board. Should probably test it with Prime and OCCT to make sure it's still solid.

 

[mfenn]

I installed and reinstalled the RAM repeatedly, so it wasn't that. With the way the sticks lock in I'm not sure how RAM could be seated improperly.

It turns out that I had placed an extra standoff where I thought it was needed, and that was apparently causing the issue. This'll teach me to pay a bit more attention. Thanks for your help guys. :thumbsup:

You're welcome! Glad you got it working.

As for how RAM could be seated improperly, you'd be surprised. I remember a thread where it took something like 3 pages to figure out that the guy wasn't pressing down hard enough to seat the memory.