New PC Restarting cant get even to bios

Punny1g

Reputable
Dec 30, 2015
21
0
4,510
So my friend bought a new PC and when we put it together and turn it on PC is restarting every 15-20s it doesn't even get to the bios screen.
PC Components are:
-Gigabyte GA-Z170-HD3P
-Intel i5-6600K
-Cooler Master EVO 212
-Kingston HyperX Savage 2133MHz DDR4 2x4GB
-Seasonic M12-520w
-WD Blue 1TB
-Gigabyte R9 270X

So far we have tried next:
-Resitting RAM, started it with 1 ram, started it without any ram
-Removed CMOS Battery for few minutes and put it back
-Removed Graphic Card, tried on integrated graphic, tried without any graphic card
-Other HDD
-Replugged all cables but mobo power cable and connected them back

One more thing when i tried to turn pc without PSU to CPU cable it was restarting even faster like 3-5s.

Sorry for my bad english, hope you guys can help us.
 
Solution
Could you please unmerge the topics, no disrespect to you, but this is a bad mess.
Two people having different problems in one thread doesn't make sense especially with info getting mixed up.
Also I know the timing is different but check with the gigabyte memory support list.
Thats what they said will work out, the savage won't though, he could call gigabyte tomorrow to trouble shoot it.

Punny1g

Reputable
Dec 30, 2015
21
0
4,510


We tried mine HyperX Fury 2133MHz DDR4 2x4GB, and the PC is starting normally. Also i tried putting his HyperX Savage in my PC and then my PC was restarting all the time. Should we RMA the memory?
 

rgd1101

Don't
Moderator
MERGED QUESTION
Question from Punny1g : "PC keeps restarting with HyperX Savage"





the timing is different
Savage Timings: 2133MHz, 13-13-13, 1.2V
Fury Timings: 2133MHz, 14-14-14, 1.2V
 
Could you please unmerge the topics, no disrespect to you, but this is a bad mess.
Two people having different problems in one thread doesn't make sense especially with info getting mixed up.
Also I know the timing is different but check with the gigabyte memory support list.
Thats what they said will work out, the savage won't though, he could call gigabyte tomorrow to trouble shoot it.
 
Solution

rgd1101

Don't
Moderator


It the same person. problem with HyperX Savage yesterday, and now the OP try with a HyperX Fury and that works.
 


None the less its still a bad idea, I would rather troubleshoot 2 different issues and seperate topics.
It goes by more smoothly in the long haul but I appreciate you trying to help the op.
 

rgd1101

Don't
Moderator


it the same issue, the op just start a new one because he find out HyperX Fury works.