When a game server crashes or the Steam update fails at startup, it almost always leaves a clear line in the log. It tells you whether the game process was terminated abruptly, whether game files are missing, or whether an add-on component is simply reporting something that doesn't matter for operation. Each section below covers exactly one of these messages, from CS2 and Unreal and Unity games to Enshrouded, Hytale and Bannerlord.

You can see the full message in the Console and in the game's log files, which you open under Files. Read the lines before it as well, because the actual cause is often a bit further up. Before you have the game files reinstalled, remove mods or change configuration files, create a backup under Backups.

“Segmentation fault”: Game server process crashed

What the message looks like:

/entrypoint.sh: line <Line>: <Process> Segmentation fault ./game/bin/linuxsteamrt64/cs2 -dedicated <StartupParameters>
/entrypoint.sh: line <Line>: <Process> Segmentation fault /home/container/Insurgency/Binaries/Linux/InsurgencyServer-Linux-Shipping <StartupParameters>

What's behind it: The startup script entrypoint.sh calls the server program. “Segmentation fault” means the program attempted an invalid memory access and was terminated by the system. The server is then offline and connected players are disconnected. In CS2, plugins are usually responsible, especially Metamod or CounterStrikeSharp after a game update; a damaged installation is another possibility.

How to fix it:

  1. Check whether crashes started after a game update. If so, investigate server plugins first.
  2. For CS2, update Metamod, CounterStrikeSharp and plugins to compatible releases. If none exist, temporarily remove the extensions. For Insurgency: Sandstorm, check mods instead.
  3. If the server runs without extensions, add them back individually until you identify the cause.
  4. If crashes continue without extensions, save the server data under Backups. Then verify or reinstall the game files following your server software's instructions.
  5. If crashes persist, open a ticket and include the time of the message.

Good to know: More on CS2 plugins: CS2 Plugins: MetaMod, CounterStrikeSharp and MatchZy.

Game Update via Steam Not Completed ("state is 0x…")

What the message looks like:

Error! App '<App ID>' state is 0x6 after update job.

What's behind it: SteamCMD is Steam's command-line program that downloads and verifies your server's game files. The line means: the download or verification did not complete. The value after state is is an internal Steam status value and doesn't need to concern you. The most common causes are no free storage left, an interrupted download or a disruption on the Steam servers. With incomplete game files, the server may not start.

How to fix it:

  1. First check the "Storage" display in the panel to see how much space is free. A full directory is the most common cause.
  2. If the storage is full or almost full, free up space under Files. What you can safely delete is covered in Disk Full: Fixing "No space left on device".
  3. Restart the server so the verification runs again.
  4. In the Console, look for the line Success! App '<App ID>' fully installed. Then the update is done.
  5. If the error persists despite free storage, open a ticket and include the time of the message.

Good to know: If it was caused by a Steam disruption, the update usually works on a later restart.

Native Program Library Missing ("DllNotFoundException")

What the message looks like:

DllNotFoundException: <Library>
System.DllNotFoundException: Unable to load DLL '<Library>'

What's behind it: A native library is a precompiled program file (usually .so on Linux, .dll on Windows) that the game or a mod loads for specific tasks, such as the Steam integration. Games based on .NET or Unity use DllNotFoundException to report that they couldn't load such a file. Depending on who needs it, either a single function fails or the entire startup. Often the game files are incomplete after an interrupted update, or a mod expects a library that isn't present on the server.

How to fix it:

  1. Read in the message which library is missing. If the name belongs to a mod or the file is located in a mod folder, that mod is the first suspect.
  2. Remove the most recently installed mods as a test and restart the server.
  3. If that doesn't help, have the game files checked via a reinstall in the panel. Create a backup first.
  4. If the error persists, open a ticket, include the time of the message and attach the full startup output from the Console.

Server Terminated Abruptly: "Segmentation fault (core dumped)"

What the message looks like:

Segmentation fault (core dumped)

What's behind it: The operating system terminated the game server abruptly because it accessed memory it isn't allowed to. The addition "core dumped" refers to a memory image for developers and changes nothing for you. The server is offline, and anything that happened since the last save may be lost. The most common causes are damaged game files after an interrupted update, an incompatible mod or too little RAM.

How to fix it:

  1. Restart the server. Many of these crashes are one-offs.
  2. If the crash repeats, remove the most recently installed mods and test again.
  3. Then have the game files checked via a reinstall in the panel. Create a backup first.
  4. If the server crashes mainly under load, such as when many players are online, check the RAM usage. You can get more RAM under Settings & Plan → Plan.
  5. If it keeps happening, open a ticket and include the time of the message.

Unreal Engine Server Crashes with "Fatal error"

What the message looks like:

[2026.10.20-18.04.12:345][512]LogCore: Fatal error!
[2026.10.20-18.04.12:346][512]LogExit: Executing StaticShutdownAfterError

