Minecraft Error Codes: How to Fix Every Java and Bedrock Error

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 covers every major Minecraft error code for Java Edition and Bedrock Edition on Windows 10, Windows 11, Xbox, and consoles.

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

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)

Versions affected: All Java versions. Most common on 1.16+ with Forge or Fabric mods.

Exit Code 1 is the most frequently reported Java crash. It almost always points to a mod conflict, outdated Java, or broken GPU drivers. Tested on Java 1.21.4 with Forge 1.21.4-54.1.0.

Fix steps:

1. Update Java. Uninstall old versions, install 64-bit Java 21 (required for 1.21+) or Java 17 (for 1.16-1.20).
2. Remove mods. Open .minecraft/mods. Move all mods to a backup folder. Launch vanilla. Add mods back one by one to isolate the conflict.
3. Update graphics drivers. NVIDIA: use GeForce Experience. AMD/Intel: download directly from the official driver site.
4. Reinstall Minecraft. Go to Launcher > Installations > Reinstall.

Exit Code 0

Versions affected: All Java versions. More common after launcher updates.

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

Fix steps:

1. Open Minecraft Launcher, sign out, then sign back in.
2. Delete the launcher cache folder at AppData\Roaming\.minecraft.
3. If the crash continues, reinstall the game via the launcher.

Exit Code -1

Versions affected: All Java versions. Seen frequently on 1.17+ due to OpenGL rendering engine changes.

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

Fix steps:

1. Update Java to the version matching your Minecraft release (Java 21 for 1.21+).
2. Update GPU drivers. If updating alone does not resolve the crash, use DDU (Display Driver Uninstaller) to fully remove the existing driver, then install the latest version clean. This is the same step that fixes GLFW Error 65542 and is equally effective here.
3. Disable overlays: Discord overlay, NVIDIA overlay, Xbox Game Bar.
4. Run Minecraft as Administrator.

Exit Code 255

Versions affected: All Java versions. Common after launcher profile corruption.

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:

1. Reset launcher settings by deleting the launcher_profiles.json file.
2. Remove custom JVM arguments under Installations > Edit > More Options.
3. Repair the game installation via the launcher.

Error Code 5

Versions affected: All Java versions. Common on systems with strict antivirus or limited user account permissions.

Error Code 5 is a Windows access denied error. Minecraft or the Java executable is being blocked from running or writing files, usually by antivirus software or because the game is launched from a restricted user account.

Fix steps:

1. Right-click the Minecraft Launcher and select Run as Administrator.
2. Open your antivirus settings and add the .minecraft folder and Java executable to the exclusions list.
3. If using a work or school computer, confirm the account has permission to run third-party applications.
4. Reinstall Minecraft to a directory where your user account has full write access (avoid Program Files).

Error Code -805306369 (Out of Memory)

Versions affected: 1.16+. Heavy mod packs such as ATM9 and Vault Hunters frequently hit this on default settings.

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:

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

Error Code -1073741819

Versions affected: 1.17+ (OpenGL renderer). Most common on systems with integrated and dedicated GPU.

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:

1. Update graphics drivers. Use DDU (Display Driver Uninstaller) for a clean install if the issue persists.
2. Disable all overlays: Discord, NVIDIA, Steam.
3. Run Minecraft as Administrator.
4. In NVIDIA Control Panel, set Minecraft to always use the dedicated GPU.

GLFW Error 65542

Versions affected: 1.16+. Most common on systems where the GPU driver does not properly support OpenGL 3.2 or higher.

GLFW Error 65542 means Minecraft failed to initialize the OpenGL context. This is a display driver issue, not a game file issue. Reinstalling Minecraft will not fix it.

Fix steps:

1. Update your GPU drivers from the official source: NVIDIA GeForce Experience, AMD Software, or Intel Driver Support Assistant.
2. If updating does not help, use DDU to fully remove the existing driver, then install the latest version clean.
3. If you are running on integrated graphics, make sure your Intel or AMD integrated GPU drivers are also up to date.
4. On laptops with dual GPU (Intel + NVIDIA), open NVIDIA Control Panel > Manage 3D Settings > Program Settings > add Minecraft > set preferred graphics processor to High-performance NVIDIA processor.
5. As a last resort, add -Dfml.earlyprogresswindow=false to your JVM arguments if using Forge, which disables the early loading screen that sometimes triggers this error.

