What "Exception in server tick loop" means in a Minecraft crash report
"Exception in server tick loop" in a Minecraft crash report means an error reached the main server code without anything catching it, so the server stopped. It is the Description: line, a label, and it reads the same whatever went wrong. Six reports from servers we host all carried it:
| Server | Line under the label | Where the cause sits |
|---|---|---|
| NeoForge 1.21.1, twice | java.lang.NullPointerException: Cannot read field "x" because "mf.axis" is null | A bug in the mod Create 6.0.10 |
| NeoForge 1.21.1 | java.util.NoSuchElementException: No value present | A worldgen class of the mod The Sift |
| Spigot 1.16.5 | java.lang.IllegalArgumentException: Unexpected exception java.lang.reflect.InvocationTargetException while attempting to construct a new instance of org.bukkit.plugin.java.JavaPluginLoader | The plugin loader, before any plugin ran |
| Purpur | java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached | The server ran into a resource limit |
| Fabric 26.3 | java.lang.NullPointerException: Cannot invoke "it.unimi.dsi.fastutil.objects.ReferenceArrayList.get(int)" because "this.wrapped" is null | Only Minecraft classes in the trace |
So skip the label. Read the next line, the exception: its type before the colon and its message after it. Then read the at lines below it until you reach code that is not Minecraft, not your loader and not Java. Where the crash report sits and how its parts fit together is in the guide to crash reports and logs; this guide is about this one label.
Exception in server tick loop: how to find which mod caused it
To find which mod caused an Exception in server tick loop crash, look for the first at line whose package is not java., net.minecraft, net.neoforged, net.minecraftforge, net.fabricmc or org.bukkit. On Forge and NeoForge that line also names the jar it came from. This is the Create crash, shortened:
NeoForge 1.21.1, crash report, shortened
Description: Exception in server tick loop
java.lang.NullPointerException: Cannot read field "x" because "mf.axis" is null
at TRANSFORMER/.../com.simibubi.create.foundation.collision.ContinuousOBBCollider.collideMany(ContinuousOBBCollider.java:153) ~[create-1.21.1-6.0.10.jar%23187!/:6.0.10] {re:classloading}
at TRANSFORMER/.../com.simibubi.create.content.contraptions.ContraptionCollider.collideEntities(ContraptionCollider.java:166) ~[create-1.21.1-6.0.10.jar%23187!/:6.0.10] {re:mixin,pl:runtimedistcleaner:A,re:classloading,pl:mixin:APP:aeronautics.mixins.json:...
...
at MC-BOOTSTRAP/net.neoforged.bus/net.neoforged.bus.EventBus.post(EventBus.java:360) ~[bus-8.0.5.jar%2362!/:?] {}
at TRANSFORMER/.../net.neoforged.neoforge.event.EventHooks.fireLevelTickPost(EventHooks.java:1013) ~[neoforge-21.1.264-universal.jar%23174!/:?] {...pl:mixin:APP:aether.mixins.json:common.EventHooksMixin from mod aether,pl:mixin:A}
at TRANSFORMER/.../net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1043) ~[server-1.21.1-20240808.144430-srg.jar%23173!/:?] ...
at TRANSFORMER/.../net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:917) ~[server-1.21.1-20240808.144430-srg.jar%23173!/:?] ...| Part of the line | What it tells you |
|---|---|
com.simibubi.create...ContinuousOBBCollider.collideMany | The class and method that broke. com.simibubi.create is Create's package. |
(ContinuousOBBCollider.java:153) | The source file and line number. Useful for the mod's author. |
~[create-1.21.1-6.0.10.jar...:6.0.10] | The jar in your mods folder and the mod version. This is the file you act on. |
{...pl:mixin:APP:aeronautics.mixins.json...} | Changes other mods made to this class while it loaded. A lead to keep in mind, not the cause by itself. |
net.neoforged.bus, net.minecraft.server | The loader and the game passing the tick along. They carry the error, they did not make it. |
Read top down. The first frame here is already Create, in create-1.21.1-6.0.10.jar, and every Create frame below it points to the same jar. The trace runs through tickServer, so the crash came while the server was running, during the end of a world tick.
The curly brackets need care. aeronautics.mixins.json on ContraptionCollider means a mod with that mixin config changed the class, and the Aether line spells it out with from mod aether. That does not make them guilty. In this case the bug was in Create itself: on 14 November 2026 Create's source code got the commit "Fix crash in OBB Collider when an entity is aligned with the collider on all 3 axes". Two different servers crashed with the exact same first line, which is also why searching that line together with the mod name finds the bug report.
Exception in server tick loop on startup
An Exception in server tick loop on startup carries the same label even though no tick has run yet. The frames just above MinecraftServer show when it happened. Two of the six reports came at start:
NeoForge 1.21.1, crash report, shortened
java.util.NoSuchElementException: No value present
at java.base/java.util.Optional.orElseThrow(Optional.java:377) ~[?:?] {re:computing_frames}
at TRANSFORMER/.../mielon.thesift.worldgen.SiftPortalVegetation.restore(SiftPortalVegetation.java:205) ~[mielons-the-sift-2.0.0-mc1.21.1-neo.jar%23130!/:?] {re:mixin,re:classloading}
...
at TRANSFORMER/.../mielon.thesift.platform.NeoEvents$ServerLifecycleEvents.lambda$static$0(NeoEvents.java:57) ~[mielons-the-sift-2.0.0-mc1.21.1-neo.jar%23130!/:?] {re:classloading}
...
at TRANSFORMER/.../net.neoforged.neoforge.server.ServerLifecycleHooks.handleServerStarted(ServerLifecycleHooks.java:113) ~[neoforge-21.1.265-universal.jar%23126!/:?] {re:classloading}
at TRANSFORMER/.../net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:674) ...The first frame is Java: Optional.orElseThrow throws NoSuchElementException when the value it was asked for is not there. Java is the messenger. The next frame is the first one that matters, mielon.thesift.worldgen, in mielons-the-sift-2.0.0-mc1.21.1-neo.jar. NeoForge called the mod from handleServerStarted, the hook for a server that has just started, and the mod's portal code asked for a value that was not there.
Spigot 1.16.5, crash report, shortened
java.lang.IllegalArgumentException: Unexpected exception java.lang.reflect.InvocationTargetException while attempting to construct a new instance of org.bukkit.plugin.java.JavaPluginLoader
at org.bukkit.plugin.SimplePluginManager.registerInterface(SimplePluginManager.java:95)
at org.bukkit.craftbukkit.v1_16_R3.CraftServer.loadPlugins(CraftServer.java:369)
at net.minecraft.server.v1_16_R3.DedicatedServer.init(DedicatedServer.java:291)
...
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
...
Caused by: java.lang.NullPointerException
... 10 moreThis one has no third party frame at all. DedicatedServer.init and CraftServer.loadPlugins place it at start, while Spigot was setting up the loader for plugins, before a single plugin was read. The last Caused by: is a NullPointerException with no lines of its own, so the report does not say what was null. Read latest.log from the top for the lines written before the crash. sun.reflect also shows the server ran on Java 8; newer Java versions keep that class under jdk.internal.reflect. For start problems in general, see Minecraft server not starting, and for plugins that fail one by one, plugin not loading.
Exception in server tick loop with no mod in the stack trace
An Exception in server tick loop with no mod in the stack trace means the error was thrown inside Minecraft's own code. That says where it broke, not who caused it. On a Fabric 26.3 server it looked like this:
Fabric 26.3, crash report, shortened
java.lang.NullPointerException: Cannot invoke "it.unimi.dsi.fastutil.objects.ReferenceArrayList.get(int)" because "this.wrapped" is null
at knot//it.unimi.dsi.fastutil.objects.ReferenceOpenHashSet$SetIterator.next(ReferenceOpenHashSet.java:522)
at knot//net.minecraft.server.level.DistanceManager.runAllUpdates(DistanceManager.java:85)
at knot//net.minecraft.server.level.ServerChunkCache.runDistanceManagerUpdates(ServerChunkCache.java:273)
...
at knot//net.minecraft.server.MinecraftServer.waitUntilNextTick(MinecraftServer.java:859)
at knot//net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:758)knot// is the name of Fabric Loader's class loader, not a mod. it.unimi.dsi.fastutil is a collections library that Minecraft calls here, and every other frame is net.minecraft. The game was updating chunk loading in DistanceManager between two ticks when a list it walked through was empty where it should not be.
- A mod can still be behind it. Mods change Minecraft classes with mixins, and on Forge and NeoForge the curly brackets after a frame list those changes. This Fabric report carries no such list, so the trace cannot rule a mod in or out.
- Read the report further down. Blocks with
Details:show what the game was handling, andlatest.logshows what happened right before. A warning from a mod a few lines earlier is a lead. - Watch whether it comes back. One crash after weeks without trouble is different from a crash at the same spot after every restart.
- Test without the newest mods. With a backup made, take out the mods you added last and see whether the crash returns. Searching the first exception line with the Minecraft version also shows whether others hit the same bug on an unmodded server.
java.lang.OutOfMemoryError: unable to create native thread on a Minecraft server
java.lang.OutOfMemoryError: unable to create native thread on a Minecraft server means Java asked for one more thread and did not get it. The message gives 2 reasons itself: memory ran out, or a limit on processes or resources was reached. Here the type of the exception tells you more than any frame.
Purpur, crash report, shortened
Description: Exception in server tick loop
java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached
at java.base/java.lang.Thread.start0(Native Method)
at java.base/java.lang.Thread.start(Thread.java:1444)
...
at me.lucko.spark.paper.common.monitor.MonitoringExecutor.scheduleAtFixedRateMillis(MonitoringExecutor.java:41)
at java.base/java.lang.Thread.run(Thread.java:1474)The first frame outside Java is spark's monitoring code, me.lucko.spark. Spark did not cause this. It happened to be the code that asked for a thread at the moment none was left, and on another run it could be any other plugin or the game itself. With an OutOfMemoryError, the trace shows who asked last, not who used everything up, so removing the plugin in the trace does not fix it.
Treat it as a resource problem. Check whether memory use was near the limit of your plan before the crash, and see how much RAM a Minecraft server needs for what your player count and plugins call for. If it comes back while memory use looks normal, look at what you added last and take those plugins out one at a time.
How to fix Exception in server tick loop
How to fix Exception in server tick loop depends on what the line under the label says. Match it to one of these 5 cases:
| What the trace shows | What to do |
|---|---|
| A mod jar in the first frames, as with Create 6.0.10 | Update that mod, or report the crash to its author with the full report. Search the exception line with the mod name first: the bug may already be known. |
| A mod jar during start, as with The Sift | Check for a newer build for your loader and Minecraft version. If none helps, take the mod out after a backup and report it. |
org.bukkit or the plugin loader at start | Read latest.log from the top, check the server version against your plugins and Java version. See the Java version guide. |
OutOfMemoryError | A resource limit. Do not chase the plugin in the trace; check memory and recent additions. |
Only net.minecraft and Java | Read Details: and the log before the crash, then test without the newest mods. |
For the Create crash, the fix is in Create's source code since 14 November 2026, but on 16 November 2026 the newest Create release for NeoForge 1.21.1 on Modrinth was still 6.0.10. Until a newer version is out, the crash can return when a moving contraption meets an entity lined up with it on all 3 axes. Check Create's page for 6.0.11 or later, and install it from the Mods tab once it is there.
Swap or remove the mod on Lodehost
Note the jar and the exception
Open the newest file in
crash-reportson the Files tab, or scroll up in the Console tab. Write down the exception line and the jar name from the first frame that is not Minecraft, the loader or Java.Make a backup
On the Backups tab, make a backup before you change mods. A mod that adds blocks or generates parts of the world leaves data behind that can be lost once the world loads without it.
Install a newer build
On the Mods tab, press Remove next to the jar under Installed mods. Then type the mod's name in Search mods under Verified Modrinth catalog and press Verify & install. It only offers builds for your loader and exact Minecraft version, and required dependencies come along.
Or upload a file yourself
A build that is not in the catalog goes in through the Files tab: open
mods, orpluginson Spigot, Paper and Purpur, and use Upload, or From link for a direct download address.Start and read the console
If the same exception comes back from the same jar, the build has the bug as well. Leave the mod out or wait for a fixed release. If a different mod shows up, start over with that one.
Do not restore a backup to fix a mod bug
Restoring a backup, which on the Backups tab needs the server stopped, puts the world back but leaves the same jar in place, so a mod bug can crash it again. Restore when the world itself was damaged, and change the jar when the trace points to a mod.
Written and checked by the Lodehost team, last reviewed on 16 November 2026.