What's behind it: Many games such as ARK, Conan Exiles, Palworld or Satisfactory are based on Unreal Engine. If the log shows Fatal error! or StaticShutdownAfterError, the server crashed with a severe error and shut itself down. It is offline, and progress since the last save may be missing. The cause is usually in the lines directly before it, for example insufficient RAM, a damaged game file or a mod.

How to fix it:

  1. Read the lines before Fatal error! in the Console or in the game's log file. Unreal games usually store them in the Saved/Logs folder, which you can find under Files.
  2. Restart the server.
  3. If it crashes again, have the game files checked via a reinstall in the panel. Create a backup first.
  4. Remove recently added mods and test without them.
  5. If the lines before it mention a lack of memory (out of memory), increase the RAM under Settings & Plan → Plan.

Steam Update Failed at Server Startup

What the message looks like:

Error! App '<App ID>' state is 0x<Value> after update job.
Failed to install app '<App ID>' (No subscription)
steamcmd.sh: No such file or directory

What's behind it: At startup, the server fetches the current game version via Steam. This update failed, and the cause lies with our server template, not with your settings. No subscription means that Steam doesn't release the game files for the download account being used. steamcmd.sh: No such file or directory means that the Steam download program wasn't found. We are notified about this automatically. Your server keeps running with the previous game version.

How to fix it:

  1. Check in the Console whether the server starts up normally after the message.
  2. Don't change any settings because of this message. A reinstall doesn't help here, because it uses the same template.
  3. Whether a later start manages the update, you can tell in the Console from the line Success! App '<App ID>' fully installed.
  4. If players can no longer join because their game is already newer than the server, open a ticket and include the time of the message.

Hytale: Server Authentication Doesn't Start

What the message looks like:

Failed to create HytaleServer
java.lang.NullPointerException: Cannot invoke "….I18nModule.getMessage(…)" because the return value of "….I18nModule.get()" is null

What's behind it: At startup, the Hytale server sets up its server authentication, meaning the login it needs for operation. For that, it requires its internal language module (I18n, short for internationalization: it provides the texts in the appropriate language). If this module wasn't available yet, the startup crashes at this point. As a result, the server doesn't reach a playable state, and players can't join.

How to fix it:

  1. First, restart the server.
  2. If the error repeats, update the Hytale server files or reinstall them. Back up your world first under Backups.
  3. If the error persists even then, it lies in the Hytale version itself, meaning this exact release of the server software. Then only a newer version helps.
  4. If you get stuck, open a ticket and include the time of the message.

Good to know: You can find more on the state of the Hytale server under Hytale Server: Status, Hosting and Preparation.

"Video driver not supported": Add-on Component Finds No Graphics Driver

What the message looks like:

System.PlatformNotSupportedException: Video driver  not supported
  at Xalia.Sdl.WindowingSystem.Create () […]

What's behind it: A dedicated server runs "headless", meaning without a graphical user interface. Some games or helper programs still start an optional interface or accessibility aid that wants to open a graphics driver. No usable graphics driver is available for this interface, so the component reports this error. The message often contains Xalia, the name of such a helper component; the actual game server doesn't need it and can keep running normally anyway.

How to fix it:

  1. Check whether the server goes online normally after the message: the Console shows further startup lines, and players can join.
  2. If that's the case, you can ignore the message.
  3. If startup aborts, stop the server, remove recently installed mods with interfaces or accessibility aids (UI or accessibility mods), and restart.
  4. If you get stuck, open a ticket and include the time of the message.

Good to know: The message shows up on many servers at every startup. As long as your server is reachable, it's no cause for concern.

“NullReferenceException”: Game or mod accesses a missing object

What the message looks like:

NullReferenceException: Object reference not set to an instance of an object
  at NetworkVisibilityGrid.PositionToLayer (…)
  at ZPlayFabMatchmaking.OnCheckJoinCodeSuccess (…)

What's behind it: Unity games such as Rust and Valheim use objects as program components. This message means a component tried to use a missing or uninitialized object. The server usually keeps running while the affected feature fails. Lines beginning with at form the stack trace: the list of program calls that helps locate the failure. The two example call lines come from separate incidents.

How to fix it:

  1. Update the game and mods to compatible releases.
  2. If the error repeats, read the full stack trace. If it identifies an external mod as the source, stop the server, temporarily remove that mod and restart.
  3. If this resolves the error, look for an updated mod release or report it to its author.
  4. If only built-in game components are involved, report the error with the stack trace to the game project, for example through its official forum or bug tracker.

Good to know: In Rust, NetworkVisibilityGrid handles network visibility; in Valheim, ZPlayFabMatchmaking belongs to matchmaking. Check the full stack trace before removing an external mod.

Enshrouded Reports "Bad Performance"

What the message looks like:

