@Sonix I have not used the Microcode Update feature of UBU v1.69.7 for my CPU Haswell-E on BIOS AMI Aptio 5 ASUS Sabertooth X99 v3801 because you warm: "There may be problems with updating the CPU microcode"
Do I have to understand that with the future UBU v1.70.x this problem will be fixed ?
In my case, for the current UBU version (v1.69.7) I observe you display the Current Microcode Update Revision = "3A". Is it correct to understand that does reflect the "3A" Revision embedded into the BIOS ? Is it correct to understand that W10 can ignore it and does apply another one (for various criteria) ?
Tools such as HWINFO64 or SIV64 does display also "3A" but I ignore if it is the BIOS "3A" or the Windows "3A".
I observe that Intel CPU Identification Tool does use different CPUID "datas" such as (for i7-5930K): Type= 0 Gamme= 6 = Family Model= 3F Stepping= 2 Revision= 3A
It is confusing for me to understand what UBU "Platform ID" = "6F" does refer. Please, can you clarify me ?
Here are attached HWINFO64 and SIV64 screenshots related to "CPUID".
Unfortunately no. The problem is in MMTool. This utility can not work with fixed volumes. There is no alternative yet, only if you add the finished FFS-file manually in UEFITool. But this problem is not for all BIOSes. Therefore, we try to update, if there is no error message, then everything is fine.
Some questions. I successfully updated CPU microcode on ASRock H87 Pro4. Ubu had no warning and PC works fine. No I wanted to do the same for ASRock H97 Pro4, but I am a little afraid to do. It contains Microcode for Broadwell and Haswell, so I get a message:
1 2
Attention! If you select two microcode may require an adjustment in the _FIT_
and after update the code, I get:
1 2 3 4
Attention!!! Check the Address in the _FIT_ Address 01 mCode + Size 01 mCode = Address 02 mCode 0xFFF36D30 + 0x00002C00 = 0xFFF39930
Is this something I need to worry about? How do I adjust and check the _FIT_? What do I need to care if everything is correct?
Also, why many modules get stuck in mmtool ending with:
Zitat von Morku im Beitrag #3384Some questions. I successfully updated CPU microcode on ASRock H87 Pro4. Ubu had no warning and PC works fine. No I wanted to do the same for ASRock H97 Pro4, but I am a little afraid to do. It contains Microcode for Broadwell and Haswell, so I get a message:
1 2
Attention! If you select two microcode may require an adjustment in the _FIT_
and after update the code, I get:
1 2 3 4
Attention!!! Check the Address in the _FIT_ Address 01 mCode + Size 01 mCode = Address 02 mCode 0xFFF36D30 + 0x00002C00 = 0xFFF39930
Is this something I need to worry about? How do I adjust and check the _FIT_? What do I need to care if everything is correct?
You should see the _FIT_ table. If address 02 is the same as 0xFFF39930, then do not do anything. (I will then make the test more visible) If the address does not match, then you need to edit it using UEFITool and/or Hex Editor.
ZitatAlso, why many modules get stuck in mmtool ending with:
1
file size exceeds the volume size
This means that there is no free space in the volume. And for updating you need to use UEFITool.
No u are not: Check the Address in the FIT Address 01 mCode + Size 01 mCode = Address 02 mCode 0xFFF36D30 + 0x00003400 = 0xFFF3A130 not the same as 02 mCode Address - FFF39130
If u want to be the same for easy use broadwell microcode 17 it has the same size hex as 00002400. In few word use broadwell microcode 17 and haswell 23 and tell me the numbers.
Did not match. In UEFITool we look for the string FIT (as Text, no Unicode) or GUID - see above. Extract as body… Open the file in the Hex editor. Editing FFF39130 on FFF3A130, and Save In UEFITool - Replace as body…
Oh, thank you for saving me for a bad decission. Now I am looking into fix the Address 02 mCode. Do I have to do on original BIOS before I copy CPU microcode or on the modded one? I loaded the modded in UEFITool, searched for FIT, found in B52282EE-9B66-44B9-B1CF-7E5040F787C1, extract body… as raw file. Loaded the raw file into hex editor, but I have trouble to find “FFF39130”. Did I extract the wrong file?
Morku u have a haswell cpu so put the microde broadwell 17 (the last before spectre patch) and haswell 23 witch provide the spectre patch and u dont need to hex edit anything.
Except u try all of them because u want to learn.
Also i have tried personally the microcode 23 with the asrock z97 and it have problems. WHEA errors in stock settings and i am not the only one. Asus seem to work. U have better to use 22 witch i use and i have no problems.
I’m newbie for modding BIOS. I have Gigabyte H61MA-D3V (REV 2.0) with a Intel i5-3450 CPU.
I think it’s difficult for manufacturer to have BIOS update for Spectre/Meltdown bug on this motherboard, so I want to update microcode myself. I searched Intel site and found there is a microcode update for this CPU with date 2018/1/8. I knew UBU can be used to update microcode, but not sure how to do it.
How do I use UBU to write the updated microcode got from website of Intel into my current BIOS? (ver. F7c)
1 – (Kaby Lake U/Y, U23e, H/S/X) Symptom: Intermittent system hang during system sleep (S3) cycling. If you have already applied the firmware update and experience hangs during sleep/wake, please flash back to the previous BIOS/UEFI level, or disable sleep (S3) mode on your system; and then apply the improved update when it becomes available. If you have not already applied the update, please wait until the improved firmware level is available.
2 – (Broadwell E) Symptom: Intermittent blue screen during system restart. If you have already applied the update, Intel suggests continuing to use the firmware level until an improved one is available. If you have not applied the update, please wait until the improved firmware level is available.
3 – (Broadwell E, H, U/Y; Haswell standard, Core Extreme, ULT) Symptom: Intel has received reports of unexpected page faults, which they are currently investigating. Out of an abundance of caution, Intel requested Lenovo to stop distributing this firmware.
But is it really a good idea to hand out the current Intel Microcode Security Updates without any warning? I read a lot of users having problems of unstable system and also I saw this: https://www.wsj.com/articles/intel-warns…uggy-1515715212
@Kennbo : Welcome to the Win-RAID Forum! I have moved your post into this UBU Discussion thread, because the other one is strictly reserved for SoniX and his announcements of a new UBU tool version or update. Regards Dieter (alias Fernando)
Hi Fernando, Does “UBU Tool” compatible with Lenovo Yoga 2 Pro (20266) - BIOS 76CN43WW (2015/08/12)? I would like to update latest Intel’s microcode for i7 4500U (Haswell) but don’t know the correct steps. Regards,
Random question that might deserve its own thread…
A long while back I recall talking to or seeing talk regarding the AMD RAID ROM’s having a “license level” that each MFG pays/license’s (I think it was an ASUS support ticket, as it was not AMD made but licensed from another MFG), I was complaining about why a competitors board with the same Chipset was able to do RAID 6 or maybe RAID 10 but mine couldn’t…
SO, the question is, the RAID rom upgrades that are in UBU, they have a modified license level? AND what might make it require a whole new thread, is that possible? (understandably not distributable)
Ya, looking at the manual it seems some had different license level’s in the RAID rom! so, above question
