# How to Find and Read Minecraft Server Crash Reports (/docs/minecraft/find-read-crash-reports)



import { Step, Steps } from 'fumadocs-ui/components/steps';
import { Files, Folder, File } from 'fumadocs-ui/components/files';

When the Minecraft server JVM crashes (not just an error — a full crash), it writes a detailed **crash report** to the `crash-reports/` folder. These reports contain everything you need to identify the root cause: the exception, the stack trace, the affected entity or chunk, and the full list of mods/plugins that were loaded.

> **Crash report vs log:** A *log* records everything that happened. A *crash report* only exists when the server died. Some errors don't generate crash reports — for those, check `logs/latest.log` instead.

Where Crash Reports Live [#where-crash-reports-live]

<Files>
  <Folder name="(server root)" defaultOpen>
    <Folder name="crash-reports" defaultOpen>
      <File name="crash-2026-04-07_10.30.45-server.txt" />

      <File name="crash-2026-04-06_22.15.10-server.txt" />
    </Folder>

    <Folder name="logs">
      <File name="latest.log" />
    </Folder>
  </Folder>
</Files>

Filenames follow the format `crash-YYYY-MM-DD_HH.MM.SS-server.txt`.

Find a Crash Report [#find-a-crash-report]

<Steps>
  <Step>
    Open Files [#open-files]

    In the [XGamingServer Panel](https://panel.xgamingserver.com), click **Files** in the sidebar.
  </Step>

  <Step>
    Open the crash-reports folder [#open-the-crash-reports-folder]

    Open `crash-reports/`. Reports are sorted by date — the most recent is usually at the top.
  </Step>

  <Step>
    Open the latest report [#open-the-latest-report]

    Click the most recent file. The report opens in the panel's text editor.

    > If `crash-reports/` is **empty** but the server keeps crashing, the JVM was killed externally (usually OOM — exit code 137). See [Java Exit Codes](/docs/minecraft/fix-java-exit-codes) and check `logs/latest.log` instead.
  </Step>
</Steps>

Anatomy of a Crash Report [#anatomy-of-a-crash-report]

A typical crash report has these sections:

<div className="fd-steps">
  <div className="fd-step">
    Description [#1-description]

    ```
    ---- Minecraft Crash Report ----
    Description: Ticking entity
    ```

    The **description** is a one-line summary of where the crash happened. Common descriptions:

    | Description                     | What it usually means                                                                        |
    | ------------------------------- | -------------------------------------------------------------------------------------------- |
    | `Ticking entity`                | An entity (mob, item) errored — see [Fix Ticking Entity](/docs/minecraft/fix-ticking-entity) |
    | `Ticking block entity`          | A tile entity (chest, furnace, mod block) errored                                            |
    | `Exception in server tick loop` | The main game loop crashed — see [Fix Tick Loop](/docs/minecraft/fix-server-tick-loop)       |
    | `Loading NBT data`              | Corrupted player or world data                                                               |
    | `Watching Server`               | Server hung past `max-tick-time` and the watchdog killed it                                  |
    | `Initializing game`             | Crash during startup                                                                         |
  </div>

  <div className="fd-step">
    The exception (Caused by:) [#2-the-exception-caused-by]

    ```
    java.lang.NullPointerException: Cannot invoke "..." because "..." is null
        at net.minecraft.world.entity.LivingEntity.tick(...)
        at com.example.somemod.entity.WeirdMob.tick(...)
    Caused by: java.lang.IllegalStateException: ...
    ```

    **The line that starts with `Caused by:` is the actual root cause.** If there are multiple `Caused by:` lines, the **last one** is the deepest root cause.
  </div>

  <div className="fd-step">
    Stack trace [#3-stack-trace]

    The lines starting with `at ` show the call stack. Look for:

    * **Mod or plugin package names** (`com.somemod.`, `me.someplugin.`) — that's your culprit
    * **Minecraft class names** (`net.minecraft.`) without a mod name above them — points to a vanilla bug or chunk corruption
    * **Specific entity types** (`EntityZombie`, `WitherBoss`) — narrows down the trigger
  </div>

  <div className="fd-step">
    Affected entity / block / level [#4-affected-entity--block--level]

    ```
    -- Entity being ticked --
    Details:
        Entity Type: minecraft:zombie (...)
        Entity ID: 12345
        Entity Name: Zombie
        Entity's Block location: World: (123, 65, -456)
    ```

    This tells you **exactly which entity** crashed and **where in the world**. Use this to find and remove the entity (with `/kill @e[type=zombie,limit=1,sort=nearest]`) or to delete the chunk if it's corrupted.
  </div>

  <div className="fd-step">
    System Details [#5-system-details]

    ```
    -- System Details --
    Details:
        Minecraft Version: 1.20.4
        Java Version: 21.0.1
        Memory: 1234 MB / 4096 MB
        JVM Flags: ...
        Loaded Mods: ...
    ```

    This is the full environment. Useful when sharing — supporters need to know the version and mod list.
  </div>
</div>

Diagnostic Workflow [#diagnostic-workflow]

<Steps>
  <Step>
    Read the Description first [#read-the-description-first]

    It tells you the broad category (entity, tick loop, NBT, startup).
  </Step>

  <Step>
    Find the last Caused by: [#find-the-last-caused-by]

    That's the root cause. Read the message and the next 5–10 stack trace lines.
  </Step>

  <Step>
    Identify the mod/plugin [#identify-the-modplugin]

    Look for non-Minecraft package names (`com.`, `org.`, `me.`, `dev.`). Match them to the mods in your `mods/` or `plugins/` folder.
  </Step>

  <Step>
    Search the error [#search-the-error]

    Paste the exact `Caused by:` line into Google or the mod's GitHub issues. Most crashes are known bugs with documented fixes.
  </Step>

  <Step>
    Try the fix [#try-the-fix]

    Common fixes: update the mod, downgrade the mod, remove a conflicting mod, restore from backup, delete the affected entity/chunk.
  </Step>
</Steps>

Share a Crash Report [#share-a-crash-report]

Use [mclo.gs](https://mclo.gs/) — the same paste service used for logs:

1. Copy the entire crash report
2. Paste at [mclo.gs](https://mclo.gs/) → **Save**
3. Share the URL in our [Discord](https://discord.xgamingserver.com/) or with support

mclo.gs **auto-detects** crash report format and highlights the root cause in its Analysis tab.

Common Issues [#common-issues]

| Problem                                   | Fix                                                                                               |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------- |
| `crash-reports/` folder doesn't exist     | Server hasn't crashed yet, OR the JVM was killed externally (OOM) — check exit codes              |
| Multiple crash reports in the same minute | Server crash-looped on restart. Read the **first** one                                            |
| Crash report blames vanilla code          | Could be world corruption — restore backup or delete the affected chunk with MCA Selector         |
| Crash mentions `Watchdog`                 | Server hung — usually a mod stuck in an infinite loop. Check the thread dump in the report        |
| Same crash on restart                     | The state that caused it is persisted (a corrupted entity or chunk). You must delete or repair it |

Related Guides [#related-guides]

* [Find / Share Server Logs](/docs/minecraft/find-share-server-logs)
* [Fix: Ticking Entity Crash](/docs/minecraft/fix-ticking-entity)
* [Fix: Server Tick Loop](/docs/minecraft/fix-server-tick-loop)
* [Java Exit Codes](/docs/minecraft/fix-java-exit-codes)
* [Server Won't Start](/docs/minecraft/fix-server-wont-start)
* [Common Issues](/docs/minecraft/common-issues)