Ohh, I'm not familiar with method, so didn't know anything about how to do it or how to try etc I do not know how BIOS is secured Even when mod BIOS programmed in with programmer Crash Free BIOS 3 invokes on reboot
Now, that could just be due to we're breaking the BIOS with all currently tried methods to replace microcodes, or could be due to checksum or something else needs fixed first, not sure. I was hoping you already would know due to BIOS type etc, maybe you will see when you get home and start looking at the BIOS.

Hi again mates (@Lost_N_BIOS and @MiesMosel), excuse me for the delay to answer you guys, well, I've flashed the "factory lastest version BIOS -1801-" using EZ Flash 2 tool from the BIOS, and then, I've used the CH341A to make a dump.

Here is the dump (google drive link):

BIOS dumped file

I don't know if the MiesMosel's question is about this, but the message that appears when I try to flash a BIOS image with the microcodes updated (E2 extracted, edited and replaced) is about "Boot block", which if you take a look at MMTool 3.26 is EBB or Extended Boot Block, I think that MiesMosel is right, the ASUS's BIOS are secured and maybe, we can do nothing about this, I don't know.

The ways that I've used to flash the updated BIOS have been using ASUS EZ Flash 2 and using a CH341A programmer.

Regards.

Thanks @RaskaipikaFWR - it's not so much about Asus being secured, we go around that every day flashing different methods, this is the first/only board I've ever ran into that couldn't even run microcode updated mod BIOS, since you programmed one in and saw the same issue on reboot.
I've updated microcodes for users without issue for many many years on many Asus boards much older than yours and much newer too, all without issue. There's something different about this BIOS, and since it's older, I'm sure it's just something to be done while modding probably forgotten over time and it's not coming to mind just yet

Asus EZ Flash will always fail to flash mod BIOS, this is a given, so don't waste your time with that ever. It's always AFU using a certain version or method, other known flash tool for given BIOS version (for example some might use a phoenix based flash tool etc), or programmer.
Programmer should be no issue, so this means something in the mod process is not right, hopefully we can figure out..... or remember

@ Lost_N_BIOS, I've used ASUS EZ Flash to be sure that the dumped created with the programmer CH341A was a "goog dump", and the few information available at Internet about how to update microcodes for AMD non-UEFI BIOSes, makes this process more complicated, at least for me.

I don't think taht we broke the BIOS the last year trying to update the CPU microcodes because when I've update the BIOS "without cpu microcodes" the result it has been satisfactory ever, I want to say that the updated BIOS with the last available PCI ROMs works well, no BSODs in Windows or problems with those PCI ROMs updated, and all the information about the motherboard itself is ok (MAC, serial number...).

I hope that you guys can be find the root of the problem with this motherboard taking a look in deep to the dumped BIOS because it's a good motherboard that works like a charm with a FX 6300 processor.

Thanks for your time and help.

Regards.

EZ Flash may or may not program a dumped BIOS, it's not designed for that but may accept it. It will never accept mod BIOS, usually, this is by design, so I simply meant don't waste your time trying to EZ Flash any mod BIOS.

Last year? Do you mean I or someone here, updated a BIOS for you to modify other items but not microcodes, on this exact board before in the past, and you were able to use that one?
If yes, how did you flash it then, and did you try that same method now? And, what all was updated, please link the thread/discussion location. Thanks for mentioning this, it helps us know mod BIOS itself is not the issue then, only the actual microcode updating mod this time around.

Zitat von Lost_N_BIOS im Beitrag #35

---

EZ Flash may or may not program a dumped BIOS, it's not designed for that but may accept it. It will never accept mod BIOS, usually, this is by design, so I simply meant don't waste your time trying to EZ Flash any mod BIOS.

Last year? Do you mean I or someone here, updated a BIOS for you to modify other items but not microcodes, on this exact board before in the past, and you were able to use that one?
If yes, how did you flash it then, and did you try that same method now? And, what all was updated, please link the thread/discussion location. Thanks for mentioning this, it helps us know mod BIOS itself is not the issue then, only the actual microcode updating mod this time around.

---

