Jump to content

Game Crash During Initial Loading


Recommended Posts

Hi, I'm having issues with the game crashing during the initial loading phase using Forge version 36.2.9 for Minecraft 1.16.5. This is happening during the "Deep Scan" phase of the Forge loading and it crashes right after saying Deep Scan of Translocators completed. I have a lot of mods present and I'm pretty sure it is one of them causing it as I have experimented with different forge versions to see if that could be the cause. I also removed a few mods to see if that would help, but no luck. The biggest issue is that the log doesn't actually provide any insight to what mod it could be and no actual crash report is generated. I really don't want to go through the process of deleting half the mods then readding until I find the culprit, as it is a lot of mods to go through (368 to be exact). 12GB are allocated to the game and I'm using the Twitch launcher, my PC is also fully capable of handling the amount of mods as I have done it before. This is strictly an issue with a specific mod and I need help figuring which one it could.

This is my latest.log file: https://pastebin.com/raw/gLtN5rmA

This is my full mods list (hefty I know): https://pastebin.com/raw/1m9dfhGU  

Edited by Icetok
Link to comment
Share on other sites

Please provide debug.log, more info on where it is and how to provide it can be found in my signature below (just expand the spoiler)

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.


As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.


For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.


Logs (Most issues require logs to diagnose):


Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.


What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...


...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension


Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.


Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.






or alternately, 


Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft


Server Not Starting:


If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.


Reporting Illegal/Inappropriate Adfocus Ads:


Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.


Posting your mod as a GitHub Repo:


When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.


  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]


Link to comment
Share on other sites

11 minutes ago, DaemonUmbra said:

Please provide debug.log, more info on where it is and how to provide it can be found in my signature below (just expand the spoiler)

Here is the debug.log file: https://gist.githubusercontent.com/Icetok/12aa285f0c499c80f571ebba2bf24eb0/raw/05a796defd34ef589696aafc0126e95deeacd1f9/debug.log

Had to upload it on GitHub Gist because it exceeded the Pastebin Free size limit.

Great tutorial btw. :)

Link to comment
Share on other sites

6 minutes ago, diesieben07 said:

Looks to be an issue with "supplementaries", "libx", "losttrinkets" or "valhelsia_structures".

It worked! LibX was the final culprit, after removing that and the mods that were dependent on it, the game finally loaded. Thank you so much for your help! :D

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.