[OFFER] Intel, AMD, VIA CPU Microcode Archives (1995-Present)

Special Topics CPU Microcodes
1

All currently known Intel, AMD and VIA CPU microcodes have been made available by plutomaniac (AKA platomav on Github) for the Win-RAID community!

MICROCODES

Note that this thread will be updated from Plutomaniac’s Github when I have time, if you want to test the latest microcode and it isn’t here then you can still download the latest file(s) from Github.

The Microcodes have been sorted into folders that are labeled by CPUID.

To find your specific CPU folder use the search box at the top of the Mega folder to enter your CPUID e.g.

906A4
906A41246×581 64.1 KB

Intel has subfolders for each Platform ID (i.e. 0906A4_40, 0906A4_80, 0906A4_C3), please make sure to use the same Platform ID for compatibility when swapping/updating microcodes in your BIOS.

In some cases you can use a higher Platform ID but this is not guaranteed!

WARNING: Replacing a working microcode + Platform ID with a non-compatible Platform ID can result in a POST (Power On Self Test) failure which may require BIOS recovery with a hardware programmer! Be careful!

Here is some helpful information taken directly from plutomaniac’s Github readme to help understand Platform ID on Intel systems:

  • Platform (Intel only)
  • Provides information about the supported sockets (LGA775, LGA1366 etc) or platform types (Desktop, Mobile etc) depending on CPU generation.
  • Up to 8 supported Platforms, encoded in Little Endian binary form (bitfield).
    • Examples: 0xC0 = 0b11000000 = 6,7 ; 0x03 = 0b00000011 = 0,1 ; 0x76 = 0b01110110 = 1,2,4,5,6.
  • When updating to another microcode, ensure that at least the same or more Platforms are supported. You can use MC Extractor to check each Intel microcode’s supported Platforms.
    • Example: Changing from 0x5C (2,3,4,6) to 0x5D (0,2,3,4,6) is okay, due to the additionally included platform “0”.
  • To not risk losing socket/platform support, avoid reducing the supported platforms.
    • Example: Changing from 0x5C (2,3,4,6) to 0x58 (3,4,6) might not be okay due to the missing platform “2”.
  • If you cannot find the exact CPUID & Platform combo at the repository, as the one you currently have, it might be because there is another microcode with the same CPUID but with more supported Platforms.
    • Example: Microcodes with CPUID 0x906E9 & Platform 0x22 (1,5) were superseded by CPUID 0x906E9 & Platform 0x2A (1,3,5) in order to add LGA2066 socket/HEDT platform type support at KBL(-X).
  • Null Platform (0x00) is implicitly the same as single Platform (0x01), since at least one platform must be supported.
    • Example: At CPUID 0x633, Platform 0x00 = 0x01 = 0
6 Likes
3

Thank you @chinobino for creating this!

The README at the CPUMicrocodes github repo explains the naming of each Intel, AMD, VIA microcode as well as how to use the Intel Platform ID correctly:

Feel free to copy it here, if you think it will make things easier to understand.

2 Likes
4

This is amazing, new refreshing post for Microcodes are always welcomed!

I use it mainly to convert from .bin–>.dat so that I can use it with VMware CPU Microcode Update Driver on any windows without needing to mess with the BIOS. Safest thing to update microcode.

Here’s an example… this is old microcode that came with the BIOS

image
image888×244 36.2 KB

Thanks to VMware driver… I can update the microcode easily
image

And a picture from Event Viewer confirms the update

image
image783×346 13.4 KB

1 Like
5

Hello @chinobino, r305 is released on the plutomaniac website with new miccrocodes for Intel and AMD.

6

@wiens

Added:

