New PC Build

[Nofrell]

Greetings LTT forum members, 

 

I've recently built a brand new ryzen system and ran into a problem: the pc doesn't boot. When trying to power on the pc, it gets stuck on the VGA led. I've tried connecting an older graphics card but the problem persisted. 

 

Specs:

CPU: Ryzen 5 2600x

Motherboard: Gygabyte AB350-Gaming 3

RAM: Corsair Vengeance LPX 2x8Gb 2400MHz

Graphics Card: MSI Gtx 1070ti Gaming

PSU: EVGA 600W

[KingLuvely]

What do you mean stuck on the vga led? Can you post pic?

[Nofrell]

As far as I'm aware these LEDs indicate in what stage of testing the mobo is in. The LEDs are supposed to flash quickly and the the next one to do the same, yet the VGA led just stays on. 

[ZacoAttaco]

So from the research I've done online, the Ryzen 5 2600x doesn't have integrated graphics. So if the system is trying to use the CPU it's gonna have this error. Maybe double check the GPU is seated correctly and power is in firmly?

 

VGA LED means CPU and RAM are good, so we're just working out issues with the graphics.

[Nofrell]

I have tried reseating the graphics card already but I'll try once more after I get back from work today.

[Nofrell]

Reseating the graphics card didn't seem to do anything and the power connectors are fully in. 

[KingLuvely]

1 hour ago, Nofrell said:

Reseating the graphics card didn't seem to do anything and the power connectors are fully in. 

From what I've seen it is a graphics card not being recognized. Maybe try a different card? Or different PCI slot. Hopefully it isnt a dead slot or power cable.

[Nofrell]

I have tried both a different graphics card and a different pcie slot, didn't help at all. Could it be that the bios on this motherboard do not support the 2600x? And would that cause such a problem? 

[Nofrell]

Update on what I've tried so far:

Changing graphics cards(One with PCIe power connector and one without it) 

Switching PCI slots

Swapping out RAM and their slots(local tech shop recommended to try it) 

 

None of these seemed to help, so I'm guessing it might be BIOS related.