Page MenuHomeFeedback Tracker

Recurrent unhandled exception access violation crash in exp server 1.27
Need More Info, NormalPublic

Description

Every 20 minutes or so my dedicated server is crashing, with the same memory address (0x7ff69d8b52f0) trying to access 0xffffffffffffffff

I have noticed other current threads describing server crashes trying to access 0xffffffffffffffff however this is an unhandled exception rather than the listed cause of those other threads, and the calling address of 0x7ff69d8b52f0 differs from the other threads as well.

The crash appears to be time-triggered, as I could not correlate any specific action or circumstance against the crashes. I even tried connecting and simply standing still, and the crash occurred, which implies the cause is not player-triggered per se.

Log output and memory dumps of 3 such crashes attached below

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
Dedicated server is windows 10 64 bit, client is windows 11 64 bit
Category
Game Crash
Steps To Reproduce

Starting the server, connecting and waiting causes the crash to happen after around 20 minutes.

Additional Information

The server is running CF, BasebuildPlus 2.0 and MMG storage - all of which have been updated to the latest 1.27-friendly versions.

Event Timeline

Geez changed the task status from New to Need More Info.Mar 3 2025, 4:10 PM
Geez added a subscriber: Geez.

Hello Schrodinger.
Can you please check on stable if the issue occurs there as well? Also does this occur on a vanilla setup?

I can't prove a negative but I can confirm that I haven't yet seen this issue on an official server I started on the same machine.

Also anecdotally it looks like vanilla doesnt seem as prone

Can I infer that whatever code tweaks resovle this will make their way back to the experimental fork in due course?