Good morning,
I've been gathering parts to build my PC, and finally yesterday got the last missing part to be able to give it a go, the cpu. When the decisive moment came, instead of turning on, disappointment, got a constant repetitive power on, poweroff. Read a lot of the guides here (sticky included) and always got the boot loop. The fans go on and off and yet no lights on the motherboard.
My equipment list is the following
CASE: Bitfenix Neos Window
MB: Gigabyte Z170X Gaming 3
CPU: Intel i5 6600k
CPU cooler: Cooler Master Hyper T4
RAM: DDR4 Corsair Vengeance 3000Mhz, 2x8, (CMK16GX4M2B3000C15)
HDD: 250 GB SDD and 500 GB HD
GPU: No GPU yet, will work for now with integrated graphics.
PSU: EVGA Supernova NEX750B
Thermal Paste: Arctic Silver 5
Procedures: First I started to build the system, put it in the case, thinking all would be ok.
After first failure read the comments, assured all cables were plugged correctly, no success, fans spin for a second, hardrives sound like starting and one second and all shuts down.
Disassembled MB, to check if stands were positioned correctly, they were, no way of shorting there.
Removed the cpu cooler to check if there were thermal paste leaks, none.
Removed cpu to see if there were any bent pins, none.
Assembled again, no success.
Removed RAM and place it again, no success.
Tried with only one RAM stick in position 1, furthest from cpu, no success.
Tried with the other RAM stick, no success.
Tried without the reset MB pin connection, no success.
Tried jumping the CMOS reset for 10 seconds, no success.
Removed MB from case again, place it over the cardboard case with only power in the MB 24pin and the cpu 8pin connected, only RAM and CPU (with cooler) installed turned on carefully using a screw driver to connect the power, the same, boot loop.
Fortunately I have another PSU stored, a Thermaltake TR2 450, used it to see if it was PSUs fault, nope, same boot loop on the basic card board assembly.
I'm running out of ideas here, anyone think of another possible cause/solution for this. Is it a damaged MB?
Thanks for any help suggestion, more than welcome!
I've been gathering parts to build my PC, and finally yesterday got the last missing part to be able to give it a go, the cpu. When the decisive moment came, instead of turning on, disappointment, got a constant repetitive power on, poweroff. Read a lot of the guides here (sticky included) and always got the boot loop. The fans go on and off and yet no lights on the motherboard.
My equipment list is the following
CASE: Bitfenix Neos Window
MB: Gigabyte Z170X Gaming 3
CPU: Intel i5 6600k
CPU cooler: Cooler Master Hyper T4
RAM: DDR4 Corsair Vengeance 3000Mhz, 2x8, (CMK16GX4M2B3000C15)
HDD: 250 GB SDD and 500 GB HD
GPU: No GPU yet, will work for now with integrated graphics.
PSU: EVGA Supernova NEX750B
Thermal Paste: Arctic Silver 5
Procedures: First I started to build the system, put it in the case, thinking all would be ok.
After first failure read the comments, assured all cables were plugged correctly, no success, fans spin for a second, hardrives sound like starting and one second and all shuts down.
Disassembled MB, to check if stands were positioned correctly, they were, no way of shorting there.
Removed the cpu cooler to check if there were thermal paste leaks, none.
Removed cpu to see if there were any bent pins, none.
Assembled again, no success.
Removed RAM and place it again, no success.
Tried with only one RAM stick in position 1, furthest from cpu, no success.
Tried with the other RAM stick, no success.
Tried without the reset MB pin connection, no success.
Tried jumping the CMOS reset for 10 seconds, no success.
Removed MB from case again, place it over the cardboard case with only power in the MB 24pin and the cpu 8pin connected, only RAM and CPU (with cooler) installed turned on carefully using a screw driver to connect the power, the same, boot loop.
Fortunately I have another PSU stored, a Thermaltake TR2 450, used it to see if it was PSUs fault, nope, same boot loop on the basic card board assembly.
I'm running out of ideas here, anyone think of another possible cause/solution for this. Is it a damaged MB?
Thanks for any help suggestion, more than welcome!
Facebook
Twitter
Instagram