Yes, I did mention that another Z790 mobo(ASUS Z790 Dark hero) works just fine with the GOP Xe driver replaced. The GOP/VBT info is as following. Thank you for further investgation.
I think this is a similar situation with GOP 9.0.1082. Necesitaba una versión VBT 221 o superior…
In your case, VBT 237 and 240 are installed on the Z590, and 250 on the Z790.
In order for GOP 17 to work correctly on different chipsets, you need to search and check all versions from 1060 to 1084.
1 Like
@SoniX, for my Vostro 3670 project, my hex editor work broke the FIT table, so I ran a16_DVfix5 just to compare/contrast.
When I ran a16_DVfix5 selecting the use of MMTool, I had no problem replacing microcodes. When I selected 0 - Do not use MMTool. (As in UBU v1.7x) I’m getting the following:
mCode.ffs (2/2)
╔══════════════════════════════════════════════════════════════════════════════════════════════╗
║ Intel ║
╟───┬───────────┬───────┬───────────┬──────────┬────────────┬───────┬─────────┬─────────┬──────╢
║ # │ Type │ CPUID │ Platforms │ Revision │ Date │ State │ Size │ Offset │ Last ║
╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼─────────┼──────╢
║ 1 │ Microcode │ 906EA │ 22 (1,5) │ F8 │ 2024-02-01 │ PRD │ 0x19C00 │ 0x18 │ Yes ║
╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼─────────┼──────╢
║ 2 │ Microcode │ 906EB │ 02 (1) │ F6 │ 2024-02-01 │ PRD │ 0x1A000 │ 0x19C18 │ Yes ║
╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼─────────┼──────╢
║ 3 │ Microcode │ 906EC │ 22 (1,5) │ F8 │ 2024-02-01 │ PRD │ 0x1A000 │ 0x33C18 │ Yes ║
╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼─────────┼──────╢
║ 4 │ Microcode │ 906ED │ 22 (1,5) │ 100 │ 2024-02-05 │ PRD │ 0x1A000 │ 0x4DC18 │ Yes ║
╚═══╧═══════════╧═══════╧═══════════╧══════════╧════════════╧═══════╧═════════╧═════════╧══════╝Note: Microcode #1 is not in the database! You can help this project
by sharing it at https://win-raid.com forum. Thank you!Note: Microcode #2 is not in the database! You can help this project
by sharing it at https://win-raid.com forum. Thank you!Note: Microcode #3 is not in the database! You can help this project
by sharing it at https://win-raid.com forum. Thank you!Note: Microcode #4 is not in the database! You can help this project
by sharing it at https://win-raid.com forum. Thank you!
These microcodes will be entered into your BIOS fileR - Start replacement
A - Start replacement Alternative with MMTool
0 - Cancel
Choice:R
[Preparing for replacement]
BIOS file backup
[Replacement]
mCode FFS: The syntax of the command is incorrect.
The program ends and goes back to a dos prompt.
Edit1: Selecting R - Start replacement craps out. The assumption was that UEFIReplace would be used.
Selecting A - Start replacement Alternative with MMTool worked, but it worked when selecting MMTool at the beginning:
R - Start replacement
A - Start replacement Alternative with MMTool
0 - Cancel
Choice:A
[Preparing for replacement]
BIOS file backup
[Replacement]
Delete old mCode - 906EA 906EB 906EC 906ED
Insert new mCode - 906EA 906EB 906EC 906ED Real Pointer
FIT Offset - FFD50100 == FFD50100Real _FIT_01 mCode Offset - FFD50400 == FFD50400
mCode Size - 19C00
02 mCode Offset - FFD6A000 == FFD6A000
mCode Size - 1A000
03 mCode Offset - FFD84000 == FFD84000
mCode Size - 1A000
04 mCode Offset - FFD9E000 == FFD9E000
mCode Size - 1A000
Press any key to continue . . .
Edit2: Removing MMTool from the UBU_v1_80_a16_DVfix5 folder gives essentially the same output:
R - Start replacement
0 - Cancel
Choice:R
[Preparing for replacement]
BIOS file backup
[Replacement]
mCode FFS: The syntax of the command is incorrect.
@SoniX, DON’T CHANGE ANYTHING! Selecting 0 - Do not use MMTool. (As in UBU v1.7x) and then A - Start replacement Alternative with MMTool puts a Padding file under File GUID: B52282EE-9B66-44B9-B1CF-7E5040F787C1!!!
THANK YOU!
Thanks for reply. Do you mean I have to get GOP Xe driver 17.0.1084(or below) to work with Z590 BIOS ? GOP Xe driver 17.0.1085 only works for Z790 BIOS ?
2 options - search for a clean and customized VBT 250 or search for a working GOP from 17.0.1060 to 108x. It is not necessary to check all versions selectively. The principle is simple, but dreary - if it works newer, it does not work, we reduce the version.
Or leave it as it is.
Add
Here there is a version 17,0,1071.
You need to put the file in a folder - “Files\Intel\GOP\v17”
Be sure to rename it to “IntelGopDriver.efi”.
Check if it works, then it will be easier to look for other versions.
1 Like
v1.80.a16.1 corrected the Microcode update bug when I selected 0 - Do not use MMTool, followed by R - Start replacement.
The Padding file under File GUID: B52282EE-9B66-44B9-B1CF-7E5040F787C1 for my Dell Vostro 3670 bios is not there, but that’s not a problem. For me and other Dell users with these modern bios’ (Winbond W25Q256JV 32MB bios chip, in my case), you will select 0 - Do not use MMTool, followed by A - Start replacement Alternative with MMTool.
Or, you can select 1 - Use MMTool, followed by A - Start replacement Alternative with MMTool.
The bottom line is that whether or not you use MMTool (mmtool_a5.exe), make sure you select A - Start replacement Alternative with MMTool.
Thanks again @SoniX !
Not entirely true.
You can choose any option (“use MMT or not use MMT”). If there is only one container with microcodes in the BIOS, there will always be an “Alternative replacement” option.
Hi @SoniX,
thank you very much for your awesome tool.
Version 16.1 works perfectly for me on ASRock Z170 and Z790. It would be fantastic if @Platomav’s Python database could be swapped 1:1 again.
I hope you’ll be with us forever.
SoniX thank you for your tool but
I can’ t update the AMD cpu microcode with the latest version.
MSI B550 TOMAHAWK - AMD R7 5700X
@SoniX thank you for new version!
All is working well for me, except one thing: with modded bios I can’t save changes. After update via DOS and clearing CMOS, changes are not saved.
Reverted to original BIOS and all is working.
MSI 970A-G43 PLUS
I have updated storage, lan and microcodes.
Out of the box this feature does not work. You either need an .exe from MCE or you need to install Python to run MCE.py. Anyway, I made you an updated BIOS.
westlake thank you for the update bios.
It’s definitely interesting, I wonder if anyone will figure it out. I attach two BIOSes. The “mm” is the one that should theoretically match your modified BIOS, but doesn’t. There is minimal difference, I don’t know if it makes any difference. Everything in this version has been replaced with MMTool. On the other BIOS, only the microcodes were replaced with that one. Try both if you like.
BIOS.rar (4.4 MB)
Thank you. I will try it.
You made these mod’s from the file I sent you? Or from original BIOS? It is safe to flash from DOS? I prefer to ask you because I’m not an expert.
EDIT: both tested. Same issue. Changes on BIOS after flashing didn’t save.
Thanks for the feedback, very useful! Now I just need someone smarter to tell me what the cause of the error might be.
1 Like
I only can say that in the past old UBU Tool version always worked with this motherboard and this BIOS
1 Like