Memtest86+ don't boot on MSI MAG X870E Tomahawk WiFi with 7E59v2A95 or 7E59v2A94 bios

M

mkdante3815e702eb

New member
Joined
Jan 26, 2026
Messages
9
Memtest86+ doesn’t boot when the BIOS version is 7E59v2A95 or 7E59v2A94. Both versions are probably pre-release BIOS builds with AGESA PI pre-1.3.0.0. After run Memtest86+, there’s only a black screen with a “-” on the left side, and nothing happens. On an older BIOS (two versions back) everything was OK with the same settings.

Tested with Secure Boot enabled and disabled on the motherboard, and with Ventoy configured with Secure Boot support enabled and disabled. Key certificate enrollment was done. I also tested different boot modes alternately. What’s strange is that it should start with UEFI + Legacy and Secure Boot disabled, but it still doesn’t work.

On the BIOS versions where it worked, I used Ventoy with Secure Boot support enabled, with the Memtest86+ image as a file on the Ventoy USB drive. Secure Boot was enabled on the motherboard, UEFI-only, with no CSM/Legacy.
 
Sort by date Sort by votes
It's been tested, but the issue can't be duplicated.
What CPU you are using?

Try clear all additional secure key generated from Ventoy or any other tool,
restore BIOS to absolutely default and re-test again.
 
Upvote 0 Downvote
Svet said:
It's been tested, but the issue can't be duplicated.
What CPU you are using?

Try clear all additional secure key generated from Ventoy or any other tool,
restore BIOS to absolutely default and re-test again.
Click to expand...
AMD Ryzen 9700x. On olders BIOS all work. Bios was updated and all settings are cleared(CMOS cleared) and set with the same settings like before updating. Like I write before, tried everything, also full wipe USB, formatted in NTFS, exFAT, FAT32 and all work before updated to AGESA PI pre-1.3.0. Something is with this bios versions. I had no idea that this was a pre-release version.
I create also ticket to MSI support
 
Upvote 0 Downvote
Upvote 0 Downvote
mkdante3815e702eb said:
AMD Ryzen 9700x. On olders BIOS all work. Bios was updated and all settings are cleared(CMOS cleared) and set with the same settings like before updating. Like I write before, tried everything, also full wipe USB, formatted in NTFS, exFAT, FAT32 and all work before updated to AGESA PI pre-1.3.0. Something is with this bios versions. I had no idea that this was a pre-release version.
I create also ticket to MSI support
Click to expand...

Got it. MSI is checking about this issue.
Will update the topic when there is a updates.
 
Upvote 0 Downvote
plutomate said:
This happens with new AGESA code but don't know it has anything to do with yours.
Are you using latest memtest v8.00? Any chance trying earlier version?
www.memtest.org

Memtest86+ | The Open-Source Memory Testing Tool

Memtest86+ is an advanced, free, open-source, stand-alone memory tester for 32- and 64-bit computers (UEFI & BIOS supported)
www.memtest.org www.memtest.org
Click to expand...
Problem is on AGESA PI pre-1.3.0.0 or latest stable AGESA PI 1.3.0.0, so probably similar problem.
 
Upvote 0 Downvote
Svet said:
Got it. MSI is checking about this issue.
Will update the topic when there is a updates.
Click to expand...

Update, FYI:
There had been a security update from AGESA 1270 to 1271.
Memtest86+ contains self-modifying code so it’s blocked by BIOS.
Reversing security update might create more potential security risks and MSI will not change it.
 
Upvote 0 Downvote
Svet said:
Update, FYI:
There had been a security update from AGESA 1270 to 1271.
Memtest86+ contains self-modifying code so it’s blocked by BIOS.
Reversing security update might create more potential security risks and MSI will not change it.
Click to expand...
Memtest86 also don't work, so it's possible to work this tool, by changing code in Memtest86 or Memtest86+? This tool was the best to check stability memory and work everywhere from decades! Now AMD "fix" this? In Windows is impossible check whole memory... It's safe to back to old bios? AMD block back when AGESA is new and you want back to older AGESA...
 
