How to Find and Read Minecraft Crash Reports
Learn how to locate crash reports, understand stack traces, and identify the cause of server crashes.
When your server crashes, it generates a crash report with details about what went wrong. Learning to read these helps you fix issues faster.
Finding Crash Reports
Open your server files
Access the XGamingServer panel and go to Files.
Navigate to crash reports
Open the /crash-reports/ folder. Files are named with the date and time of the crash.
Open the latest report
Open the most recent file. If there's no crash report, check /logs/latest.log instead — not all errors generate crash reports.
Reading a Crash Report
Key sections to look for:
Description: A one-line summary of what crashed.
Description: Ticking entityCaused by: The actual error.
Caused by: java.lang.NullPointerExceptionStack trace: Shows which code caused the error. Look for:
- Plugin or mod names in the trace
- Minecraft class names (for vanilla bugs)
- Line numbers for code references
System Details: Server version, Java version, mods/plugins loaded.
Sharing Crash Reports
Upload the crash report to mclo.gs for easy sharing. It automatically highlights errors.
💡 Tip: The most important information is usually in the first 10-20 lines. Look for "Description", "Caused by", and any plugin/mod names mentioned.
📝 Note: If the
/crash-reports/folder is empty, the server may have been killed without generating a report (e.g., out-of-memory). Check Java Exit Codes instead.
See also: Find and Share Server Logs | Troubleshooting
If you need help, join our Discord.
How is this guide?
