Direct answer

A server crash during chunk generation may come from a world-generation mod/datapack, corrupted region data, JVM failure or resource exhaustion. Preserve the crash location and error before deleting chunks.

What it means

A failure limited to brand-new terrain suggests a different cause than a failure when loading an existing corrupt region. The stack trace and coordinates are more useful than the final server stopped line.

Practical example: Example: crashing only while generating brand-new terrain after adding a worldgen datapack suggests a generator compatibility problem. Crashing every time a known coordinate is loaded may instead point to a damaged existing region. Those require different backup-based tests; deleting region files loses builds and is not a first-line fix.

If you are a player

  • Record whether the crash happens when exploring new terrain or entering the same old location.
  • Avoid repeatedly forcing that area to load on the live server.

If you run the server

  1. Back up the complete world, player data and current generation mod/datapack set.
  2. Read the first meaningful crash cause in crash-reports and latest.log, including any chunk coordinates or generator class.
  3. On staging, try generating a small region with the same exact game version and mods.
  4. Check memory and disk errors independently, without assuming all crashes are RAM issues.
  5. If one existing region is corrupt, restore the specific area from backup; destructive region deletion is a last resort with explicit data-loss warnings.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000