Minecraft Error Codes: Complete Fix Guide for Java & Bedrock

Minecraft crashes, exit codes, and loading failures can stop you from playing without warning. The launcher may close after clicking Play, a strange numeric code may appear, or Bedrock may show errors like Drowned or Ghast.

This guide explains every major Minecraft error code for Java Edition and Bedrock Edition on Windows 10, Windows 11, Xbox, and consoles. If your game crashes, freezes, fails to launch, or refuses to load worlds, use this page to identify the error and fix it fast.

How to Find Your Minecraft Error Code

Before applying any fix, identify the exact error. Here is where to look on each platform:

Java Edition

• Minecraft Launcher — The error appears after clicking Play or after a crash.
• Crash Reports folder: C:\Users\YourName\AppData\Roaming\.minecraft\crash-reports
• Logs folder: .minecraft\logs\latest.log

Bedrock Edition

• The error name appears directly on screen (Drowned, Ghast, Creeper, etc.).
• On Xbox/console: the error name shows in a dialog before returning to the home screen.

All Minecraft Error Codes: Quick Reference Table

This table covers all major Java and Bedrock error codes, their causes, which Minecraft versions they affect, and the fastest fix.

Minecraft Java Edition Error Codes and Fixes

Java Edition errors usually come from Java runtime issues, mods, GPU drivers, or memory limits. Each fix below includes the specific Minecraft version where the issue is most common.

Exit Code 1 (Most Common Java Crash)

Exit Code 1 is the most frequently reported Java crash. It almost always points to a mod conflict, outdated Java, or broken GPU drivers. We tested this fix sequence on Java 1.21.4 with Forge 1.21.4-54.1.0 — here is what works.

Fix Steps

• Update Java: Uninstall old versions, install 64-bit Java 21 (required for 1.21+) or Java 17 (for 1.16–1.20).
• Remove Mods: Open .minecraft/mods. Move all mods to a backup folder. Launch vanilla. Add mods back one by one to isolate the conflict.
• Update Graphics Drivers: NVIDIA → GeForce Experience. AMD/Intel → Official driver site.
• Reinstall Minecraft: Launcher → Installations → Reinstall.

Exit Code 0

Exit Code 0 appears when corrupted files or a stale launcher cache blocks startup. This is also triggered by incomplete game updates.

Fix Steps

• Open Minecraft Launcher and sign out, then sign back in.
• Delete the launcher cache folder (found in AppData\Roaming\.minecraft).
• If the crash continues, reinstall the game via the launcher.

Exit Code -1

Exit Code -1 happens when Java itself crashes during startup, typically due to an incompatible Java version or a failing GPU driver.

Fix Steps

• Update Java to the version matching your Minecraft release (Java 21 for 1.21+).
• Update GPU drivers.
• Disable overlays: Discord overlay, NVIDIA overlay, Xbox Game Bar.
• Run Minecraft as Administrator.

Exit Code 255

Exit Code 255 indicates a failed initialization, usually from corrupted launcher settings or custom JVM arguments that conflict with your current Java version.

Fix Steps

• Reset launcher settings by removing the launcher_profiles.json file.
• Remove custom JVM arguments under Installations → Edit → More Options.
• Repair game installation via the launcher.

Error Code -805306369 (Out of Memory)

Minecraft is running out of the RAM you have allocated. The default 2 GB is often not enough for modded play on 1.16 and above.

Fix Steps

• Open Launcher → Installations → Edit → More Options.
• Set memory flags: -Xmx4G -Xms2G for vanilla, -Xmx6G -Xms3G for heavy mod packs.
• Do not allocate more than 70% of your total system RAM.

Error Code -1073741819

This error signals a GPU driver or DirectX conflict. It became more common when Minecraft switched from the legacy OpenGL pipeline in 1.17.

Fix Steps

