Gigabyte GA-H110N refuses to POST with F20 BIOS

[waitandhope123]

@BIOS flashed to F20a (Beta). Recently saw F20 (Final) was released so again used @BIOS to flash it. After flashing it refuses to POST, simply powers on and off endlessly.

I disconnected the CMOS battery for a few mins with it unplugged, still same result.

I shorted the jumper still same result.

GPU is pulled along with hard drives and TPM module. Still same result.

Everything worked fine before this, very strange. No ideas left but I'll take the m.2 wifi card out today and hope maybe that's it. I can try resetting the CMOS again but I don't believe those settings carry over when you flash a new image so it should not be effecting this motherboard at all. Anytime I flash a new BIOS no settings carry over so I don't see why resetting CMOS would do anything.

Wish me luck and any advice is great.

 

[Barty1884]

Clearing the CMOS likely won't do anything, like you suspect.

I would attempt to flash the BIOS again, if possible - I would even suggest using the prior, known working one.... again, if possible.

Unless you have a *need* for a new BIOS update (CPU/GPU support etc), it's rarely a good idea to be an early adopter - even if it is a 'final' release.
Moving to 'final' just means inhouse QC was complete. You're not round #1 of consumer trials.

 

[Calvin7]

F20
Support next generation CPU
* This BIOS prohibits updating to earlier version BIOS

Supports the new Intel Kaby Lake Core CPU which should be available in mid-December.

 

[Barty1884]

Installing the BIOS may prohibit it, but if it didn't take correctly (judging from the no boot conclusion), the prohibited aspect likely didn't take either.

 

[Mikel_4]

I guess there's still charge left on capacitors, you can try :

• ■Unplug power Install the NEXT GENERATION CPU, this what F20 suppose to be, for skylake the supported BIOS is only to F2.
  ■ Remove battery, plug power, hold power button for 5 sec while still on hold unplug power, the idea is to drain capacitor, do it to three times, unplug power.
  ■ Reinstate battery, plug power, turn on, enter BIOS, check BIOS version make sure it's a F20.

Where you buy the next generation CPU?

 

[Calvin7]

The next generation CPU release date has been postponed to 1st quarter 2017.

 

[Barty1884]

@Mikel_4, I don't think the BIOS update removes prior gen support like you alluded to. It adds support for next gen.

 

[Mikel_4]

@ Barty1884, if you think F20 for H110N include F2 codes than perhaps you'll be kind to present F20 low level codes similar to F2, if F20 contain all F2 (skylake line support) I'll update my reply

 

[Barty1884]

@Mikel_4 what are you talking about? Do you believe updating to F20 *removes* supports for Skylake and only allows use of Kaby Lake chips?
BIOS updates don't work like that.

 

[Mikel_4]

@Mikel_4 what are you talking about? Do you believe updating to F20 *removes* supports for Skylake and only allows use of Kaby Lake chips?
BIOS updates don't work like that.

I bought Gigabyte X99 Gaming 5P with i7 6900K, it was having issue, so I use Gigy esupport, replied me to use V3 or hashwell e CPU and then use F22 BIOS, so I bought e5 2603 v3, later I use it as GPU render and reuse 2603 with F22 still installed, again got some issue so I revert to F1 and remain stable.
The downgrade solution is on gigabyte forum

BIOS updates don't work like that

do share your personal knowledge, "grandmaster" are you writing BIOS code? for what vendor?

• ■ Wasn't implying F20 purges skylake compatibility on H110N, if skylake installed than F2 kicks in / next generation installed than F20 kicks in, since vendors have received engineering sample(s) of NG CPU which make them release a BIOS version, maybe "grandmaster" can make things clearer by showing the F2 and F20 machine code denote to skylake and NG.
  ■ So grandmaster barty, what are you talking about? Do you believe F20 *include/enhance* skylake "chips", give us the machine code so I can stroke "NEXT GENERATION CPU, this what F20 suppose to be, for skylake the supported BIOS is only to F2."
  ■

  Clearing the CMOS likely won't do anything, like you suspect.

  What are you talking about? the H110N doesn't have dual BIOS, meaning F20 configuration is the only set that CMOS use so if F20 setting is BIOS hardware failure then where else skylake gets its POST?

 

[Barty1884]

Mikel, I'm not even sure if there's a question in there?

You did imply (intended or not) that F20 'purges' Skylake compatibility by stating

for skylake the supported BIOS is only to F2.

