Stalls before the main menu

[cranberryowo]

Have you tried the solutions mentioned above?

Yes

Modpack

FTB StoneBlock 4

Modpack Version

1.9.6

Describe what happened

Game freezes before the main menu upon launching it. sometimes stalls near completion of the loading bar, sometimes before the loading bar appears, sometimes just over midway through the loading bar.

Link to logs

StoneBlock 4 crashed without a crash report. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log head / tail (~33k lines) | PrismLauncher-0.log head / tail (~16MB & ~43k lines) | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt

Mod list changes on top of the modpack:

Added mods:
ExtraDataModels-1.21-4.3.zip (resourcepack)

Updated mods:
particular-1.21.1-NeoForge-1.17.jar > particular-1.21.1-NeoForge-1.1.7.jar

Steps to reproduce

Launch the game, wait

Additional information

RTX 3060, driver version 595.97 (lastest). Ryzen 5 3600. 32gb ram, 8gb allocated to modpack instance.
I do not encounter this issue on my laptop (Gigabyte G5 KF5, 4060 laptop GPU).

When the game stalls, task manager shows it having typical memory usage but less than 1 percent CPU usage.

Has the pack been modified

No

Additional information

No response

[Gaz492]

Does reinstalling the modpack or using a different launcher allow the modpack to start up?

[cranberryowo]

Does reinstalling the modpack or using a different launcher allow the modpack to start up?

No. Reinstalled multiple times each from both the curseforge and FTB sources and tried both FTB launcher and Prism launcher.

[Gaz492]

Ok, When using Prism, are you importing the pack from the FTB App or installing it via CurseForge?

[cranberryowo]

I've tried both importing the pack from the FTB App and installing via CurseForge when using Prism. Restarted computer and fully deleted the instance in between trying each.

[Gaz492]

Hmm, if you leave the pack for 10-20 minutes at the point where it gets stuck does it just stay there or will it automatically close/crash?
The logs unfortunately don't show anything obvious as to what's going wrong.