Official GIGABYTE Forum

Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: deeman79 on July 08, 2014, 11:08:12 am

Title: HELP! H77N-WIFI - PC wont boot, just hangs after boot screen...
Post by: deeman79 on July 08, 2014, 11:08:12 am
Hi,

I have the H77N-WIFI Board, built my new machine back in January this year and up until now have had absolutely no issues with it. Yesterday when I switched it on last night and it did not boot into Windows 8.1, instead showing me a recovery screen with he message "Boot Configuration Data file missing required information" After this the computer was totally unresponsive, couldn't ctrl alt del so did a reset. Tried inserting the windows 8 disk but system will not boot from the disk, and hitting F12 doesn't let me into the bios menu. After several attempts at resetting the system stopped showing the windows recovery screen. It would get as far as showing the gigabyte boot menu and then hang, after a while the screen goes blank and it stays like this. Sound like the board has an issue, given that it wont even let me into the bios or boot from the original windows disk. any ideas???
Title: Re: HELP! H77N-WIFI - PC wont boot, just hangs after boot screen...
Post by: autotech on July 08, 2014, 11:54:26 pm
Disconnect PSU reset cmos then take battery out and leave it out for a couple of hours then install battery and connect power cord back to the psu and try and see if that helps.
Title: Re: HELP! H77N-WIFI - PC wont boot, just hangs after boot screen...
Post by: deeman79 on July 09, 2014, 12:19:08 pm
Hi

The issue is now fixed! Turns out the main bios was corrupted, but for some reason it wasn't initially being detected and I wasn't able to force it to copy from the  backup. After one of my attempts last night it eventually came up with a message telling me the BIOS was corrupted and did the copy from the backup bios. All seems to be working, but a bit worried about the bios getting corrupted. I haven't updated the firmware, and haven't been into the BIOS setting for a long time, so no idea how this could have happened.    ???