Have you tried the solutions mentioned above?
Yes
Modpack
FTB Presents Architect's Exodus
Modpack Version
1.0.0
Launcher/App used to start the modpack
FTB App
Describe what happened
Similar as this 1.21.1 issue: #12369
The issue seems to be a three-way mod conflict/race condition between BrandonsCore (CurseForge | GitHub), Ice and Fire: Dragons (CurseForge | GitHub), and FTB Chunks (CurseForge | GitHub).
Seems to be this issue on Ice and Fire's issue tracker, with the last comment in there also mentioning this, which I could reproduce: AlexModGuy/Ice_and_Fire#5364
Similar issue on BrandonsCore issue tracker (but has very little context): Draconic-Inc/BrandonsCore#124
Similar conflict as the 1.21.1 issue with a specific Twemoji version (as per #12369), which has this issue on their tracker: Draconic-Inc/BrandonsCore#128
Also created an issue on FTB Chunks' issue tracker here, in case there's something that can be done from that mod's end (just like how Twemoji's 1.0.4 update addressed the conflict in 1.21.1): FTBTeam/FTB-Mods-Issues#2121
Reproduction in an isolated MC 1.20.1 instance with Forge 47.4.10 (recommended 1.20.1 version) or 47.4.20 (like the pack uses) and the following modlist (which is just BrandonsCore + Ice and Fire Dragons + FTB Chunks, and their dependencies, these are both the latest available and also same versions as the pack uses):
architectury-9.2.14-forge
BrandonsCore-1.20.1-3.2.1.302-universal
citadel-2.6.3-1.20.1
CodeChickenLib-1.20.1-4.4.0.516-universal
ftb-chunks-forge-2001.3.8
ftb-library-forge-2001.2.13
ftb-teams-forge-2001.3.2
iceandfire-2.1.13-1.20.1-beta-5
Latest.log | Debug.log | hs_err_pid.log
Disabling any of them (say FTB Chunks and still keeping its dependencies like architectury/ftb library, or disabling ice and fire and keeping citadel) stops the crash from happening, all of those are needed for it to happen.
Link to logs
FTB Architect's Exodus crashed. The logs have been uploaded to gnomebot.dev:
# Problematic frame:
# C [atio6axx.dll+0xbbec00]
Found �[2;34m1�[0m log analysis results:
�[2;34mAtio6axx�[0m in: hs_err_pid10724.log
Steps to reproduce
Launch pack on older AMD GPUs/iGPUs
Has the pack been modified
No
Have you tried the solutions mentioned above?
Yes
Modpack
FTB Presents Architect's Exodus
Modpack Version
1.0.0
Launcher/App used to start the modpack
FTB App
Describe what happened
Similar as this 1.21.1 issue: #12369
The issue seems to be a three-way mod conflict/race condition between BrandonsCore (CurseForge | GitHub), Ice and Fire: Dragons (CurseForge | GitHub), and FTB Chunks (CurseForge | GitHub).
Seems to be this issue on Ice and Fire's issue tracker, with the last comment in there also mentioning this, which I could reproduce: AlexModGuy/Ice_and_Fire#5364
Similar issue on BrandonsCore issue tracker (but has very little context): Draconic-Inc/BrandonsCore#124
Similar conflict as the 1.21.1 issue with a specific Twemoji version (as per #12369), which has this issue on their tracker: Draconic-Inc/BrandonsCore#128
Also created an issue on FTB Chunks' issue tracker here, in case there's something that can be done from that mod's end (just like how Twemoji's 1.0.4 update addressed the conflict in 1.21.1): FTBTeam/FTB-Mods-Issues#2121
Reproduction in an isolated MC 1.20.1 instance with Forge 47.4.10 (recommended 1.20.1 version) or 47.4.20 (like the pack uses) and the following modlist (which is just BrandonsCore + Ice and Fire Dragons + FTB Chunks, and their dependencies, these are both the latest available and also same versions as the pack uses):
Latest.log | Debug.log | hs_err_pid.log
Disabling any of them (say FTB Chunks and still keeping its dependencies like architectury/ftb library, or disabling ice and fire and keeping citadel) stops the crash from happening, all of those are needed for it to happen.
Link to logs
FTB Architect's Exodus crashed. The logs have been uploaded to
gnomebot.dev:latest.log | debug.log head / tail (~29k lines) | hs_err_pid10724.log | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt
Steps to reproduce
Launch pack on older AMD GPUs/iGPUs
Has the pack been modified
No