To fix a Minecraft crash, first identify the edition, version, and exact moment it fails: before the launcher opens, during world loading, after adding a mod or add-on, or only when joining a server. Then test the game with a clean profile and no custom content. An Exit Code 1 is a broad Java launch failure, not a diagnosis by itself; the log or crash report is what helps narrow down the cause.
This Minecraft crash troubleshooting guide covers Java and Bedrock on current 1.21+ installations. Back up important worlds before changing files, reinstalling, or testing content that may affect a save.
| What happens | First thing to check |
|---|---|
| Java Edition closes on launch or shows Exit Code 1 | Start an unmodded installation of the same game version; review custom JVM arguments and the latest log. |
| The game crashes after adding a mod, shader, or resource pack | Disable the new content and test again. Check that each remaining mod supports the exact Minecraft version and loader. |
| Java slows down, stutters, then closes | Check available system memory and Minecraft’s memory allocation; reduce demanding graphics settings. |
| Only one world crashes while loading | Back up that world, then compare it with a separate test world. Avoid editing or deleting world files as a first step. |
| Bedrock crashes after enabling packs | Back up the world and deactivate its resource or behavior packs one at a time. |
For Java Edition, create a backup from the world list: select the world, choose Edit, then Make Backup. Minecraft’s Java world backup instructions explain where the backup is stored. Bedrock backup methods vary by device, so use the instructions for your platform in Minecraft’s Backup & Restore support section.
Next, in the official Java Launcher, open Installations and create a new installation using the same release as the world or server that fails. Leave custom game-directory and JVM settings at their defaults. Minecraft recommends this clean-profile check for launcher crashes; if it works, the old profile’s mods or advanced settings are likely involved. This test does not require deleting your existing game folder or saves. See Minecraft’s clean-installation troubleshooting steps.
If a clean Java profile launches, close the game and temporarily move the contents of the profile’s mods folder somewhere safe. Disable shaders and custom resource packs too, then retry. If the crash stops, restore items one at a time until the problem returns. Before restoring a mod, verify that its author lists support for your exact Minecraft release and mod loader. Fabric and Forge mods are not interchangeable simply because both target Minecraft.
For Bedrock, make a world backup first, then deactivate resource packs and behavior packs one at a time. Mojang’s Bedrock add-on troubleshooting guide recommends testing packs individually because add-ons can conflict.
Do not paste a blanket -Xmx6G command into JVM arguments. On Java Edition, open the affected installation’s advanced options, save a copy of the existing arguments, and change only the memory value if the log or symptoms point to low memory. Minecraft’s memory-allocation guidance says systems with 4 GB of total RAM or less may need a 2 GB allocation; on 64-bit systems, it gives half of installed RAM as a recommended maximum. Leave enough memory for the operating system and other apps, and restore the saved arguments if a change makes launch worse.
Install pending operating-system updates, update your graphics driver from the computer or GPU maker, and test with lower render distance and graphics settings. Temporarily disable optional overlays or unplug nonessential controllers and USB devices if the crash started after connecting them. Minecraft’s Java graphics troubleshooting guide covers drivers, system updates, external devices, and disabling mods. For custom launchers, check the launcher’s runtime requirements for the selected game version instead of installing or forcing a Java runtime at random.
If the crash continues, capture the newest Java log or crash report from the game directory used by that installation. The standard game directory commonly has a logs folder containing latest.log and may have a crash-reports folder; custom profiles can store these elsewhere. Note the first reported exception and any named mod, driver, or library near the end of the report. An Exit Code 1 alone does not tell you which component failed.
For a Windows launcher that freezes or will not open, follow Minecraft’s launcher repair and reinstall guidance. Reinstalling the launcher or game should come after a world backup; manually deleting the .minecraft folder can remove saves and other personal game data. If you share a log for help, remove account names and personal file paths first.
If a separate test world works but one saved world repeatedly crashes, stop experimenting on the original and use a copy or backup for further checks. A single affected world does not prove that a chunk is corrupted, so avoid deleting chunks with third-party editors unless you understand the risks and have a separate backup.
If Minecraft only disconnects or returns to the menu when joining a multiplayer world, that may be a connection or server issue rather than a game-process crash. Check whether the same problem happens in a solo world and ask the server owner to review server logs if multiple players are affected. A crash that occurs on your device in every world is more likely to need local game, driver, or content troubleshooting.
No. It indicates that the Java process ended with an error, but the code alone does not identify the faulty mod, runtime, driver, or setting. Test a clean installation and inspect its log.
Not as an early troubleshooting step. That folder can contain worlds, screenshots, resource packs, and profiles. Back up the data you want to keep, and try a separate clean installation first.
Troubleshoot Bedrock separately: update the game through its platform, restart the device, back up the affected world, and test with add-ons disabled. The two editions use different content systems and fixes.
Enable Server Latency and Packet Loss in Warzone to monitor connection quality, read the overlay, and use recurring spikes to guide troubleshooting.
Learn how to carry from mid lane in League of Legends by setting up waves, choosing safe roam windows, reading side lanes, and converting pressure into objectives.
Fix Minecraft Evoker spell problems with a safe vanilla test, version checks, log review, and a step-by-step way to isolate mod or datapack conflicts.
Fix PUBG stuck on Initializing on Steam with a focused checklist for PC service notices, launch options, game files, downloads, and connection issues.
Fix Brawl Stars stuck at 92% loading with an ordered checklist for service notices, network tests, safe updates, Android cache, and account-safe reinstalling.
Best Dead by Daylight visual filter settings start with a small Gamma lift, neutral color and contrast, and a quick check for dark corners, fog, and bright lights.
Find the Steam and EA app fields for Apex Legends launch options, use EA’s documented FPS command, and see why +exec autoexec.cfg remains unverified.
Reduce input lag on a Nintendo Switch dock for Smash Ultimate with TV Game Mode, a direct HDMI test, controller checks, and online-latency troubleshooting.
Find the best EA SPORTS FC audio settings for a clearer referee whistle: tune Stadium Ambience and Commentary, then troubleshoot output or timing issues.
Compare the best Attack Move Click keybinds in League of Legends—A, Shift + right-click, mouse side buttons, and left-click—with setup and kiting tips.