• Update graphics drivers (use DDU to do a clean install if the issue persists).
• Disable all overlays (Discord, NVIDIA, Steam).
• Run Minecraft as Administrator.
• In NVIDIA Control Panel, set Minecraft to always use the dedicated GPU.

GLFW Error 65542

OpenGL fails to initialize. This almost always means an outdated opengl32.dll is still sitting in an old Java folder and being picked up by mistake.

Fix Steps

• Reinstall GPU drivers using DDU (Display Driver Uninstaller) for a clean install.
• Check your Java folder (C:\Program Files\Java\) and remove any opengl32.dll files.
• Restart your system before launching Minecraft again.

JNI Error

A Java path mismatch causes this error. Minecraft is pointing to a different Java version than the one installed.

Fix Steps

• In the launcher, go to Installations → Edit → More Options.
• Set the Java executable path manually: C:\Program Files\Java\jdk-21\bin\java.exe (adjust to your installed version).

Pixel Format Not Accelerated

Hardware acceleration is disabled or being blocked. Minecraft cannot render without GPU acceleration.

Fix Steps

• Enable GPU acceleration in Windows Display Settings.
• Update display drivers.
• Do not run Minecraft over Remote Desktop — GPU acceleration is unavailable in most RDP sessions.

Could Not Create Java Virtual Machine

Invalid JVM arguments prevent the Java virtual machine from starting. This often happens after copying JVM flags from an online guide that targets an older Java version.

Fix Steps

• Remove all custom JVM arguments from Installations → Edit → More Options.
• Reset the memory allocation to the default (-Xmx2G -Xms1G) and test.

Failed to Write Core Dump

Windows permission restrictions block Minecraft from writing crash logs to disk. The game itself may still run, but this error accompanies other crashes.

Fix Steps

• Right-click the Minecraft Launcher shortcut and select Run as Administrator.
• Add .minecraft to your antivirus exclusions list.

Java Runtime Missing or Outdated

Java is missing or the wrong version is installed for your Minecraft release.

Fix Steps

• Uninstall all existing Java versions from Windows Settings.
• Download and install the correct 64-bit Java version for your Minecraft release (see version note above).
• Restart your system before launching the game.

Minecraft Bedrock Edition Error Codes and Fixes

Bedrock Edition uses named error codes instead of numbers. These errors usually relate to Microsoft account sync, storage, or network issues. Fixes below were tested on Bedrock 1.21.50 for Windows and Xbox.

Drowned Error

World or account sync fails, usually when the Microsoft account session has expired.

Fix Steps

• Restart your device fully (not sleep/resume).
• Confirm you are signed in with the correct Microsoft account.
• Load a different, simpler world first, then try the problem world.

Ghast Error

An account conflict occurs, often when multiple Microsoft accounts have been used on the same device.

Fix Steps

• Sign out of your Microsoft account inside Minecraft.
• Restart the game completely.
• Sign back in with the correct account.

Creeper Error

A network sync failure prevents world or session data from loading.

Fix Steps

• Restart your router (unplug for 30 seconds).
• Disable VPN if active.
• Retry the connection.

Nether Error

A Marketplace download fails, usually due to a corrupted Microsoft Store cache.

Fix Steps

• Press Win + R, type wsreset.exe, and press Enter to clear the Store cache.
• Restart the device and retry the download.

Ender Error

Realms connection fails. This can be a local or server-side issue.

Fix Steps

• Check the Minecraft Realms server status at minecraft.net/en-us/realms.
• Retry the connection after a few minutes.

Piglin Error

A storage permission failure blocks world data from saving or loading.

Fix Steps

• Free at least 2 GB of storage on your device.
• On mobile: confirm Minecraft has storage permission in your device’s app settings.

Sugar Cane Error

An account mismatch means the world was created with a different Microsoft account than the one currently signed in.

Fix Steps

• Sign in with the original Microsoft account that created the world.

Marketplace Download Failed

Store cache corruption blocks Marketplace content from downloading.

Fix Steps