Whether you intended to or not, you essentially stated that F20 does not support Skylake and the OP must install a Kaby Lake (or 'next gen') chip.

Upgrading your BIOS, unless you're having issue or require the enhanced support is rarely a good idea shortly following release, as you're the first line of consumer testers. Downgrading is a common workaround but, depending on whether the F20 BIOS 'took', there may not be that option since F20 won't allow downgrading.

I never said F20 enhanced Skylake, but is not intended to remove the compatibility like you implied. The OP is not the only one with an issue though, so it's likely an oversight on Gigabyte's part. If it removed Skylake compatibility, it would be stated in the 'description' of the BIOS on Gigabyte's support page.

 

[Deleted member 217926]

New BIOS updates add features or fix bugs. Not once in my 20+ years of owning and building PCs have I seen a BIOS update remove support for an entire generation of CPUs. Or even remove support for a single CPU much less an entire generation. That would be pretty stupid from a manufacturers standpoint.

 

[BadActor]

I believe the board does have DualBios. I would unplug the PSU, remove the CMOS battery, then hold the power button on the case for TWO MINUTES to completely discharge the board. Then replace the battery, plug the PSU back in and reboot normally. If it still fails to boot, shut it down and try booting several more times. If the board is functioning properly, it should revert to the back up Bios.

 

[Karadjgne]

My dual bios mobo has a jumper/switch to manually change from bios A to bios B. Mobo software allows for flash of either bios as selected by user, so if bios A gets trashed, boot in bios B, flash bios A.

 

[Mikel_4]

Mikel, I'm not even sure if there's a question in there?

You did imply (intended or not) that F20 'purges' Skylake compatibility by stating

for skylake the supported BIOS is only to F2.

Whether you intended to or not, you essentially stated that F20 does not support Skylake and the OP must install a Kaby Lake (or 'next gen') chip.

Upgrading your BIOS, unless you're having issue or require the enhanced support is rarely a good idea shortly following release, as you're the first line of consumer testers. Downgrading is a common workaround but, depending on whether the F20 BIOS 'took', there may not be that option since F20 won't allow downgrading.

I never said F20 enhanced Skylake, but is not intended to remove the compatibility like you implied. The OP is not the only one with an issue though, so it's likely an oversight on Gigabyte's part. If it removed Skylake compatibility, it would be stated in the 'description' of the BIOS on Gigabyte's support page.

the question was >>>> have you ever actually write one BIOS code or do you have experience in micro controller programming,

Install the NEXT GENERATION CPU, this what F20 suppose to be

If I was ordered to made a code for new type of CPU why would I temper the working version?

Whether you intended to or not, you essentially stated that F20 does not support Skylake and the OP must install a Kaby Lake (or 'next gen') chip.

maybe you misunderstood the whole idea of 128 Megabyte available space and BIOS flashing and didn't read my reply if skylake installed than F2 kicks in / next generation installed than F20 kicks in

What are you doing? are you try to blame something? or me?

• 
  ■ None of your replies offer solution, me, I included BIOS downgrade solution http://forum.giga-byte.co.uk/index.php?topic=17957.0 and some capacitor draining work flow as BadActor showed (wow steven, an honour, I am your big fan).
  ■ You were too busy arguing my comment, how we suppose to know the weight of your argue
  - BIOS update don't work like what? give us knowledge on how you wrote BIOS code
  - " there may not be that option since F20 won't allow downgrading. " that's like doctor saying " you only have couple weeks left"
  ■

  @Mikel_4, I don't think the BIOS update removes prior gen support like you alluded to. It adds support for next gen.

  Check again at my 1st reply, where is the word denote to remove skylake support

 

[Barty1884]

Mikel, you implied F20 removes Skyline support, simple as that. It's not a matter of F2 works for SkyLake and F20 if KabyLake installed, F20 will work for Sky or Kaby lake.

I do not have experience writing code or BIOS, to answer your question. Relevance?

BIOS updated not removing prior support is common knowledge and does not require experience writing code. As anort mentioned, that would be horrible business sense from any board manufacturer.

You posted downgrade options, which may or may not work. As per the description of F20, downgrading will not work if it flashed correctly.

I don't disagree the OP should attempt to re-flash the BIOS with F2. I suggested that in my my first response. But as above, there's no guarantees. Your suggestion may or may not be 'the solution'.

 

[Karadjgne]

