Newly Built Computer with Gigabyte Motherboard starts for about 20 seconds then restarts endlessly

CaptainKNT

Reputable
Nov 27, 2015
3
0
4,510
Hello, I recently built my new computer but, upon trying to boot it up, it just runs for a short time then shuts off and turns on again without displaying any thing or giving any indication of an error on the monitor. I suspect that its the motherboard (Gigabyte GA-z170-HD3P) since I've read that this mobo has RAM compatibility issues. However, even after switching around my 2 Crucial Ballistix Sport 8gb DDR4 2400s in the various slots none of them work. I'm 95% certain that the PSU (EVGA 650 SuperNova NEX 650W 80+ Gold) is not the issue since I tested the mobo with another PSU. I am very afraid that I got a faulty motherboard or damaged it during installation or maybe even my CPU (Intel i5 6600k 3.5GHz Quad Core) is faulty or damaged.
Any help or suggestions at all would be greatly appreciated as I have no idea what to do at this point. If you need me to post my whole build let me know.
 

LuisL

Reputable
Nov 27, 2015
4
0
4,510
I have the same mobo and RAM, GB Nvidia GTX 970, i5 6400, XFX XRT 850w. And the same issue. I've pulled out the mobo from the case, pulled the RAM, GPU, fan, case headers etc. Only PSU connectors (this PSU brought two CPU cables, a 12v 8 pin and a 12v 2x4 pin. I've test them both) and HDMI from onboard GPU to my TV and still persist the issue (20 secs of no post). I don't have a mobo speaker and this mobo doesn't brought one.

I don't think is the PSU. I've looked the CPU pins and they are fine as well as the mobo CPU pins.

Have you found a solution yet?
 

CaptainKNT

Reputable
Nov 27, 2015
3
0
4,510


This motherboard does not have a start switch so I'm not sure what you are referring too.
 

Push button, Start switch on the case of course. It's connected to Pwr_sw on MB F_Panel.

 

CaptainKNT

Reputable
Nov 27, 2015
3
0
4,510

looks like I found the problem; one of the pins on the motherboard CPU link is bent. I'm not sure if bending one means the end because that's extremely stupid and I'm pretty sure that I was not the one that bent it. Either way, im just going to get a new motherboard and refund this one. Thank you for your help.
 

LuisL

Reputable
Nov 27, 2015
4
0
4,510
Good to know you found what was wrong. Too bad you need to replace the mobo.

I still don't know what is wrong with mine. Mi mobo'a CPU pins look ok to me. I am turning on the mobo with a screwdriver so is not a stock start button.
 

LuisL

Reputable
Nov 27, 2015
4
0
4,510
After a long study of what component could be the cause, I've conclude that the RAM is not supported by the motherboard. I have a Crucial Ballistix Sport bls8g4d240fsa.16fadg and in the list of supported ram there is a bls8g4d240fsa without .16fadg so it might not be the same.

As I don't have a mobo speaker or display to see error code, I've counted how many seconds take before restart. This is what I've got so far:

- CPU = 20 secs
- CPU + 1 ram stick = 26 secs
- CPU + 2 ram sticks = 30 secs
- CPU + 2 ram sticks + CPU fan = 30 secs
- CPU + 2 ram sticks + CPU fan + SSD = 30 secs