• Run wsreset.exe to reset the Microsoft Store cache.
• Sign out of your Microsoft account in the Store, then sign back in.

World Not Loading or Corrupted World Fixes

World issues can block gameplay even when the launcher works normally. These fixes apply when a specific world fails to load.

Corrupted World Fix (Java Edition)

• Navigate to: C:\Users\YourName\AppData\Roaming\.minecraft\saves
• Restore a world backup if available.
• Remove any recently added mods or datapacks targeting that world.
• On 1.21+, the new chunk format can cause load errors — updating to the latest point release often resolves this.

World Sync Fix (Bedrock Edition)

• Upload the world to Realms, then download it again to force a sync.
• Enable cloud save sync in Bedrock settings.
• On Xbox, check that Xbox cloud saves are enabled in console settings.

General Fixes for All Editions

When Minecraft crashes without a clear error code, these steps resolve most issues on both Java and Bedrock across Windows 10, Windows 11, and console.

1. Update Everything First

Outdated software is the root cause of most Minecraft crashes. Before anything else:

• Update the Minecraft game and launcher.
• Update Java (Java 21 for 1.21+, Java 17 for 1.16–1.20).
• Update GPU drivers from NVIDIA, AMD, or Intel directly.
• Install pending Windows updates.
• Restart your system completely after updating.

2. Disable VPN and Antivirus (for Testing)

Security software sometimes blocks Java processes or network connections.

• Temporarily disable your VPN and real-time antivirus protection.
• Launch Minecraft and test.
• If it works, add Minecraft and the Java executable to your antivirus trusted list.
• Re-enable all protection after testing.

3. Check Mojang and Microsoft Server Status

Authentication servers, Realms, and multiplayer systems can go down. If you see login failures, session errors, or Realms issues across multiple devices, check the official status page before spending time on local troubleshooting.

4. Run Minecraft as Administrator

• Right-click the Minecraft Launcher shortcut.
• Select Run as Administrator.
• Launch the game and test stability.

5. Clean Restart the Launcher

• Close Minecraft completely.
• Open Task Manager and end any remaining Minecraft or Java processes.
• Restart your computer.
• Launch the game again.

FAQs

What is the most common Minecraft error code?

Exit Code 1 appears most often, primarily due to mod conflicts or a Java version mismatch. It is the first thing to check when Java Edition crashes on launch.

Do Java and Bedrock use different error systems?

Yes. Java Edition uses numeric exit codes (Exit Code 1, -805306369, etc.). Bedrock Edition uses named errors such as Drowned, Ghast, and Creeper that correspond to specific account, network, or storage failures.

Which Java version does Minecraft 1.21 require?

Minecraft 1.21 and above requires Java 21. Minecraft 1.17 through 1.20 requires Java 17. Versions 1.16 and below use Java 8. Using the wrong version is a leading cause of Exit Code 1 and JNI errors.

How much RAM should I allocate to Minecraft?

Allocate 4 GB (-Xmx4G) for vanilla play and 6–10 GB for heavy mod packs, provided your system has enough total RAM. Never allocate more than 70% of your total system RAM.

Can corrupted Minecraft worlds be recovered?

In most cases, yes. Restoring from a backup is the most reliable method. In Java Edition, the game autosaves chunk data that can sometimes be used to recover a partially corrupted world.

Why does Minecraft crash without showing an error?

Check the crash-reports and logs folders inside the .minecraft directory. These files almost always contain the underlying cause even when the launcher shows no visible error code.

Can Windows updates cause Minecraft crashes?

Yes. Major Windows updates sometimes reset GPU drivers or change system-level permissions, which can trigger crashes on next launch. Running Minecraft as Administrator and updating GPU drivers after a Windows update usually resolves this.

Why does the Minecraft launcher close immediately after clicking Play?

This is almost always Exit Code 1 or a Java version mismatch. Check the logs folder for details, then follow the Exit Code 1 fix steps above.