Repeated game crashes at different instances - unplayable since June

Please attach the crash report or log. The crash report is a text file located in the [.minecraft|https://minecrafthopper.net/help/finding-minecraft-data-folder/]/crash-reports folder named crash-date-client.txt. If not available attach the launcher_log.txt file.

I'm wondering what else I can do or info to provide to further advance a resolution?

Mojira's Community Support may be able to help. Some crash reports I can read. Launcher logs are tougher.

Adding more game installation details as to where & when these crashes occur  😉 :

• Game (1.17.1) reinstalled to E:\Minecraft

• MinecraftLauncher.exe is located in C:\Program Files (x86)\Minecraft Launcher

• Confirmed newly created world was saved to C:\Users\Admin\AppData\Roaming\.minecraft\saves and does not crash or freeze

• Created new installation by duplicating Latest release, renaming to Latest release (E) and changing GAME DIRECTORY to E:\Minecraft

• Copied backups of 21 saved worlds to E:\Minecraft\saves

• Playing any of these 21 previously saved worlds results in MC freezing within 5-6 mins. AND\OR anytime ESC is used, the MC menu is displayed with non-selectable buttons, spinning circle...

• Ctrl-Alt-Del results in OpenJDK Platform binary is not responding (as per attached capture .jpg), output log displays Process crashed with exit code -805306369, MC displays ERROR Game crashed An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience. Exit Code: 0 (also as per attached capture .jpg). My Event Viewer displays the javaw.exe Application Hang in the original description above

• Creating a new world in Latest release (E) installation, does not freeze or crash

• Optimizing the 21 saved worlds did not help the issue

• Confirmed the 21 saved worlds play fine on another computer

• Confirmed the 21 saved worlds play fine and do not crash when copied back to C:\Users\Admin\AppData\Roaming\.minecraft\saves

Is there some file/s within my 21 saved worlds (that need to be altered or deleted ) that won't allow these worlds to be played from my new E:\Minecraft\saves location? Otherwise, to continue playing my many-years-old saved worlds, they can only reside where they were originally created? 😞

I hope this helps to shed more light on the problem, that I believe started when I added another drive & reinstalled all my games to E: in an attempt to save space on C:  (In Minecraft's case - not as simple as I thought!)

In desperation to play an old world, I copied one of my 21 saved worlds back from E:\Minecraft\saves to C:\Users\Admin\AppData\Roaming\.minecraft\saves and selected installation Latest release. This no longer works - MC crashed again after a few minutes. I attached the latest log and it shows the same errors loading saved data - raids, map_3, map_4, map_15, map_16. Then finally the warning error: UUID of added entity already exists: bec['Chicken'/800, l='ServerLevel[New World_21]', x=-879.87, y=78.00, z=-1808.50] before the fatal error.

I have no idea what this means or how to stop it.

Tried OptiFine installation and the same world failed to load. Fatal error: Process crashed with exit code -805306369 and the same raid & map errors. Next went back to Latest release and the world loaded again but crashed when I hit escape. 

Please expand on your explanation - my computer rarely utilizes more than ~8/16 GB as monitored per task manager with MC running. And in reading the text of this one-time, recent out of memory error capture, it states: "Minecraft has run out of memory." (not my computer). "This could be caused by a bug in the game or by the Java Virtual Machine not being allocated enough memory. ... "  Understood, for this one event. My very next step was to duplicate the installation and bump up the memory to 4 GB to complete a world optimization.

I'm reporting my troubleshooting steps and events encountered to the best of my abilities to drill down to the root cause of my freezes and crashes.

As it stands now, I'm still back to the original reported problem of freezes & crashes. But now being determined to only occur with older saved worlds, optimized for 1.17.1. (I'd really like to preserve the time & effort investment in). These worlds were continually played and saved in newer releases of MC over the years. Output logs repeatedly report different map errors like Error loading saved data: map_26 and fatal error Process crashed with exit code -805306369. And event viewer log application hang events all pointing to javaw.exe version 16.0.1.0.

I've noticed in the few short minutes I have to play a world that displayed maps are one by one being erased after each crash. (appears as unused new map).

In my case, it appears that with 1.17.1 only newly created worlds run without errors and older saved worlds must be abandoned? After attempting all optimizations I plan to attempt to reproduce problem by again coping saved worlds to another computer and reporting my results (haven't ruled out this Radeon RX 580 yet).

Optimization attempts continue with my remaining saved worlds. As the saved worlds backups get larger, I'm encountering more problems - failure to complete optimization, java.lang.OutOfMemoryError & hangs while Joining world.

Steven Gerard Segovia Mejia > 

Minecraft Unified Launcher uninstalled. Now using Minecraft Launcher for Windows.

1.17.1 Optimization of New World_20 (backup size: 1683 MB) stopped at 37% and MC eventually crashed (java.lang.OutOfMemoryError, exit code 1).

• • Noticed changes in my Event Viewer logs related to new launcher:
    The program javaw.exe version 16.0.1.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
    Process ID: 1014
    Start Time: 01d7d1b626cd4b97
    Termination Time: 15
    Application Path:  C:\Users\Admin\AppData\Local\Packages\Microsoft.4297127D64EC6_8wekyb3d8bbwe\LocalCache\Local\Microsoft\WritablePackageRoot\runtime\java-runtime-alpha\windows-x64\java-runtime-alpha\bin\javaw.exe
    Report Id: 2ef12a52-b55b-4d7f-885b-116e0a757a3c
    Faulting package full name: Microsoft.4297127D64EC6_1.0.92.0_x64__8wekyb3d8bbwe
    Faulting package-relative application ID: Minecraft
    Hang type: Unknown

  • Previously with old launcher:
    The program javaw.exe version 16.0.1.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
    Process ID: 4c48
    Start Time: 01d7d1b2131f25a8
    Termination Time: 13
    Application Path: C:\Program Files (x86)\Minecraft Launcher\runtime\java-runtime-alpha\windows-x64\java-runtime-alpha\bin\javaw.exe
    Report Id: f941dd15-654f-4c0d-a569-9096b3d2ba42
    Faulting package full name:
    Faulting package-relative application ID:
    Hang type: Unknown

2nd attempt of 1.17.1 Optimization of New World_20 (backup size: 1686 MB) stopped at 40% and MC crashed (java.lang.OutOfMemoryError: Java heap space, exit code 0).
Watched Task Manager Minecraft Launcher process memory usage increase to >5,000 MB just before crash occurred. (MC installation w/ JVM Argument = 4 GB)

3rd attempt of 1.17.1 Optimization of New World_20 (backup size: 1699 MB) stopped at 60% and MC eventually crashed (java.lang.OutOfMemoryError: Java heap space, exit code 0).
Watched Task Manager Minecraft Launcher process memory usage increase to ~9,300 MB just before crash occurred. (MC installation w/ JVM Argument = 8 GB) Overall system memory performance 13.8/16 GB. 

19:01:30.458
launcher
main

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Render thread"

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "IO-Worker-19"
AL lib: (EE) alc_cleanup: 1 device not closed
19:01:30.458
monitor
Process Monitor
Process crashed with exit code 1

4th attempt of 1.17.1 Optimization of New World_20 (backup size: 1701 MB) stopped at 63% and MC eventually crashed Process crashed with exit code -805306369.
rem Watched Task Manager Minecraft Launcher process memory usage increase to ~9,300 MB just before crash occurred. (MC installation w/ JVM Argument = 8 GB) Overall system memory performance 13.8/16 GB.

5th attempt of 1.17.1 Optimization of New World_20 (backup size: 1704 MB) stopped at 74% and MC eventually crashed Process crashed with exit code 1.
Watched Task Manager Minecraft Launcher process memory usage increase to ~10,980 MB before crash occurred. (MC installation w/ JVM Argument = 10 GB) Overall system memory performance 15.5/16 GB.

15:51:13.486
launcher
main

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "IO-Worker-20"

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "IO-Worker-19"

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "IO-Worker-18"

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Render thread"
AL lib: (EE) alc_cleanup: 1 device not closed
15:51:13.486
monitor
Process Monitor
Process crashed with exit code 1

Is this still an issue in 1.18 Pre-release 4 or later?

In reply - I have not attempted to reproduce my problems with 1.18.

My scenario has changed significantly with the upgrade to Windows 11.  * I decided to run with the MC windows launcher (as suggested) and ditched the MC unified launcher (wish I hadn't - prefer desktop shortcuts). 

Then, starting MC & just hitting Play caused Win 11 to crash & reboot! In desperation to make MC playable again, I had to follow a suggestion to abandon using the bundled java runtime, install Java SE 17 and point MC installations to it. MC is atleast again playable!

Continuing on, I decided to re-optimize my older saved worlds with Java SE 17 installed. This was just as problematic as before where smaller backup worlds would complete and larger backup worlds would stall (even w/ 10 GB allocated to the installation). Never the less, attempting to play optimized older saved worlds, most will hang after a few mins or immediately when hitting ESC. Still a NO-GO playing older worlds.

I have gone a week only playing a world created in 1.17.1 and building upon it. Until today. Maybe coincidentally, while having a map in hand, MC froze and I'm back to the Open JDK Platform binary error. Along with my event viewer: The program javaw.exe version 17.0.1.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 2d50
 Start Time: 01d7dd823d0496df
 Termination Time: 11
 Application Path: C:\Program Files\Java\jdk-17.0.1\bin\javaw.exe
 Report Id: d56b9dab-5fd3-4d61-bff0-d6e16fac85ae
 Faulting package full name: 
 Faulting package-relative application ID: 
 Hang type: Unknown

This was reproduced 3 times. Rebooted Win11, switched to 4 GB installation, grabbed a map & within mins - SCREECH. I can't even open the latest.log w/o rebooting windows 1st.

I guess my next course of action is to try a pre release of 1.18 

For confirmation I tried playing this new world (created in 1.17.1) two more times. Once with a quick look around, a few placed blocks and exit - the world saved. The 2nd try I picked up 3 maps, moved to another location and tried to exit - couldn't select any button, Process crashed with exit code -805306369. An awful lot of my errors are pointing to MC maps with old saved worlds and now with new worlds!

Please let us know in case you were able to reproduce in 1.18.2.