MSI motherboard error b2 - No signal on monitor

[Goldensyrup92]

New build!
MSI z170a m7 mother board
MSI gtx970 gpu
Intel i5
Just finished building a new set up. When I power on, monitor says no signal.
Mother board is displaying error code b2 and there is a little LED lit up in the bottom right with the letters HW underneath it.
I have tried putting the hdmi cable into the motherboard socket and I have tried all pci-e ports.
I have also tried removing the CMOS battery for 5 mins but no luck.
Any ideas?

 

[alexoiu]

Try re-seating the CPU and taking a picture of the CPU socket. Post the picture here.

 

[Goldensyrup92]

Try re-seating the CPU and taking a picture of the CPU socket. Post the picture here.

Tried that but no luck
Can't post picture right now but socket is a LGA 1151

 

[alexoiu]

When possible, try posting the picture, just to make sure that there are no bent pins.

 

[Goldensyrup92]

well I've found the problem! i will try to explain...
I am building a wall mounted gaming pc and i have the GPU mounted underneath the motherboard. I bought 2 x PCIE 16x Extender ribbon ( 25cm each, can't seem to get longer than this...) cables off ebay so that i could join them together and create a 50cm cable to reach the GPU.
However! when I turned the pc on for the first time it said "no signal" on the screen, so i unplugged the GPU and plugged the HDMI into the motherboard and it worked.
Then I tried the GPU directly in the mother board and it worked!
So obviously an issue with the ribbon cable... Plugged one of the cables into the mother board and the GPU and it worked! so i tried the other ribbon cable and that worked!! WTF!

Conclusion: Two ribbon cables in a row don't work. Why not?! Too much voltage drop or interference maybe?

Anyone got an idea how to get around this problem? Ribbon cable needs to be a minimum of 35cm

 

[alexoiu]

From your original post:
"I have tried putting the hdmi cable into the motherboard socket and I have tried all pci-e ports. "
That's why it's good to provide as many details as possible when explaining the issue. Your last post sounds so much different than the original one.
I suggest opening a new thread.