Compuer powers on but fails to boot...

Associate
Joined
8 Mar 2012
Posts
18
Hi all,

Hoping someone might be able to help.

My PC is about 3 years old and has worked fine the whole time I've had it apart from a failed HDD and DVD drive a year or so back. A few weeks back my PC was switched on sitting on the desktop with nothing running. The PC would not respond at all when I came back to use it, the screen was just frozen. I turned the PC off and switched it back on and ever since it has failed to boot up.

Everything seems to power up, the fans spin (including the graphics card fan), the DVD drive spins etc etc but the PC doesn't get to the point of the motherboard POST.

I've tried to disconnect everything apart from the power supply and CPU/CPU fan. It will not boot. I've tried replacing the CMOS battery as well as leaving the battery out for a few hours to see if that clears any errors.

Tried different combinations of moving the RAM to different slots.

I've tried using another PSU from another computer but that made no difference.


System specs are:


AMD Vishera FX-8 Core 8350 4.0Ghz (4.2Ghz Turbo)

GIGABYTE 970A-DS3P

16GB DDR3 1600Mhz - CRUCIAL Ballistix (2 X 8gb)

240GB CRUCIAL BX200 SATA3 - 6Gb/s 1

1TB Samsung SSD

SAMSUNG 24X DVD+/-RW Dual Layer & Dual Format

nVIDIA GeForce GTX 960 4GB PCI-E 3.0 Ready

500W PSU

WINDOWS 7 Home - 64Bit

Wireless Networking LAN N - 150Mbps

INTERNAL 80IN1 3.5'' Media Card Reader


I've already replaced the motherboard believing that was the issue but now I'm thinking it might be the CPU and debating whether it is worth the expense of trying to replace more parts of the system or just buy a new computer.

Can anyone suggest anything else that may be the cause of this?
 
You need graphics card for it to power into BIOS.

If PSU is as "modern" as CPU that could be some designed to fail junk.
CPU itself is rather reliable part and without some external cause should either fail fast, or then last very long time.
Though also that motherboard model was complete Cheapo and that power hogging CPU could have burned out its VRM, whose failure then killed CPU.
 
Back
Top Bottom