GA-H170M-D3H DDR3. 5 Long Beeps then rebooting

[KostasNs]

Good Evening to everyone

My client brought me a new desktop system which consists of:

MOBO: GA-H170M-D3H DDR3
CPU: INTEL CORE I7-6700K 4.00GHZ LGA1151
RAM: HYPERX HX316LC10FBK2/16 (2x8GB) - 16GB DDR3L 1600MHz
PSU: COOLERMASTER G750M 750W

The RAM kit is set on 1-2 module position.

When I turn it on, MOBO sends 5 Long beeps and reboots again and again.

I noticed from Gigabyte specs that the 5-long beeps mean a CPU error, so I reseated it and checked for bend pins but the socket and the CPU is OK.

I tried also to reposition RAM modules from 1-2 and placed on 3-4 position. No result.

I also notice that this processor and RAM sticks are supported by MOBO and processor supports this type of RAM, according to motherboard support list and specifications.

Anyone with a similar issue? Any help and ideas might help.

Thank you in advance.

[ElectroStingz]

Hello,

Just to make sure, do you have the 8 pin +12v power connector plugged into the board?

What CPU cooler are you using?
Sometimes the bracket on after market ones can cause issues.

And have you tried using just one memory stick / both on their own?

What happens if you try the board with no memory installed, does the error code / beep change?

[KostasNs]

Hello,

The CPU has a "COOLERMASTER SEIDON 120V V3 PLUS" water cooling system attached on it. After all, it is connected properly on CPU.

The 8-pin CPU connector is plugged on the board correctly.

I have tried to use one memory stick (8GB) in every slot, but there was no result. The beep keeps on.
And finally, when I removed all memory sticks from the board, and turned it on the same thing happened: Five long beeps and restart.

[ElectroStingz]

You will need to get your CPU tested or try another one in your board.
The beep code should change when you have no ram installed.

[KostasNs]

Good Evening,

After a long test with memory, I have just realized that a couple of pins in motherboard are bent in terrible position, from the first time. They can not be fixed, so the problem is on the motherboard, whereas CPU is OK. That was an oversight on my part!

Thank you for your advice!