Resetting an asrock z77 extreme 4 and problems entering UEFI

Menzii

Honorable
Nov 9, 2013
4
0
10,510
First I have searched and found some threads with very similar questions, but I have very little experience working with motherboards and could use some clarification/explanation.

I have the asrock z77 extreme 4. At some point I set it to fast startup, which hides the splash screen and POST details while booting, but I can't imagine would interfere with opening BIOS options. In the process of reinstalling windows 7 I wanted to check to make sure my boot option were set to cd, but found that pressing f2 or del would cause my computer to get stuck on a blank screen with no output to my monitors. Frustrated, I decided to try to reset the CMOS, and just start over.

Present day: shut down, turned off ps, unplugged, and used the cclr CMOS button on the back of the motherboard. Waited 10 minutes. Restarted, and got an a2 error (IDE detect) on the display.

What happened and how do I move forward? Don't be afraid to assume I am totally ignorant.
 

bdiddytampa

Honorable
Dec 2, 2012
1,012
0
11,660
I may be incorrect but if you use the clear cmos button on the back the PC may need to be on. Otherwise if you want to clear it while off you can remove the cmos battery for 30 secs and replace it. Give either or both of those a shot and let me know how it goes :)
 

Menzii

Honorable
Nov 9, 2013
4
0
10,510


Ok I tried pressing the button while the computer was on and error a2 was showing. It all shut down, then turned back on. Still getting error a2. Is removing the battery the last option? I must say I want to avoid messing with the hardware for as long as possible. Thanks for the rapid response!
 

Menzii

Honorable
Nov 9, 2013
4
0
10,510


When I press f2 I get an A6 error instead of the A4, but no difference - still nothing doing on the monitor.
 

Menzii

Honorable
Nov 9, 2013
4
0
10,510


Thanks - at least I'm not just bad at searching forums. Remember I originally tried to reset because I couldn't get into UEFI even when the computer was running fine, which is another problem I haven't found any info on. Thanks for helping!