Game's crashing on 1.20.11

[Kassc]

I've restarted my PC, updated my video drivers, re-installed vintage story and I continue to randomly crash.

 

Running on 64 bit Windows 10.0.19045.0 with 65298 MB RAM

Event Log entries for Vintagestory.exe, the latest 3
==================================
{ TimeGenerated = 5/28/2025 11:27:52 PM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.11.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: 0x4ac8
Faulting application start time: 0x01dbd0334a04eb15
Faulting application path: E:\Users\Kassc\AppData\Roaming\Vintagestory\Vintagestory.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.10\coreclr.dll
Report Id: 35a69aeb-35fb-45cf-b43a-799882cf616c
Faulting package full name: 
Faulting package-relative application ID:  }
--------------
{ TimeGenerated = 5/28/2025 8:47:03 PM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.11.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: 0x4e0c
Faulting application start time: 0x01dbd032db85fb2e
Faulting application path: E:\Users\Kassc\AppData\Roaming\Vintagestory\Vintagestory.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.10\coreclr.dll
Report Id: 4a4b862c-b4b9-454e-8612-e92001fc3f6a
Faulting package full name: 
Faulting package-relative application ID:  }
--------------
{ TimeGenerated = 5/28/2025 8:44:32 PM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.11.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: 0x362c
Faulting application start time: 0x01dbd0329f3af00a
Faulting application path: E:\Users\Kassc\AppData\Roaming\Vintagestory\Vintagestory.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.10\coreclr.dll
Report Id: 28ae906b-ded1-40a3-8ac0-f1ac13d66933
Faulting package full name: 
Faulting package-relative application ID:  }

[Matt Covino]

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:  }

[LadyWYT]

Welcome to the forums! The only thing I can think of to do is reinstall the game. You might try grabbing a new download from the client area, just in case something went wrong with the original download.

[Krougal]

I'd try reinstalling .NET7

 

[Matt Covino]

30 minutes ago, Krougal said:

I'd try reinstalling .NET7

 

