New build won't post

[goaway]

So my friend just finished his build, but when we turn the system on nothing comes up on our monitor. He's currently using the integrated graphics chip, since his GPU hasn't arrived yet. First off, we connected the VGA output on his motherboard to his moms monitor, but we did not get anything up on the screen. The fans of our NZXT coller aswell as pump started up(they are connected to the waterpump itself, wich is connected directly to the psu), but his other systemfans wich are connected to his motherboard did not move(I just assumed it had something to do with pwm/dc compatibility and that we just had to change som settings in bios.

 

Since we did not get any signal on the monitor, we switched to his TV, and also changed the video output to the HDMI port. We got the same problems again. We have currently tried to reseat the prossessor, but nothing changed. We also noticed that none of the error leds on the motherboard lighted up(that being vga,cpu, bott device and ram error leds) though the power led is lit.

 

At this point I would assume one of the parts is DOA, but I'm not sure witch. Hoping I'm wrong but just asking for your opinions. His system specs are as following:

Intel i5 6600k 

Asus z170-A motherboard

Kingston hyper-x fury 2x8 2400mhz ram

Evga 650 GQ psu

nzxt kraken x61

Samsung 850 evo + WD black 1tb

 

[GDRRiley]

just trie 1 stick of ram the mobo, PSU and CPU and see if you can get it to post if it doesn't start moving the ram to different spots and try the other stick.

[burnttoastnice]

My build personally took a very long time to post when it was powered on the first time - after that it took just seconds.

 

Try resetting the CMOS and see if that helps.

[Bananasplit_00]

look up what the error light means in the manual for the motherboard and then try what @GDRRiley said

[goaway]

15 minutes ago, GDRRiley said:

just trie 1 stick of ram the mobo, PSU and CPU and see if you can get it to post if it doesn't start moving the ram to different spots and try the other stick.

Sadly did not work

14 minutes ago, burnttoastnice said:

My build personally took a very long time to post when it was powered on the first time - after that it took just seconds.

 

Try resetting the CMOS and see if that helps.

Alredy did, and didn't work

11 minutes ago, Bananasplit_00 said:

look up what the error light means in the manual for the motherboard and then try what @GDRRiley said

wasn't an error light, just the power led

[Bananasplit_00]

2 minutes ago, larsi239 said:

Sadly did not work

Alredy did, and didn't work

wasn't an error light, just the power led

oh ok then, how long have you waited for a POST?

[goaway]

1 minute ago, Bananasplit_00 said:

oh ok then, how long have you waited for a POST?

5min probably

[Bananasplit_00]

1 minute ago, larsi239 said:

5min probably

ok that should be well enough time for it to POST, i have never needed to wait more then 2mins or so...  i would wait for the GPU before starting to blame parts but im thinking its CPU right now

[StainlessSR]

Just want to verify, you have the 8 pin cpu connector on also.

if it still will not post

remove the cpu and check for bent pins on the socket

Spoiler

 

[goaway]

4 minutes ago, StainlessSR said:

Just want to verify, you have the 8 pin cpu connector on also.

if it still will not post

remove the cpu and check for bent pins on the socket

  Reveal hidden contents

 

Already checked all cable connections, and reseated the cpu (aswell as looking for bent pins)

[StainlessSR]

If the psu is new, try a known good one in the new build (You got a good model but there can be mistakes in manufacturing)

 

do you have a known good mb that is compatible?

 

if so try the suspect cpu in the known good. (I would advise this route rather than a known good cpu in a suspect mb, I have heard of a mb killing a cpu but not a cpu killing a mb)

 

if not then just rma both and wait.

[goaway]

8 minutes ago, StainlessSR said:

If the psu is new, try a known good one in the new build (You got a good model but there can be mistakes in manufacturing)

 

do you have a known good mb that is compatible?

 

if so try the suspect cpu in the known good. (I would advise this route rather than a known good cpu in a suspect mb, I have heard of a mb killing a cpu but not a cpu killing a mb)

 

if not then just rma both and wait.

Well,  we'll have to wait till tomorrow then...