Windows Game keeps shutting down

S

s_spowart

Refugee
In the past month or so I have not been able to complete any mission due to the game shutting down on me repeatedly.

I play with 3 friends, and they remain connected, but my game started crashing randomly. It used r=to work fine but suddenly stopped.
I even tried re-installing my windows 11 operating system from scratch and even that didnt work.
All my drivers have been updated to the latest versions.
I attached my DXDiag report to this thread.
Any idea whats going on?
I dont have this problem with other games. Adobe Photoshop did it occasionally but since windows was re-installed photoshop hasnt shut down, it is just 7 days.

I am playing cross platform, my system is on PC, 1 of the friends is on playstation the other 2 are on PC with Windows. I dont play solo, so no idea if it crashes then or not. It usually decides to shut down in the middle of a mission but that could be a co-incidence. It tends to happen randomly.

Thanks
 

Attachments

s_spowart said:
In the past month or so I have not been able to complete any mission due to the game shutting down on me repeatedly.

I play with 3 friends, and they remain connected, but my game started crashing randomly. It used r=to work fine but suddenly stopped.
I even tried re-installing my windows 11 operating system from scratch and even that didnt work.
All my drivers have been updated to the latest versions.
I attached my DXDiag report to this thread.
Any idea whats going on?
I dont have this problem with other games. Adobe Photoshop did it occasionally but since windows was re-installed photoshop hasnt shut down, it is just 7 days.

I am playing cross platform, my system is on PC, 1 of the friends is on playstation the other 2 are on PC with Windows. I dont play solo, so no idea if it crashes then or not. It usually decides to shut down in the middle of a mission but that could be a co-incidence. It tends to happen randomly.

Thanks
Click to expand...
We would need to see your game log where it crashes to have much chance of helping you. DxDiag is helpful, but the log is really important for finding out what is happening.
 
Instructions for reporting bugs are here (including where the Logs Files are):

Umbionis

Thread 'HOW TO REPORT AN ISSUE ~~ Please Read Before Creating New Threads! ~~'

NOTE: This thread is resurrected from a very old version. I need to update it and make some changes, but it should be mostly correct.

Howdy folks,
If you're reading this, you're probably thinking about starting a thread for help with an issue. This post is intended for you to understand what we need in order to assist you properly, and how you can give it to us.
Threads created without the information outlined in this post are not likely to get you a good resolution. (Most likely you will simply be re-directed to this thread to get instruction on posting the information...
  • Like
 
I'm no expert at most errors in the game, but the error leading to your trouble in the most recent log seems to indicate a problem with chunks and/or meshes. You may want to try to disable dynamic meshes and see if it helps at all (it's in your options). That's just a guess, though. The other possibility is a map problem that is affecting you but not the others. Have you tried playing a game solo (not on a server) to see if you have problems?
 
Riamus said:
I'm no expert at most errors in the game, but the error leading to your trouble in the most recent log seems to indicate a problem with chunks and/or meshes. You may want to try to disable dynamic meshes and see if it helps at all (it's in your options). That's just a guess, though. The other possibility is a map problem that is affecting you but not the others. Have you tried playing a game solo (not on a server) to see if you have problems?
Click to expand...
I havent tried it solo, I only play with the same friends. Friends I have known since my school days, but the map was re-downloaded when I re-installed windows. I will look for the dynamic mesh option when I play this afternoon. Thanks.
 
I expected to see a normal 7D2D stack trace, but in the 2026-02-21_17-31-49 file I saw something different. I was out of my depth on that one, so I shared it with Claude...


Here's a thorough breakdown of what you're looking at:

Yes, it's Windows — confirmed by the C:\ paths, .dll files, and Windows-specific APIs throughout. The OS version reports as 10.0.0, which is how Windows 11 identifies itself when the version string isn't fully populated. The NT kernel DLL versions (e.g., ntdll.dll at 10.0.26100.7824) place this firmly in the Windows 11 24H2 era.

