CLR CMOS Problem

devilgodspider

Distinguished
Mar 7, 2013
265
1
18,795
The following is what a friend is experiencing, since he has a iPhone and only had that PC, he can't post this so I'll be doing the talking (I thought you could go to the internet on a iPhone but I never had one and he's talking to me on Steam via the App), anyway here it goes:

Motherboard: ASRock P67 Pro3
ire0BZj.jpg


I was changing the usb cables on the back and accidently hit a small button called clr cmos
It turned to this red light (as seen below)
KemRmCO.jpg

And the fans got louder cause of the speed, so I restarted the pc but that didn't turn it off. So I opened the case up trying to push those red buttons on the M/B in the pic
But that would just turn off or reset pc, so i tried taking out the clr cmos battery out and leave it for 10 mins and mixing with the jumper pin below it.
And now as I try to turn pc on it'll bring up the boot up menu and all and the clr cmos wont flash as much as it used to, but the fan speed is still the same.
Trying to get to desktop menu will only cause blue screen for like half a sec and quickly get back to boot menu, Reparation just errors.
I can bring up Asrock's UEFI utility but idk how to use it, I need to somehow reset the bios to get rid of "clr cmos" oc stuff.

Anything posted here or questions I'll tell my friend via Steam.

PS.: The CLR CMOS Button he hit is NOT the one on the picture with a red light, it's on the back I/O Panel while he was switching his Headphone jack.
 
Solution
Clr_Cmos or Clear_RTC are all the same.

The bios has been set to its default settings.

Now if the system had any changes made, they have to be re-made and saved.

One thing I can think of is to ensure the SATA mode is AHCI if it was before(or RAID or IDE all depends on what it was set to in the first place). The wrong SATA mode can cause these blue screens when trying to boot because the driver setup has changed and Windows does not like this change.
Clr_Cmos or Clear_RTC are all the same.

The bios has been set to its default settings.

Now if the system had any changes made, they have to be re-made and saved.

One thing I can think of is to ensure the SATA mode is AHCI if it was before(or RAID or IDE all depends on what it was set to in the first place). The wrong SATA mode can cause these blue screens when trying to boot because the driver setup has changed and Windows does not like this change.
 
Solution