Yes, there was >one< complaint, also a Asrock Z270 board, maybe Asrock specific bug? I don’t know.
Of course i will test if you make a change, but i will not be able to do it before tomorrow morning.
nvm I figured it out, thx
@bobypf
@Pacman
@ ALL
Only for AMI Aptio V BIOSes.
Test the work without LZMA compression + GUID Defined.
I disabled the compression method LZMA + GUID Defined. Now compression by the EFI 1.1 method.
Attached file unpacked to the UBU folder as is.
Edit:
File deleted. Implemented in UBU v1.69.4.
@ SoniX
Wow, that was fast, so i had time to test it anyway, and it works 
Thank you very much for your work, and superfast solution!
This thing finally works! I managed to successfully replace my EFI RAID driver and I could see it in the menu after that. Thank you very much! Hats down!
@bobypf
@Pacman
Well!
Do you have KabyLake processes?
If yes, which version of the microcode is loaded?
Yes. Mine looks like this:
Kabylake CPUID 0906E9 - 48
Skylake CPUID 0506E3 - A6
Do I need to change anything?
It is necessary to check the new microcode 5E for Kabylake (fix bug HT). But I’m confused by Platform ID 2A, before this ID was 22.
Current version - GUID 17088572-377F-44EF-8F4E-B09FFF46A070
±----------------------------------------------------------+
|No| CPUID | Platform | Version | Date | Size Hex |
±-±---------±---------±---------±-----------±---------+
|01| 000506E3 | 36 | 000000A6 | 21-08-2016 | 00017C00 |
|02| 000906E9 | 22 | 00000048 | 15-11-2016 | 00017800 |
|03| 000506E8 | 22 | 00000034 | 10-07-2016 | 00017800 |
±----------------------------------------------------------+
MPDT Boot - NO
FIT in GUID B52282EE-9B66-44B9-B1CF-7E5040F787C1
01 mCode Address - FFE10400
02 mCode Address - FFE28000
03 mCode Address - FFE3F800
Update Intel CPU MicroCode
1 - Update CPU MicroCode Skylake
m - User Select Microcode File
s - Search for available microcode in DB.
9 - View CPU Microcode Patch list
0 - Exit to Main Menu
This is what the UBU shows for the current BIOS.
Does this just turn off hyper threading till they fix it?, or does it actually fix the problem?
Does this just turn off hyper threading till they fix it?, or does it actually fix the problem?
This is what we need to check.
Because this new microcode appears in the new BIOS for 200-series chipsets.
Added:
Attention! Check at your own peril and risk.
Test update for UBU v1.69
Extract content to the UBU folder. This will add a new Microcode 5E for Kabylake CPUID 0906E9.
If you do not have the opportunity to restore BIOS, do not experiment.
Please, write down the results of a successful update of this microcode.
Edit:
File deleted. Implemented in UBU v1.69.4.
Unfortunately i have only Sky Lake.
Mine is i5-7600K.
Just giving an advice here if you’re just for testing the microcode, a safer way if you don’t want to modify the BIOS and restore it and you’re running Windows.
https://labs.vmware.com/flings/vmware-cp…e-update-driver
Been using this, it works like in Linux distros when you update the microcode.
@ acid96
Good offer.
We have already figured out that this microcode is for Kabylake S1151 and S2066.
This microcode will be added in the next release of UBU.
does this fix the hyper threading or just turn it off?
In Little Endian from 0-7:
22 = 00100010
2A = 00101010
So 22 supports platforms 1 and 5 whereas 2A supports platforms 1, 3 and 5. Thus, 2A succeeds 22. The new Platform 3 should be for LGA2066 KBL-X.
You can use MC Extractor to view Platform details at -info parameter:
@ f3bandit:
Fix, obviously.
I have i7 7700k on Asus Z170 Deluxe; I can test… Anyway, will I be able to restore old bios using USB flashback in case of brick, right?
EDIT by Fernando: Unneeded part of the fully quoted post removed (to save space)
That explains why “Kaby Lake-X” is marked as “not affected” by the hyper-threading bug in Intel’s docs: due to the platform mask/platform id bits in the microcode, the minimum microcode version that will work for those chips already has the fix…
Flashed bios with latest microcodes on my Asus Z170 Deluxe (and i7700k); actally no issues, i still have 8 cores in device manager.