Finally i catched one of those crashes. Since a couple of weeks
mass crashes do occur, causing multiple (usually 5-10) people
to crash simultanously. Although mines was not the most recent version,
even people with a newer one have been affected, so this may
be still valueable for future releases.

I was able today to get the call stack with windows symbols.

Verson 0.5Z
Executable size : 1.818.624 bytes


Unhandled exception at 0x7723e23e in LFS.exe: 0xC0000005: Access violation reading location 0x61b6b069.

> ntdll.dll!@RtlpLowFragHeapFree@8() + 0x2c bytes
ntdll.dll!_RtlFreeHeap@12() + 0x7e bytes
kernel32.dll!_HeapFree@12() + 0x14 bytes
LFS.exe!0053d0fd()
[Frames below may be incorrect and/or missing, no symbols loaded for LFS.exe]
LFS.exe!0053be99()
LFS.exe!005560f7()
LFS.exe!0053bee0()
LFS.exe!0053d0fd()
LFS.exe!0048bcbf()
LFS.exe!0048baf5()
LFS.exe!00440221()
LFS.exe!004cbb5f()
LFS.exe!0049478d()
LFS.exe!004a97c0()
LFS.exe!00447d56()
LFS.exe!004833bb()
LFS.exe!0053db4d()
kernel32.dll!@BaseThreadInitThunk@12() + 0x12 bytes
ntdll.dll!___RtlUserThreadStart@8() + 0x27 bytes
ntdll.dll!__RtlUserThreadStart@8() + 0x1b bytes

I've seen a fair few reports of crashes similar to this (ie ntdll.dll)

To clarify, several clients can crash at the same time with the same error. The server does not crash or throw any errors as far as I'm aware.

We haven't noticed any patterns that may reproduce it yet.