Raptor Lake-HX/S
cpuB0671_plat32_ver00000124_2024-02-22_PRD_1D9740B2 (old)
Updated MCE.db (v1.101.0 r303 Dev, 07/11/2024)
Intel_240711.rar (446.3 KB)
2 Likes
Whiskey Lake-U
cpu806EB_platD0_ver000000F6_2024-02-01_PRD_8F812A37
Comet Lake-U
cpu806EC_plat94_ver000000FC_2024-02-05_PRD_F4173A11
Updated MCE.db (v1.101.0 r304 Dev, 07/20/2024)
Intel_240720.rar (444.8 KB)
5 Likes
Interestingly, there is a microcode with the same date and version (917DC5C4).
1 Like
Didnât check thoroughly, Sorry if itâs an old one?
cpu00A10F81_ver0A108105_2023-07-11_4E0DC6A8
cpu00A10F81_ver0A108105_2023-07-11_917DC5C4
cpu00A10F81_ver0A108108_2024-02-27_3E4DC125
To my knowledge, there are no other public. At least one that someone has found.
Granite Rapids
cpuA06D0_plat97_ver80000640_2024-04-17_PRE_36102A34
Sierra Forest
cpuA06F3_plat01_ver13000162_2024-04-12_PRD_54992EFC
1.43 MB files. The largest size so far was 600 KB (Sapphire Rapids).
Updated MCE.db (v1.101.0 r304 Dev, 07/25/2024)
Intel.rar (3.2 MB)
4 Likes
Yeap, correct observation. A big issue with AMD is that microcode blobs donât have an end user-verifiable checksum or hash. Thus, any corruption can manifest as a new (valid) blob.
@lfb6 Do you remember the source of this particular blob? Maybe bad extraction of the original BIOS image or similar can be identified.
I was able to (re-)find the currently known blob here, for instance:
From LVFS, so thereâs much Dell, HP or Lenovo. Traveling now, so not able to look it up, Iâm sorry!
1 Like
Strix Point
cpu00B20F40_ver0B204011_2024-04-16_AD27994B
Cascade Lake-SP
cpu50656_platBF_ver04003707_2024-03-01_PRD_9BC8D6D6
Updated MCE.db (v1.101.0 r304 Dev, 07/30/2024)
240730.rar (291.1 KB)
3 Likes
IceLake-SP
cpu606A6_plat87_ver0D0003E7_2024-04-01_PRD_D7026D0B
Sierra Forest
cpuA06F3_plat01_ver030001B2_2024-05-20_PRD_8DEA5D5B
Updated MCE.db (v1.101.0 r304 Dev, 08/02/2024)
Intel_240802.rar (2.0 MB)
4 Likes
Since cpu00A10F81_ver0A108105_2023-07-11_4E0DC6A8 is not in the database, I assume itâs classified as junk, right?
You mean the one posted by lfb6 last week? I cannot verify if itâs correct or where it came from (to check if anything went wrong while extracting it). I did download all recent LVFS packages from that day (from 23rd to 29th I believe, only the last 50 are listed easily by LVFS) and I could not find this particular blob. On the other hand, I can verify that the pre-existing cpu00A10F81_ver0A108105 can be found in many other BIOS from multiple vendors, so I have to assume that itâs the correct/expected one.
2 Likes
Raptor Lake-S
cpuB0671_plat32_ver00000129_2024-07-18_PRD_A6890DD3
Updated MCE.db (v1.101.0 r305 Dev, 08/08/2024)
Intel_240808.rar (227.3 KB)
My recollection is that Intel promised that particular microcode by mid-August, and this is 18 July. And after 18 July, they said that they did not know what the root cause was at all. So it is suspicious to me. But Iâm not surprised by anything to do with Intel anymore.
Although, itâs also true that this statement is from the 22nd, and here itâs written as a fact what the root cause is. Which means that the patched microcode could have been ready on the 18th.
6 Likes
Thank you for releasing this, Canât thank you enough for your work you are doing.
I just wanted to let you know that I copy & pasted your quote to ASUS forums related to 0x129 ucode not being the Intelâs promised fix for the sake of increasing awareness & public knowledge & ofc by making sure that Iâm not the one who said it 
Again, thank you!
1 Like
18th July? What do you mean? Microcode date?
This micro ode is the solution for intel CPU crash problems. this is what intel said
This seems to have been misunderstood by a large proportion of users. Intel may not have communicated it properly, but the point is this: there are two classes of processors in terms of failure. One that contains the ones that have already failed (hardware-wise), and the other that contains the ones that have the potential to fail. The microcode update can only be a solution for the latter, not for the former! RMA is the only solution for the former. This should be understood and acknowledged by all users.
2 Likes
not in my case but iâll like to know where these cpuâs fail
The âOxidationââŚ
Addressing Manufacturing Speculation on Intel Core 13th/14th Gen Desktop Processors - Intel Community
The âFixesââŚ
Microcode (0x129) Update for Intel Core 13th and 14th Gen Desktop Processors - Intel Community â
"In addition to extended warranty coverage, Intel has released three mitigations related to the instability issue â commonly experienced as consistent application crashes and repeated hangs â to help stabilize customer systems with Intel Core 13th and 14th gen desktop processors:
- Intel default settings to avoid elevated power delivery impact to the processor (May 2024)
- Microcode 0x125 to fix the eTVB issue in i9 processors (June 2024)
- Microcode 0x129 to address elevated voltages (August 2024)"
The âAffectedââŚ
Additional Warranty Updates on Intel Core 13th/14th Gen Desktop Processors - Intel Community
Further and deep reading into the subject, follow the same user statements on Intel forum.
And thatâs itâŚany further releases its mcode based âfixâ nothing more it can be done as they were already built and in circulation, my POV only.
2 Likes