yep.
And since the defaults enable CSM, then it boot correctly with screen ON.
Disabling CSM and rebooting = blank screen
Reseting CMOS = default CSM ON = screen ON
With unmoded bios disabling CSM has no side effect and screen turn ON.
Strangely, this technique has been tried in the implementation of SLIC and had no problems.
You can send a file that has been flashed after the modification?
Here you are : stock and moded bios with your instructions
I see your post only to the original BIOS.
And another question. You use built-in or external graphics card?
9.0.xxxx. While there is no more accurate information.
And so. From reliable sources it became known that since version OROM VBIOS 1034 and EFI GOP Driver 1040 adds support Kabylake. Numbering version (9.0.xxxx) remains have not changed since the GPU Kabylake similar to Skylake.
I see your post only to the original BIOS.
And another question. You use built-in or external graphics card?
Here is a link to .zip that have both bios : https://drive.google.com/file/d/0B0_EWmI…iew?usp=sharing
I use only build in IGPU.
@ propergol
Your BIOS mod is made from the original, rather than from a backup.
I wrote that the events should be done from the BIOS backup.
1) Flash the original BIOS file.
Create Backup file.
2) Using FPT (v11.0.0.xxxx) to copy the Region BIOS:
- fptw -d bios.bin -bios
Use Backup file -> Backup Mod file.
3) Modify bios.bin
Use Backup Mod file.
4) Flash the modified file using FPT (v11.0.0.xxxx):
- fptw -f mod_bios.bin -bios
If not difficult, repeat the procedure, but do not update until the GOP Driver and OROM.
This can also be tested on the modules themselves, even without a direct mention of Kabylake. If you test the GOPs with "igop ids" and the VBIOS with "romscan", you will find two new IDs in the mentioned releases: 8086-190B and 8086-192D.
@ propergol
[Discussion] UBU Tool related Questions, Reports and Suggestions (150)
Do you have any results or still intact? It is important to determine why a blank screen in UEFI mode.
My guess is that I did put in the .zip by error the stock bios (donwloaded from Asrock) but the modded one was made by extracting first from my mobo the stock one then modded.
I will do it again tomorrow.
It is important not update until the GOP driver and OROM. Other modules will update the result.
Hello 
Intel SKL microcode rev. 76 Date: 07-01-2016.
cpu000506E3_plat36_ver00000076_date#07-01-2016.zip (93.2 KB)
It is important not update until the GOP driver and OROM. Other modules will update the result.
Sorry for the delay.
Here is the extracted bios region from my Z170M Extreme4’s bios :
https://drive.google.com/file/d/0B0_EWmI…iew?usp=sharing
I didn’t mod it since guess you can do it if needed on your side.
EDIT : extraction was made using
1
fptw64 -d bios.bin -bios
on Windows 10 pro 64bit administrator command prompt.
ONLY for propergol!
@propergol
Good! I attach mod. Attached BIOS mod_file it is necessary to flash the command:
1
fptw64 -f mod_bios.bin -bios
Reboot, reset and check UEFI mode.
We are waiting for the result.
PS: update only EFI's IRST, LAN and microcode 76.
Intel is going to ban Skylake Non-K CPU OC feature and Acer has already updated their latest BIOS with a new MicroCode that won’t allow Non-K CPU OC feature Acer released previously in their BIOS update!
Questions:
1. Can UBU integrate Acer’s Non-K OC CPU MicroCode into newer Acer BIOS releases and will UBU allow it, considering Intel’s ban on that feature? I know that UBU allowed (and still goes) use of different CPU MicroCodes on Sandy and Ivy Bridge CPU’s. I hope the same goes for this Skylake Non-K OC MicroCode…
2. Can UBU integrate Acer’s Non-K OC CPU MicroCode into other manufacturer’s BIOS updates? I was hoping at least ASUS, Acer, GigaByte, MSI could utilize Acer’s Non-K CPU OC MicroCode…
3. How can I fix / make the latest UBU detect my MEI Firmware version accurately? It detects my Intel MEI version as 8.1.2.1318, but my MEI firmware is updated to the latest version (along with Intel MEI drivers) and when I get into BIOS / UEFI itself, it shows me the accurate version, one newer than 8.1.2.1318). Also, when I tried to flash my Intel MEI with the latest Intel MEI version (just in case), it would not work because it detected the latest version was applied already. I was thinking that maybe UBU MEI Analyzer was detecting BIOS FILE MEI version (BIOS.BIN MEI version), but I don’t see how it would because I flashed my BIOS with UBU-edited BIOS.BIN files that MEI Analyzer detected as out-dated (8.1.2.1318) while my BIOS version remained the same when I checked it out in BIOS (the same = the latest and newer than 8.1.2.1318). That is assuming that BIOS.BIN files actually contain MEI version. If they do, then maybe my system would not update that particular firmware because it detected a newer one, although it should flash everything apply-able when flashed through ASUS BIOS Flashback…
EDIT by Fernando: Moved into the correct UBU Discussion thread (the other UBU thread is just for the guide and SoniX’s update announcements)
@ MonarchX
1) “Acer’s Non-K OC CPU MicroCode” - what is that microcodes??
2) “Error in Replacing File” - to update the microcode on Aptio 5 Asus, MSI, Gigabyte. The Volume, where the microcode, fixed by changing the size.
New: AMI Aptio UEFI MMTool v5 now available (4)
3) ME Analyzer: Intel Engine Firmware Analysis Tool
@ MonarchX:
There is no Acer microcode. These are all Intel microcodes which are usable will all systems of the same platform. So yes, if a microcode XX is found to allow non-k overclocking, it can be applied to any SKL system no matter the OEM.
Also, UBU is not sanctioned by Intel so of course SoniX can add whatever microcodes he wants as an option. If it’s determined that all new ucodes block non-k overclocking functionality then I suppose SoniX will introduce two options (newest w/o non-k and last w/ non-k), similarly to what happened with Ivy Bridge (newest, better overclocking).
For the ME questions, as SoniX said, you should expect replies at the Engine-related threads.
Zitat von SoniX im Beitrag #2257Update successful!
Good! I attach mod. Attached BIOS mod_file it is necessary to flash the command:
Reboot, reset and check UEFI mode.1
fptw64 -f mod_bios.bin -bios
We are waiting for the result.
PS: update only EFI's IRST, LAN and microcode 76.
Boot in UEFI mode CSM disabled : perfect for now.
Thanks
Fine! 
Please make a another test.
Now you have to flash the mod with an updated version of the GOP Driver 9.0.1042.
1
fptw64 -f gop_bios.bin -bios
Reboot, reset and check UEFI mode. We are waiting for the result.
PS It is necessary to ensure that the new GOP Driver works without problems.
Added:
And please answer the following question. How do you updated OROM, when using MMTool or UEFITool?
Zitat von SoniX im Beitrag #2262Blank screen at post if CSM disabled and or fast boot enable.
@propergol
Please make a another test.
Now you have to flash the mod with an updated version of the GOP Driver 9.0.1042.
Reboot, reset and check UEFI mode. We are waiting for the result.1
fptw64 -f gop_bios.bin -bios
PS It is necessary to ensure that the new GOP Driver works without problems.
Added:
And please answer the following question. How do you updated OROM, when using MMTool or UEFITool?
Disabling fast boot and enabling CSM for video : screen turns on correctly.
(When I did try myself to update OROM I did use UEFITool.)