Jump to content

My build is :

Asus Crosshair VI hero wifi-ac

32GB G-Skill trident z ram 3200mhz

Nvidia gtx 1070

Amd Ryzen 7 1800x

Samsung 960 EVO SSD

Corsair H200I water cooler

4 Cooler master RGB case fans

4TB WD Black hard drive

Corsair HX 1000W PSU

NZXT S340 Elite case

 

Now for background info, I built this PC a few years ago and It worked fine for those years once it was built, Then I moved to Germany and upon moving there I had to fix my PC as it again would not boot I quickly ran down the issues and decided to get a new board (My old board was also a Crosshair VI hero but no wifi-ac). It was working fine for about 2 months but then  Yesterday I was playing some dauntless and my audio started glitching and I Was getting crazy lag spikes, (This was happening as the software for the wifi adapter was updating and during that you can't turn off or restart PC unless you cancel it) When these glitches were happening I decided to restart my PC so I closed everything and canceled the wifi software update and restarted it, However after I pressed restart it did not boot up and the Mobo was going crazy with q-codes and cycling through the onboard LED's without going to the green led(boot) but the cpu_ready led is green meaning the CPU is ready for boot, There is also no display on monitor and I cannot enter the BIOS,but the fans are spinning and all the lights are working including my mouse and keyboard. I really don't know what to do.

 

Things I have tried are:

Reseating ram

Removing gpu

Updating BIOS

Resetting cmos

checking all power connections

Running it with 1 stick of ram

 

I won't be able to take it to a repair shop for a while so Really hoping I am able to fix this with the help of everyone that (hopefully responds) So thanks in advance!

Link to comment
https://linustechtips.com/topic/1084663-pc-will-not-boot-really-stuck-need-help/
Share on other sites

Link to post
Share on other sites

When resetting the CMOS, try to leave the reset jumper in with the battery out for about 10 minutes to half an hour. This normally does the trick with me. Also, try reseating the CPUImage result for cmos reset jumper

If you want me to see your reply, please tag me @Faisal A

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×