GRUB4DOS UEFI boot freeze on Gigabyte X870I/B850i motherboard

[nexusarx]

Hi everyone!

First of all, I would like to thank the developers for their hard work! I have been using the MBR version of grub4dos with great satisfaction for a long time, and recently the UEFI version as well. However, I have unfortunately encountered the following issue with a new configuration.

Hardware Environment:
Motherboard: B850i AORUS PRO (Link: Gigabyte X870I AORUS PRO ICE) MotherBoard
BIOS version: F9
CPU: AMD Ryzen 5 8600G / Radeon 760M

BIOS Settings:
Boot: Fast boot: Disabled | CSM Support: Disabled
Secure Boot: System mode: User | Secure boot: Disabled | Secure boot mode: Custom
Keys: All cleared/deleted (PK, KEK, db, dbx, dbt, dbr)
Other: Above 4G decoding: Enabled | Resize BAR support: Enabled
Issue Description:
Upon booting, the boot screen (logo or text) appears, but then the process stops immediately. Grub completely freezes during the boot process; nothing happens.

What I have tried so far (unsuccessfully):
rEFInd + GRUB4DOS chainloading: The rEFInd bootloader starts, but as soon as it attempts to hand over control to grub, it freezes just like during a normal boot.
GitHub Issue #447 suggestions: I tried the suggestions described there, but none of them solved the problem : Issue "Bios setting for asus x870 ..."
Perhaps it works on an ASUS X870 motherboard, and Gigabyte's X870 implementation handles things differently?
This is might be a specific issue with Gigabyte's UEFI implementation regarding memory mapping on the X870 chipset. Has anyone tested this on an ASUS or MSI X870 motherboard? Is it possible that they handle the UEFI environment differently?

Comparison:
I was able to boot the VHDs (Windows 11) from the disk using other bootloaders (Ventoy vhdboot, agFM - based on GRUB2), so the hardware and the bios settings is functional. However, these solutions do not support the memory disk handling specific to GRUB4DOS, which I require.

Question:
Does anyone have any ideas? I would prefer not to switch to another bootloader because the flexibility of menu.lst makes it much easier to launch various VHDs with specific parameters (a capability I do not see in Ventoy).

Thank you in advance for your help!