Zitat von plutomaniac im Beitrag #1198

---

Fun fact: whoever has Python installed can replace MCE.exe with MCE.py and it works just fine because the UBU batch script does not explicitly mention the file extension. That's what I've been doing all this time.

---

I think that for starters you can do simpler. Run simple source code for output to the screen and pass text to a variable. Then check the variable and if it matches, then use the option you need.
Later it will be possible to think over a full check.

Edit:

Checked, this method does not work. I immediately open the file in VS2017.
So install Python right away. Now there are not enough other problems before the checks. Sorry.

OROM VBIOS Cezanne - 017.010.000.018.000000 date_05/13/20 (>017.010.000.015.000000 date_03/04/20)
OROM VBIOS GeminiLake - ☺↓♀1 (strange version)

@westlake

Do not pay attention to such a version of OROM VBIOS GLK. Very rarely, this happens with other OROMs, due to a version shift of 3 bytes.

Zitat von SoniX im Beitrag #1186

---

!!!WARNING!!!
Now I checked the replacement of AMD microcodes for Aptio 4 and found that the code is replaced which is not microcode!!!
To avoid problems, check the number of microcodes before and after replacement!
If there are more microcodes, then BIOS is corrupted.

---

@cgm

Intel motherboards will not work after interference in their BIOS. They have digital signatures for everything.

@cgm - Yes, best to dump Intel branded board with programmer, then manually edit for microcodes and program back. If you need help with that once you get programmer let me know.
Normally this is the only way you can flash a mod BIOS there too, so not sure how you flashed in mod BIOS to brick the board?

My apologies for the confusion, the board it's an Asus Z87-A (Intel CPU) with a bios Aptio 4. I use afuwin with GAN option without problem (many update) but on the last bios update (with UBU 1.79.1) Board don't run.

@cgm

The problem was at 1.79.0, but it was resolved. Otherwise, nothing has changed.

Zitat von Lost_N_BIOS im Beitrag #1159

---

@ket - Show me this "place to enable CBS/PBS"
Yes, those 32MB BIOS are the ones I was talking about, and at least in the few I looked at it's complete BIOS image at top and second at bottom, not just microcodes and little overflow.

---

@ket - Nice, I'd never seen this posted by anyone, unsuppress combo CBS option makes CBS appear?
Do you have those reversed above?? "Change To" is original, and "Eg" is post-mod - Looks backwards there
This applies to boards that do not show CBS or PBS by default?? If yes, how to do PBS, is there a "Combo PBS" setting in PBS file too?

Only way I knew previously, was edit AMITSE PE32 and if either there, zero or FF out
59 B9 63 B8 C6 0E 33 40 99 C1 8F D8 9F 04 02 22 - AMD PBS
E3 35 45 B0 04 30 46 49 9E B7 14 94 28 98 30 53 - AMD CBS

Hello,

I have a msi cubi 3 silent s-009b and I want to update the microcode. The Bios is a Aptio V, Intel i3 7100u.

The 920 BIOS (https://www.msi.com/Desktop/support/Cubi-3-Silent-S-7m) has three CPUID microcodes: 406E8, 806E9, 806EA.
In the MSI is a CPU with the ID: 806E9

When I select R (Start replacement): mmtool_5a: Error 4001 FV size is too small
P: Replacement in PEI volume: works with

#Do not remove this file.
#This file is for updating microcodes for MSI x299.
#
#To avoid a possible error - "Error in Saving",
# set '#' at the beginning of the line that you turn off.
#
 
406E8 MSI\cpu406E8_plat80_ver00000026_2016-04-14_PRD_4BA87933.bin 
806E9 MSI\cpu806E9_platC0_ver000000D6_2020-04-27_PRD_C979B5EA.bin 
#806EA MSI\cpu806EA_platC0_ver000000D6_2020-04-27_PRD_D9DD064F.bin 
 
 

D: Inserting into a DXE volume: works

Two questions:
1. Can be delete 806EA (maybe 406E8) microcode or is there a problem after a flash?
2. Is DXE volume a save method?

Zitat von mouseT447 im Beitrag #1213

---

Two questions:
1. Can be delete 806EA (maybe 406E8) microcode or is there a problem after a flash?

---

Zitat

---

2. Is DXE volume a save method?

---

It is better to replace it in the PEI volume, but if the size of the PEI volume does not allow all microcodes to be accommodated, then we try to save it in the DHE volume.

@Lost_N_BIOS

Zitat von Lost_N_BIOS im Beitrag #1150

---

@Dnatwork - This can be any number of things, even drivers. Test a clean windows install on another drive with no drivers installed and see if it works then or still an issue. If it's still an issue there, best you can do is try older BIOS or ask Manufacturer to look into current BIOS bug.
You can also try newer ME FW, but then you can't easily go back. ...
You should also google around about your exact model and Sleep/resume issues, this may be common complaint for your model.

---