Custom built PC turns LEDs on twice and proceeds to turn off

Dan_29

Reputable
Jan 6, 2016
1
0
4,510
All my parts arrived yesterday and I proceeded to build my pc. Everything went fine until I noticed some pins were bent on my CPU. As soon as I noticed them I grabbed a pair of tweezers and a plastic card and straightened them up.

I tried to boot up my machine and everything seemed fine for less than a second. It didn't turn on, at all; the fans spun for a second and the LEDs turned on but nothing happened afterwards.

I tested without some components such as:

  • Testing out my power supply by powering the fans directly, it worked
    Tried powering only the GPU, it didn't work at all, the same thing happened
    Tried without some hardware such as without ram, it was the same deal as before

When I removed the CPU and tried turning my computer on without it everything lit up, fans started blowing and everything seemed ok.

My questions is, what could be going wrong?!

CPU: AMD Fx8320
Motherboard: gigabyte a970-ds3p
GPU: Nvidia GTX 970
PSU: EVGA 80PLUS 600w
RAM: Kingston HyperX Fury 8gb
Case: SPEC-02 Corsair

I'm currently searching for someone who's able to test if my CPU is faulty, I'm afraid I might have broken or burnt something when I straightened the pins.

Any help would be greatly appreciated, this is the first computer I've ever built.
 
Solution
you said you tested without some component. did you took off the cooler and tried then? if yes: probably your CPU is burned. if not. just adk the company for a trade. i think they can return yours and send you a new one.
some motherboard are secured that they can't start when the CPU isn't in good state. so that would explain the problem.

Mike

Mkarmelk

Reputable
Sep 13, 2015
55
0
4,660
you said you tested without some component. did you took off the cooler and tried then? if yes: probably your CPU is burned. if not. just adk the company for a trade. i think they can return yours and send you a new one.
some motherboard are secured that they can't start when the CPU isn't in good state. so that would explain the problem.

Mike
 
Solution