Ya'll understand what a bios (basic input/output system) really is at heart? Not much to do with coding at all. It's nothing more than a QVL. It's a giant list of all components registered by intel/amd as being viable for use. The F2 bios contains a list of all the cpus viable for use on that mobo chipset. Upgrading the bios to F20 does nothing more than add a few cpus of the kaby-lake line. What it doesn't do is remove any prior listings. Considering at the time of manufacture of the bios on that board, that kaby-lake didn't exist, upgrading from F2 to F20 just means the addition of the kaby-lake cpus to the existing skylake cpus.

The issue isn't the upgrade, in the sense of what's in or not included. The issue is that Op got a corrupted bios. Which can and does happen with downloads over the Internet. There's multiple warnings about such happening during the update process. The only solution is to download a fresh copy and reinstall, overwriting the prior version. This is regardless of dual bios, even with a working copy, the secondary bios is still corrupted and needs to be overwritten. Most all newer mobo's have a designated USB in the rear for just this purpose. Use a secondary source to dl a fresh bios copy, save to USB drive then use the designated USB to install the new bios. Not a hard concept, and requires no intimate knowledge of microcode or other crap. Just a little common sense. If you go to the boards website, you'll find complete directions for installation via USB drive as some manufacturers require the use of additional software to make it happen.

 

[Mikel_4]

Mikel, you implied F20 removes Skyline support, simple as that. It's not a matter of F2 works for SkyLake and F20 if KabyLake installed, F20 will work for Sky or Kaby lake.

I do not have experience writing code or BIOS, to answer your question. Relevance?

BIOS updated not removing prior support is common knowledge and does not require experience writing code. As anort mentioned, that would be horrible business sense from any board manufacturer.

You posted downgrade options, which may or may not work. As per the description of F20, downgrading will not work if it flashed correctly.

I don't disagree the OP should attempt to re-flash the BIOS with F2. I suggested that in my my first response. But as above, there's no guarantees. Your suggestion may or may not be 'the solution'.

removes GT Skyline

sorry I don't do automotive.

■ What is it take for you to understand this.
Some micro controller primitives for you:
- let say F2 has function A B C for skylake, its a 6MB file size
- because I want to add new function for NG CPU so I add D E F in F20 container, meaning skylake won't respond to function D E F and vice versa, at least that was the plan.
- so you have F20 along with F2 codes, to make it simple I won't entitle it as F2+F20 because it's not awesome.
- as F20 built base on engineering sample there could be complications within F20 codes, the possibility is skylake recognize some function within F20 and activate it. It could not be easy to resolve so that's why vendors release it as BETA.
- other complication possibility is F20 treating skylake as NG because of user preset.
■ Yes you don't have experience of BIOS code assembly, period. Relevancy, none,

 

[Karadjgne]

What we’ve got here is failure to communicate. Some men you just can’t reach. So you get what we had here the last few posts, which is the way he wants it; well, he gets it. He's the only one who gets it. I don’t like it any more than you guys.

 

[Mikel_4]

Spoiler

Ya'll understand what a bios (basic input/output system) really is at heart? Not much to do with coding at all. It's nothing more than a QVL. It's a giant list of all components registered by intel/amd as being viable for use. The F2 bios contains a list of all the cpus viable for use on that mobo chipset. Upgrading the bios to F20 does nothing more than add a few cpus of the kaby-lake line. What it doesn't do is remove any prior listings. Considering at the time of manufacture of the bios on that board, that kaby-lake didn't exist, upgrading from F2 to F20 just means the addition of the kaby-lake cpus to the existing skylake cpus.

The issue isn't the upgrade, in the sense of what's in or not included. The issue is that Op got a corrupted bios. Which can and does happen with downloads over the Internet. There's multiple warnings about such happening during the update process. The only solution is to download a fresh copy and reinstall, overwriting the prior version. This is regardless of dual bios, even with a working copy, the secondary bios is still corrupted and needs to be overwritten. Most all newer mobo's have a designated USB in the rear for just this purpose. Use a secondary source to dl a fresh bios copy, save to USB drive then use the designated USB to install the new bios. Not a hard concept, and requires no intimate knowledge of microcode or other crap. Just a little common sense. If you go to the boards website, you'll find complete directions for installation via USB drive as some manufacturers require the use of additional software to make it happen.

I love take on grandmasters, makes me feel like grand nemesis.
If you own intel 100 family gigabyte board, why not try to flash it with a OPs downloaded F20 (PM him and ask to send)
after that share your steps, would it be better that way? or send your own working F20 to him.

