Minecraft Exit Code -805306369: How to Fix Out of Memory Crashes

Exit code -805306369 means Minecraft ran out of system memory or Java heap space and crashed. The likeliest cause is the RAM setting not matching what you're running, and it's usually a one-slider fix.

Calculated as an unsigned 32-bit integer, exit code -805306369 converts to hexadecimal 0xCFFFFFFF, which is a non-standard status code returned when Windows or Java forcefully terminates the process due to memory exhaustion. It indicates that the Java Virtual Machine could no longer allocate heap space or reached 100% Garbage Collection capacity without freeing memory.

Identifying Exit Code -805306369 in Log Files

When Minecraft crashes due to memory exhaustion, SuperLauncher displays a red notice pointing directly to its log file. Checking the log files helps confirm whether your crash was caused by Java heap exhaustion or an external system event.

You can inspect three log locations depending on where the failure occurred:

• Launcher log: %APPDATA%\SuperLauncher\logs\superlauncher.log
• Game log: %APPDATA%\.minecraft\logs\latest.log
• Crash reports: %APPDATA%\.minecraft\crash-reports\

The SuperLauncher log is overwritten every time you launch the application. I'd copy superlauncher.log to another folder before relaunching the game if you want to inspect the exact failure history.

The superlauncher.log ends with the game's console output and the exit code of that launch, so it tells you the game died, but the useful detail is in the crash report. Inside .minecraft\crash-reports\ or .minecraft\logs\latest.log, look for lines like these (illustrative; your stack trace names whatever the game was building when it ran out):

java.lang.OutOfMemoryError: Java heap space
	at net.minecraft.class_1058.method_1234(class_1058.java:42)

Another common entry in crash reports is Garbage Collection overhead limit exhaustion:

java.lang.OutOfMemoryError: GC overhead limit exceeded

If these lines appear in your log files alongside exit code -805306369, your Java Virtual Machine ran out of heap RAM before it could finish rendering or loading game objects.

How Exit Code -805306369 Compares to Native Crashes

Exit code -805306369 is specifically tied to Java heap memory starvation or process termination under extreme memory pressure. It is important to distinguish this code from other crash exit codes that indicate native hardware or driver failure.

While exit code -805306369 stems from memory allocation limits, exit code -1073741819 (0xC0000005) indicates a native memory access violation where a graphics driver or native DLL attempted to read or write to an invalid memory address. Similarly, exit code -1073740791 (0xC0000409) represents a security fast-fail trigger typically caused by third-party graphics overlays or corrupted GPU drivers.

If your crash log points to a native DLL crash address in GPU driver files such as nvoglv64.dll rather than OutOfMemoryError lines, see our guides on exit code -1073741819 and exit code -1073740791.

Causes and Solutions

The following causes are ranked by how likely each is to be the cause.

1. Insufficient Java Heap RAM Allocation (Most Common)

The most common cause of exit code -805306369 is allocating too little memory for the version or modpack you are running. Modern Minecraft versions require more heap memory than older releases. Modern Minecraft 1.18, 1.20, and 1.21 require at least 4 GB of RAM for smooth vanilla play, while heavily modded profiles require 6 GB to 8 GB.

SuperLauncher automatically selects the correct Java version (Java 8, 17, 21, or 25) depending on the Minecraft release you choose and downloads missing Java components automatically. The first launch of each version downloads game files and Java runtimes, which takes a few minutes on initial startup. Users cannot set a custom Java path or custom JVM arguments. You adjust Java heap memory directly through the launcher settings.

To increase allocated RAM in SuperLauncher:

1. Launch SuperLauncher.
2. Click Settings in the navigation menu.
3. Select 'Game launch' from the options menu.
4. Locate the 'Memory (RAM)' slider. The slider ranges from a minimum of 2 GB up to your computer's physical RAM limit, with standard presets at 2, 4, 6, 8, and 12 GB.
5. Drag the slider to 4 GB for vanilla Minecraft or 6 GB to 8 GB for modded version profiles.
6. Close Settings and start the game.

How to confirm it worked: Launch Minecraft, load a world, press F3 to open the debug overlay, and look at the top right corner. The memory indicator displays your updated maximum heap limit (such as Mem: 45% 3640/8192MB). The percentage should fluctuate comfortably below 85% during gameplay without triggering exit code -805306369.

2. Excessive Render Distance or Intensive Shaderpacks

