--- title: "Minecraft crash report: how to read it and find the cause" description: "Learn to read a Minecraft server crash report and latest.log: where the files are, how to spot the line that matters and what each common error means." url: "https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report" type: "page" language: "en-US" --- Minecraft · 10 min · Intermediate Published on Aug 26, 2026 · Updated on Aug 26, 2026 # How to read a Minecraft server crash report The server went down and left behind a huge file full of text. This guide shows where to look, how to separate the noise from the real cause and what to do with each type of error. By [Equipe StreetHosting](https://streethosting.com.br/en/autores#equipe-streethosting) · StreetHosting infrastructure and support team [Deploying and running apps](https://streethosting.com.br/en/guides/topics/deploy) Summarize with: [](https://chat.openai.com/?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fminecraft%2Fread-minecraft-crash-report.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "ChatGPT") [](https://claude.ai/new?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fminecraft%2Fread-minecraft-crash-report.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Claude") [](https://www.google.com/search?udm=50&aep=11&q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fminecraft%2Fread-minecraft-crash-report.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Google AI Mode") [](https://x.com/i/grok?text=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fminecraft%2Fread-minecraft-crash-report.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Grok") [](https://www.perplexity.ai/search/new?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fminecraft%2Fread-minecraft-crash-report.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Perplexity") Share: [](https://x.com/intent/tweet?text=How%20to%20read%20a%20Minecraft%20server%20crash%20report&url=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fminecraft%2Fread-minecraft-crash-report "Share on X") [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fminecraft%2Fread-minecraft-crash-report "Share on Facebook") [](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fminecraft%2Fread-minecraft-crash-report "Share on LinkedIn") [](https://wa.me/?text=How%20to%20read%20a%20Minecraft%20server%20crash%20report%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fminecraft%2Fread-minecraft-crash-report "Share on WhatsApp") For agents: Copy as Markdown [.md](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report.md) In this guide 6 sections * [Where the files are](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#onde-ficam) * [Anatomy of a crash report](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#anatomia) * [How to find the line that matters](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#linha-que-importa) * [The most common errors](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#erros-comuns) * [Isolate the culprit by bisection](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#bisseccao) * [When the machine is the problem](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#hardware) Quick answer A Minecraft crash report is read back to front: skip the description, find the line that starts with `Caused by` and look there for the first package that is not `net.minecraft` or `java.*`. That name is the guilty plugin or mod. If you prefer the shortcut, drop the file into crashdoc, which recognizes the known errors and explains in Portuguese what the stack trace is saying. ## Where the files are[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#onde-ficam) Every Minecraft server writes two kinds of file when something goes wrong, and they are not for the same thing. | Path | What it is | When to use it | | --------------------------------------------------- | --------------------------------------- | ------------------------------------------------------------ | | crash-reports/crash-YYYY-MM-DD\_HH.MM.SS-server.txt | Snapshot of the moment of the crash | The server died suddenly and you want the exception | | logs/latest.log | Full history of the current run | Almost always. It is the most informative file | | logs/YYYY-MM-DD-1.log.gz | Logs from previous runs, compressed | When the problem has happened before and you want to compare | | logs/debug.log | Detailed log, when enabled in the build | Deep investigation of strange behavior | On a managed control panel these files show up in the file manager, in the server root. On a root VPS, they sit in the same folder as `server.jar`. Always download both: the crash report tells you what broke, the latest.log tells you what was happening before. The `latest.log` is overwritten on every startup. If the server restarted automatically after the crash, the file you care about has already become a dated `.log.gz`. Download it before restarting again. ## Anatomy of a crash report[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#anatomia) The file is intimidating because of its size, but it has a fixed structure. Always the same four parts, always in the same order. ### 1\. Description[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#anatomia-descricao) The first lines carry a random joke line generated by the game, which you can ignore, and right below it a `Description` field. That field tells you at what moment the server went down: `Exception in server tick loop`, `Ticking entity`, `Ticking block entity`, `Exception initializing level`. That alone narrows the pool of suspects a lot. ### 2\. Exception and stack trace[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#anatomia-stacktrace) Next comes the exception name, followed by dozens of lines starting with `at`. Each of those lines is a method call, from the most recent to the oldest. It is the execution stack at the exact moment of the break, and it is where the answer lives. ### 3\. Server details[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#anatomia-detalhes) A section with the server version, the exact build, the loaded world, the list of plugins or mods and the relevant settings. This is where you check whether the guilty plugin is really on the version you think it is. ### 4\. System details[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#anatomia-sistema) Java version, allocated and free memory, operating system, number of cores. This section alone solves two kinds of crash: too little heap and the wrong Java version. Before you go googling the error, read the system section. A `Memory: 42 MB free` on a server with 4 GB of heap explains the crash without needing anything else. ## How to find the line that matters[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#linha-que-importa) Ninety percent of the stack trace is noise. The trick is knowing which kind of line to throw away. * **Discard the platform packages.** Lines with `net.minecraft`, `java.util`, `java.lang`, `io.netty` and `org.bukkit`are almost always just the machine running someone else's code. * **Look for the odd package out.** Names like `com.someplugin.core` or `net.somemod.tile` give away the author of the code that broke. The first one to appear from top to bottom is the closest to the problem. * **Go to the Caused by.** A stack trace can have several chained `Caused by` blocks. The last one is the real root cause, the rest is the error being passed up layer by layer. * **Write down the coordinates when there are any.** In `Ticking entity` and `Ticking block entity` crashes, the file reports the position in the world. Going there and removing the block or the entity closes the case. If you have the file but not the patience, crashdoc does exactly this triage: it finds the Caused by, isolates the third-party package and translates the error pattern into an explanation in Portuguese, with the suggested fix. The file is read in your own browser. It sits alongside the other [free StreetHosting tools](https://streethosting.com.br/en/ferramentas). ## The most common errors and what they mean[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#erros-comuns) The vast majority of server crashes fall into half a dozen patterns. Recognizing the pattern is faster than understanding the code. ### NoClassDefFoundError and NoSuchMethodError[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#erro-versao-plugin) The plugin or mod called a method that does not exist in the server version that is running. It is the classic error of a plugin compiled for another Minecraft version, or of a plugin that depends on another one you did not install. The fix is to download the plugin version compatible with your build, or to install the missing dependency. ### Mixin apply failed[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#erro-mixin) Shows up on Fabric and Forge. Two mods tried to change the same piece of game code and one ran over the other, or the mod was written for another version. The mixin name almost always carries the name of the mod responsible. Updating both mods to the same game version solves it most of the time. To build the environment from scratch without this kind of conflict, see [installing mods and plugins together](https://streethosting.com.br/en/guides/minecraft/minecraft-mods-and-plugins-together). ### java.lang.OutOfMemoryError: Java heap space[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#erro-oom) The JVM asked for memory and there was none. There are two possible readings, and they call for opposite solutions. If the server has genuinely grown, with more people online, a bigger world or a new modpack, the heap is too small and needs to go up. If the error repeats after the same amount of uptime every time, even with few people on, some plugin has a memory leak, and raising the heap only pushes the crash later. Never set the heap larger than the real memory available. The system starts swapping, TPS plummets and the process ends up killed anyway, now with no crash report at all. ### Server thread dump and watchdog[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#erro-watchdog) When a tick hangs for longer than the configured limit, the server watchdog kills the process and dumps the state of the main thread into the log. The message usually says the server stopped responding. The dump shows exactly which method the thread got stuck in, and that is where the culprit comes from. If instead of hanging completely the server just gets slow, it is not a crash case but a profiling one: read [how to reduce lag on Paper](https://streethosting.com.br/en/guides/minecraft/reduce-lag-paper-server). ### Address already in use: bind[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#erro-porta) The port the server is trying to open is already taken. It is almost always the previous process that did not die properly after a restart, or two servers configured on the same port. Kill the old process or change the port in `server.properties`. ### UnsupportedClassVersionError[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#erro-java) The installed Java version is older than the one the server build requires. The message carries two class version numbers, and the higher one is what the jar requires. Modern Paper builds ask for Java 21. Installing the right version fixes it on the spot. ### Failed to load eula.txt[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#erro-eula) Not quite a crash, it is the server refusing to start because the EULA was not accepted. Just change the value in the file. The full context is in [what the Minecraft EULA is](https://streethosting.com.br/en/guides/minecraft/what-is-minecraft-server-eula). ## Isolate the culprit by bisection[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#bisseccao) Sometimes the stack trace points at no third-party package, or points at a plugin that was clearly just a victim. In those cases the solution is not to read more, it is to test. And testing in an organized way saves hours. 1. Back up the plugins or mods folder before touching anything. 2. Take half the files out of the folder. Start the server and reproduce what caused the crash. 3. If it broke, the culprit is in the half that stayed. If it did not break, it is in the half that left. 4. Take the suspect half and split it in half again. Repeat. 5. In four or five rounds you get down to a single file, even starting from fifty plugins. If the crash only happens with people online, reproducing it gets hard. In that case compare the logs from several crashes: what repeats across the last three files is the trail of the problem, and what shows up only once is coincidence. * Backup done before removing any plugin * One change at a time, always * Same way of reproducing on every test * Write down the result of each round somewhere * Server and Java versions unchanged during the test ## When the machine is the problem[](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#hardware) There is a category of crash that generates no crash report at all: the process simply disappears and the log ends in the middle of a normal line. That is not a plugin bug, it is the machine. * **The system killed the process.** When the machine runs out of memory, the operating system picks the fattest process and terminates it. The Minecraft server is always the one picked. Clear sign: log cut off mid-line, with no exception at all. * **Full disk.** With no space, the server cannot save the world or write the log. A write error usually shows up before the crash. * **Saturated CPU.** It does not bring the server down by itself, but it makes the watchdog kill the process for a hung tick. If TPS was already bad before the crash, this is the path. * **A plan too tight for the project.** A two-hundred-mod modpack in 2 GB of heap is not a configuration problem, it is math that does not add up. If the diagnosis points at a machine limit, the way forward is to move up a plan or migrate to hardware with more headroom. On the [Minecraft Pro](https://streethosting.com.br/en/minecraft-pro) plans and the [Ryzen VPS](https://streethosting.com.br/en/vps/ryzen) the high per-core clock gives headroom precisely for the spike that brings the server down today. Before spending, though, confirm in the log that this really is the cause: switching plans does not fix a broken plugin. In this guide * [Where the files are](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#onde-ficam) * [Anatomy of a crash report](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#anatomia) * [How to find the line that matters](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#linha-que-importa) * [The most common errors](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#erros-comuns) * [Isolate the culprit by bisection](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#bisseccao) * [When the machine is the problem](https://streethosting.com.br/en/guides/minecraft/read-minecraft-crash-report#hardware) ## Frequently asked questions What is the difference between a crash report and latest.log? The crash report is a snapshot of the moment of the crash, with the exception and the state of the machine. The latest.log is the full history of the run, with everything that was loaded and every warning before the problem. In most cases the latest.log explains better what happened. What does Exception in server tick loop mean? It means something threw an exception while a tick was being processed and the server could not continue. It is a generic message: the real cause is in the Caused by line further down, almost always pointing at a plugin, a mod or a corrupted entity in the world. I got java.lang.OutOfMemoryError. Do I just add more RAM? Adding RAM helps when the server has genuinely grown, with more players, a bigger world or a heavy modpack. But if the error comes back at the same interval every time, some plugin or mod has a memory leak, and raising the heap only delays the crash. The server won't even start and there is no crash report. Now what? Without a crash report, the answer is in logs/latest.log. The most common causes are an unaccepted EULA, a port already in use by an old process, a Java version incompatible with the server build and a config file with a syntax error. Do I need to know Java to understand a crash report? No. You need to know where to look. Finding the Caused by line and the name of the package that is not Minecraft's solves most cases without writing a single line of code. Can I send the crash report to someone to analyze? Yes, and that is the normal path when the error comes from a specific plugin. Before that, it is worth running the file through an analyzer so you reach the plugin author with the information already digested and the exact version where the problem shows up. Next step Minecraft plans Compare Minecraft hosting options in Brazil. [Minecraft plans](https://streethosting.com.br/en/minecraft) [See Minecraft Pro Managed hosting on Ryzen with modpacks, optimized Paper and technical support.](https://streethosting.com.br/en/minecraft-pro) [See Ryzen VPS Ryzen 9 9950X VPS in São Paulo with root access, NVMe and gamer Anti-DDoS.](https://streethosting.com.br/en/vps/ryzen) ## Related guides [Minecraft Intermediate How to reduce lag on a Minecraft Paper server (TPS and mspt) Lag is not 'the host's fault' until you measure it: high mspt comes from the world, the configuration and the code running in the tick. This guide puts diagnosis ahead of aggressive tuning. 6 min Read guide](https://streethosting.com.br/en/guides/minecraft/reduce-lag-paper-server) [Minecraft Intermediate How to install mods and plugins together on a Minecraft server Plenty of people want to combine mods and plugins on the same server. It works in some setups, but it takes the right server software and careful testing. 3 min Read guide](https://streethosting.com.br/en/guides/minecraft/minecraft-mods-and-plugins-together) [Minecraft Beginner Minecraft server EULA: what it is and how to accept it A server that will not start because of the EULA scares beginners. This guide explains what it is, why it exists and how to accept it without errors. 2 min Read guide](https://streethosting.com.br/en/guides/minecraft/what-is-minecraft-server-eula) [← Back to the Guide Center](https://streethosting.com.br/en/guides)