2 years ago? Are you sure you remember correctly EZ Flash was how you updated? Do you still have that modified BIOS you made? If yes, can EZ Flash flash it now?
Yes, I knew I made some BIOS for you to try and update microcodes, I was asking only about the previous mod you said you flashed, I didn't know you did that yourself so I was asking for a link to the thread to see what all was done.

Don't worry, we will try to find a fix. I did re-read page one before I called in MiesMosel too, so yes I did remember all the issues
It's good your board and EZ flash took mod BIOS back then, see if it does now with same BIOS you created two years ago (or mod new one without microcodes), maybe it's not updated to where it blocks mod BIOS like all currently do.
If new or old mod, minus microcodes can be flashed in still via EZ Flash, then yes, we need to figure out how to correctly update the microcodes is all and than you can EZ flash that too. Don't worry about "More work/Harder for us" etc, we (at least I) enjoy the challenges!

I will try again tomorrow when I have some time, and see if I can figure out proper method!

I'm so sorry but I don't have that BIOS thtat I made by myself, but like the only thing that I did was update the PCI ROMs and nothing more, when I flashed the "stock BIOS" from ASUS webpage, the changes are reverted and the actual BIOS into the chip is like the original, well I think that, maybe that's not true, you've more lnowledgment abou the process than me.

Yes, I'm sure that when I inserted time ago the slic 2.1 table for Windows 7, I flashed the BIOS with EZ Flash 2 BIOS tool without problems, after, when I began to use Windows 10, I flashed with EZ Flash 2 too the stock BIOS to "delete" the SLIC table and have a "clean BIOS (without SLIC table), and like I've said before, when I mod the BIOS by myself to update the ROM modules, I flashed it with EZ Flash 2 too without problems.

I've to say that this time I've tried to do the process of update the CPU microcodes with the CH341A programmer because I bought it a few months ago, when we tried the last year update the CPU microcodes, I didn't have the programmer, I used the EZ Flash 2 tool from BIOS that time; finally, all the BIOS MODs that I've made and flashed these last years (SLIC Table and ROM modules), they have been done downloading the last available BIOS (1801) file, editing it and flashing it with EZ Flash Tool 2 without problems.

I haven't used the AFU DOS program never, that's for sure.

@Lost_N_BIOS and @MiesMosel, take a look to my BIOS file posted at this post when you have time and you can, one more time, thank you so much for your time and help.

Regards.

P.S.: I've made a new MOD BIOS only updating the ROM modules (AHCI, RAID and LAN) and it can be flashed without problems using EZ Flash 2 tool from BIOS, I've done this to be sure at 100% taht the root of the problem is the CPU microcodes update process, I've done this at two different ways:

- First: Downloading the BIOS from ASUS webpage, update the modules and flash the BIOS file form the BIOS.
- Second: Using the dumped BIOS made with the progammer, update it with ROM modules and flash the BIOS file from the BIOS.

Both methods work like a charm using EZ Flash 2, now, we can be sure at 100% that the problem is the CPU microcode update process and not the flashing method used.

I don´t know how nobody tried this process (update CPU microcodes) at AMD ASUS non-UEFI BIOS (Legacy BIOS) before, or at least, if somebody has been able to do the process correctly, why he/she didn't share the correct steps and order to make it possible, maybe if we will be able to do it, of course, we will share it with the community at this fantastic forum.

You're assumption about reflashing stock is about what happens, but if between 2 years ago and now, even the same BIOS "Version" from Asus could be updated silently between then and now to allow EZ Flash to flash mod BIOS back then but blocked now.
Please lets test, take stock BIOS and do some mods to it again like you did before except no microcodes, does that now EZ Flash in or not? Or, flash in any mod BIOS you have now for a test. - great, you did this already, thanks, I didn't see as I was replying

I agree, and dislike AFU, so I wouldn't suggest using anyway.

As I mentioned before, we (all modders) update microcode like this all the time in similar BIOS, without issue, there is something fishy/funky going on here, usually microcode is one of the easiest things to update, especially on older BIOS.
So this is unusual case, and why you don't see some special secret sauce guide out there, because it's not required usually anything special other than a general "how to update microcodes" using various methods.
Normally, for BIOS like this, MMTool microcode tab works properly, in at least some MMTool version, so ucode could be updated that way or via hex/module extraction either one, and it's usually fine.
As I mentioned, I will make some more attempts at this for you! Please wait

