CMOS BIOS problem resetting

m3rlin

Prominent
Dec 20, 2017
11
0
510
Hey Everyone,

So I was an idiot and was messing with the bios when I shouldn't have been and ended up messing up my computer surprise surprise (SPECS at the bottom). Long story short the Monitor, Keyboard, and Mouse do not work when the computer starts. The case fans and LED's fire up no problem however there are zero beeps on startup.

I tried taking out the CMOS battery several different times, even leaving it out up to three hours, and even tried clearing by short-circuiting the 2-pin CLRTC for 5-10 seconds as suggested by the owners manual. The one important thing to note here is that when the computer was unplugged I didn't know I could use my finger to release the CMOS battery. Instead I used a screw driver. I'm curious if its possible if residual power could have been stored and this fried the mobo?

I've taken out all the PCI cards and even the ram one at a time switching from DIMM slots. I've even gone so far as to move the jumper from the CPU_OV enabled to the default of disabled with no luck.

With the fact that there a no beeps at start up means its either the PSU, CPU, or mobo correct? I'll buy another CMOS battery hoping that will fix the problem but if not what would you recommend? I know its troubleshooting at this point but curious if anyone has any insight?

Mobo: Asus Prime Z370-a
CPU: Intel i7-8700k Coffee Lake
CPU Heatsink: Noctua NH-D15
PSU: Seasonic FOCUS Plus Series SSR-650FX 650W
GPU: Gigabyte GeForce GTX 1060 6gb
RAM: Ballistix Sport LT 8GBx2 DDR4 2666
SSD: Samsung 850 EVO 2.5"
OS: Windows 10 Pro 64-bit

Any help would be much appreciated.

Thanks,
Merlin
 
Have you tried plugging your keyboard and mouse in different USB ports? Some of your USB ports are controlled by an add-on ASMedia controller chip and some are controlled by the Intel chipset. All the USB 2.0 ports are controlled by the Intel chipset, so they should work properly.

What do the Q-LED's show when you boot?

ASUS Q-LED (CPU, DRAM, VGA, Boot Device LED)
 


I haven't tried plugging into any other USB 2.0 slots other than the ones they were initially in.

The VGA "LED" has a somewhat yellow hue to it but doesn't look very bright.

I have another PSU that I will swap out to see if that's the problem later today.

-Merlin

 


I just realized that I didn't have the CPU 12V plugged in. When I plugged it in and tried starting up, the case fans no longer came on and only the mobo LEDs came on.

I tried a different PSU and the same thing happened except the Q-LED CPU lit up red for a brief second before going off.

Did I fry the CPU or is it the mobo?
 

Have you cleared the CMOS again?
 
I know this might sound trivial, but try after shutting down your PC to turn off your PSU from it's back button, unplug the power cord off it, let your system sit for a bit (like 15 minutes or more) then hook up everything and start your PC.
 


Yes I took both the CMOS battery out when swapping out PSU's and even shorted the CLRTC before trying to boot with the new PSU. It was during this attempt that the CPU Q-LED lit up red for a couple of seconds. Since the case fans no longer were working I could hear my SSD trying to boot.
 

The CPU Q-LED lighting up red for a couple of seconds does not indicate a problem, that is normal. Since an SSD has no moving parts, it does not make any sound when it is running. Just as a test, try booting with the graphics card in the 2nd x16 slot.

 


When I get a chance I will try to boot with only the processor in. If there are no beeps I'm thinking/hoping it is the mobo. I just ordered the same mobo with wishful thinking.

I took out my GPU and trying to boot with the onboard graphics with still no luck.

It must have been my HDD then that was trying to boot even though the SSD has my OS.
 
Still same scenario with the RAM completely out and using on board graphics. No beeps, no QLED's.

Tried again shorting the CLRTC and trying various USB slots. Still same thing. Since there were no beeps I'm fairly sure it's the mobo. I'll get the other one Friday and will update if that fixes it.

-Merlin