Minecraft Crashing on PC: Fix Exit Code 1 and Every Crash

Minecraft crashing on PC almost always comes from one of five things: a mod that doesn’t match your game or mod-loader version, the wrong Java version, too little memory allocated, a graphics driver or overlay problem, or damaged game files — and the exact reason is written in the newest crash report in %appdata%\.minecraft\crash-reports. Match your exit code or symptom in the table, then work only that section. This guide covers Java Edition first; Bedrock (the Windows/Microsoft Store version) is at the end.

Match your crash to the fix

When Java Edition crashes, the launcher shows “Game crashed — An unexpected issue occurred and the game has crashed” with an exit code. That number is your first clue.

What you see	Most likely cause	Go to
Exit Code: 1, often right after adding or updating mods	Mod or mod-loader mismatch, wrong Java, corrupted settings	Fix 1 then Fix 2
”Incompatible mods found!” or “Mixin apply failed”	A mod built for another Minecraft or loader version	Fix 2
Crash only on a modpack or a third-party launcher	Wrong Java version for that Minecraft version	Fix 3
Exit Code: -805306369, or crash after loading many chunks	Out of memory	Fix 4
Exit Code: -1073741819 (0xC0000005), black screen, driver error	Graphics driver, overlay, or the wrong GPU on a laptop	Fix 5
Crash after switching Graphics API to Vulkan	Vulkan backend on an unsupported or outdated driver	Fix 5
Crashes in every game, not just Minecraft	System instability (overclock, XMP, CPU)	Fix 6

Fix 1 — Read the crash report

Minecraft Java Edition writes down why it crashed, and reading it takes two minutes and saves an hour of guessing.

1. Press Win+R, type %appdata%\.minecraft and press Enter.
2. Open the crash-reports folder and open the newest file. Near the top, the Description: line and the first lines of the error name the problem — a mod ID, java.lang.OutOfMemoryError, an OpenGL or driver error.
3. If there is no crash report (the game died before writing one), open logs\latest.log and read the last 30–50 lines.
4. Modded launchers (CurseForge, Prism, Modrinth App) keep the same folders inside each instance folder, not in .minecraft.

Whatever name you find there — a mod, Java, memory, a .dll from your GPU driver — tells you which fix below to use.

Fix 2 — Mods and mod loaders

Mods are the single most common cause of Exit Code 1. Each mod is built for one Minecraft version and one mod loader (Fabric, Forge, NeoForge or Quilt), and a mismatch crashes the game on launch.

1. Check versions match. Every mod must target your exact Minecraft version and your loader. Fabric mods won’t run on Forge, and a 1.21.1 mod won’t load on 26.1.
2. Install required libraries. Most Fabric mods need Fabric API; many need a shared library mod. Fabric tells you directly with an “Incompatible mods found!” screen naming what’s missing.
3. Remove the newest mod first. If the crash started after adding or updating a mod, take that one out.
4. Halve the mods folder. Move half of the mods out of mods, launch, and keep halving the half that crashes until one mod is left. With 100 mods this takes about seven launches.
5. Shaders and performance mods. Iris, OptiFine and Sodium hook into rendering and are frequent crash sources after an update. Remove them first when testing a rendering crash.

If the game runs fine without mods, you have your answer — update or replace the mod that broke it.

Fix 3 — Wrong Java version

Every Minecraft Java Edition version needs a minimum Java version, and launching with an older Java crashes immediately.

Minecraft version	Java needed
26.1 and newer	Java 25
1.20.5 to 1.21.11	Java 21
1.18 to 1.20.4	Java 17
1.17 to 1.17.1	Java 16
1.12 to 1.16.5	Java 8

1. The official Minecraft Launcher bundles the right Java automatically. If you use it, open Installations → your profile → Edit → More Options and make sure Java Executable is empty or set to the bundled runtime — a custom Java path left over from an old guide is a common cause of crashes.
2. Third-party launchers and modpacks (CurseForge, Prism, Modrinth App, TLauncher alternatives) may use a Java you installed yourself. Set the instance to the Java version in the table, or let the launcher download it.
3. Old modpacks for 1.16.5 and earlier need Java 8 — a newer Java can crash them too.

Fix 4 — Out of memory

When Minecraft runs out of the memory it was given, it crashes with java.lang.OutOfMemoryError in the log, or with Exit Code -805306369. Modpacks, high render distance and shaders are the usual triggers.

1. In the official launcher, open Installations → your profile → Edit → More Options.
2. The JVM Arguments box starts with -Xmx2G — the 2 GB default. Change it to:
   • -Xmx4G for vanilla or light mods
   • -Xmx6G to -Xmx8G for large modpacks
3. Don’t go above about half your system RAM. On a 16 GB PC, 8 GB is the ceiling. Windows and the GPU driver need memory too, and an oversized allocation can bring longer garbage-collection pauses rather than fewer crashes.
4. Lower render distance to 12–16 chunks if crashes happen while flying or exploring fast — every loaded chunk costs memory.

Modded launchers have a memory slider in each instance’s settings; it sets the same -Xmx value.

Fix 5 — Graphics driver, overlays and Vulkan

Exit Code -1073741819 is the Windows error 0xC0000005 (an access violation). In Minecraft it usually means something went wrong in the graphics driver or in software hooked into the game.

1. Clean-install your GPU driver. Remove it with DDU and install the latest from NVIDIA, AMD or Intel. If crashes began right after a driver update, install the previous version instead.
2. Close overlays and injectors. Discord overlay, screen recorders, RGB and monitoring tools, and old capture software hook into the game’s rendering — close them all and re-test.
3. Laptops: use the dedicated GPU. Minecraft runs as javaw.exe, which Windows often sends to the integrated GPU. With the game running, open Task Manager, right-click javaw.exe → Open file location to find its path. Then go to Settings → System → Display → Graphics, add that javaw.exe, and set it to High performance.
4. Vulkan. Minecraft 26.2 added a Graphics API option in Video Settings — Default, Prefer Vulkan (Experimental) and Prefer OpenGL. Vulkan needs a GPU and driver that support Vulkan 1.2. If the game crashes at startup on Prefer Vulkan, Minecraft switches back to Default on its own; if crashes continue, set Prefer OpenGL and update your driver. Mods that render with OpenGL — shaders especially — may not work with Vulkan yet.

If the log names 0xc0000005 with a module other than your driver, the 0xc0000005 access violation fix covers how to read the faulting module.

Fix 6 — Random crashes in every game

If Minecraft crashes at random and other games do too, the cause is the PC, not Minecraft.

1. Remove CPU and GPU overclocks and undervolts, including Precision Boost Overdrive and MSI Afterburner curves.
2. Disable XMP/EXPO as a test. An unstable memory profile can pass everyday use and crash Java’s heavy memory use. See how to enable XMP or EXPO to re-enable it at a safer speed.
3. Intel Core 13th/14th Gen desktop CPUs: update the motherboard BIOS to get Intel’s microcode fix for the Vmin Shift instability.
4. Check temperatures with an FPS and hardware overlay — crashes that arrive only after a long session often mean heat.

Fix 7 — Repair the game files

If nothing above names a cause, refresh the game itself.

1. Test a fresh profile. In the launcher, create a new installation for the latest release with no mods and default settings. If it runs, the problem is in your old profile.
2. Reset settings. Rename options.txt in .minecraft to options.old. Minecraft rebuilds it with defaults, which clears a video setting your PC can’t start with.
3. Back up saves, then rename the versions folder so the launcher downloads a clean copy of the game.
4. Repair the launcher itself: Settings → Apps → Installed apps → Minecraft Launcher → Advanced options → Repair (for the Microsoft Store/Xbox app version).

Bedrock Edition (Windows) crashes

Bedrock is a different program with no exit codes or Java, so most of the fixes above don’t apply. Work through these instead:

1. Update the game and Windows — Bedrock crashes often follow a version mismatch with the Xbox app or Gaming Services. If the Xbox app itself misbehaves, see the Gaming Services repair tool fix.
2. Turn off Ray Tracing and lower render distance if crashes happen while loading a world.
3. Remove add-ons and resource packs from the world and global resources to test.
4. Repair, then Reset the app in Settings → Apps → Installed apps → Minecraft → Advanced options. Back up your worlds first — Reset can delete local data.

The short version

• Read the crash report in %appdata%\.minecraft\crash-reports — it names the cause.
• Exit Code 1 → check mods and Java versions first.
• -805306369 → raise -Xmx, lower render distance.
• -1073741819 → clean-install the GPU driver, close overlays, put javaw.exe on the dedicated GPU.
• Vulkan crashes → set Graphics API to Prefer OpenGL and update the driver.

If Minecraft runs but stutters or drops frames instead of crashing, the Minecraft lag and stuttering fix and best Minecraft settings for FPS are the next step.

Related guides

• How to fix Minecraft lag, stuttering and FPS drops
• Best Minecraft settings for FPS
• 0xc0000005 access violation crash fix
• Out of video memory error fix
• How to clean install GPU drivers with DDU
• The ultimate guide to timer resolution for gaming