Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

1.16.1 Game Crash

SarJonesy

By SarJonesy
in Support & Bug Reports

 Share

Recommended Posts

SarJonesy Tree Puncher

SarJonesy

Posted
Posted (edited)

Hello,

I've been trying to use forge with Minecraft 1.16.1 with no luck. I originally installed the new beta version of forge for 1.16.1 but that was crashing every time i tried to run it. Now, I installed forge 32.0.34 and it is still crashing. I made sure my Java was updated, I deleted all of my mods, and have been searching for an answer. 

When it crashes it says: "an unexpected issue has occurred and the game has crashed. We're sorry for the inconvenience"

Latest: https://pastebin.com/88LqsWFL 

Debug: https://pastebin.com/uVpeyQQc

Any Ideas?

Update:

Started everything up again to mimic the crash...

Here is the latest and debug files for that

Debug: https://pastebin.com/81yJjGiR

Latest: https://pastebin.com/RXLFMRu5

 

Edited by SarJonesy
Link to comment
Share on other sites
Curle Creeper Killer

Curle

Posted
Posted

Unfortunately we can't help without the crash log information.

What we have now, is like going to the doctor and saying "Doc, it hurts."

 

You should have a latest.log and a debug.log file in the %APPDATA%/.minecraft/logs folder.

Upload them to a paste site like pastebin.com, and send us the link it creates.

Link to comment
Share on other sites
SarJonesy Tree Puncher

SarJonesy

Posted
  • Author
Posted (edited)
17 minutes ago, Curle said:

Unfortunately we can't help without the crash log information.

What we have now, is like going to the doctor and saying "Doc, it hurts."

 

You should have a latest.log and a debug.log file in the %APPDATA%/.minecraft/logs folder.

Upload them to a paste site like pastebin.com, and send us the link it creates.

Sorry, That makes sense now. For some reason I thought I was supposed to find them under crash logs in the Minecraft folder. I was close haha. Right place, wrong folder. Anyways, I did what you said and edited in the links :) Thanks!!

Edited by SarJonesy
Link to comment
Share on other sites
Curle Creeper Killer

Curle

Posted
Posted

You open the log, CONTROL-A to select all the text, copy the text from the log file,

Then go into the large text box in pastebin, paste the log into it,

Then hit "save" at the bottom, and copy-paste the new URL into here.

Link to comment
Share on other sites
SarJonesy Tree Puncher

SarJonesy

Posted
  • Author
Posted

I think I got it now! Just edited the post with the proper links. Now that i look at what i linked i see that i just linked files in my laptop like you said. SMH if i just read what i copied and pasted i would have realized that was definitely wrong haha. 

Link to comment
Share on other sites
SarJonesy Tree Puncher

SarJonesy

Posted
  • Author
Posted (edited)
53 minutes ago, Ugdhar said:

 

 

53 minutes ago, Ugdhar said:

That is super weird, there are no crashes in those logs, they look like a normal startup.

 

Is there a crashlog file in your .minecraft folder?

Maybe try and cause the crash again and repost logs?

I just tried again. I updated the post with the new latest and debug links

Note* it typically gets through the forge load up but once it shows the main screen for a second thats when it crashes.

Edited by SarJonesy
Link to comment
Share on other sites
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Are there any files that something like hs_err_pidXXXX in the server's root folder?

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.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

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:

Spoiler
  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.

Video:

Spoiler

 

 

 

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:

Spoiler

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:

Spoiler

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:

Spoiler

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
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Ah, sorry you're running a client not a server and I'm going through so many threads they're starting to blur together.

For a client that file would be in .minecraft.

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.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

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:

Spoiler
  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.

Video:

Spoiler

 

 

 

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:

Spoiler

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:

Spoiler

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:

Spoiler

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
ChromaKey81 Tree Puncher

ChromaKey81

Posted
Posted (edited)

I've been having issues with Forge 1.16.1, I'm pretty sure it just isn't 100% stable and done yet.

 

Just realized that you're having the issues on a 1.15.2 version so nevermind my comment. Why can't we delete comments on this forum? What is this madness?

Edited by ChromaKey81
Link to comment
Share on other sites
SarJonesy Tree Puncher

SarJonesy

Posted
  • Author
Posted
18 hours ago, ChromaKey81 said:

I've been having issues with Forge 1.16.1, I'm pretty sure it just isn't 100% stable and done yet.

 

Just realized that you're having the issues on a 1.15.2 version so nevermind my comment. Why can't we delete comments on this forum? What is this madness?

I am using a version for 1.16.1 actually. So you're right haha. Unless im horribly mistaken and have been using an old version but last i checked this was for 1.16.1 . And I know right?? haha I didn't even know you couldnt delete it. 

Link to comment
Share on other sites
SarJonesy Tree Puncher

SarJonesy

Posted
  • Author
Posted

Hello everyone!

Thanks for all the help. I think i may have figured out the problem. I had just set up the new John smith resource pack. It was working fine in vanilla for me. My partner has been having a lot of issues with it. She said it was crashing her game all the time. Turns out there was a post about some issues with the new resource pack needing to have some files renamed. Long story short I removed the pack and now forge is working. :)

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.

Guest
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.

×
 Share
Go to topic listing


×
×
  • Create New...

Important Information

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

  I accept