#Can someone help me decipher these crash logs?

1 messages · Page 1 of 1 (latest)

rose cradle
#

Windows 11
Installed via SteamCMD
Ryzen 5900x
64gb ram
1.718gb free / 1862gb SSD
Windrose+
Windrose Server Manager
No additional mods
4x harvest, 2x Loot

World keeps crashing after about 30 minutes to an hour even when only 2 people are connected.

Crash log pretty much always reports the same thing

📎 message.txt
rose cradle
#

Server was up for 2.5 hours, once a specific person connected, it crashed

#

there was another person who was consistently connecting and they were crashing it too

rose cradle
#

2.5 hours uptime, only me and for most of the connected time, 1 hour of that had 1 other person connected

📎 message.txt
glacial sphinx
#

Only happens when certain uses connect? Could they have something in their inventory like a modded item that the server can’t process?

rose cradle
#

not that I can think of. It's now just happening randomly. I tried doing the save clear on mine, I was the only one connected for 2+ hours and it still crashed

#

I thought it was specific users. I had one friend on for 11 hours the other night,

frank ivy
#

Here is the exact breakdown from your logs of what is happening:

  1. The player connects successfully
    First, we can see that the server successfully handles the network connection for the player named 'Tiff':

[2026.04.26-15.24.26:078][140]LogNet: Join succeeded: Tiff

  1. The game validates the character data (and fails)
    The moment Tiff connects, the server reads their character save file and runs a mandatory logic check. It finds a fatal math error in their progression stats—specifically, the game's code strictly requires a character's RewardLevel to be lower than their CurrentLevel. Tiff's character violates this rule:

[2026.04.26-15.24.26:294][140]R5LogCheck: Error: [-1:219140]
!!! R5Check happens !!!
Condition: 'RewardLevel < CurrentLevel'

  1. The server shuts itself down
    Because the server detects this 'impossible' data, it refuses to let the player load in. To protect the rest of the world database from becoming corrupted by bad data, the server intentionally forces a shutdown:

[2026.04.26-15.24.26:327][140]LogWindows: Error: appError called: Fatal error: ...
[219140] UR5GameProblems::UpdateGameStatus Server will be stopped due to data inconsistency

In Early Access games like Windrose, this specific type of progression corruption usually happens if:
• The save file is from an older version of the game, and a recent update changed how leveling/rewards are calculated.
• A mod that altered XP or rewards was used previously and isn't present now.
• Admin commands were used to alter character levels in a way the base game doesn't support.

Since the corruption is isolated to Tiff's character data (R5BLPlayer ID: 07E56DE8CC78476B7EBCAF4B94BEA8A9), you have two options:

  1. Wipe the Character: Have Tiff delete their local character profile and start a fresh character on the server. If this is a dedicated server, you may need to use a database tool to wipe that specific player ID from the RocksDB files while leaving the rest of the world intact.
  2. Rollback: Restore an older backup of the world from before Tiff's character data became corrupted.

That’s just based on one log, same will apply to any other people causing the issue

rose cradle
#

Thank you @frank ivy that really helps. I was digging through the logs more, seems like there's one other person that possibly had this happen. I guess the regular stack trace isn't very helpful on its own.

remote sentinel
#

I wonder what would happen if someone use mod for increased lvl cap and then try to connect to world that have vanilia lvl cap zz_purpleThinking

If perhaps that what that errror mean or not

rose cradle
#

the 'RewardLevel < CurrentLevel' is exactly what that error means. I reached out to Tiff and she apparently created her own server and set it at 1.5x XP.

After a lot of trial and error with server settings, it turns out the RCON built into Windrose+ was causing my server to have latency issues and stability issues. It would ping idle but then get an unresolved ping which stacked up. It would prevent people from logging in as well as eventually a server crash.