Thanks for report. I tagged a few users in an edit above, maybe they can advise.

Reading Notes on Intel Microcode Updates and searching for clues that leads us to go deeper in this.

Thanks.

UPDATE

I'm just trying to find the bytes of code that could be identified as executing the MSR_IA32_UCODE_WRITE instruction, because near it there is the offset that leads the CPU to read the microcode from, as seen in the link above.



Still working on this, because if discovered, it would lead to a better understanding of Phoenix BIOS microcode updates.

I've seen that the very first instruction any x86 cpu will run te code located at F000:FFF0 location in memory. (seen here). It seems to be that in that location, the instruction is always

JMP   F000:E05B
 

The bytes of that instruction are EA 5B E0 00 F0. So I loaded ML110G6_SLIC.rom (my proliant's SLIC'd BIOS mod) file, loaded in HxD and tried to locate that sequence of bytes. Well... It seems that it isn't there, but... Maybe the code where this instruction is compressed, so I took the whole DUMP folder, loaded it in HxD and made a search in every file.

There are two matches: One in the BB.BIN file in another one in the BIOSCOD00.ROM file. It seems that the BB.BIN file contains the code that runs when the motherboard is set to recover a bad BIOS flash (that's what they say here).

Now I have just one file, that is BIOSCOD00.ROM. The EA 5B E0 00 F0 is there, but something is not right... the offset is not FFF0 at all. Is far less, so... false positive.

Now... How can I get a working dump of the BIOS? Well... It seems that with certain BIOSDUMP.BAT file that I found in the same website, I have been to dump the first megabit of memory, and I feed HxD with that.

Now yes... there is this EA 5B E0 00 F0 sequence there in the right offset. And what's most important now... several WRMSR, aka MSR_IA32_UCODE_WRITE instructions. I think they are part of the different subroutines that points the CPU to different offsets where to load the microcodes from...

Well... In all these days nobody replied or gave a clue. I keep trying to mod the BIOS until a point where I had to move the starting points where the microcodes were and finally softbricked my motherboard.

But this time I did messed something because the boot block of the rescue bios was moved and even the procedure didn't work.

I ordered a CH341a programmer and a Intel Xeon X3440 CPU from Korea.

Now I've just finished to reflash the BIOS with the programmer and tested the X3440, that boots just fine, and is a supported CPU.

So... what now? I don't know. Keep testing? Or just as I found the replacement CPU I was looking for (X3440 instead of i3-550), I should let this pass?

Sounds like you're all set now, happy accident caused good CPU replacement and BIOS recovery
Plus, now you have flash programmer so can recover other boards in the future too, it's a win-win!

The attempt to update microcodes on ga-ma770-ud3 r2 failed, system didnt boot after post. I used first guide with the amendment from "FAQ and Problems" for last problem with old and new microcodes mixing.

@molex

Hard to say what the problem is. Here are some verifications you can do:

- Did you verify it with MC Extractor before flashing?
- Did you restore the checksum by replacing the last module in the end?
- Are all your microcodes the same size as the originals? If no, verify with HxD that they are installed correctly.

Those are the most common problems.

@molex - And using wrong cbrom versions usually causes above errors if you find them, sometimes unavoidable and you must correct post ucode edit, but it's easy to do.
If you need it done let me know - Actually, here, FKe w/ all microcodes updated to latest.


https://ufile.io/kabxu6o2

Nothing special needed here, however you do have to use certain version cbrom, others may work too, but I use 155 here (115 fails) This is what I did in this case, since some ucodes different sizes and 800h offsets used
I copied out ucode region from original BIOS, saved as ucode.bin (0xDC7E0h - 0xE2FDFh) 00-fill the 3 out of date ucodes in place, pasted in the new ones in original positions, saved file as NCPUCODE.BIN, marked it read only.
Using CBROM155 >> cbrom155.exe MA77UD32.FKe /nc_cpucode NCPUCODE.BIN
Using CBROM155 >> cbrom155.exe MA77UD32.FKe /LOGO extract (Saving as original name UD3_D.bmp)
Using CBROM155 >> cbrom155.exe MA77UD32.FKe /LOGO release
Using CBROM155 >> cbrom155.exe MA77UD32.FKe /LOGO UD3_D.bmp
Done Last three steps ^^ Always do something similar, with last module, to force recalculate of checksums

@Lost_N_BIOS Thanks, all works nice!

I have problem to update microcode amd on a k8n pro sli, CBROM do nothing when launch CBROM k8npsli.10d /nc_cpucode NCPUCODE.BIN (empty) this for clear all microcode inside of the bios.
Who can help?

ps. There are greats peoples in this forum!

@pipes80

It seems your empty file may not be write protected. That would explain why it seems to do nothing. In fact, it probably did something but the result is the same as it was because of it. To understand how CBROM works in the background, i suggest you to read post #339.

Hope this help.

yes, I have try with write protect too

@pipes80

It is rare but sometimes there is an incompatibility between some motherboard's bios and some Cbrom versions. Maybe you can try with another Cbrom version to see if it can work. As long as the version is not more than 1.55, it can work fine. Worth a try.

I have try many version before and after cbrom155.
-do you think to try a dos version?

@pipes80

You can try but i doubt it would make any difference at this point.

You can either try to find another program that can work with your bios or modify it manually with the HxD editor then restore the checksum by replacing the last module with cbrom155. That should work.

happy new year to all.
I have solved with hex editor for update two of four microcode amd k8.
I did not understand why for each action, for example by updating the nvmm module or the pci rom, cbrom creates an output file equal for example to the pci rom but compressed, it created an original temp module for me?