In conclusion the system restart when checking the ram info (I'm guessing)

Tomorrow I'll buy supported ram to see if I am right or not.
 

unixbrain

Reputable
Nov 30, 2015
3
0
4,510


Any update on this? I built a new computer just a couple days ago - exact same RAM, with an ASRock z170 Extreme6. Their site lists support for bls8g4d240fsa, but not the .16fadg variant. System will boot with either stick in single-channel mode, but refuses to do anything but boot-loop when both are present.

I was terrified I got a bad board or a bad processor, but now I'm starting to think it might be this RAM?
 

LuisL

Reputable
Nov 27, 2015
4
0
4,510
Oh I forgot to reply after I successfully made my pc work. I ended up buying two G.Skill Ripjaw memory sticks that are shown in the RAM support list of my mobo. Mine is a z170n mITX no the X series.

That's weird that with only one mem stick your system works, maybe you need to update your bios to support dual channel? Check your mobo's bios versions in asrock website.

These Crucial mem sticks are very odd. Didn't find a lot of other websites that recognize this model.
 

gk9

Reputable
Dec 1, 2015
3
0
4,510


Looks like I'll be trying to switch to a different type of RAM as well. I too have the .16FADG variant and I tried it on the Gigabyte z170x-ud3 and then drove an hour and a half back to Microcenter and exchanged for the Gigabyte z170x-gaming 5 after I had convinced myself that the mobo was bad. If anyone else has this issue please chime in, as I don't want to make another 3 hour round trip to microcenter if it isn't the RAM. Thanks.
 

unixbrain

Reputable
Nov 30, 2015
3
0
4,510


I am in the same situation! Purchased from Microcenter - I really, really don't want to drive down there again, replace one or the other, and then turn out to be wrong.

I got in touch with Crucial support and they informed me that the .16FADG at the end of the product number is simply a batch number and that it should not affect the memory's compatibility. They didn't have many suggestions other than trying the sticks individually and updating the BIOS.

ASRock support (I know this is a Gigabyte thread) suggested updating the BIOS to their latest beta release - I was unaware there was a beta, so I will try that tonight. If it doesn't work, they suggested that I should exchange both the RAM and the motherboard. That's one way of solving it, I guess.

Is this just a thread of people who got unlucky with a particular batch of Crucial RAM, maybe? I've been phoning around to find some other DDR4 to see if it will work in this board, but nobody I know (including local stores) has any...
 

gk9

Reputable
Dec 1, 2015
3
0
4,510


You didn't happen to buy it from the Boston/Cambridge Microcenter, did you?

Interesting about the batch number. I noticed that on the list of compatible memory for my mobo, they had the bls8g4d240fsa listed as 16-16-16-40 timings, whereas my bls8g4d240fsa.16fadg sticks say 16-16-16-39 on them. Not sure if the list was wrong, but I couldn't find any spec sheets saying what it was supposed to be.

As for updating the BIOS, my computer won't even show anything on the monitor. It just loops over and over giving error code 55 (memory initialization error) on the motherboard display. Does yours display anything?

I did search around 4 different stores today to see if I could find anything, but I decided to buy some Corsair RAM off Amazon and return the Crucial ones for a refund.
 

unixbrain

Reputable
Nov 30, 2015
3
0
4,510


Twin Cities/St. Louis Park. I also ended up just buying some Corsair RAM off of Amazon - figured it would be easier to return the Crucial for a refund this weekend, and only replace the motherboard if it doesn't work either.

My system *was* occasionally hanging on error code 55, but only if I was changing settings around -- more often than not it would go through its sequence and (in the same order every time) pause on 32, then flash past 35, 39, and then jump back to 00. At that point, the fans would all spin up like the system was just powered on, and then it would do that same thing over and over until I shut the power supply off.

With the latest beta bios from ASRock, I was able to get them working - but only at 2133 MHZ with relaxed timings.

I just got my Corsair Vengeance in the mail and despite not being on the compatibility list, the system works just fine with it. Strangely enough - - just to see, I installed the Crucial sticks alongside the new Corsair ones, and they also work just fine this way. They refuse to boot on their own, but have no problem whatsoever running at their standard speed/timing with the other memory in the system. This is true whether they are in slots A1/A2 or B1/B2.

I can't even begin to figure out why this is, and I don't even care at this point. I'm returning this strange, confusing memory tomorrow.
 

gk9

Reputable
Dec 1, 2015
3
0
4,510


I just received my new RAM in the mail. It is also Corsair Vengeance. I popped it in and it fired right up. I'll be returning the funky Crucial memory this weekend. So glad that I've sorted this out.