I take it you don`t mind doing this kind of thing at all as it gives you more experience in modding
BIOS for this platform and it is also a helpful thing for others that have this platform to know?
Ready FFS-files with microcode for LGA2011v3 (Haswell-E) I posted above. So who should do everything yourself. Nothing complicated.
What tool did you use again to insert those Ready made FFS-files with updated microcode and how did you insert them in the BIOS, for example in my board BIOS?
I understand everything you are saying. I was aware of the issue and when i got the chip i was very surprised to see the extension enabled. I even updated to latest asus bios 2012 for my mobo which was dated 10/17/14 and tsx was still there. I am going to ask Intel on there forums as I thought the same thing as you do until i seen so many posted with extension listed.
MMTool 5 (for updated microcodes and Extract as is FFS file) + UEFITool 0.20.1 (Replace as is FFS file)
Actually, I do not advise to change the microcode unnecessarily. Let those involved motherboard manufacturers.
OK,
I can confirm that TSX instruction is still enabled with Microcode 06C319.
Disabled is with 06C31A and 06C31C.
Doesn’t that make sense? uCode 319 is older than 31A or 31C (judging by hex number, haven’t checked the reported dates of the microcodes manually).
Make sense…newer microcode (by date) disable TSX… (as per my post above)
06C319…2014/02/26…and older TSX enabled
06C31A…2014/05/23…and newer TSX disabled
06C31C…2014/07/03
Exactly. So the user above should just apply the latest microcode which (correctly) disables TSX.
yes it does & ty. I could not understand how asus would not apply it in there z97 boards with latest bios especially with it being faulty. .
@SoniX
Found “1022-7805-8803 AMD RAID 7.0.0-00084.bin” and “AMD RAIDXpert2-F10 7.0.0-00079.efi” in sp69079. Broadcom Lan UNDI 16.4.6 is also present, but now it is signed by Microsoft, for those who want secured drivers.
Since the pair was missing, I modded them. Only 1-2 bytes are different anyway.
AMD Xpert.rar (299 KB)
Speaking of microcodes replacement, I remember CodeRush mentioning the FIT table as being important. For RAMPAGE-V-EXTREME modding there were no problems in replacing the microcodes, being of the same size. But what happens when the structure is messed up? I’ve been paying close attention to FIT lately and it is always spot on with the structure of the respective file/chip. Why would they bother to build a proper table if it was not important?
For instance, this is for RAMPAGE-V-EXTREME from previous pages:
I have noticed other things about this FIT table, but I will take them to UEFITool thread, where they make more sense.
@lordkag
The new version UEFIFind can be displayed 2 GUID, if the search string is found in "Guided freeform".
example:
1
2
3
4
5
2
3
4
5
for /f "tokens=*" %%b in ('uefifind body list 31332E312E302E32313236 X99-DELUXE-ASUS-1305.CAP') do (
echo Found pattern in GUID %%b
)
Result -
1
2
3
4
2
3
4
Found pattern in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 E095AFFE-D4CD-4289-9B48-28F64E3D781D
Found pattern in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 20FEEBDE-E739-420E-AE31-77E2876508C0
Hello modders i inform that i cant update microcode with 1.10 versions of ubu just usb flasback refuses to flash it i manged to update mcode with 1.9.0 version and its flashed sucsess on my asus M7H
What is that such a model?
I will fix it. Instead MMTool 4 again MMTool 5 works.
Added:
Fixed in UBU v1.10.beta7.
Its ASUS MAXIMUS 7 HERO Z97
Well. Checked on Ubu 1.10.beta7. Header UBF does not break.
Yes its not break now tested and works with 1.10.beta 7
Within the start post there are download links to both latest UBU versions (v1.9.1 and v1.10.Beta7) as well.