Intel cpuB0671_plat32_ver00000129_2024-07-18_PRD_A6890DD3
Intel cpuA06A4_platE6_ver0000001E_2024-04-15_PRD_ABD389AA
Intel cpu90661_plat01_ver0000001A_2024-04-05_PRD_6A8705D7
Intel cpu606C1_plat10_ver010002B0_2024-04-03_PRD_B7E32709
Intel cpu5065B_platBF_ver07002904_2024-04-01_PRD_A6D30104
Intel cpuA0661_plat80_ver000000FC_2024-02-01_PRD_D71870FA
Intel cpuA0660_plat80_ver000000FE_2024-02-01_PRD_EE2F0157
Intel cpuA0652_plat20_ver000000FC_2024-02-01_PRD_DDE02540
Intel cpu906E9_plat2A_ver000000F6_2023-07-27_PRD_C0B5A822
AMD cpu00B40F40_ver0B40401C_2024-07-15_A253F4FA
AMD cpu00A50F00_ver0A500011_2024-02-29_C6F4A482
AMD cpu00A20F12_ver0A201210_2024-02-29_F845D1C5
AMD cpu00A70F80_ver0A708007_2024-02-28_4855DCDD
AMD cpu00A70F52_ver0A705206_2024-02-28_6EC8DA0F
AMD cpu00A60F12_ver0A601209_2024-02-27_0307BB9D
AMD cpu00870F10_ver08701034_2024-02-23_52FB44A3
AMD cpu00860F01_ver0860010D_2024-02-23_76CD7CC5

Superceded (not added):

Intel cpuB06A3_platC0_ver00004106_2022-09-05_PRD_5B588C90
Intel cpuB06A2_platC0_ver00004106_2022-09-05_PRD_5B588C91

1 Like
7

I have a question about the Intel microcode update, my processor is i5-7200U, laptop is Acer Aspire F5-573G, I came across a thread about the “safe” processor microcode update, my microcode version is B4

1
11034×601 113 KB

the latest version I found F4

2024-09-03 (2)
2024-09-03 (2)1477×101 19 KB

the question is whether it will fit the acer aspire f5-573G and I would like to ask which version of the file should be uploaded and what is pla10 and platC0 about because I don’t understand it

are these versions also suitable for updates??

8

Explanation…

10 (4)
C0 (6,7)

Latest bios v1.27 for your system presents the 806E9 as C0 (6,7)

EDIT:

05/31/2019,05.11.01.51
Yes
Microcode │ 806E9 │ C0 (6,7) │ B4 │ 2019-04-01

1 Like
9

I will ask again because I have a different BIOS version than 1.27, I have 1.51 installed

1
1840×119 23.8 KB

downloaded from this page:
https://www.catalog.update.microsoft.com/Search.aspx?q=UEFI\RES_{12b99262-648c-4365-bafd-eb869fb72094}

does pla10 and platC0 change with the bios update??
I mean that 806E9 as C0 (6,7) is the same as for version 1.27 and for 1.51

11

@martin4562

Intel is running the CPUID 806E9 concurrently on two different platforms:

806E9_C0 = Kaby Lake-U (socket BGA 1356)
806E9_10 = Amber Lake-Y (socket BGA 1515)

You know that you have a Kaby Lake-U processor (i5-7200U) so your only option is to use C0 which is what is in the BIOS you linked for v1.51.

Microcode versions released after B4 will have a performance penalty as Intel attempted to add more security patches - personally I wouldn’t worry about updating it to the latest.

12

@chinobino
I’ll ask again because as I remember, the BIOS update for my laptop model from 1.27 to 1.51 always had the processor microcode version B4. Can switching from B4 to F6 cause anything other than a drop in performance, for example with the BIOS? I’m asking because I’ve never done it and I recently discovered VMware CPU Microcode Update Driver, which as @THEBOSS wrote, can be updated without having to tinker with the BIOS. You also added that “personally I wouldn’t worry about updating to the latest version.” So I understand that the B4 microcode version that is in the BIOS is safe and ok.

1 Like
13

@martin4562 You can update to F6 if you want to, the performance decrease is determined by workloads that use specific instructions e.g. The Downfall exploit (CVE-2022-40982) effects SGX which is enabled on many Intel machines by default. According to Intel:

