Arch Linux

Trevor_B

Member

Registered: 2019-12-28

Posts: 141

Re: EFI stub: Warning: unable to unprotect memory range

Hi all

For info 4.10 BIOS released by Asrock
It works fine on my B650 RS Pro, no error message

@Boogleix  Taichi Lite X870E has a beta available since Feb 7th

faetter

Member

Registered: 2019-09-21

Posts: 29

Re: EFI stub: Warning: unable to unprotect memory range

Hi guys

So, given that Asrock have released a fixed version, is it known whether the fix was due to the new AGESA 1.3.0.0a or is it something Asrock themselves fixed? I recently bought an X870E Aorus Master and an X870E AORUS Elite X3D, so this couldn't be more annoying.

Thanks

---

None are more enslaved than those who falsely believe they are free

Lr2bej77n892lio

Member

Registered: 2025-04-30

Posts: 19

Re: EFI stub: Warning: unable to unprotect memory range

Have same problem with GIGABYTE B650M K (rev 1.1)
I have updated recently from FB to FC1.

Last edited by Lr2bej77n892lio (2026-02-16 16:47:16)

Reboot9012

Member

Registered: 2025-11-25

Posts: 17

Re: EFI stub: Warning: unable to unprotect memory range

The only solution for gigabyte owners like us is to pester them enough and pray they do something, I tried as mentioned before and got the usual answer.

Last edited by Reboot9012 (Yesterday 20:13:00)

Lr2bej77n892lio

Member

Registered: 2025-04-30

Posts: 19

Re: EFI stub: Warning: unable to unprotect memory range

I downgraded and no errors anywhere

Which BIOS version are you using?

Last edited by Lr2bej77n892lio (2026-02-16 17:00:10)

Reboot9012

Member

Registered: 2025-11-25

Posts: 17

Re: EFI stub: Warning: unable to unprotect memory range

I have the b850 and I'm at the F7 version but you have to use the one before the asega 1.2.8 bios unless you have a new Ryzen CPU but as far I know this problem didn't mess my system but I'm no expert I downgraded anyway because who knows

Last edited by Reboot9012 (Yesterday 20:11:29)

Drz49

Member

Registered: 2026-02-21

Posts: 1

Re: EFI stub: Warning: unable to unprotect memory range

Just to chime in, I have this problem on Gigabyte X870E AORUS ELITE WIFI7 (Rev. 1.2)
When I have went from FA6 bios to FA9
I have downgraded to FA7 and the error went away.
FA8 is the bios verson with asega 1.2.8.0

Last edited by Drz49 (2026-02-21 09:53:43)

Xerxes_II

Member

Registered: 2026-02-25

Posts: 1

Re: EFI stub: Warning: unable to unprotect memory range

Same with MSI B850 Edge Ti after upgraded from A46 to A50 (AGESA PI 1.2.0.8g to pre-1.3.0.0)

destiper

Member

Registered: 2026-03-02

Posts: 1

Re: EFI stub: Warning: unable to unprotect memory range

Same error on MSI MPG X870E Carbon WiFi, BIOS version 7E49v1A8. updated from AGESA PI 1.2.0.3e to pre-1.3.0.0

Last edited by destiper (2026-03-03 04:26:19)

srahman5317

Member

Registered: 2021-11-19

Posts: 4

Re: EFI stub: Warning: unable to unprotect memory range

Same issue on MSI MPG B650I EDGE WIFI . Just a warning and everything runs (but I don't like it)

UrbenLegend

Member

Registered: 2021-03-26

Posts: 33

Re: EFI stub: Warning: unable to unprotect memory range

Btw, it is not just a warning. If you're using TSME as a means to better safeguard your disk encryption, keep in mind that this error will cause it to be disabled. SMAP (Supervisor Mode Access Prevention) is also disabled. Someone more knowledgeable than me can probably better explain why that's important, but it seems to control when code running in privileged mode can access user-space memory.

Either way, it seems like a reduction in security so I would encourage people to downgrade until AMD fixes the issue.

Prosdocimo

Member

Registered: 2024-02-16

Posts: 2

Re: EFI stub: Warning: unable to unprotect memory range

I tested the latest BIOS F12a on my Gigabyte X870E AORUS PRO, which comes with AGESA 1.3.0.0a, and the issue is still present. I rolled back to F9 (AGESA 1.2.0.3g)

burzikak

Member

Registered: 2026-03-22

Posts: 1

Re: EFI stub: Warning: unable to unprotect memory range

I had have this issue on my Gigabyte X870E AORUS MASTER.   I only noticed it today and hadn't updated the BIOS since early Feb (BIOS F12).

Updated to F13a today and the message still appeared

Internet search brought me to this thread and also this from the linux mint forums https://forums.linuxmint.com/viewtopic.php?t=436503.   It referenced an askubuntu thread (https://askubuntu.com/questions/1519290 … 39#1528839) which suggested turning on secure boot, resetting keys to default, and then turning off secure boot.

EDIT:  Spoke too soon,  message came back after a couple of reboots

This worked for me.

Steps from the linked posts are below:

1. Boot into your computer's BIOS settings. (Repeatedly pressing the delete key during reboot is the most common way to get into the BIOS.) In the BIOS go to the Security tab. (in my case it was the "boot" tab in the gigabyte BIOS.)

2. Enable Secure Boot. Change Secure Boot from Standard to Custom. This creates a new menu to configure Secure Boot.

3. In this new menu it lists Secure Boot keys. There should be a reset to defaults option. Select it to reset your Secure Boot keys.

4. Leave the custom menu and turn Secure Boot back into Standard mode, then disable Secure Boot. (Most, maybe all, Linux distros do not support Secure Boot.)

Last edited by burzikak (2026-03-22 04:52:46)

Leonito

Member

Registered: 2025-10-27

Posts: 1

Re: EFI stub: Warning: unable to unprotect memory range

The only solution for gigabyte owners like us is to pester them enough them and pray they do something I tried as mentioned before and got the usual answer.

I think pestering worked, as I was sent a patched BIOS after messaging them (B650 Gaming X AX). The issue is now gone for me, hopefully they'll deploy it globally soon.

Reboot9012

Member

Registered: 2025-11-25

Posts: 17

Re: EFI stub: Warning: unable to unprotect memory range

The only solution for gigabyte owners like us is to pester them enough them and pray they do something I tried as mentioned before and got the usual answer.

I think pestering worked, as I was sent a patched BIOS after messaging them (B650 Gaming X AX). The issue is now gone for me, hopefully they'll deploy it globally soon.

Thanks for the update I will try the fix when they release it