I just did an install of .Net 9.0.304 (most recent version) and the game crashed again not 10 minutes in. :(

[Matt Covino]

44 minutes ago, LadyWYT said:

Welcome to the forums! The only thing I can think of to do is reinstall the game. You might try grabbing a new download from the client area, just in case something went wrong with the original download.

Thanks for the welcome, and the reply!

I'm brand new to the game, so I only installed it yesterday. I'll try a fresh install tomorrow, I guess. 

[Krougal]

6 minutes ago, Matt Covino said:

I just did an install of .Net 9.0.304 (most recent version) and the game crashed again not 10 minutes in.

VS 1.2.x uses .net7

VS 1.21.x uses .net8

You need to have whatever applicable version (look at your crash log towards the bottom)

The major version releases generally aren't backwards compatible. So just having the latest and greatest doesn't help you.

Edited August 19, 2025 by Krougal

[LadyWYT]

15 minutes ago, Krougal said:

VS 1.2.x uses .net7

VS 1.21.x uses .net8

You need to have whatever applicable version (look at your crash log towards the bottom)

The major version releases generally aren't backwards compatible. So just having the latest and greatest doesn't help you.

I can verify though that 1.20 will run on .net8...or at least, I've had no issues running it after installing .net8. I've been bouncing back and forth between 1.20 and 1.21 without problems.

[Krougal]

Just now, LadyWYT said:

I can verify though that 1.20 will run on .net8...or at least, I've had no issues running it after installing .net8. I've been bouncing back and forth between 1.20 and 1.21 without problems.

Check your add/remove programs. Depending how long you've had your computer, you will probably see quite a few versions.

I currently have 10.

[LadyWYT]

1 minute ago, Krougal said:

Check your add/remove programs. Depending how long you've had your computer, you will probably see quite a few versions.

I currently have 10.

Or I mean...it could be that too. 

[Matt Covino]

So I have now uninstalled every instance of .Net from my system, uninstalled VS, rebooted, reinstalled the latest VS, and reinstalled .Net v8 (as per installer notes).

The game will now run for between 30 and 60 minutes before throwing a BSOD.

I'm running an overnight memory check now just to rule that out, but no other game is having these issues. Really frustrating, as I like what I've seen in VS so far, but this frequent crashing is going to make me abandon it.

[LadyWYT]

9 hours ago, Matt Covino said:

reinstalled the latest VS, and reinstalled .Net v8 (as per installer notes).

Sounds like you've got the release candidate installed, which is unstable. I would go report the issue on the github bug tracker, and then download the latest stable client(1.20.12) and try that instead. You will need net .7 for 1.20.12 stable.

[Matt Covino]

10 minutes ago, LadyWYT said:

Sounds like you've got the release candidate installed, which is unstable. I would go report the issue on the github bug tracker, and then download the latest stable client(1.20.12) and try that instead. You will need net .7 for 1.20.12 stable.

So I originally was using the 1.20.12 release. After all the issues, I reinstalled using the 1.21 release candidate instead.

 

I got a solid hour in this morning before the game froze (no blue screen, but hard locked my system so that I had to manually power cycle).

Running on 64 bit Windows 10.0.19045.0 with 32682 MB RAM

Event Log entries for Vintagestory.exe, the latest 1
==================================
{ TimeGenerated = 8/23/2025 9:28:34 AM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.21.0.0, time stamp: 0x68760000
Faulting module name: coreclr.dll, version: 8.0.1925.36514, time stamp: 0x68769299
Exception code: 0xc0000005
Fault offset: 0x00000000000ed967
Faulting process id: 0x3f94
Faulting application start time: 0x01dc14317627657d
Faulting application path: C:\Users\mattj\AppData\Roaming\Vintagestory\Vintagestory.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.19\coreclr.dll
Report Id: 30bb1205-73a8-4d0b-91e4-3c5c62a010db
Faulting package full name: 
Faulting package-relative application ID:  }

I've checked my Services app and I only see the one Gaming Input service, so this isn't a multiple-installs-of-DotNet issue.

[LadyWYT]

12 minutes ago, Matt Covino said:

So I originally was using the 1.20.12 release. After all the issues, I reinstalled using the 1.21 release candidate instead.

Gotcha. I would 100% submit a bug report then, as it could be an issue related to the unstable release.

 

12 minutes ago, Matt Covino said:

I got a solid hour in this morning before the game froze (no blue screen, but hard locked my system so that I had to manually power cycle).

What were you doing in the game before it froze? I know that I encountered a pretty bad memory leak on a previous unstable candidate and nearly had a BSOD(managed to close everything and shut down normally, at least), but that bug has since been fixed.

[Matt Covino]

Every time it happens (freeze or BSOD), I am interacting with a block in some way. Either chopping a tree, or cutting grass, or (the most recent) panning some sand. Never happens when I'm just walking around, standing still, reading the help text, etc.

[Thorfinn]

coreclr is commonly invoked for garbage collection. The intent is to make things easier to support across multiple platforms. Some types of memory leaks can cause a fault. I was unaware of it being a BSOD situation, usually it's "just" a CTD.

Yes, definitely file a bug report. If it is "just" a memory leak, they can put someone on monitoring it. You should include all relevant details about your machine and setup, since this doesn't seem to be happening to others.

[LadyWYT]

I will note there are still a couple of memory leaks lurking in the rc, but from what I've seen of them, they're relatively minor compared to the one before. That being said, I've been watching the github, and a few others have been reporting various crashes, so it's worth reporting in case this is a related issue.

[Teh Pizza Lady]

Well this is confusing to me because Vintage Story doesn't use .NET Core to the best of my knowledge... maybe the .dll files are shared somewhat 

screenshot taken from https://devblogs.microsoft.com/dotnet/coreclr-is-now-open-source/

Anyway Thorfinn

1 hour ago, Thorfinn said:

coreclr is commonly invoked for garbage collection. The intent is to make things easier to support across multiple platforms. Some types of memory leaks can cause a fault. I was unaware of it being a BSOD situation, usually it's "just" a CTD.

is correct. 

@Kassc I would definitely double check to make sure you have .NET 7 installed for Vintage Story version prior to 1.21, just to be doubly sure you are not running into a back porting issue between later versions of .NET. They are not always backwards compatible.... Thanks, Micro$oft

[Teh Pizza Lady]

Nevermind, I answered my own question.

.NET Core and .NET Framework were kind of merged. NET Core was renamed .NET 5.

We are now on .NET 8 which is .NET Core 8 just without the "Core" branding. my mistake there.

[LadyWYT]

11 minutes ago, traugdor said:

I would definitely double check to make sure you have .NET 7 installed for Vintage Story version prior to 1.21, just to be doubly sure you are not running into a back porting issue between later versions of .NET. They are not always backwards compatible.... Thanks, Micro$oft

Incidentally, Vintage Story should prompt you to install the correct .NET version for the game version you're trying to install, if you don't already have it. I was prompted to download and install .NET 8 when installing the 1.21 release candidate. 

[Teh Pizza Lady]

2 minutes ago, LadyWYT said:

Incidentally, Vintage Story should prompt you to install the correct .NET version for the game version you're trying to install, if you don't already have it. I was prompted to download and install .NET 8 when installing the 1.21 release candidate. 

I actually did not know that. However I did some research on OP's error and it looks like their specific error is a crash inside the .NET 7 CoreCLR runtime, not within Vintage Story itself. I wonder if this is the cause of the memory leaks we are seeing in 1.21 release candidates...

@Kassc I would run two commands when you have a bunch of free time:

1. sfc /scannow
2. mdsched.exe

sfc will rule out Windows file corruption

mdsched.exe is a memory test just to ensure no RAM errors

 

If you keep getting this error, see if it's always crashing at the same place (0x1c98a6). If it is, then you may try using different versions of .NET 7 to see if it fixes the issue. For example, I am on .NET 7.0.20, but you are on 7.0.10... might be worth an upgrade to see if there was a bugfix between those versions. You can also run dotnet --list-runtimes in a command prompt to see if you can get a full list like mine:

 

 

DISCLAIMER: I am not affiliated with Anego Studios in any way. If these bugs persist in the newest version of Vintage Story, then you may consider submitting a bug report on the Official Vintage Story Bug Tracker on Github.

[LadyWYT]

10 minutes ago, traugdor said:

However I did some research on OP's error and it looks like their specific error is a crash inside the .NET 7 CoreCLR runtime, not within Vintage Story itself. I wonder if this is the cause of the memory leaks we are seeing in 1.21 release candidates...

1.21 runs on .NET 8, not .NET 7, so I'm guessing it's not the cause of the leaks. 

[Teh Pizza Lady]

5 minutes ago, LadyWYT said:

1.21 runs on .NET 8, not .NET 7, so I'm guessing it's not the cause of the leaks. 

OP's error was on 1.20.11, so .NET 7 is still relevant.

My comment did not mention the supposition that the memory issues from 7 would be present in 8 if not fixed properly.

Edited August 23, 2025 by traugdor

[LadyWYT]

Just now, traugdor said:

OP's error was on 1.20.11, so .NET 7 is still relevant.

Right, but the latest poster having issues was running 1.21, which is what I was referring to. 

[Teh Pizza Lady]

Just now, LadyWYT said:

Right, but the latest poster having issues was running 1.21, which is what I was referring to. 

Ahh one of the many pitfalls of hijacking a thread instead of making your own... I did not see those messages because I was attempting to reply to the OP. The other posts have muddied the watering hole! Hold it right there, cowboy!