Intel® SGX is designed to protect data in use with isolation, encryption, and attestation capabilities to help guard against threats while also allowing users to maintain control of and use of their data.

Tom’s hardware wrote an article about Intel’s Downfall mitigations suggesting that:

there’s a potential claimed performance impact of up to 50% on AVX2 and AVX-512 workloads involving the Gather instruction.

The problem with using the VMware CPU Microcode Update Driver:

The big issue with the VMWare solution is that currently the OS mitigations are not enabled. On boot, the kernel is started and does a CPUID check. The BIOS microcode is loaded at this point, and fails the HW mitigation check, and the OS disables the support. THEN the VMWare driver is loaded.

We would need to see if we can force the OS level support to be enabled in conjunction with the VMWare driver loaded.

So while the newer microcode is ‘running’ the OS mitigations aren’t, which defeats the whole purpose of updating the microcode for increased security.

I can understand why THEBOSS would want the latest microcode for their 13th Gen system as the microcode effects CPU voltage but for older CPUs this method may not be practical.

Hope this helps.

1 Like
14

If you want… I can help provide you the latest micrcode available for your CPU specifically if you want. Just let me know and I will send it you. :slight_smile:

1 Like
15

Hi @jen11. In Jan 24, you posted cpu506E3_plat36_ver000000F2_2023-01-02_PRD_86DC342B on this post.

I’m trying to cross-reference that MC, and I’m only being pointed back here. Can you let us know where that one came from? I’m updating an older Dell with an i5 6500 CPU.

Thanks

EDIT 1:

╔════════════════════════════════════════════╗
║ MC Extractor v1.101.0 r305 ║
╚════════════════════════════════════════════╝

cpu506E3_plat36_ver000000F2_2023-01-02_PRD_86DC342B.bin (1/1)

╔════════════════════════════════════════════════════════════════════════════════════════════════╗
║ Intel ║
╟───┬───────────┬───────┬──────────────┬──────────┬────────────┬───────┬─────────┬────────┬──────╢
║ # │ Type │ CPUID │ Platforms │ Revision │ Date │ State │ Size │ Offset │ Last ║
╟───┼───────────┼───────┼──────────────┼──────────┼────────────┼───────┼─────────┼────────┼──────╢
║ 1 │ Microcode │ 506E3 │ 36 (1,2,4,5) │ DC │ 2020-04-27 │ PRD │ 0x19800 │ 0x0 │ No ║
╚═══╧═══════════╧═══════╧══════════════╧══════════╧════════════╧═══════╧═════════╧════════╧══════╝

Press enter to exit

[[OFFER] Intel CPU Microcode Archives]

506E3 Skylake-S, Skylake Xeon E3 v5

cpu506E3_plat36_ver000000DC_2020-04-27_PRD_65F0B5D1
cpu506E3_plat36_ver000000E2_2020-07-14_PRD_FD2D8E22
cpu506E3_plat36_ver000000EA_2021-01-25_PRD_84B6F8F9
cpu506E3_plat36_ver000000EC_2021-04-29_PRD_D912FEAB
cpu506E3_plat36_ver000000F0_2021-11-12_PRD_D39CBFD5
cpu506E3_plat36_ver000000F2_2023-01-02_PRD_86DC342B

It’s possible that the version F2 is a repackaged DC. Looking for cpu506E3_plat36_ver000000F0_2021-11-12_PRD_D39CBFD5. I’ll check it and will follow up when found.

Edit 2: I found F0

╔════════════════════════════════════════════╗
║ MC Extractor v1.101.0 r305 ║
╚════════════════════════════════════════════╝

cpu506E3_plat36_ver000000F0_2021-11-12_PRD_D39CBFD5.bin (1/1)