Ohh, and to answer some of what you mentioned at the linked BIOS post, Boot Block, EBB and Romholes are all different things.

@MiesMosel - I do see "BIOS header" data changes sometimes, is there checksum there, I can't tell? Or maybe one in ImageInfo module? I can't find one in the actual module that contains the microcodes either, so still at a loss here
Maybe it's crashing/failing out due to new ucode and original old Agesa? Maybe I should build modified BIOS with all same microcodes, just switch them around and rebuild, see if issue same or not. And another, with update single ucode to one version older than current, see if same issue or not.
Do you think that would be worth testing, and maybe confirm some possible Agesa/ucode conflict, if it was working/bootable this way - then I think it could confirm this mod methods OK but ucode/agesa issue.

I have to remember you guys that this motherboard is an AMD board, we can't use the MMTool microcode tab and other thing is the order of the modules like they are showed by MMTool when they are updated:

If I update ONLY the ROM modules, the order don't change, but if I update (extract, edit and replace it) ONLY the E2 module, the program changes its position, I think that the problem maybe can be that we lose other dependant module that is necessary for the microcodes, I don't know.

One last thing, to update the RAID modules, at AMD motherboard you need to replace the module itself and the MIS.SIG, and at the same time, this motherboard has two RAID modules that you've to update to the motherboard works well, 4392 and 4393. The MISC.SIG for RAID modules (4392 and 4393) are F0 and F1, and there aren't problems replacing them, I want to say that the order of MISC.SIG modules don't change when you replace them.

Yes, we work on BIOS all the time, we know it's AMD board. MMTool microcode tab normally works on any AMI BIOS, Intel or AMD, and shows microcodes in the microcode tab, this isn't not showing here only because it's AMD board.

And yes, I know about the order of modules switching around, we already discussed this. Please, you keep in mind that we are not new to this and edit BIOS all the time, I have been editing BIOS with VERY high success rate for 10+ years.
So you don't have to think we are new to this, or maybe don't know what we're doing or what the norm should be for various tools or BIOS types etc.
Only say this because of the replies you give, make it sound like you think we're new to editing BIOS and only trying to help, we've been doing long time so don't feel like we're unknowledgeable

Thank you for info on the MISC.Sig and RAID. That sounds like a signature, I will check it out. How did you learn this is needed when replacing RAID modules? When you do this process for the RAID, are you extracting that module first and then putting back when you are done (Or replacing with original when you are done)?
That might be the key to all this if it is a signature, thanks for mentioning. Did you already try, updating microcodes in place via hex (and or replace modified E2 modules) and then also do the RAID/MISC too, then save? If that is signature and you pull then replace after RAID edit, then same might work for microcode edit too.

I have not that knowledge like Lost_N_BIOS, but some experience from the last years.

Hello @Lost_N_BIOS .Can you please remod an old bios from a gigabyte h67ma-usb3-b3. The new microcode 2f for 206a7 cpuid has been released and if you can can you update it? Also can you update the qflash module sbf.bin to 2.24? thanks again i have attached the stock and your old mod bios with every microcode updated to the latest at the time of the modding and also the sbf.bin.

@ektorasdj - Qflash module is above a sensitive module (GV3 - PPMInit), so had to do the long tedious way to preserve sensitive module location, you owe me 2 hours worth of free beer

http://s000.tinyupload.com/index.php?fil...452172024255060

Flash using FlashSPI from DOS, due to Qflash change this is almost always required (or @BIOS = not suggested)

@Lost_N_BIOS Thanks and i am sorry for your wasted time. If i knew it was so time consuming i would not tell you to help me.. sorry again
Can i ask something ? whats exactly is dummy.bin? and now there are 26 instead of 25 roms is that a problem? Also Oemcode 0 changed to 1

Edit:
I flashed the modded bios and i couldn't boot to anything and when i tried to go to qflash it froze.
i had to use a ch34a1 programmer .
can you mod the bios with only the microcode?
Thanks

Edit 2:
Managed to update only the microcodes and works fine. I will look into it about the qflash 2.24 and also i will try to update the ahci rom to 2.00h.
Thanks for all your help and sorry for this.