Z170 Gaming K6+ new 2.10 bios is crap

Remember, without knowing what changes were made in a newer BIOS revision, your carrying over the same changes from one revision(2.00) may not work on the newer one(2.10).

Can I ask why you updated to 2.10?

Your computer rebooting twice is normal and working as designed. Instead of me again typing out(plagerizing) the whys, please read redduc900's post #5 below. He's explains it short and sweet. And too, notice the date it was posted.
http://www.overclockers.com/forums/showthread.php/725971-Boot-has-two-false-starts?p=7399937&viewfull=1#post7399937





Edited by wardog - 11 Feb 2016 at 8:35pm

Thx for reply. I updated because of new microcode and hope, that other problem (for example freezing UEFI in fan-tastic setting) are solved. But it seems things getting worse. And I think it is not normal when same OC in one bios is stable and in other bios versions windows cannot start. Double boot is not problem, problem is starting after power loss, even it is disabled in bios and strange frozen state with black screen and power led diode shining. But there are few nice things too. Headphones output is very clear without any hiss or buzz.

Running it just fine here with my previous overclock settings with no issue. Make sure you are not OC'd when updating BIOS. Also make sure you adjust the VCCIO, VCCSA manually (I use 1.10 for VCCIO and 1.15 for VCCSA). Currently running 6600k at 4.6ghz at fixed 1.32v and G.Skill TridentZ DDR 3200 16 GTZ at 1.35v. I should note that I had no boot, no post issues until I MANUALLY set VCCIO voltage to 1.10 with ram above 3000mhz. YMMV of course.

Edited by GripS - 14 Feb 2016 at 10:14am

Oggy wrote: Yesterday I tried update new bios 2.10. Oh, my mistake. After flash I loaded default setting, rebooted and set all settings from scratch. I set OC the same as in older bios (look at my signature). My PC (win 10pro) became totally unstable. I reverted back to bios 2.00 and my PC is running again. I have to say, that almost all versions asrock bios on my MB are buggy. I have another problem with PC start after power loss (when PC is off). When power is back online, PC begins to start (even when off is set in bios), but I only hear ventilators, monitor is black and PC is still in this state. Or PC is normally starting for few seconds, and then shut down and then start again. I tried 2 different PSU, same behaviour. But after first succesfull start up PC starts normally everyday without problems, till next power loss.

peroni wrote: Oggy, you win for the best thread title of the week Smile About booting after a power outage, I noticed the same behaviour. If the computer is on and I lose power, I want it to stay off when the power returns. Instead it tries to boot up but fail then goes off again. I would understand the need for double boot if I was the one triggering the startup.

Just thought I'd mention that everyone does not think the thread title is good.

Personally, I feel a title like that immediately makes the author's credibility questionable. If that's the best that can be done for a thread title, then what will the content of the post be?

For example, we have "I tried update new bios 2.10... My PC (win 10pro) became totally unstable.". The only follow up is, "I reverted back to bios 2.00 and my PC is running again.".

What is unstable? BSODs? If so, what error(s)? Lockups or freezing? Or something else?

Your CPU OC consists of setting the multipliers to 46, with the CPU VCore set to Offset mode, with a +70mV offset, right? Otherwise all default settings?

Did you verify that the VCore and VID was the same at load with the new UEFI that it was with the previous version? Are you sure that all the default settings are identical to those of the previous UEFI version?

What is the purpose of the 2.10 UEFI version? From the Fatal1ty Z170 Gaming K6+ UEFI download page description for UEFI version 2.10:

1. Update CPU microcode to 0x76.
2. Remove SKY OC function.

The two items are related to each other. The purpose is to change the CPU microcode to a version (0x76) that stops the Sky OC feature. Any UEFI options related to Sky OC would also be removed, as they are now useless.

Do we know this new microcode from Intel is not affecting our CPUs in other ways? Could this new microcode be causing some or all of the stability problems you seem to have?

The CPU microcode that is part of the UEFI/BIOS file is not changed/updated with every UEFI/BIOS update. If the microcode is not changed in a UEFI update, it is left alone, or the "current" version is used again with the new update.

Notice in this case, that changing to the version 2.00 UEFI, does the following:

1.Update microcode to 0x74.
2.Improve DRAM compatibility.

My point is, if you change to UEFI 2.00, you no longer have the 0x76 microcode in your system, you have the 0x74 microcode.

It is unusual for two adjacent UEFI updates to have different microcode versions. That allows us to compare the two microcodes with very few if any other changes in the UEFI besides the microcode. I have never been able to do that with any mother board I've used to build a PC.

Do I know positively that the 0x76 microcode is causing the problems you seem to have? No.

Do I know positively that the main difference between the 2.00 and 2.10 UEFI versions is the 0x76 microcode? Yes.

Do I know that the next UEFI versions for all of our Z170 boards will have the 0x76 microcode? No, not positively, but another microcode change so soon?

It may sound strange, but I hope the microcode change is not the cause of the problems you have. That's because if it IS the cause, all the owners of ASRock Z170 boards (I am one) will probably have similar problems because we too have a UEFI update that has the 0x76 microcode. Ouch.

The automatic start after a power loss, with the Restore on AC/Power Loss option set to Power Off is a problem, if the PC was in the Shutdown state when the power loss occurred. That seems to be the situation for Oggy and peroni. Was the Deep Sleep option set to its default value?

Where I live I very rarely have power outages, and I've never come home to one or more of my PCs running that were shutdown. Usually the default value of this option is Power On.