You can always fix with flash programmer (Ch341A), costs $3-4 plus a SOIC8 test clip cable $2.50, then time waiting for shipment of course , but it's never a total loss you can fix it!

For microcode, open in UEFITool, in BIOS region, expanding only "BIOS Region" microcode is in the second "Padding" file (offset 544000). Extract that as-is, and hex edit in the microcodes you want starting at the very top, there is no space between microcodes.
In hex, do not write past 00014000, this is DMI area onwards. Save your modified file, and insert back at same location using replace as-is with UEFITool.

Zitat von Lost_N_BIOS im Beitrag #32

---

You can always fix with flash programmer (Ch341A), costs $3-4 plus a SOIC8 test clip cable $2.50, then time waiting for shipment of course , but it's never a total loss you can fix it!

For microcode, open in UEFITool, in BIOS region, expanding only "BIOS Region" microcode is in the second "Padding" file (offset 544000). Extract that as-is, and hex edit in the microcodes you want starting at the very top, there is no space between microcodes.
In hex, do not write past 00014000, this is DMI area onwards. Save your modified file, and insert back at same location using replace as-is with UEFITool.

---

Yes, all above is microcode space. And yes, if you want you can only edit/update one microcode. Be sure if size is same or not, you may need to add FF after is it's smaller (So you remove all the one you are replacing), or you may need to move to the end if larger and no room to insert in place.
Don't remove all others, that might give you hassles later. You can drag and drop that padding file on MC extractor to see contained microcodes and their sizes and offsets

Zitat von Lost_N_BIOS im Beitrag #34

---

Yes, all above is microcode space. And yes, if you want you can only edit/update one microcode. Be sure if size is same or not, you may need to add FF after is it's smaller (So you remove all the one you are replacing), or you may need to move to the end if larger and no room to insert in place.
Don't remove all others, that might give you hassles later. You can drag and drop that padding file on MC extractor to see contained microcodes and their sizes and offsets

---

@jordanpchome - Yes, you can delete all, then rearrange all into one file. I do this at command prompt, with all single microcodes in folder, combine into one file, FF all old microcode, then copy back all new from my file
Here is example of what I do, initially created this process for old cbrom NCPUCode updating, but still use it now for these kinds of updating too

Make list of folder contents
dir /b > dir.txt

Create blank .bin file (Name anything you want for this process, we're only opening and copying contents via hex)
Nul > NCPUcode.bin

Combine all single microcode files to new .bin (Space after last +file and ending NCPUcode.bin)
copy /b ncpucode.bin + 1060319.bin + 1060312.bin + whatevermicrodoe + moreucode ncpucode.bin


Image and File look OK to me, good work!

Zitat von Lost_N_BIOS im Beitrag #52

---

@jordanpchome - Yes, you can delete all, then rearrange all into one file. I do this at command prompt, with all single microcodes in folder, combine into one file, FF all old microcode, then copy back all new from my file
Here is example of what I do, initially created this process for old cbrom NCPUCode updating, but still use it now for these kinds of updating too

Make list of folder contents
dir /b > dir.txt

Create blank .bin file (Name anything you want for this process, we're only opening and copying contents via hex)
Nul > NCPUcode.bin

Combine all single microcode files to new .bin (Space after last +file and ending NCPUcode.bin)
copy /b ncpucode.bin + 1060319.bin + 1060312.bin + whatevermicrodoe + moreucode ncpucode.bin


Image and File look OK to me, good work!

---

SATA orom version is shown there, I am unsure if it's something you can see/view in windows. Maybe with AIDA64 or HWINfo64, but I am not certain on that, maybe with Intel RST program somewhere too?
Version you see there in that image is the version used though, you don't need any further verification than that, it's the only possible one being used.

If you cannot enter that section anymore, mod may not be done correctly, or sometimes in certain BIOS/versions of the orom you have to have at least two disks connected to the controller, and RAID enabled in BIOS of course, so it can think you are going to enable RAID on those disks, then it will let you in there.

Zitat von Lost_N_BIOS im Beitrag #54

---

SATA orom version is shown there, I am unsure if it's something you can see/view in windows. Maybe with AIDA64 or HWINfo64, but I am not certain on that, maybe with Intel RST program somewhere too?
Version you see there in that image is the version used though, you don't need any further verification than that, it's the only possible one being used.

If you cannot enter that section anymore, mod may not be done correctly, or sometimes in certain BIOS/versions of the orom you have to have at least two disks connected to the controller, and RAID enabled in BIOS of course, so it can think you are going to enable RAID on those disks, then it will let you in there.

---

I'm not sure what your first paragraph is about? SRT.IRST is software, option rom is BIOS, these two are totally separate and anything inside a BIOS can be deleted, updated etc any time you want, doesn't matter what software you have or do not have installed.

EFI rom and orom are also two different things, one is EFI for UEFI booting and orom is for legacy booting. They can be different or same version, depending on what you use.

My advice to you is to slow down, do some reading and research on what is best roms for your board and chipset, then put only those and be done with it.
It should not be difficult or confusing for you, there is guides here where Fernando shows what he knows is best tested versions of each rom and driver to use in windows too.
I think you are making it too tough on yourself by trying to mod BIOS too much. Read, decide, then put only that in BIOS and you're done. When you do that, start with clean stock BIOS, or have someone do for you if you are still unsure.

Here is both guides for picking which roms to use - AHCI & RAID ROM Modules & Intel EFI "RaidDriver" and "GopDriver" BIOS Modules
Here is guide for best driver to use - Which are the "best" Intel AHCI/RAID drivers?

I successfully updated the CPU microcode
ME firmware has also been successfully updated
:)

Good work! Did you sort out the Intel storage stuff?

Zitat von Lost_N_BIOS im Beitrag #58

---

Good work! Did you sort out the Intel storage stuff?

---

@jordanpchome

Zitat

---

do you have the latest version of the "H2OEZE" tool?

---

Nope.

Several counter-questions.
1) Do your current updates work?
2) If I understand correctly, then can not you update VBIOS?

But if you use the UEFI mode, then updating the VBIOS does not make sense.