@Koven - Yes, CPUID found for your CPU model at CPU-world.com
Current microcode version in BIOS is found by dropping BIOS file on MC Extractor - https://github.com/platomav/MCExtractor
To find the old microcode, I'll simply go to our pre-spectre microcode repo and get the one there for your CPUID

Windows updates is fine, you can't disable windows updates anyway can you? What you need to do is delete the microcode file windows uses, and check often to make sure it's not added back again (or check often current in-use microcode with AIDA64 or HWINFO64)
Here's how to delete the windows microcode file - Intel, AMD, VIA & Freescale CPU Microcode Repositories Discussion (19)

Yes, I would use the mod BIOS I already made for you, and just edit that. Yes, flash with service mode jumper on and FPT. And yes, that page you linked is the repo I meant.
Microcode edit can be done with MMTool 4.5, or UEFITool 25 and hex editor, sorry I've not written any guide for this, but we do have some already here for UEFITool editing
However, it's outdated and does not apply directly to your BIOS type -[GUIDE] AMI INTEL CPU Microcode Update Guide
MMTool is much easier, but no guide here about it. Basically, open BIOS in MMTool 4.50.0.23 go to "CPU Patch" tab and delete the one one for your CPUID, and insert new one, then save file with new name (and rename extension to .bin once done)
^^ MMTool 4.50 does not show all microcodes, and does not do the edit correctly (removes a bunch of others), so do not use this. 5.07 shows them all, but you can't edit, same for 5.024/25 too.

So, this edit must be done with UEFITool 51-55 for extract and version 25 for insert. In this BIOS all microcodes must begin at a multiple of 800h (so 0h, 800h, 1000h, 1800h, 2000h, and so on), if previous ends before a 800h multiple fill with FF till the next 800h multiple
Since the one you want to edit in is smaller than original you can FF the entire original 306A9 space of the extracted microcode body 2000h-5800h and then paste in the 1C version at 2000h (make sure you past over, not insert, so all alignments are kept and file size is not increasing)
Once done drop new mod BIOS on MC Extractor to confirm your new microcode is in there replacing the old, and no errors shown in MC Extractor.
In MC Extractor, you're mod microcode body should look like this once done, vs stock one. Notice the offsets all remain same, and the size of the one we edited is now different


Then flash like before, making sure you use the -bios flag >> FPTw.exe -bios -f nvmeucode.bin

I have BIOS done for you if you want, but didn't upload since it sounded like you wanted to try doing yourself

@Lost_N_BIOS my FIT tab is greyed out. I am not sure if has always been like that... The only thing that changed is that I installed my OS again. I believe it worked a few days ago... It doesn't matter if I use the bios file from the NVMe edit last time or if I dump a new one or if I use the full 12MB one... All have FIT tab greyed out...
Does your FIT tab work with my BIOS?

Zitat von Lost_N_BIOS im Beitrag #16

---

@Koven - Yes, CPUID found for your CPU model at CPU-world.com
Current microcode version in BIOS is found by dropping BIOS file on MC Extractor - https://github.com/platomav/MCExtractor
To find the old microcode, I'll simply go to our pre-spectre microcode repo and get the one there for your CPUID

---

Zitat von Lost_N_BIOS im Beitrag #16

---

I have BIOS done for you if you want, but didn't upload since it sounded like you wanted to try doing yourself

---

@Koven - Dell 7010 BIOS does not have FIT table, so you're OK there

Yes, if you want, you can update all the others if you want. That makes the edit a bit different though, just follow the rules I mentioned above, and since you're going ahead with all, you can go ahead and put your CPU's microcode first if you want.
Yes, sorry, you are correct! Not sure why I showed changing 306A9, I guess my incorrect mention of it at previous post made me assume I said correct one there and I just carried on
306A4 already has latest microcode, and it is a pre-Spectre/meltdown one too (since 2011). I see why I said 306A9 now, because this pre-spectre thread had 306A9 as only one shown for IVY - [OFFER] Intel CPU Microcode Archives)
Your CPUID not there, because default/latest is already pre-spectre, the 3770K is 306A9 and has a Spectre/Meltdown update - you don't need to do anything here for microcodes (Sorry I didn't notice that sooner!)

So, do you just need NVME Mod BIOS, or you already did that yourself?

* Edit - @chinobino - I see some posts saying all quad IVY 306A9, why this one is 306A4 in CPU-world, or did it used to be 306A4 at launch, but now all IVY Quad load/use 306A9?

@Koven - load HWINFO64 , see image below, what do you see, 7 or 20?

Zitat von Lost_N_BIOS im Beitrag #18

---

@Koven - Dell 7010 BIOS does not have FIT table, so you're OK there

---

Zitat von Lost_N_BIOS im Beitrag #18

---

Yes, if you want, you can update all the others if you want. That makes the edit a bit different though, just follow the rules I mentioned above, and since you're going ahead with all, you can go ahead and put your CPU's microcode first if you want.
Yes, sorry, you are correct! Not sure why I showed changing 306A9, I guess my incorrect mention of it at previous post made me assume I said correct one there and I just carried on
306A4 already has latest microcode, and it is a pre-Spectre/meltdown one too (since 2011). I see why I said 306A9 now, because this pre-spectre thread had 306A9 as only one shown for IVY - [OFFER] Intel CPU Microcode Archives)
Your CPUID not there, because default/latest is already pre-spectre, the 3770K is 306A9 and has a Spectre/Meltdown update - you don't need to do anything here for microcodes (Sorry I didn't notice that sooner!)