Giant list of QVL
Y'all know what vondor ID is, BIOS OSD displays installed or on-board components, to display that on screen a component need a specific title to identify it self, if a title not included then BIOS will read its architecture design and show it. The BIOS translate ASCII code to alphabet, that's why we see ASUS instead of 0x0AC8. And you need to provide evidence of F20 BIOS stores the list, if I were to write a BIOS codes, I won't batter doing that because the component's MCU already provide that.
For the sake of users, vendors wouldn't hassle their customers with machine/assembly language {*pardon*} crap, that's why UEFI become standard interface. To intermediate machine language to human language, the BIOS chip has an embedded codes usually C++.

Doesn't do is remove earlier listing
The initial F1 guaranty its on-board controller, skylake family, and other add-on device, the little common sense for gigabyte is not to temper the working F1 codes, unless,,, some vendor releases a bad firmware which will cause hardware conflict issue.

 

[BadActor]

Spoiler

Ya'll understand what a bios (basic input/output system) really is at heart? Not much to do with coding at all. It's nothing more than a QVL. It's a giant list of all components registered by intel/amd as being viable for use. The F2 bios contains a list of all the cpus viable for use on that mobo chipset. Upgrading the bios to F20 does nothing more than add a few cpus of the kaby-lake line. What it doesn't do is remove any prior listings. Considering at the time of manufacture of the bios on that board, that kaby-lake didn't exist, upgrading from F2 to F20 just means the addition of the kaby-lake cpus to the existing skylake cpus.

The issue isn't the upgrade, in the sense of what's in or not included. The issue is that Op got a corrupted bios. Which can and does happen with downloads over the Internet. There's multiple warnings about such happening during the update process. The only solution is to download a fresh copy and reinstall, overwriting the prior version. This is regardless of dual bios, even with a working copy, the secondary bios is still corrupted and needs to be overwritten. Most all newer mobo's have a designated USB in the rear for just this purpose. Use a secondary source to dl a fresh bios copy, save to USB drive then use the designated USB to install the new bios. Not a hard concept, and requires no intimate knowledge of microcode or other crap. Just a little common sense. If you go to the boards website, you'll find complete directions for installation via USB drive as some manufacturers require the use of additional software to make it happen.

I love take on grandmasters, makes me feel like grand nemesis.
If you own intel 100 family gigabyte board, why not try to flash it with a OPs downloaded F20 (PM him and ask to send)
after that share your steps, would it be better that way? or send your own working F20 to him.

Giant list of QVL
Y'all know what vondor ID is, BIOS OSD displays installed or on-board components, to display that on screen a component need a specific title to identify it self, if a title not included then BIOS will read its architecture design and show it. The BIOS translate ASCII code to alphabet, that's why we see ASUS instead of 0x0AC8. And you need to provide evidence of F20 BIOS stores the list, if I were to write a BIOS codes, I won't batter doing that because the component's MCU already provide that.
For the sake of users, vendors wouldn't hassle their customers with machine/assembly language {*pardon*} crap, that's why UEFI become standard interface. To intermediate machine language to human language, the BIOS chip has an embedded codes usually C++.

Doesn't do is remove earlier listing
The initial F1 guaranty its on-board controller, skylake family, and other add-on device, the little common sense for gigabyte is not to temper the working F1 codes, unless,,, some vendor releases a bad firmware which will cause hardware conflict issue.

There is no need to be adversarial here, we are all here to help. Please refrain from being disrespectful to other members, it serves no purpose. If you disagree with someone, simply make your point and let it go.

 

[Karadjgne]

Mikel, you assume the badge of Grandmaster is some kind of recognition for being some sort of Supreme intelligence when it comes to IT. That would be wrong. It's just a recognition of 1000 users application of Best Answer to their question. Many times is some question so simple such as 'can I use this gpu on my mobo' or 'how big a psu do I need' and the Best answer is usually the first and only answer. So loose the attitude that you are somehow superior, it's not helpful in the slightest.

The simple answer is Op needs to go to the manufacturer website, look up the instructions for flashing a corrupted bios via USB and reflash the bios. Or, if Op's mobo is in fact dual bios capable, swap the jumper/switch to the secondary bios, and follow manufacturers directions for flashing the primary bios, which is usually done through the bios itself or motherboard software.

 

[Deleted member 217926]

