Windows Random crash only with other players

My error is not multithreading. It's 7 Days eating all of my RAM (64GB), then starting to use pagefile (swap), bringing the game and my system to its knees and dying. I was initially told that this was video RAM (VRAM), so I logged my VRAM usage using nVidia's own tool and when the game crashed I wasn't even using 2/3 of the VRAM.
 
Re-install your legal copy of Windows 10 Enterprise, or even better, install Windows 11.
My guess is that your PC is messed up and Installing Windows again will clear everything up.
 
Hello,

Can you try without mods and see what the result is, please? We need to be able to look at this in vanilla and without being able to compare vanilla to vanilla stats, we will have some difficulties.

Thanks,
Dollie
 
I did that already, but never posted the logs. I can do it again. The mods I run shouldn't affect anything though. I wrote them. One allows you to set time up to 360 minutes per in-game day, one tones down the heat of dew collectors (we have not used any dew collectors in our saves), and one adds two guns we were not using (not even spawned into the world). I'll remove them and go back to 2.6 tomorrow and get you some logs.
Post automatically merged:

Re-install your legal copy of Windows 10 Enterprise, or even better, install Windows 11.
My guess is that your PC is messed up and Installing Windows again will clear everything up.
Right. So Windows is hosed, but the only thing affected is 7 Days. Playing Panzer Elite for hours doesn't trigger the mess-up, right? I work in IT. I'm the assistant systems admin to a multi-million dollar business. Windows is fine. Checking event logs show nothing except when 7 Days crashes. Every other game on the planet runs fine. It isn't the PC.
 
I did that already, but never posted the logs. I can do it again. The mods I run shouldn't affect anything though. I wrote them. One allows you to set time up to 360 minutes per in-game day, one tones down the heat of dew collectors (we have not used any dew collectors in our saves), and one adds two guns we were not using (not even spawned into the world). I'll remove them and go back to 2.6 tomorrow and get you some logs.
Post automatically merged:


Right. So Windows is hosed, but the only thing affected is 7 Days. Playing Panzer Elite for hours doesn't trigger the mess-up, right? I work in IT. I'm the assistant systems admin to a multi-million dollar business. Windows is fine. Checking event logs show nothing except when 7 Days crashes. Every other game on the planet runs fine. It isn't the PC.
I didn't realize you only had this problem with 7 Days to Die.

I would also suggest you remove all mods (if any are installed) before you test again.
If you remove 7DTD, make sure to actually delete the folder also prior to the re-install, just to make sure there isn't something left (like a mod), because some games leaves the folder on the PC, even when you delete the game from Steam.

Good luck!
 
Done that twice now, mentioned previously. No mods, clean install, and verified files.

Now, an update. Last night I uninstalled 7 Days. Steam actually deleted the 7 Days folder from my drive. I then went into my AppData/Roaming folder and removed everything except my own prefabs and config files. This includes the cache folders and all. Then I reinstalled the game using the default branch.

I started the game and everything was right. Keybinds, player profile, audio levels, etc etc. No mods, mind you. Deleted the corrupted save and started fresh... AGAIN. Played for two-and-a-half hours. No crash. This was with the friend who is always on when it crashes. The thing is, I did a lot of things. Deleted the cache folders. Removed mods. Reinstalled fresh despite passing file verification.

With that said, We're playing again in a bit. If we get away with no crashes I'm posting the code to my modlets. I am 99.99% sure they are not the problem. The additional time modlet only adds three or four more options for number of real minutes per in-game day. Two lines of code. We'll see though. I will report back tonight.
 
Thank you.

In order for us to compare apples to apples, we need a clean baseline to compare to in-house, so a log from a mod/modlet free game is vital for that.

Cheers,
Dollie
 
We have multiple hours in with no crashes. That said, it isn't gobbling RAM now, so I want to share the source code to the two "massive" mods we had running. I would like to know how they can eat 64GiB of RAM so I can fix them. I am the author.

Additional time options. Modifies XUI_Menu/Windows.xml and nothing else.
Code:
<configs>
    <set xpath="/windows/window[@name='newContinueGame']/rect[@name='rightPanel']/rect[@name='tabs']/rect[@name='tabsContents']/rect[@tab_key='xuiGameSettingsGeneral']/grid/gameoption[@name='DayNightLength']/@values">10, 20, 30, 40, 50, 60, 90, 120, 180, 240, 300, 360</set>
    <set xpath="/windows/window[@name='serverBrowser']/panel[@name='serverfilters']/panel[@controller='TabSelector']/rect[@name='tabsContents']/rect[@tab_key='xuiGameSettingsGeneral']/grid/browsergameoptioncombined[@name='DayNightLength']/@values">10, 20, 30, 40, 50, 60, 90, 120, 180, 240, 300, 360</set>