Setting render distance beyond your hardware's capacity or using complex shaderpacks consumes massive amounts of RAM and VRAM. When render distance is set above 24 chunks in modern Minecraft, chunk loading creates a lot of block and entity state objects in Java memory, rapidly exhausting the allocated heap.

To lower memory demand from graphics:

1. Open Minecraft to the main menu.
2. Select Options, then click Video Settings.
3. Reduce the Render Distance slider to 12 or 16 chunks.
4. If you have shaderpacks installed, click Shader Packs in Video Settings and select Off.
5. If the game crashes before reaching the main menu, open File Explorer and go to %APPDATA%\.minecraft.
6. Open the shaderpacks folder and temporarily move your shader files to a folder outside .minecraft.

How to confirm it worked: Load into your singleplayer world and fly across terrain. Open the F3 debug screen to monitor RAM usage. Garbage collection pauses will disappear, memory allocation will remain stable, and the game will not crash to SuperLauncher.

3. Memory Leaks from Incompatible or Buggy Mods

In modded Minecraft profiles, memory leaks occur when a mod retains references to unloaded world chunks, entities, or texture assets in RAM. Over time, the Java heap fills with uncollectable objects until the Garbage Collector fails, leading to java.lang.OutOfMemoryError and exit code -805306369.

SuperLauncher stores game files in %APPDATA%\.minecraft (or C:\Users\<user>\AppData\Roaming\.minecraft). Modded profile files and mods are stored inside %APPDATA%\.minecraft\versions\<profile name>\mods.

To isolate a memory-leaking mod:

1. Open SuperLauncher and highlight your modded profile.
2. Click the 'Open version folder' button to open %APPDATA%\.minecraft\versions\<profile name>.
3. Open the mods folder located inside that profile directory.
4. Move half of your .jar mod files into a temporary folder on your desktop.
5. Launch Minecraft and play for 10 minutes to test stability.
6. If the game runs without crashing, the leaking mod is inside the removed half. Repeat this process by dividing the remaining mods until you isolate the exact mod causing the memory leak.

How to confirm it worked: After removing or updating the problem mod, memory usage in the F3 screen will drop periodically as Garbage Collection runs, keeping RAM usage steady during extended play sessions.

4. Background Applications Starving Physical System Memory

If your PC has 8 GB or 16 GB of total physical RAM and you allocate 6 GB to Minecraft while running web browsers, video playback, or recording software, your operating system will run out of physical RAM. When physical RAM is exhausted, Windows is forced to page memory to disk or terminate background processes abruptly, resulting in exit code -805306369.

To free physical memory on your computer:

1. Press Ctrl + Shift + Esc to open Windows Task Manager.
2. Click the Processes tab and click the Memory column header to sort processes by RAM usage.
3. Select memory-heavy applications such as web browsers, media players, or background utilities.
4. Click End task to close unnecessary applications.
5. Verify in the Performance tab under Memory that total system memory usage is below 50% before launching Minecraft.

How to confirm it worked: Task Manager shows several gigabytes of free physical RAM while Minecraft is running, ensuring Windows does not forcefully terminate the Java runtime process.

What Doesn't Help

When troubleshooting exit code -805306369, avoid these common but ineffective steps:

• Allocating 100% of your computer's physical RAM in launcher settings. Assigning 16 GB of RAM on a system with 16 GB total memory deprives Windows, background services, and graphics drivers of basic operating memory. This leads to system freezes, disk paging lag, and forced process kills. I wouldn't allocate more than 50% to 60% of your total system physical RAM to Minecraft.
• Attempting to add custom JVM flags or manually change the Java executable path. SuperLauncher automatically selects and manages Java versions (Java 8, 17, 21, or 25) per Minecraft version and manages JVM launch arguments internally. Users cannot set a custom Java path or custom JVM arguments. Manual edits to launcher configuration files will be overridden or ignored.
• Running Display Driver Uninstaller (DDU) to wipe graphics drivers. Reinstalling GPU drivers helps with native system crashes like exit code -1073740791 or exit code -1073741819, but does not resolve Java heap space exhaustion.
• Deleting .minecraft\options.txt or reinstalling game files without adjusting the RAM slider in SuperLauncher. Exit code -805306369 is a RAM capacity issue, not a corrupted configuration file issue.

Always ensure you own a legitimate copy of Minecraft: Java Edition purchased from official channels. Purchasing Minecraft: Java Edition ensures your game files, runtime dependencies, and account authentication download correctly through SuperLauncher.