New PC Restarting cant get even to bios

[Punny1g]

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.

 

[corroded]

RMA

 

[Punny1g]

RMA

Any specific component or all?

 

[corroded]

If it was purchased as a built system. The whole thing. not worth hassling.

 

[Punny1g]

If it was purchased as a built system. The whole thing. not worth hassling.

It wasn't purschased as a built system.

 

[corroded]

it does seem like the MoBo.

 

[Punny1g]

it does seem like the MoBo.

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]

MERGED QUESTION
Question from Punny1g : "PC keeps restarting with HyperX Savage"

Yesterday my friend finished building his PC and when we turned it on it wont even get to bios with HyperX Savage DDR4 2133MHz 2x4GB. When I gave him my HyperX Fury 2133MHz DDR4 2x4GB the PC is starting normally. Also when i plugged HyperX Savage in my build it is also restarting all the time and wont get to bios.
Do you have any tips or suggestion or should we RMA the memory?

If you are interested in full build here are the list of his components:
-Gigabyte GA-Z170-HD3P
-Intel i5-6600K
-Cooler Master EVO 212
-Seasonic M12 II 520w
-WD Blue 1TB
-Gigabyte R9 270X 4GB

That memory won't work this one here should though:
http://www.newegg.com/Product/Product.aspx?Item=N82E16820104673

http://www.gigabyte.com/products/product-page.aspx?pid=5495#
Check the memory support list for more details.

the timing is different
Savage Timings: 2133MHz, 13-13-13, 1.2V
Fury Timings: 2133MHz, 14-14-14, 1.2V

 

[maikutech]

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.

 

[rgd1101]

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.

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

 

[maikutech]

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.

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]

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.

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.

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