Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: Dropbear67 on February 12, 2011, 08:16:53 am
-
Having an issue trying to use F12 to get into the boot menu when I restart the PC. Pressing F12 a few times just restarts the machine..
Any ideas what's going wrong?
Not sure if this bug was present in previous versions of the bios.
(running I7-2600k CPU)
Running USB keyboard. Power supply is a Corsair HX-650
Can't think what else might be relevant.
-
I have never used the final F7, so it could be a BIOS bug? I'd suggest you try with a PS/2 keyboard and if you see the same try the latest BIOS F7f or F8x
-
According to the gigabyte site, F7 is the latest bios for that mobo.. I could try a PS2 keyboard, but that's a pretty shoddy work around even if it does work..
Wonder if anyone else running F7 has experienced the same issue?
-
I agree that it is a workaround but what Lsdmeasap suggested is a decent enough idea for a start. It is after all about finding where the problem lies. I too would think it is a BIOS issue and you could try the updates he suggested, they should be available on the TweakTown Forum site in the Gigabyte section.
http://forums.tweaktown.com/
-
I just suggested the PS/2 keyboard to see if it works, because some BIOS versions have issues with certain USB Devices.
Latest UD4 BIOS is here, and it works great as I am using it now (F8b)
http://www.mediafire.com/?xuh694688srw1yb
Previous BIOS was great as well (F7f)
http://91.121.148.119/downloads/BIOS/p67aud4.f7f
-
cheers guys, thanks..
Im loathe to change the bios at the moment as i finally have a stable overclock, but may look into it ...
-
Well you can leave it if you want, just thinking updating might help resolve the problem you were having is all.
-
Had same issue with F7 final.
Hitting any key on keyboard for options (Tab, Del, F12, etc..) caused it to restart once it got to the RAID BIOS screen.
F8b fixed it for me.
-
Thanks man!
I thought it might be a BIOS bug, that is why I suggested trying PS/2 and then a different BIOS if the same issue persisted.