[I 02:25:28,824] [server] Bad Performance 16,751 us (peak: 49,165 us)

What's behind it: With this, Enshrouded reports delayed processing on the server. us stands for microseconds, and the comma separates the thousands: 16,751 us is just under 17 milliseconds, and the value after peak is the peak value. The line alone proves neither that the server lacks performance nor that your configuration is wrong. Several such lines in quick succession usually belong to a single event and are not individual incidents.

How to fix it:

  1. Look at when the lines appear. During the startup phase, while the world loads, delays are not unusual.
  2. Compare the time with what was happening in the game: how many players were online, and what were they doing at that moment?
  3. If the players didn't notice any lag at that time, you can ignore the lines.
  4. If there is noticeable lag over a longer period even though little is going on, open a ticket and include the time of the messages. Whether the server was throttled at that moment, for example by CPU throttling, can be checked specifically using the time.

Crest Texture Helpers Don't Start ("TypeInitializationException")

What the message looks like:

TypeInitializationException: The type initializer for 'Crest.TextureArrayHelpers' threw an exception.

What's behind it: Crest is a Unity extension that games use to render water and oceans. Each program class runs its static startup routine once on first access (type initializer), and for the Crest texture helpers, exactly this has failed. On a dedicated server without a graphics card, a missing graphics feature may be involved. The concrete cause, however, is only named by the inner exception, meaning the actual error message that belongs directly to this line.

How to fix it:

  1. Update the game and all mods.
  2. In the Console, read the inner exception that follows directly. It says what exactly failed.
  3. If the server starts normally and everything works, you can treat the message as a pure rendering warning.
  4. If, however, a function is missing or the startup aborts, fix what the inner exception names. If you get stuck, open a ticket and include the time of the message.

Steam Connection Briefly Hung ("MainLoop appears to have stalled")

What the message looks like:

Assertion Failed: CSteamEngine…MainLoop appears to have stalled > 15 seconds

What's behind it: The Steam part of the server handles the login to Steam, the server list and the verification of players. The line means that it gave no sign of life for over 15 seconds. Usually the server was under heavy load during this time, for example while saving or loading the world. Players may briefly freeze or be disconnected. "Assertion Failed" sounds dramatic, but here it is a check notice and not a crash.

How to fix it:

  1. You can ignore isolated messages.
  2. If they pile up, compare the times with automatic saves, restarts and the number of players.
  3. Check the CPU and RAM usage in the panel. If the server permanently runs at its limit, reduce the player count or increase the RAM under Settings & Plan → Plan.
  4. If the message also appears regularly without load, open a ticket and include the time of the message.

Good to know: How to reduce the load is covered in Improving Game Server Performance.

MariaDB Aborts with "[ERROR] Aborting"

What the message looks like:

2026-10-20 18:04:12 0 [ERROR] <root cause>
2026-10-20 18:04:12 0 [ERROR] Aborting

What's behind it: MariaDB is a database server in which some games and plugins store their data. With Aborting, it shuts itself down after a previous error. This line is only the conclusion, and the actual cause is directly before it. As long as MariaDB isn't running, the game or plugins can neither read nor save data there.

How to fix it:

  1. In the Console, scroll up from Aborting to the first line with [ERROR]. It names the reason.
  2. Common reasons are an unknown or misspelled entry in the configuration file (unknown variable), missing permissions (Permission denied) or damaged data files.
  3. If you changed the configuration recently, undo that change and restart.
  4. Before you change anything in the data files, create a backup.
  5. If you can't find the cause, open a ticket and include the time of the message.

Bannerlord: Restart Loop Caused by an Invalid Token

What the message looks like:

Login Failed! Server is shutting down.

What's behind it: A Bannerlord server registers with a token at TaleWorlds' login service at startup. If this AUTH_TOKEN is invalid or expired, the service rejects it. The server shuts itself down about 20 seconds after starting, is restarted automatically and fails again: that's how the restart loop arises. The tokens are bound to the account you generate them with and expire after three months.

How to fix it:

  1. Open the console in Bannerlord on your computer and enter customserver.gettoken. This generates a new token.
  2. Enter it in the panel as the startup variable AUTH_TOKEN and replace the old value completely.
  3. Restart the server.
  4. In the Console, check that Login Failed! no longer appears.

Good to know: Without a new token, no restart will help. Because the tokens expire after three months, it's best to plan the replacement in good time.

Your message isn't listed?

Read the entire message in the Console or in the game's log file, including the lines before it: crashes are often foreshadowed a few lines earlier. In the stack trace, the list of the program parts that were called, folder and file names show whether a mod or a plugin is involved. Create a backup under Backups before any change. You can find errors from individual mods and plugins under Mod and Plugin Errors in CS2, Valheim, SCP:SL and Other Games. If you get stuck, open a ticket and include the time of the message.