Spoiler

Ya'll understand what a bios (basic input/output system) really is at heart? Not much to do with coding at all. It's nothing more than a QVL. It's a giant list of all components registered by intel/amd as being viable for use. The F2 bios contains a list of all the cpus viable for use on that mobo chipset. Upgrading the bios to F20 does nothing more than add a few cpus of the kaby-lake line. What it doesn't do is remove any prior listings. Considering at the time of manufacture of the bios on that board, that kaby-lake didn't exist, upgrading from F2 to F20 just means the addition of the kaby-lake cpus to the existing skylake cpus.

The issue isn't the upgrade, in the sense of what's in or not included. The issue is that Op got a corrupted bios. Which can and does happen with downloads over the Internet. There's multiple warnings about such happening during the update process. The only solution is to download a fresh copy and reinstall, overwriting the prior version. This is regardless of dual bios, even with a working copy, the secondary bios is still corrupted and needs to be overwritten. Most all newer mobo's have a designated USB in the rear for just this purpose. Use a secondary source to dl a fresh bios copy, save to USB drive then use the designated USB to install the new bios. Not a hard concept, and requires no intimate knowledge of microcode or other crap. Just a little common sense. If you go to the boards website, you'll find complete directions for installation via USB drive as some manufacturers require the use of additional software to make it happen.

I love take on grandmasters, makes me feel like grand nemesis.
If you own intel 100 family gigabyte board, why not try to flash it with a OPs downloaded F20 (PM him and ask to send)
after that share your steps, would it be better that way? or send your own working F20 to him.

Giant list of QVL
Y'all know what vondor ID is, BIOS OSD displays installed or on-board components, to display that on screen a component need a specific title to identify it self, if a title not included then BIOS will read its architecture design and show it. The BIOS translate ASCII code to alphabet, that's why we see ASUS instead of 0x0AC8. And you need to provide evidence of F20 BIOS stores the list, if I were to write a BIOS codes, I won't batter doing that because the component's MCU already provide that.
For the sake of users, vendors wouldn't hassle their customers with machine/assembly language {*pardon*} crap, that's why UEFI become standard interface. To intermediate machine language to human language, the BIOS chip has an embedded codes usually C++.

Doesn't do is remove earlier listing
The initial F1 guaranty its on-board controller, skylake family, and other add-on device, the little common sense for gigabyte is not to temper the working F1 codes, unless,,, some vendor releases a bad firmware which will cause hardware conflict issue.

There is no need to be adversarial here, we are all here to help. Please refrain from being disrespectful to other members, it serves no purpose. If you disagree with someone, simply make your point and let it go.

^ This is the best advice you're going to get all day. Argue your point and back it with facts. Name calling, personal attacks and generally being adversarial will make your continued participation on the site short.

 

[Mikel_4]

^ Seems like anort will pull some moderator string here, not that I'm worry for getting kicked out, what I don't like is a misleading reply that will make OP follow that, before any of you mods enforce disciplinary action consider these:

• ■There's no POST screen, so Q-Flashing is impossible, you need to fix the CMOS=BIOS issue first.
  ■ As short-jumping is no good, and again stop arguing Dual Bios because obviously if wait123's H110N comes with Dual Bios he'd picked karag's BIOS switching as solution.
  ■Modern BIOS chips such as what Gigabyte use for H110N possibly don't rely to CMOS chip anymore to run POST because it was loaded with (rarely) incompatible data to wait123's setting, in regular expression I assume :
  a = F1 */initial shipped BIOS resided on CMOS RAM
  b = Fx */resided on BIOS Non Volatile RAM
  if (x = 0, b=F1)(x=2 b=F2, x=3 b=F3, x=20 b=F20)
  */ we need to make BIOS chip loose the data so it will load F1 to its RAM,
  
  After you get POST, further diagnostic can be perform.

 

[Karadjgne]

I installed a q6600 on a p615 chipset and got the exact same power on/off. From this I can only assume that the cmos works simultaneously with the bios during post in order to actually recognize components as being viable. Since the pc worked before flashing the bios, again I have to assume that the bios is hung up/corrupted creating a loop which is killing recognition of the cpu, shutting the pc back down. Since it seems to be unknown if the bios actually relies on the cmos or not, the one known fact is that the flash was unsuccessful. Reflashing the bios with a fresh dl copy might just fix the post issue, might not, but it's seriously doubtful it could make matters worse.