@Phoenix48 @MiesMosel Can you share the link or the file phoenixtool 2.73 with us?
Hello Dexter,
here it is. It comes from https://forums.mydigitallife.net/
Be aware, that editing this Dell BIOS is very special & risky. Your Notebook may not have a Dual-BIOS for Backup.
But in this forum above, youāll fing some guides for editing and rescuing and more ā¦
@ Phoenix48
Who do you mean?
Regards, MiMo
phoenixtool273.zip (2.83 MB)
I was refering to the post 98 of Dexter when he wrote that he will do a detailed guide for Dell bios for all those with the same issues
I did it!!! Guide is coming soon! Thanks for the support man!
Incredible - great !!
First post updated with a download link for all the valid CBROM versions i have. (Link is at the end of first post)
If you have a valid version that is not there, please post it here and i will add it. And please, be sure it is a valid CBROM before posting.
@Phoenix48
I wonder why I found this sooo late - This is so usefull!
Iām still on my good old Gigabyte GA-EX58-EXTREME with XEON W3520 4Ghz (cpu106A5) and still do not see a reason to upgrade. Especially with SSDs at SATA3 PCIe card.
Successfully did it with your guide and the āreducedā CPU modules from 8 to 6 (same as you) and CBROM155.
Was a bit hard to find that latest cpu206C0 (again same as you 
) even if I donāt need it for my CPU. But I love to see only YES in MC.exe.
Special thanks for that hint to remove the leftovers in front of the integrated modules. That did the trick finally!
If someone is interested in that BIOS - callā¦
GA-EX58-EXTREME - F13U - Modded with RAID ROM 11.2.0.1527 and other updated modules as per Fernandos recomendations for X58 - and following microcodes:
1
2
3
4
5
6
Ā
2
3
4
5
6
Ā
cpu106A2_plat03_verFFFF0019_2008-07-14_PRE_D990B74E.bin
cpu106A4_plat03_ver00000013_2015-06-30_PRD_35DDB232.bin
cpu106A5_plat03_ver0000001C_2018-01-24_PRD_77105048.bin
cpu206C0_plat13_verFFFF001C_2009-12-14_PRE_77BBF9A7.bin
cpu206C1_plat03_ver00000006_2009-12-22_PRD_45E27C49.bin
cpu206C2_plat03_ver0000001E_2018-01-23_PRD_B8C45629.bin
Ā http://imageshack.com/i/pob6CutAp
Have you posted your guide somewhere? I canāt find it.
Guys, I do not understand how to properly remove from bios microcode?
I have prepared ncpucode.bin for my BIOS and I do not want to use the old microcode (Pentium / Celeron D). they need to be deleted.
The cbrom195 command bios.bc / nc_cpucode ncpucode.bin - deletes old versions and adds new ones.
Cbrom195 command bios.bc / nc_cpucode release - does not delete the entire microcode
I have bios 35 microcode, I want to use only 16. How to remove microcode?
EP45DS3P.rar (547 KB)
new_ncpucode.rar (51.2 KB)
Could you attach your bios ,and tell us what you need and what want delete??
Now I have a bios like this (Figure 1)
Prepared by new_ncpucode.rar
How to do that in bios was like (Figure 2)
Sorry , i donāt understood what you need.
Run cbrom [bios_file ] /nc_cpucode ncpucode.bin ,it can direct write ncpcode.bin
https://drive.google.com/open?id=1SMdWwsā¦HQ3B9lBrPlhXh7l
If you want edit ncpucode.bin ,you need use a hex editor.
The cbrom [bios_file] / nc_cpucode ncpucode.bin command will update the microcode, but will not delete, for example the old microcode CPUID = 37, CPUID = 34, CPUID = 25, CPUID = 41 CPUID = 43, CPUID = 49 and beyond.
Iām sorry this is the translatorās fault. Now itās clear what I wanted to say,
You got an error knowledge ,nc_cpucode ncpucode.bin command was not update ucode , it is update ncpucode.bin on bios.
So we need edit it by hexeditor then update it from cbrom.
if set ncpucode.bin to read only ,ncpucode.bin will write to bios ,in constrast it will write i bios internal ncpucode.bin to ours ncpucode.bin.
You donāt need use āreleaseā parameter i think .
@Dagal
The best way to use that command is with a NCPUCODE.BIN file on your pc that IS write protected.
Here is what truly happen with this command and it is important to understand how it works. 2 things happens:
1- The command will extract the npcucode.bin from the bios and TRY to put it AND REPLACE (and probably also combine, i donāt remember exactly) your ncpucode.bin on your pc with what is inside the one in the bios. But it wonāt be able to do that when your ncpucode.bin file on your pc is write protected. This is what you want when you already put ALL the microcodes that you want in that file on your pc and donāt want the command to modify it.
2- Then it will put back into the bios the new NCPUCODE.BIN file that was created there. But because it was write protected, the file NCPUCODE.bin was not modified by the first step and is what you, yourself, put in it and not what the command has extracted.
An other way to use the command is to use it with an empty NCPUCODE.BIN file in your pc that is NOT write protected. It can be usefull to extract and get only the microcodes in the bios. Used this way, what truly happen is the command extract the microcodes in the bios into the file and then copy them back into the bios in the second step.
This is what the command can do and, by write protecting your file or not, you can adapt it to achieve what you want to do. But the command can NOT by itself update a microcode in the normal sense. Meaning it can NOT detect by itself an update from one file compared to the other and replace them automatically. It just blindly do the 2 steps i described.
Hope this help to understand the command.
Thank you Phoenix48. How do you know that the BIOS is write-protected?
Hello @Dagal ,
generally youāll know it, when you get errors by editing or bad checksum before flashing the BIOS-file.
But your Gigabyte EP45DS3P.F9C BIOS-file is not writeprotected.
The original has 35 microcodes & the one from genius239 has 35 MCs, too.
Where is the problem?
Itās better to have all MCs for best compatiblity!
Best regards, MiMo
@Dagal
Not the file in the bios. Only the NCPUCODE.BIN file that you do yourself in Windows. Simply right click your NCPUCODE.BIN file, click "properties", then check or uncheck "Read only" to change the write protection.
MiesMosel
Phoenix48
Thank you for the clarification.
Tell me please, what will the updated microcode give? When you change xxx.rom to a new version - this is understandable. An updated microcode that improves?