Fourtunehunter Posted August 24, 2025 Report Posted August 24, 2025 Like the title says, I've been trying to play Vintage Story lately but keep crashing. Usually it's about 10 minute delay, but this last attempt I started the game, took a few steps and crashed so I've no idea what to do. Here's my crashlog: Quote { TimeGenerated = 8/24/2025 6:54:09 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.2024.26716, time stamp: 0x6647966b Exception code: 0xc0000005 Fault offset: 0x00000000001b5988 Faulting process id: 0x3048 Faulting application start time: 0x1dc1549d7cb86d2 Faulting application path: C:\Users\USERNAME\AppData\Roaming\Vintagestory\Vintagestory.exe Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.20\coreclr.dll Report Id: bf61b0d0-36d2-43f8-8c47-b45880c1a05a Faulting package full name: Faulting package-relative application ID: } I think it has to do with .net7, but I went and installed ASP.NET Core Runtime 7.0.20, .NET Desktop Runtime 7.0.20 and .NET Runtime 7.0.20 since I wasn't sure which it was supposed to be, which may have caused the latest crash but this has been the same issue the last like 5 crashes today so I'm at my wit's end. If you need something else or something from another log lemme know, I don't really know which logs are important or not
Brady_The Posted August 25, 2025 Report Posted August 25, 2025 5 hours ago, Fourtunehunter said: I'm at my wit's end Unfortunately that crash report is rather vague. One can find a few of those on the Github bug tracker. What game version are you running? Are you playing with or without mods? Are you playing Single Player or Multi Player? Does "client-crash.log" has any more details?
Thorfinn Posted August 25, 2025 Report Posted August 25, 2025 Welcome to the forums, @Fourtunehunter. That's often a result of garbage collection, but someone recently found it also comes with some new video driver updates. Probably because .NET 7 is beyond end of life, and manufacturers don't care if they support the older software. They don't even seem to care about supporting graphics anymore. They seem to be focused on those who are repurposing GPUs for things like mining Bitcoin, or now, AI.
SodaRKov Posted August 25, 2025 Report Posted August 25, 2025 you could also try installing the .NET 8 runtime, all links are in the client area on top, and then attempt to launch the game again let us know if this solved your problem ;3
Fourtunehunter Posted August 30, 2025 Author Report Posted August 30, 2025 Hey all, thanks for the help! I think it was my graphics driver that was the issue, but with the update everything's changed anyway, and I've not seen much in the way of crashes yet, so I think I solved it? Either way, appreciate it!
PeachPainter Posted October 3, 2025 Report Posted October 3, 2025 Im having this same issue and can not seem to resolve it.
Dilan Rona Posted October 4, 2025 Report Posted October 4, 2025 The devs said you have to install DotNet 8 to play 1.21.x. I couldnt play it myself till I updated my DotNet as well.
Broccoli Clock Posted October 4, 2025 Report Posted October 4, 2025 (edited) Apropos to nothing, but since 1.21.1 release I've been experiencing quite a lot of crashes. I should say that before now, I've had maybe the odd one, but recently it's been at least one a session, sometimes two or three. The game in general is very stable for me, so well done devs. I decided to let it slide, thinking if there is an issue, I won't be the only person to suffer it so it should get patched. It was only after my 6th crash over two days (unheard of in the 100s of hours I've got in the game, up till then) that I decided to investigate. First thing was to remove the mods, I don't have a lot, mostly just chisel and better ruins, some extra icons and my own for making sticks. Problem remained, so the next step was to reinstall the game. I'd only updated it, so no harm doing a clean one. Got the client exe, uninstalled, reinstalled, and tried it (without mods enabled) and it crashed. Now, getting a little more concerned I decided to check what was the main trigger. That seemed to be opening chests/storage. Not always but about 80% of the time. I decided to go looking at the files, and in my (I'm on windows) AppData/Roaming/VintageStory folder, there was a ModConfig one. Inside that were several .json files, one of them called sortablestorage.json - I don't have sortable storage in my mod list, and the file dated back to Feb of this year, pretty much when I first installed the game. I don't even remember installing a mod for sortablestorage, especially that early on in my experience as for my first ~100 hours I used no mods, but I'll not lie and say it's something I'd like to see in vanilla. Either way, removing the sortablestorage.json file fixed my crashes. I could re-enable my mods and it was completely fine. So it seems that a file dated from February, had sat in my AppData for months, that I had no recollection putting there, acting benignly all through 1.20 and its revisions, and even into 1.21.0, not causing any (observable) issue. Then 1.21.1 drops and the game crashed repeatedly. Weird. Although I'm happy it's fixed, and I'm not suggesting anyone else is in a similar situation, but just goes to show you how these sorts of crashes manifest. Edit: I literally just suffered another crash, same style as before, although this was just after I used a "storage item" (it was the fire, which had a crucible on it). For me the game just freezes, there is no crash output, not popup, just windows saying it the program had stopped responding. Not sure exactly why this is happening, I thought I'd fixed it, but for some reason it remains. I should say, VS is pretty good in terms of saving your progress, so a crash is not a run ending event, and I have noticed it crashing less since I removed that superfluous .json file. Could it be something in my install? Perhaps, I'll just wait and see if any 1.21.x updates resolve it. Edited October 4, 2025 by Broccoli Clock
Recommended Posts