EFI stub: Warning: unable to unprotect memory range on boot

A

asd156202d5

New member
Joined
Jan 15, 2026
Messages
5
Hello,

I'm observing an error message on boot after upgrading my motherboard BIOS version (specs below), "EFI stub: Warning: unable to unprotect memory range on boot". Despite the error my operating system does appear to boot after this message, however I'm hoping for some clarification and if there is any remediation.

Specs:
Motherboard: MSI MPG X870E CARBON WIFI
Motherboard BIOS version: 7E49v1A7E
OS: Arch Linux x86_64
Kernel: Linux 6.18.5-arch1-1
CPU: AMD Ryzen 7 9800X3D
GPU: Nvidia GeForce RTX 5080

This problem has been reported for newer ASUS motherboard BIOS versions as well: https://bbs.archlinux.org/viewtopic.php?id=311516

Has anyone seen this recently and/or aware of a fix?

Thanks!
 
Sort by date Sort by votes
Unable to unprotect memory range on boot, sounds like it does a good job with the security protocol.
Do you find any problem other than the message though?
 
Upvote 0 Downvote
No other issues that I can tell, and journalctl and dmesg logs seem fine.

You allude to a security protocol, could you elaborate for me? Probably worth mentioning that secure boot is disabled in the BIOS, so I'm unsure if that's related. However googling searching around seems to indicate it might.
 
Upvote 0 Downvote
asd156202d5 said:
Hello,

I'm observing an error message on boot after upgrading my motherboard BIOS version (specs below), "EFI stub: Warning: unable to unprotect memory range on boot". Despite the error my operating system does appear to boot after this message, however I'm hoping for some clarification and if there is any remediation.

Specs:
Motherboard: MSI MPG X870E CARBON WIFI
Motherboard BIOS version: 7E49v1A7E
OS: Arch Linux x86_64
Kernel: Linux 6.18.5-arch1-1
CPU: AMD Ryzen 7 9800X3D
GPU: Nvidia GeForce RTX 5080

This problem has been reported for newer ASUS motherboard BIOS versions as well: https://bbs.archlinux.org/viewtopic.php?id=311516

Has anyone seen this recently and/or aware of a fix?

Thanks!
Click to expand...

The issue is duplicated.
MSI Team is investigating the issue, please be patient.
Thanks.
I will update this topic when there is a news and update about it.
 
Upvote 0 Downvote
asd156202d5 said:
Hello,

I'm observing an error message on boot after upgrading my motherboard BIOS version (specs below), "EFI stub: Warning: unable to unprotect memory range on boot". Despite the error my operating system does appear to boot after this message, however I'm hoping for some clarification and if there is any remediation.

Specs:
Motherboard: MSI MPG X870E CARBON WIFI
Motherboard BIOS version: 7E49v1A7E
OS: Arch Linux x86_64
Kernel: Linux 6.18.5-arch1-1
CPU: AMD Ryzen 7 9800X3D
GPU: Nvidia GeForce RTX 5080

This problem has been reported for newer ASUS motherboard BIOS versions as well: https://bbs.archlinux.org/viewtopic.php?id=311516

Has anyone seen this recently and/or aware of a fix?

Thanks!
Click to expand...
This is also happening on the mai mag b850 tomahawk wifi
Running cachyos latest build and latest bios
 
Upvote 0 Downvote
Hi @Svet , Im just curious if there has been update on this? My internal ticket was also closed with no additional information, yet I do see a new BIOS version for my particular motherboard. Do you know know if 7E49v1A8 patches the behavior reported?
 
Upvote 0 Downvote
asd156202d5 said:
Hi @Svet , Im just curious if there has been update on this? My internal ticket was also closed with no additional information, yet I do see a new BIOS version for my particular motherboard. Do you know know if 7E49v1A8 patches the behavior reported?
Click to expand...
From emails they are still looking into it at this time
 
Upvote 0 Downvote
asd156202d5 said:
Hi @Svet , Im just curious if there has been update on this? My internal ticket was also closed with no additional information, yet I do see a new BIOS version for my particular motherboard. Do you know know if 7E49v1A8 patches the behavior reported?
Click to expand...

Please wait patiently, MSI is checking with AMI.
If you have any other issue than the error message reported,
then tell full details about it.
 
Upvote 0 Downvote
Will the same fix be applied to other motherboard models too? I have this same warning on a MAG B850 TOMAHAWK MAX WIFI and wonder if the first line I see below is the exact same problem and whether or not I need to make a separate thread for my board

IMG_20260125_123455413_1_1.jpg
 
Upvote 0 Downvote
luisbocanegra17158602e7 said:
Will the same fix be applied to other motherboard models too?
Click to expand...

Probably, if the same issue exist there too.

luisbocanegra17158602e7 said:
I have this same warning on a MAG B850 TOMAHAWK MAX WIFI and wonder if the first line I see below is the exact same problem and whether or not I need to make a separate thread for my board
Click to expand...

If the issue is the same is OK to be here.
Will check if such BIOS update is planed (or already exist) and will update you.
 
Upvote 0 Downvote
Hi, same thing here after I updated BIOS of my B650 Gaming Plus Wifi to 7E26v1M. I suppose this is related to AGESA PI pre-1.3.0.0 update, since this did not happen with M beta releases (using AGESA PI 1.2.0.3). I am using Archlinux and do not see any issue.
 
Upvote 0 Downvote
luisbocanegra17158602e7 said:
Will the same fix be applied to other motherboard models too? I have this same warning on a MAG B850 TOMAHAWK MAX WIFI and wonder if the first line I see below is the exact same problem and whether or not I need to make a separate thread for my board

View attachment 209919
Click to expand...

It will be fixed with future BIOS updates,
check the new updates at web page when they are released and have a try it.

fernandez.e158d02e7 said:
Hi, same thing here after I updated BIOS of my B650 Gaming Plus Wifi to 7E26v1M. I suppose this is related to AGESA PI pre-1.3.0.0 update, since this did not happen with M beta releases (using AGESA PI 1.2.0.3). I am using Archlinux and do not see any issue.
Click to expand...

Same as above probably will be fixed for your board model too with future BIOS updates.
 
Upvote 0 Downvote
Svet said:
It will be fixed with future BIOS updates,
check the new updates at web page when they are released and have a try it.
Click to expand...
Thank you for the quick update. I will keep an eye out for a new version and report back after updating.
 
Upvote 0 Downvote
Updated my MAG B850 TOMAHAWK MAX WIFI to the newest version (7E62v2A53 2026-03-20) today and after rebooting the second line is no longer there, but the first one remains:
No EFI_MEMORY_ATTRIBUTE_PROTOCOL found, skipping NX_COMPAT support.
1774237731719.jpeg

Is this "NX_COMPAT support" something that can/will be fixed by future updates? According to https://github.com/systemd/systemd/pull/38678 the warning is logged because the firmware should support "EFI_MEMORY_ATTRIBUTE_PROTOCOL" but doesn't?

Not a big deal and the system still works, but the warning sticks out like a sore thumb in my otherwise silent boot setup. That said, I am grateful for the support given even if Linux is not an officially supported OS.
 
Upvote 0 Downvote
Back
Top