JNI Error

Versions affected: All Java versions. Common after system Java updates that change the default path.

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

Fix steps:

1. Go to Launcher > Installations > Edit > More Options.
2. Set the Java executable path manually: C:\Program Files\Java\jdk-21\bin\java.exe (adjust to your installed version).

Pixel Format Not Accelerated

Versions affected: All versions. Very common on remote desktop sessions and virtual machines.

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

Fix steps:

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

Could Not Create Java Virtual Machine

Versions affected: All versions. Caused by custom JVM arguments that conflict with newer Java versions.

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

Fix steps:

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

Failed to Write Core Dump

Versions affected: All versions. Common on user accounts without administrator privileges.

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:

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

Java Runtime Missing or Outdated

Java versions required by Minecraft release:

• Java 8 for Minecraft 1.12 and below
• Java 17 for Minecraft 1.17-1.20
• Java 21 for Minecraft 1.21+ (current patch: Java 21.0.11 as of April 2026)

Note: Java 25 LTS and Java 26 are now available but Minecraft 1.21 still requires Java 21. Do not install Java 25 or 26 as your primary Minecraft runtime.

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

Fix steps:

1. Uninstall all existing Java versions from Windows Settings.
2. Download and install the correct 64-bit Java version for your Minecraft release.
3. 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

Versions affected: All Bedrock versions. More frequent after Microsoft account system updates.

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

Fix steps:

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

Ghast Error

Versions affected: All Bedrock versions.

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

Fix steps:

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

Creeper Error

Versions affected: All Bedrock versions.

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

Fix steps:

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

Nether Error

Versions affected: All Bedrock versions.

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

Fix steps:

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

Ender Error

Versions affected: All Bedrock versions.

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

Fix steps:

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

Piglin Error

Versions affected: All Bedrock versions. Common on mobile devices and older consoles with limited storage.

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

Fix steps:

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

Sugar Cane Error

Versions affected: All Bedrock versions.

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

Fix steps:

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

Blaze Error

Versions affected: All Bedrock versions. More common after major game updates.

A content sync failure occurs when purchased or downloaded content fails to load properly. Often triggered after a Minecraft update when content needs to re-sync with your account.

Fix steps:

1. Go to Settings > Storage > Clear Cache inside Minecraft.
2. Restart the device.
3. Sign out of your Microsoft account in the game, then sign back in.
4. If the issue continues, uninstall and reinstall Minecraft, then sign in before launching for the first time.

Error Code 0x803F8001

Versions affected: Bedrock Edition on Windows 10 and Windows 11.

This is a Microsoft Store license error. Windows cannot verify your Minecraft license. This is common after a Windows reinstall, account change, or Store update failure.

Fix steps:

1. Open PowerShell as Administrator and run:

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

1. Restart your PC.
2. If the error persists, open the Microsoft Store, sign out, sign back in, and launch Minecraft again.
3. As a last resort, reset the Microsoft Store: press Win + R, type wsreset.exe, and press Enter.

Marketplace Download Failed

Versions affected: All Bedrock versions on Windows.

Store cache corruption blocks Marketplace content from downloading.

Fix steps:

1. Run wsreset.exe to reset the Microsoft Store cache.
2. 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)

1. Navigate to C:\Users\YourName\AppData\Roaming\.minecraft\saves.
2. Restore a world backup if available.
3. Remove any recently added mods or datapacks targeting that world.
4. 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)

1. Upload the world to Realms, then download it again to force a sync.
2. Enable cloud save sync in Bedrock settings.
3. 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.

1. Temporarily disable your VPN and real-time antivirus protection.
2. Launch Minecraft and test.
3. If it works, add Minecraft and the Java executable to your antivirus trusted list.
4. 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 at mojang.com before spending time on local troubleshooting.

4. Run Minecraft as Administrator

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

5. Clean Restart the Launcher

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

Related Game Error Fixes

• Minecraft Error Code Wither Rose: 6 Fixes That Work
• How to Fix Minecraft Bedrock Failed to Start Game Error on Windows 10 & 11
• How to Fix Minecraft Launcher on Xbox App (Error 0xc0000005)

Frequently Asked Questions