---

Zitat von Lost_N_BIOS im Beitrag #18

---

So, do you just need NVME Mod BIOS, or you already did that yourself?

---

Zitat von Lost_N_BIOS im Beitrag #18

---

@Koven - load HWINFO64 , see image below, what do you see, 7 or 20?

---

Zitat von Lost_N_BIOS im Beitrag #16

---

I have BIOS done for you if you want, but didn't upload since it sounded like you wanted to try doing yourself

---

@Koven - MC Extractor will give you exact location by offset where the microcodes are located, then you can use "Action >> Go to Offset" in UEFITool or go directly to each in hex editor
https://github.com/platomav/MCExtractor

Or you can use search in UEFITool, by GUID, and this is the microcode module GUID - 17088572-377F-44EF-8F4E-B09FFF46A070

Only the in-use microcode for your CPU matters here, all others you can ignore. So, I was correct first time around then, your CPU is using 306A9 Thanks for checking it out
Here is the mod BIOS I made for you previously (NVME mod one) with pre-spectre 306A9 microcode 1C from 2015
https://ufile.io/dc57xv6i

@Lost_N_BIOS - I finally had time to try and replace the microcodes by myself. This is how I did it:

1. Extracted my NVMeBIOS.bin with MC Extractor to get all the microcode.bin files.
2. Opened HxEditor and opened my NVMeBIOS.bin and all the extracted microcode.bin files.
3. I picked a microcode I wanted to edit and searched for the offset in HxEditor.
4. Then I marked the the whole content of the microcode I wanted to edit in its corresponding extracted microcode.bin to check the size (=Length in HxEditor).
5. I went back to the offset of the microcode in NVMeBIOS.bin and marked an area from the beginning of the offset until I reached the same Length of the extracted microcode.bin to see if it was the same length.
6. Then I did a "double check" before I replaced that area with a new microcode by searching the whole microcode in NVMeBIOS.bin to see if it was again the same length as I just manually checked.
7. Then I got the new microcode from the repository and replaced the old microcode. Some of the new microcodes were upgrades (newer date) and two microcodes were downgrades to the latest pre-spectre microcode (306A9 and 206A7)

Here is the result:



Download Link: https://ufile.io/6x1ynbrf

As you can read on the screenshot I had a "problem" with 306A2 and 206A7,because they were really close to each other.
The offset at which 306A2 ended, the next offset directly underneath was already the starting point for 206A7.
But the new 306A2 microcode increased in file size and therefore got longer in Length and overrode a part of the 206A7 microcode.
Therefore I had to put the beginning of the new 206A7 microcode also at another offset. The end of the new 206A7 microcode ends in a big field only filled with FF hex, so I guess that's ok then?

Can I flash my own bios mod, what do you think? MC Extractor doesn't show an error atleast and I also checked the new bios.bin in UEFITool and it looks all good to me:

@Koven - Moving them around is fine, but you need to make sure each starts at a multiple of either 400h or 800h, depending on how the original BIOS is constructed (I checked your BIOS, this one uses multiple of 800h (0, 800, 1000, 1800, 2000 etc)
Padding of FF is fine, you just have to follow the rule above. Since you were changing file sizes, it would have been easier for you to just construct an all new microcode body, pasting each microcode one after another in hex editor, then replace entire body once done.
UEFITool not something to confirm microcode edit is OK, except for when comparing all microcode volumes side by side with mod/stock BIOS, to confirm a padding file wasn't added or removed above microcode volume.

I cannot tell what is going on in your image, since I do not work with microcodes that way, sorry However, I checked your BIOS, extracted microcode body and it's OK, but not ideal (using multiple of 400h instead of 800h, by you starting #7 at FC00h, should be 10000h instead)
Start your last microcode (#7) 400h later >> Instead of starting #7 @ 2F95C0h, start it at 2F99C0h (so, 400h of FF padding between end of #6 and start of #7). Some BIOS 400h multiples is OK, and this one may be too, but I always practice of following the originally used offset multiple examples just in case

If you extract microcode body with UEFITool 51, then you can easier see the offsets I mentioned above when dropping into MC Extractor, then it's easier to see what's going on, how to edit, what spacing you need etc.
Then replace body when done. When editing other BIOS this way, be sure to check stock microcode body at the end, some have a footer that you need to put back into place once you are done (not in this BIOS)

See, here, this is how I look at microcodes from the stock BIOS, the mod BIOS I sent you, and the mod BIOS you just added above, see how much easier this is to view the microcode offsets and then be able to maintain that offset ruling

@Lost_N_BIOS - Ok I understand. I changed what you suggested. Here is the result:



And the new bios.bin link: https://ufile.io/2ei1854s

Just to be sure, I don't have to move all the hex that comes AFTER 206A7 to make a 800h multiple between 206A7 and the first "code" that comes after that? Or do I have to insert a 800h FF padding after 206A7 too?

EDIT: Just flashed. Looks good to me haha: