Minecraft help and troubleshooting

Quick diagnosis: identify your problem

Before you start looking for a fix, answer one question: what exactly happens when you try to play? The decision tree below leads you to the right guide. Find the description closest to your situation and click the link.

Does Minecraft start at all?

• No, the launcher won't open or the game won't start:
  • You see an error message about Java or a missing library → Minecraft won't launch
  • The launcher opens, but nothing happens when you click "Play" → Minecraft won't launch
  • You see a black screen → Minecraft won't launch (section: black screen)
• Yes, the game starts, but:
  • It crashes after a few seconds or minutes with an error report → Minecraft keeps crashing
  • It crashes only with mods and works fine without them → Minecraft keeps crashing (section: mod conflicts)
  • The game runs, but the FPS is low and it stutters → Minecraft lagging (low FPS)
  • An "Out of Memory" message pops up → Out of Memory error
  • You can't join a server: you get a timeout or the connection is refused → Can't connect to a server
  • The game lags ONLY on a server (singleplayer runs fine) → probably a network or server problem → Can't connect to a server

Did the problem start after an update?

• Yes, after a Minecraft update → check whether your mods are compatible with the new version. Usually it's enough to wait for the mods to update or to go back to the previous game version in the launcher settings.
• Yes, after a GPU driver update → roll the drivers back to the previous version in Device Manager (Windows) or download an older version from the manufacturer's website.
• Yes, after a Windows update → check whether Windows Update disabled your GPU drivers. Restart your computer and update your graphics card drivers.

I don't know what my problem is. Where do I look for clues?

• Check the .minecraft/crash-reports/ folder: if there are files in it, the game is crashing → crash guide
• Open .minecraft/logs/latest.log and look for lines with "ERROR" or "WARN" → copy the error text and paste it into Google
• Press F3 in the game: if your FPS is below 30, the problem is performance → lag guide
• If none of the above fits, post on our forum (in Polish) and we'll help you diagnose the problem

Fix-it guides: detailed solutions

Each of the guides below has step-by-step solutions, from the most common causes to more advanced scenarios. Click the one that best describes your problem.

Settings and account: narrator, changing your username

Not every problem is a malfunction. When the game suddenly starts reading the menus out loud, or you're tired of your username, you sort it out in the game settings or in your account. These guides walk you through both on Java, Bedrock, phones and consoles.

Common errors and exit codes

When Minecraft Java Edition closes with an error, it returns an exit code that tells you what kind of problem it was. The most common codes and what they mean:

• Exit Code 0: the game closed normally. If you see this code but the game "crashes", the problem is in the launcher, not in the game itself. Check the launcher logs.
• Exit Code 1: a general Java error, and the most common error code. Causes: mod conflicts, too little RAM, corrupted game files, an incompatible Java version. Open crash-reports/ and look for the "Caused by:" line.
• Exit Code -1: the system shut the game down (often the Out of Memory killer on Linux or the antivirus on Windows). Check that your antivirus isn't blocking javaw.exe and that you have enough RAM.
• Exit Code -805306369: a code from the Java Edition launcher when the game closes without a crash report. Update your graphics card drivers and check how much RAM you allocate to the game.
• Exit Code -1073740791: "STATUS_STACK_BUFFER_OVERRUN". Usually caused by an antivirus (Avast, Norton) or an overlay program (Discord Overlay, GeForce Experience). Turn off the overlays and add Minecraft to your antivirus exceptions.
• Exit Code 255: Java couldn't start. Check the JVM arguments in your launcher profile: a typo in an argument (for example a missing hyphen before Xmx) causes this error.

If your error code isn't on the list, copy the exact message and paste it in our forum's technical support section (in Polish). We'll help you figure out what's wrong.

The most common error messages

Besides exit codes, Minecraft shows specific error messages. These are the ones players run into most often:

• "Could not create the Java Virtual Machine": the JVM arguments are invalid. Restore the default arguments in the installation settings (they start with -Xmx2G). If you edited the arguments by hand, check them for typos.
• "Pixel format not accelerated": your graphics card drivers don't support OpenGL 4.4+. Update the drivers from the manufacturer's website (NVIDIA, AMD, Intel). Minecraft 1.17+ won't run on integrated Intel HD 3000 graphics or older.
• "GL_ERROR 1281: Invalid value": a conflict between shaders and the OpenGL version. Turn off shaders, update your GPU drivers and use a version of Iris/OptiFine that's compatible with your game version.
• "Unable to access jarfile": the launcher can't find the game file. Clear out the .minecraft/versions/ folder and let the launcher download the files again.
• "Failed to verify username": Mojang's authentication servers are down or your session has expired. First check the Mojang server status. If everything works, log out of the launcher and log back in.
• "Ticking entity" / "Ticking block entity": a corrupted mob or block in the world. Open the crash report, find the coordinates of the problem entity and remove it with the /kill command or an NBT editor (for example NBTExplorer).

How to read logs and crash reports

Instead of guessing what went wrong, open the crash report or the log and find the exact cause in it. First, check where the game saves them.

Where the files are

• Windows: %appdata%\.minecraft\ (type this path into the File Explorer address bar)
• macOS: ~/Library/Application Support/minecraft/ (in Finder, press Cmd+Shift+G and paste the path)
• Linux: ~/.minecraft/ (visible once you show hidden files with Ctrl+H)
• Prism Launcher / MultiMC: right-click the instance → open its .minecraft folder

Two folders matter here:

• logs/latest.log: the full log of the last time you ran the game. It contains warnings (WARN) and errors (ERROR).
• crash-reports/: files with the date and time in their names. Every crash produces a separate report.

How to read a crash report

A crash report can look overwhelming, but you only need four things from it:

1. The "Description" line: a short description of the problem, for example "Ticking entity", "Rendering screen" or "Exception in server tick loop".
2. The "Caused by:" line: this is the actual cause of the crash. Copy this line and the next one. They're your starting point for finding a fix.
3. The mod list in the "-- System Details --" section: Forge and NeoForge label it "Mod List", Fabric labels it "Fabric Mods". It shows your installed mods with their versions. Check that they're all for the same Minecraft version.
4. The "-- System Details --" section: information about your system, Java version and graphics card. Check that you have the right Java version (Java 21 for versions 1.20.5-1.21.11, Java 25 for 26.x; the official launcher installs the right one by itself).

If you don't know what your crash report means, paste it into a site like crashy.net: the tool analyzes the report automatically and suggests a fix. You can also paste just the "Caused by:" line into Google, since someone has almost always had the same problem.

Troubleshooting differences: Java vs. Bedrock

Troubleshooting works differently in Java Edition and Bedrock Edition. The key differences:

Minecraft: Java Edition

• Runs on Java (bundled with the launcher), so you fix memory problems with JVM arguments (-Xmx, -Xms)
• Mods can cause conflicts, so when the game crashes, always start by testing without mods
• Crash reports are detailed and readable: they're your most important diagnostic tool
• Requires OpenGL 4.4+: old graphics cards (Intel HD 3000 and older) haven't been supported since version 1.17
• Logs in .minecraft/logs/ give you a full history of errors and warnings
• Many launchers (the official one, Prism, Modrinth App), each with its own RAM and JVM settings

Minecraft: Bedrock Edition (Windows)

• Runs on a C++ engine: it doesn't use Java, so JVM arguments don't apply
• Installed through the Microsoft Store: you fix update problems with "Repair" or "Reset" in the Windows app settings
• Uses DirectX 12 / DirectX 11 and needs newer GPU drivers than Java Edition
• Add-ons (the Bedrock equivalent of mods) cause crashes less often, but they can cause performance problems
• No detailed crash reports, so diagnosis is harder and relies mainly on Windows system logs
• Xbox Live problems: a Microsoft account is required, and you fix sign-in problems through the Xbox app

In short: you can fix Java Edition problems yourself (crash reports, JVM arguments, swapping mods), while Bedrock Edition problems more often need Microsoft support or a reinstall through the Microsoft Store.

Performance optimization: the basics

Even when Minecraft "works", it can work badly: low FPS, drops while exploring new chunks, freezes when the world saves. Start with these basics before you reach for advanced solutions.

Graphics card drivers

Drivers are the most common cause of performance problems and crashes. Minecraft needs up-to-date drivers with OpenGL 4.4+ (Java Edition) or DirectX 11/12 (Bedrock). Update your drivers straight from the manufacturer's website and don't use Windows' automatic updaters, which often install generic, unoptimized versions.

• NVIDIA: nvidia.com/drivers (download the GeForce Game Ready Driver)
• AMD: amd.com/support (download AMD Software: Adrenalin Edition)
• Intel: intel.com/download (Intel Arc/UHD Graphics Driver)

Allocating RAM

By default Minecraft gets 2 GB of RAM, which is too little for modpacks and big worlds. The optimal amount:

• Vanilla (no mods): 2-4 GB
• Light mods (Fabric + Sodium): 3-4 GB
• Medium modpacks (50-100 mods): 4-6 GB
• Heavy modpacks (ATM, FTB, 200+ mods): 6-10 GB

How to change it: in the Minecraft Launcher, open the Installations tab, click the three dots next to the profile → Edit → More Options → change -Xmx2G to the value you want (for example -Xmx4G). Don't allocate more than 50-75% of your computer's total RAM, because the operating system needs memory too.

Optimization mods (Java Edition)

Two mods to start with:

• Sodium (Fabric/NeoForge): a rewritten renderer for 2-3x more FPS. Free, open source and safe.
• Lithium (Fabric): optimizes the game logic (ticks, pathfinding, AI). It doesn't change any mechanics, it just speeds up the calculations.

You'll find more details in our separate FPS optimization guide.

The video settings that affect FPS the most

If you don't want to install mods, change these options in Options... > Video Settings... (from the biggest impact on FPS to the smallest):

1. Render Distance: lower it to 8-10 chunks. It has the biggest single impact on FPS.
2. Simulation Distance: lower it to 6-8. It controls how far out the world stays "alive" (mobs, farms).
3. Graphics: "Fast" instead of "Fancy" or "Fabulous!". It turns off transparent leaves and other effects.
4. Clouds: turn them off.
5. Particles: "Minimal". Fewer particles mean fewer calculations.
6. Smooth Lighting: turn it off. It's computationally heavy.
7. VSync: turn it off if you don't have screen tearing problems. It caps your FPS at your monitor's refresh rate.
8. Mipmap Levels: lower them from 4 to 0-1. A smaller impact, but it saves VRAM.

Related guides

Minecraft problems often come from skipping the basic setup. These guides help you avoid them in the future:

• Minecraft FPS optimization guide: a detailed walkthrough of settings, optimization mods and JVM arguments
• Multiplayer guide: how to play with friends: server setup, port forwarding, Hamachi, Aternos
• Getting started in Minecraft: if you're just starting out and don't know how to set up the game
• How to install mods: installing Fabric, Forge and NeoForge correctly lowers the risk of crashes
• Download Minecraft: official download sources for the game and launchers
• Mod loaders and tools: Prism Launcher, Modrinth App and other tools that make managing the game easier
• How to make a Minecraft server: if the problems are with your own server
• Minecraft hosting: 2026 comparison: if you're looking for stable hosting instead of self-hosting

Frequently asked questions (FAQ)

Didn't find a solution?

If none of the guides above helped, you have a few options:

• minecraft.pl forum (in Polish): describe your problem in the technical support section. Include your game version, Java version (press F3 in the game), mod list, the contents of the crash report and a screenshot of the error. The more details you give, the faster you'll get help.
• Contact form: if you have a question that doesn't fit the forum.
• Official Mojang support: for problems with your account, buying the game, bans and Realms.
• Mojang Bug Tracker: if you suspect your problem is a bug in the game itself. Check whether someone has already reported it.

When you report a problem on the forum, always attach the latest.log file and any crash report. Without them, diagnosing the problem is guesswork: possible, but inefficient. You can paste the log on paste.gg and share the link instead of pasting hundreds of lines straight into your post.