PC wont boot (no beep) - red LED

Oct 4, 2018
3
0
10
Hi, after almost 3 years I decided to fix the problem I had with the dual channel function of my mainboard (it was simply not working - DRAM debug LED was shining and CPU-LED was flashing). In order to do that I disconnected every device which is not necessary for my PC to boot (CPU without cooler, 1x4GB RAM and PSU are built in right now). Since I tried to run my PC on this minimal-setup the red ez-debug CPU-LED is shining and I dont get an image on my screen. The MOBO-speaker is also quiet. Everything was working fine till I decided to fix the dual channel problem. Now its not even working without dual channel RAM configuration.

Setup - current status:
---------------------------------------------------------------------------------------------
MOBO: MSI Z170A Gaming Pro - built in
CPU: Intel i5 6600k - built in
CPU-cooler: Alpenföhn Brocken Eco - not built in
RAM: Corsair Vengeance LPX DDR4 2800MHz 2x4GB - 1x4GB built in
GPU: Nvidia GTX 1070 - not build in
PSU: be quiet! Pure Power L8 630W - built in
other PCIe/USB/SATA devices: - not built in/disconnected
--------------------------------------------------------------------------------------------

Things i tried so far to fix this problem:
-) exchanging the CMOS battery
-) removing the CMOS battery for couple of hours
-) re-inserting the CPU and looking for bent PINs on the MOBO
-) disconnecting every device which is not necessary for my PC to boot
-) inserting both RAM modules on every DIMM slot
-) checking and re-inserting every cable
-) booting without RAM - no beep sounds, same LED (CPU)
-) booting without CPU and RAM - no beep sounds, same LED (CPU)

Nothing worked - please help me 🙁
 
From your troubleshooting it looks like you've narrowed it down to two things. It's either a bad CPU or a bad motherboard. Since motherboards die more often than CPU's, I would suggest trying a new motherboard to see if that fixes the problem.

It looks like you've tried everything you can. If the new motherboard fails then it is certainly the CPU.
 


Okay I'll try that. Thank you for your fast answer.