Upvote 0 Downvote
Think Memtest/Memtest+ should release updated versions to be compatible with latest AMI security standards.
 
Upvote 0 Downvote
Hi, I’m the lead developer of Memtest86+. Could you please provide technical details about the “security standard” you mentioned? Is it related to AMD or AMI?
We work closely with AMD, and they actively contribute to our codebase, but they do not appear to be aware of any new security-related change in their AGESA.
 
Upvote 0 Downvote
ms15b502e0 said:
Hi, I’m the lead developer of Memtest86+. Could you please provide technical details about the “security standard” you mentioned? Is it related to AMD or AMI?
We work closely with AMD, and they actively contribute to our codebase, but they do not appear to be aware of any new security-related change in their AGESA.
Click to expand...

Is it related to AMD or AMI?
Click to expand...

It's related to AMI.

Could you please provide technical details about the “security standard” you mentioned?
Click to expand...

I don't know the tech details, will do a query with my msi contacts.
 
Upvote 0 Downvote
Thank you! I really don't understand what could be wrong here and how to fix that issue. I've carefully checked the whole changelog for AGESA1.2.7.1 and can't find any related change (a FWDEV or PLAT # could be helpful). "Self-modifying" code is of course used for relocation, but that's a mandatory root feature without any security drawback. Anyway, the BIOS just crashing/freezing without giving an error message is quite disturbing for users.
 
Upvote 0 Downvote
ms15b502e0 said:
Thank you! I really don't understand what could be wrong here and how to fix that issue. I've carefully checked the whole changelog for AGESA1.2.7.1 and can't find any related change (a FWDEV or PLAT # could be helpful). "Self-modifying" code is of course used for relocation, but that's a mandatory root feature without any security drawback. Anyway, the BIOS just crashing/freezing without giving an error message is quite disturbing for users.
Click to expand...

Until wait, do you have the same reports from other mainboard vendors too,
or have you tested with a different brand mainboard from the same class who have the same AGESA version? or latest version?
 
Upvote 0 Downvote
We have similar reports from some recent BIOS from Gigabyte (F9+) but that may be unrelated as a bug in AGESA preventing boot is also known on AGESA 1.2.8/1.3.0pre
ASUS and Asrock seems fine, no matter the AGESA version (1.2.x or 1.3.x) despite being also based on AMI Aptio.

I'll do some tests to check if this is related to the W^X flag used for relocation in the .text of the Memtest86+ payload.
 
Upvote 0 Downvote
I worked on a fix that seems to allow Memtest86+ to run on a Gigabyte board that previously freeze.

The PR has been pushed here if anyone want to look at the code : https://github.com/memtest86plus/memtest86plus/pull/604

I compiled a binary with this PR : https://memtest.org/download/beta/2026033104-mt86p-8.10-beta.zip
You just have to extract it (with the embedded /efi/boot folder structure) into a cleanly formatted FAT32 USB Flash Drive to try booting it (Secureboot must be disabled).

Any report (working or not) on MSI motherboard will be greatly appreciated! Thank you!
 
Upvote 0 Downvote
ms15b502e0 said:
We have similar reports from some recent BIOS from Gigabyte (F9+) but that may be unrelated as a bug in AGESA preventing boot is also known on AGESA 1.2.8/1.3.0pre
ASUS and Asrock seems fine, no matter the AGESA version (1.2.x or 1.3.x) despite being also based on AMI Aptio.

I'll do some tests to check if this is related to the W^X flag used for relocation in the .text of the Memtest86+ payload.
Click to expand...
I check later this 8.10 build. Problem on my motherboard, like I write before, was after update to bios with AGESA 1.3.0.0. On older all was ok
 
Upvote 0 Downvote
Back
Top