╔════════════════════════════════════════════════════════════════════════════════════════════════╗
║ Intel ║
╟───┬───────────┬───────┬──────────────┬──────────┬────────────┬───────┬─────────┬────────┬──────╢
║ # │ Type │ CPUID │ Platforms │ Revision │ Date │ State │ Size │ Offset │ Last ║
╟───┼───────────┼───────┼──────────────┼──────────┼────────────┼───────┼─────────┼────────┼──────╢
║ 1 │ Microcode │ 506E3 │ 36 (1,2,4,5) │ F0 │ 2021-11-12 │ PRD │ 0x1AC00 │ 0x0 │ No ║
╚═══╧═══════════╧═══════╧══════════════╧══════════╧════════════╧═══════╧═════════╧════════╧══════╝

Press enter to exit

I think F0 needs to be the latest, and F2 discarded.

Edit 3: Downloaded F2 again and ran it through MC Extractor:

╔════════════════════════════════════════════╗
║ MC Extractor v1.101.0 r305 ║
╚════════════════════════════════════════════╝

cpu506E3_plat36_ver000000F2_2023-01-02_PRD_86DC342B.bin (1/1)

╔════════════════════════════════════════════════════════════════════════════════════════════════╗
║ Intel ║
╟───┬───────────┬───────┬──────────────┬──────────┬────────────┬───────┬─────────┬────────┬──────╢
║ # │ Type │ CPUID │ Platforms │ Revision │ Date │ State │ Size │ Offset │ Last ║
╟───┼───────────┼───────┼──────────────┼──────────┼────────────┼───────┼─────────┼────────┼──────╢
║ 1 │ Microcode │ 506E3 │ 36 (1,2,4,5) │ F2 │ 2023-01-02 │ PRD │ 0x1AC00 │ 0x0 │ Yes ║
╚═══╧═══════════╧═══════╧══════════════╧══════════╧════════════╧═══════╧═════════╧════════╧══════╝

Press enter to exit

I must have extracted my current DC microcode and saved it as cpu506E3_plat36_ver000000F2_2023-01-02_PRD_86DC342B.bin.

Edit 4: I don’t know how long it takes Intel to officially post updated microcodes on their Github site, but this is what I’m seeing now:

and …

I’ll be applying the F0 microcode until I get good info on the F2.

The file attached below contains the “F0” microcodes from the Intel and platomav Github sites, and they are hex editor identical.

Ver F0 and 06-5e-03.zip (214.4 KB)

EDIT 5: The F2 microcode is being covered by Dell under their OptiPlex 5050 System BIOS.

17

Hi, added r306

@plutomaniac Could you possibly upload these 5 missing Intel microcodes? TIA

Intel cpuB06A3_platC0_ver00004106_2022-09-05_PRD_5B588C90
Intel cpuB06A2_platC0_ver00004106_2022-09-05_PRD_5B588C91
Intel cpuA06F3_plat01_ver030001B3_2024-05-29_PRD_8A72077D
Intel cpuA06F3_plat01_ver130001A0_2024-04-30_PRD_9127A7BB
Intel cpuB0671_plat32_ver00000114_2023-02-16_PRD_870CCC70

18

ucodes.rar (3.3 MB)

1 Like
19

Hello @chinobino, r307 is released on the plutomaniac website with new miccrocodes for Intel.

20

@wiens

@chinobino has made a new REPO, as you may already know, where all the mcodes are organized by folders, so grab the damm mcodes from @plutomaniac REPO, download them to the correct folders by CPUID, simply as that.

Can we know whats YOUR issue in doing this, for adding a couple of mcodes to your own archive???

1 Like
21

r307 added.

22

@MeatWar
I do this so that @chinobino is updating his archive always good (it’s trigger for him when there is a new update, see it as positive). chinobino archive got also old microcodes as well which I sometime use, which @plutomaniac doesn’t have anymore because they are superseeded. I don’t download all the microcodes from plutomaniac site, because this site exists which got most of the microcodes. To trigger chinobino I post in this topic, it is not off-topic. I post when there is a update and it is not often.