I'm having the same issue.
Running on 64 bit Windows 10.0.19045.0 with 32682 MB RAM
Event Log entries for Vintagestory.exe, the latest 2
==================================
{ TimeGenerated = 8/18/2025 8:57:19 PM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.12.0, time stamp: 0x66470000
Faulting module name: coreclr.dll, version: 7.0.1023.36312, time stamp: 0x64b06d6c
Exception code: 0xc0000005
Fault offset: 0x00000000001c98a6
Faulting process id: 0x1154
Faulting application start time: 0x01dc10a209644d75
Faulting application path: C:\Users\mattj\AppData\Roaming\Vintagestory\Vintagestory.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.10\coreclr.dll
Report Id: 0e959f94-f61f-4d7e-b327-7468b2daba70
Faulting package full name:
Faulting package-relative application ID: }
--------------
{ TimeGenerated = 8/18/2025 8:41:35 PM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.12.0, time stamp: 0x66470000
Faulting module name: coreclr.dll, version: 7.0.1023.36312, time stamp: 0x64b06d6c
Exception code: 0xc0000005
Fault offset: 0x00000000001c98a6
Faulting process id: 0x4334
Faulting application start time: 0x01dc10a18021c764
Faulting application path: C:\Users\mattj\AppData\Roaming\Vintagestory\Vintagestory.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.10\coreclr.dll
Report Id: 5ee1e2c4-346e-4765-9cbf-05a3611b6f4b
Faulting package full name:
Faulting package-relative application ID: }