Cbrom155 crashes during insert, are you sure, or only after you insert and then try to check? I just checked to confirm, it inserts fine as expected, it's only when checking afterwards it crashes as I mentioned it might (it will often crash on mod BIOS after microcodes changed, this is normal sometimes)


However, I just checked this BIOS using 155 /D post ucode insert and it's fine too (rare to see)


You can use 115 instead as I mentioned if 155 concerns you. Again, do not use 195-199 for this BIOS, it will break the BIOS due to sensitive modules (GV3, MINIT, etc) get moved.
Never mind, this BIOS is safe to use 199 on, I checked in hex and the sensitive modules don't get moved this instance nor do any other sensitive things locations (ppminit, mementrypoint x2, csimemrc.bin)
So you're fine, ignore me..... for this boards BIOS only

Microcodes being there means nothing, that only means they are in the BIOS, you can do that via hex and insert anywhere you want and MCExtractor will detect them.
You need to be sure BIOS is modified properly, otherwise you will have same brick as the original situation, so you have to be careful is all I was trying to help you do.

But watch out, I noticed I do get badly packed microcode when using 199, if you see that in MC Extractor you need to fix via hex, then after that extract OEM7 file or Logo, and reinsert to fix the checksums.
Same packed error with 155 too, and 115 doubles the ucodes so we don't want to use that one here after all either I have to fix that packaged error half the time anyway, so used to seeing that and it must be common on more than Gigabyte BIOS too since it's FAQ #1

Oh I was using Windows 10, that's probably why it crashes with 155.

Yes, I use XP for all cbrom work, inside virtual machine

Hey, I did the same thing as you did , but with a gpu bios , i bricked the card , tried to unbrick it by shorting pins and saw some smoke coming out, i also have dual bios but my ch341a can't detect either. i just get FFFFF and 00000