</configs>
This mod simply adds a few more day length options. Should not consume gigs and gigs of RAM. Yes, this is my entire mod. Next up is my mod for adjusting dew collectors.
Code:
<configs>
    <set xpath="/blocks/block[@name='cntDewCollector']/property[@name='MinConvertTime']/@value">14400</set>
    <set xpath="/blocks/block[@name='cntDewCollector']/property[@name='MaxConvertTime']/@value">21600</set>
    <set xpath="/blocks/block[@name='cntDewCollector']/property[@name='HeatMapStrength']/@value">.5</set>
    <set xpath="/blocks/block[@name='cntDewCollector']/property[@name='HeatMapTime']/@value">2000</set>
    <set xpath="/blocks/block[@name='cntDewCollector']/property[@name='HeatMapFrequency']/@value">1000</set>
</configs>
That one modifies four lines in blocks.xml and nothing else, as you can see. Bear in mind, in the last four saves that got corrupted, we didn't have a single dew collector on the map. We had a water source and boiled our water.

I had no other mods, additional 3D models, sounds, or anything when it was crashing. Maybe I wrote something wrong in one of the above mods, but the mods throw no warnings or errors when loaded, as you yourself saw in my logs. Any ideas? I am about to enable the first mod and play tonight. If it crashes, I would blame whatever part of the engine loads and parses mods, because it's literally two lines that only affect the main menu, nothing once you're playing a game. Time will tell.
 
Okay, here's a daily update. Last night we played for over an hour with no abnormalities, so we installed the first mod (adds more selectable times on new games and for searching for servers) and played for over three hours. No abnormal RAM usage, no crashes, nothing. In other words, it has been running absolutely solid without any mods and it ran solid for over three hours with one of the mods we had before.

My gut is telling me that, despite verifying files multiple times and passing, something between upgrading from 2.5 to 2.6 was not happy. The mods have not changed. My video and audio settings have not changed. It just started crashing after the 2.5->2.6 update. If the game runs another three hours without a crash using the first mod, I will add the second mod back and try for another six hours. If that works I'm getting my 250rd 5.56 mag and emptying it into the PC.
 
Hold the mag! If it makes it through both tests, we can call it rehab, not retirement.

Will wait for your next update.

Best,
Dollie
 
It appears as though it may have been something between my upgrade paths. I stopped playing at 1.0 and was playing other games. I then upgraded to 2.5, played with friends for a day or two, then had to upgrade to 2.6. This is when our crashes started and I naturally blamed the upgrade because nothing else had changed with 7 Days (no settings, no mods added or removed, etc etc) and all my other games ran fine, indicating my hardware was solid.

Now, when you asked for clean, I went dang-near full-clean. I uninstalled the game, ensured that the game directory (folder, if you're young) was gone (E:\Games\Steam\steamapps\common\7 Days to Die)) and it was. I then went to my AppData/Roaming/7DaystoDie and I removed everything EXCEPT LocalPrefabs (I have fabs I made WAY back in the day I do not want to lose), launchersettings.json, and UserOptions.ini. Everything else was gone. This includes the datastorage, RfsCache, and RfsPlayerCache directories. Then I reinstalled the game and it ran for hours with no mods flawlessly, around six hours with the time mod I showed previously (two lines of code), and now 86min with both the time mod and the dew collector mod installed. No crashes, stutters, nothing.

I am going to give it until we have at least three hours of multiplayer time with the two mods installed, but my gut is telling me that something in datastorage or one of the cache folders was not happy. I get warnings like the following occasionally, but that's a dev problem and does not appear to affect us in any way.
Code:
Couldn't create a Convex Mesh from source mesh "hull_forklift_tire" within the maximum polygons limit (256). The partial hull will be used. Consider simplifying your mesh.
Couldn't create a Convex Mesh from source mesh "Head" within the maximum polygons limit (256). The partial hull will be used. Consider simplifying your mesh.
No, I am not running any mods that mess with meshes. Just the two as stated above. If we can play tonight I may have a final report tomorrow.
 
Hey there!

Thank you for the additional update. I am really glad to hear that things are going well.

I have seen the Convex Mesh message before, so I don't think this is anything on your part. I can make some inquiries into that one. It may have something to do with the way multiblocks work.

Thanks again,
Dollie
 
To be clear, I do not believe those mesh messages have anything to do with the crash. The game was gobbling RAM. We have almost six hours with three of us playing and both mods installed without a crash though. I believe something in one of those cache directories was the issue. I mean I went from 1.0 to 2.5 and then almost instantly to 2.6. Maybe an old cache format or something was in there. If tonight goes well I am going to resume working on my guns mod again.
 
Those Convex Mesh warnings are harmless. Just means an object has a mesh collider set in Unity that has too high of a poly count.
 
Back
Top