java.io.EOFException When Loading NBT or Chunk Data

What the log looks like

java\.io\.EOFException[\s\S]{0,800}net\.minecraft\.nbt\.CompressedStreamTools
(?:CrashException|ReportedException): Loading NBT data[\s\S]{0,2000}java\.io\.EOFException
Failed to read chunk[\s\S]{0,200}(?:CrashException|ReportedException): Loading NBT data

How to fix it

1. Make a full backup copy of your world folder before attempting any file repairs or deletions.
2. Check the log right above the error for chunk coordinates (such as 'Failed to read chunk [9, 3]' or 'at 8,11'), then open the world in MCA Selector or run Minecraft Region Fixer to delete that specific corrupted chunk so the game can regenerate it cleanly.
3. If there are no chunk coordinates and the stack trace points to a mod's world data class (such as Applied Energistics 2's SpawnData), navigate to your world's 'data' subfolder and restore the damaged .dat file from a backup or delete it so the mod can generate a fresh file.
4. If the freeze occurs while testing a custom worldgen mod or datapack, check all structure .nbt files in your resources folder to ensure none are corrupted, truncated, or 0 bytes.
5. Prevent future truncation by always shutting down servers with the '/stop' command and checking that your drive or hosting plan has plenty of free disk space.

Check your own log