Game keeps crashing on server join

[Senko Aonami]

Hello!

My partner is trying to join a server we would like to play on, but the game keeps crashing. We have tried all kinds of fixes, but we both don't really know how to read the error log so we could really use some help :c If someone could please take a look:

 

Quote

Running on 64 bit Windows 10.0.19045.0 with 16271 MB RAM Game Version: v1.22.3 (Stable) 7/3/2026 3:13:43 PM: Critical error occurred Loaded Mods: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index') at Vintagestory.Client.NoObf.TextureAtlasManager.RegenMipMaps_Patch3(TextureAtlasManager this, Int32 atlasNumber) at Vintagestory.Client.NoObf.TextureAtlasManager.<>cDisplayClass58_0.<RuntimeUploadTextureToPos>b1() in VintagestoryLib\Client\Render\Atlas\TextureAtlasManager.cs:line 374 at Vintagestory.Client.NoObf.ClientMain.ExecuteMainThreadTasks(Single deltaTime) in VintagestoryLib\Client\ClientMain.cs:line 817 at Vintagestory.Client.NoObf.ClientMain.MainGameLoop(Single deltaTime) in VintagestoryLib\Client\ClientMain.cs:line 783 at Vintagestory.Client.GuiScreenRunningGame.RenderToPrimary(Single dt) in VintagestoryLib\Client\MainMenu\Screens\GuiScreenRunningGame.cs:line 173 at Vintagestory.Client.ScreenManager.Render(Single dt) in VintagestoryLib\Client\ScreenManager.cs:line 742 at Vintagestory.Client.ScreenManager.OnNewFrame(Single dt) in VintagestoryLib\Client\ScreenManager.cs:line 686 at Vintagestory.Client.NoObf.ClientPlatformWindows.window_RenderFrame(FrameEventArgs e) in VintagestoryLib\Client\ClientPlatform\GameWindow.cs:line 112 at OpenTK.Windowing.Desktop.GameWindow.Run() at Vintagestory.Client.ClientProgram.Start(ClientProgramArgs args, String[] rawArgs) in VintagestoryLib\Client\ClientProgram.cs:line 354 at Vintagestory.Client.ClientProgram.<>cDisplayClass10_0.<.ctor>b1() in VintagestoryLib\Client\ClientProgram.cs:line 131 at Vintagestory.ClientNative.CrashReporter.Start(ThreadStart start) in VintagestoryLib\Client\ClientPlatform\ClientNative\CrashReporter.cs:line 95 Event Log entries for Vintagestory.exe, the latest 2 ================================== { TimeGenerated = 7/2/2026 1:59:00 PM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.22.3.0, time stamp: 0x691d0000 Faulting module name: KERNELBASE.dll, version: 10.0.19041.7417, time stamp: 0xdaa6d673 Exception code: 0xe0434352 Fault offset: 0x0000000000025369 Faulting process id: 0x14d8 Faulting application start time: 0x01dd0a659920ca10 Faulting application path: D:\Vintagestory\Vintagestory.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 5c539c09-2653-48d3-be3c-011a83addf7f Faulting package full name: Faulting package-relative application ID: } -------------- { TimeGenerated = 7/2/2026 1:58:40 PM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.22.3.0, time stamp: 0x691d0000 Faulting module name: KERNELBASE.dll, version: 10.0.19041.7417, time stamp: 0xdaa6d673 Exception code: 0xe0434352 Fault offset: 0x0000000000025369 Faulting process id: 0x448 Faulting application start time: 0x01dd0a658c5aa317 Faulting application path: D:\Vintagestory\Vintagestory.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: ec13395f-f8af-4213-b11a-1b623e2da5b5 Faulting package full name: Faulting package-relative application ID: }

 

[Zane Mordien]

On 7/3/2026 at 6:22 PM, Senko Aonami said:

Critical error occurred Loaded Mods:

I'm not good at reading this either, but sounds like a mod problem. Have you deleted all the mods and tried it?  If the server owner is responsive you could ask them to send you the error log from the server when he joins. I run my own private server and there was a time or two when the server log was easier to understand. If you haven't tried a fresh install of the game then I'd try that as well. I've had issues connecting to my own server and had to do a fresh install and it worked after that. No clue why but that fixed it for me once.