you mean threads, an i7-7700k is a quad core
I noticed it list microcode BA for skylake as the HT bug fix, but that was the microcode from before th fix was released!?!? is this a typo?
EDIT by Fernando: Unneeded parts of the fully quoted post removed (to save space)
If you believe the information from Intel, the evaporated microcodes were released in April.
Then it turns out that:
- for Skylake - cpu000506E3_plat36_ver000000BA_date09-04-2017.bin
- for Kabylake - cpu000906E9_plat2A_ver0000005E_date06-04-2017.bin
@ ALL
HT. Bug fix.
ScreenShot on Overclockers.ru
@ SoniX: Is the updated CPU microcode for Skylake/Kabylake that pertains to the recently discovered hyperthreading error been included in UBU v1.69.4?
Thanks.
Tried running on a Supermicro X10DAX and recieved the following.
Scanning BIOS… Please wait…
Platform BIOS AMI Aptio 5
Brand Supermicro
Found FIT in PADDING
Found Option ROM in GUID 365C62BA-05EF-4B2E-A7F7-92C1781AF4F9
Found Option ROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 20FEEBDE-E739-420E-AE31-77E2876508C0
Found Option ROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 E095AFFE-D4CD-4289-9B48-28F64E3D781D
Found EFI Intel Ent Raid Controller GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 C9352CC3-A354-44E5-8776-B2ED8DD781EC
Found EFI Intel Ent Raid Controller GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 224D6EB4-307F-45BA-9DC3-FE9FC6B38148
Found EFI Intel LAN PRO/1000 Undi GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 A16CA5FB-4D9F-484F-B1E9-3277B0531818
This BIOS on Aptio 5 platform, known issues:
- It is not supported by the update files in the GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0
- There may be problems with updating the CPU microcode
Bios can be located on the right side of the page - http://www.supermicro.com/products/mothe…C600/X10DAX.cfm
Thanks!
I just ran the updated microcode fix for my kabylake I7 7700K and the UBU tool generated this, BA Version BA Date 09-04-2017 - Bug fix HT
0 Exit
Enter Microcode:BA
Checksum correct. Microcode not damaged.
Checksum correct. Microcode not damaged.
Generate FFS files Microcode
Found 3 module(s).
Remove "Empty" module.
Update Microcode Patch…Ok!
Update Microcode Patch…Ok!
Restore "Empty" module…
±----------------------------------------------------------+
|No| CPUID | Platform | Version | Date | Size Hex |
±-±---------±---------±---------±-----------±---------+
|01| 000906E9 | 2A | 0000005E | 06-04-2017 | 00017C00 |
|02| 000506E3 | 36 | 000000BA | 09-04-2017 | 00018000 |
±----------------------------------------------------------+
MPDT Boot - YES
FIT in GUID B52282EE-9B66-44B9-B1CF-7E5040F787C1
01 mCode Address - FFCEDB10
02 mCode Address - FFD05710
03 mCode Address - FFD17F10
04 mCode Address - FFD2F710
Attention!!!
Check the Address in the FIT
Address 01 mCode + Size 01 mCode = Address 02 mCode
0xFFCEDB10 + 0x00017C00 = 0xFFD05710
Press any key to continue . . . What does the above Attention!! mean.I thought to ask here first before I reflash the bios with this update…
I am getting file size exceeds the volume size when i try to update EFI IRST RAID for SATA 15.7.0.3054 any way to fix this.
Other then that it all works did’t have any problem with other version. also OROM IRST will work no problem there it only seems to be the efi part.
Thanks
That just means the version isn’t for your board. I havew a Z97X that can only update to 14.8.2.2397. I imagine your’s will only update to 14.8.2.2397 as well.
That just means the version isn’t for your board. I havew a Z97X that can only update to 14.8.2.2397. I imagine your’s will only update to 14.8.2.2397 as well.
I am using 15.7.0.2925 with no problems. will that sucks.
That just means the version isn’t for your board. I havew a Z97X that can only update to 14.8.2.2397. I imagine your’s will only update to 14.8.2.2397 as well.
I am using 15.7.0.2925 with no problems. will that sucks.
are you sure it changed it to 15.7.0.2925. Cause if it Gave you the error it most likely didn’t change it. try re-running ubu on the same bios file. and see if it changed it.
The Intel EFI RaidDriver v15.7.0.3054 has an uncompressed size of 238 KB and is the biggest of all Intel EFI RaidDriver versions.
If there is not enough space within the DXE Driver Volume, but you want to update the related EFI module nevertheless, you may have to remove another EFI module. >Here< is a tip given by CodeRush regarding the EFI modules, which can be removed without any problems (unless you want to use the Wake-on-LAN option).
@ Fernando
It can be done by replacing the body of PE32 image section of RaidDriver module with UEFITool without the need of removing any other modules.
@Ferrous :
In this special case the method you mentioned may work, because only the space for a few more bytes are missing. The DXE Driver Volume cannot be expanded by the user.
I just wanted to let Mr.Beer know the reason for the message he got and that it is not a bug of the UBU tool.
@ Fernando
UEFITool tries expanding the DXE volume if needed, while MMTool does not.
thanks for the update will look at the fourm later and do a litte reading.
you mean threads, an i7-7700k is a quad core
Well, indeed there are 8 processors under the "Processors" tab, 4 if you disable hyperthread. Obviously they are threads, but they’re shown as cores…
So i replacing the body of PE32 image section of RaidDriver module with UEFITool and it all seems to work.
Thanks for the info.
lol i soon will have to do everthing in UEFITool .
I have been meaning to get around to figuring this out but now I don’t have to - thanks Ferrous!
I have now updated the EFI module to 15.7 as well as the OROM.
Is there an updated version of MMTool.exe that fixes "OROM and EFI files in the GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 are not updated, since MMTool incorrectly replaces files."? I have a MSI Z270 Tomahawk Arctic and get this error opening the bios file.
@ ShadowFur
Maybe there is, but we are not available.
Therefore, UEFITool is used for independent work with GUID A032 A0327FE0-… ,