The stack trace format is generated by Unity's built-in crash handler on Windows, which uses the Windows dbghelp.dll API (specifically StackWalk64 and SymGetSymFromAddr64). It's not a standard Visual Studio or WinDbg crash dump — it's Unity's own crash reporting wrapper. This is why it looks unfamiliar. The two-pass structure (first listing all loaded DLLs, then attempting the stack walk) is characteristic of this system.

What the crash trace tells us:

The critical line is:

<span><span>RtlLookupFunctionEntry returned NULL function. Aborting stack walk.</span></span>

This means the crash handler tried to walk the call stack but immediately gave up. RtlLookupFunctionEntry is a Windows API that looks up stack unwinding information for a given code address. When it returns NULL, it typically means the crash occurred in a region of memory that has no registered exception handling data — often dynamically generated or JIT-compiled code. In 7D2D's case, this points squarely at the Mono runtime (the managed C# scripting layer), since Mono's JIT-compiled code doesn't always register proper Windows unwind tables.

The faulting address 0x00000247A55F9880 couldn't be resolved to any known module, which reinforces this — it's likely in a Mono JIT-compiled heap region.

Other notable observations:
  • The crash happened about 29 minutes into the session (session started ~17:32, crash at ~18:01).
  • The last game log entries before the crash were about unloading audio clip sets (Combat animation clip sets), suggesting the crash may be related to a scene/world transition or audio system interaction.
  • Bitdefender is present (antimalware_provider64.dll), which is worth noting — antivirus software hooking into game processes can occasionally cause crashes in Unity games, especially during dynamic code generation by Mono.
  • The NVIDIA driver version is 32.0.15.9186 (very recent), and DLSS (nvngx_dlss.dll v3.1.11) is active. GPU driver issues can also cause crashes that look like this.
Bottom line for the person you're helping: The crash handler couldn't produce a meaningful stack trace because the crash occurred in JIT-compiled Mono code. The actual detailed crash dump would be in C:\Users\messe\AppData\Local\Temp\The Fun Pimps\7 Days To Die\Crashes — that folder would have a minidump file that could be analyzed with WinDbg or uploaded to the 7D2D bug tracker for the developers to inspect. Without that dump, the best practical advice is to check for mod conflicts, try disabling DLSS, temporarily disabling Bitdefender for testing, and verifying game file integrity through Steam.

I don't have issues with Bitdefender, but I suppose there could be different settings and its easy enough to try. I think DLSS is a graphics setting?

Sorry, I'm not going to be much help on this one.
 
Riamus said:
I'm no expert at most errors in the game, but the error leading to your trouble in the most recent log seems to indicate a problem with chunks and/or meshes. You may want to try to disable dynamic meshes and see if it helps at all (it's in your options). That's just a guess, though. The other possibility is a map problem that is affecting you but not the others. Have you tried playing a game solo (not on a server) to see if you have problems?
Click to expand...
I checked and dynamic meshes was already turned off, but I think I managed to fix the problem another way. I updated the firmware on my motherboard, and managed to play for several hours today without any problems. Sounds like there was an issue with intel CPU's gen 13 and 14. Mine is a gen 13 intel. I only do firmware updates if I really need to, too worried about any problems during the update and the system would be knackered, but I downloaded the latest Bios update and played 7 Days and havent had any problem with it crashing today, so fingers crossed it is now fixed.
 
s_spowart said:
I checked and dynamic meshes was already turned off, but I think I managed to fix the problem another way. I updated the firmware on my motherboard, and managed to play for several hours today without any problems. Sounds like there was an issue with intel CPU's gen 13 and 14. Mine is a gen 13 intel. I only do firmware updates if I really need to, too worried about any problems during the update and the system would be knackered, but I downloaded the latest Bios update and played 7 Days and havent had any problem with it crashing today, so fingers crossed it is now fixed.
Click to expand...
Yeah, that was something that was going on a year or so ago. It's important when they have that kind of recall and update to do those updates. Not doing so could have caused irreparable damage to your CPU. It sounds like it's at least working for you now.
 
You must log in or register to reply here.
Back
Top