Crashing

F

FA_Q2

Refugee
Game crashed after 10 in game minutes pass on day 35 horde night.  I have had no other issues whatsoever and everything runs perfectly smooth until it freezes and crashes.  I seem to be able to get the game to continue running with low settings but have no performance issues and have had no other crashing problems at any other time.  I am running a 3060ti and 15 11600 with the recommended 16 gig RAM so I should have enough power to run the game at any settings and all my other gameplay has been perfectly smooth.  I REALLY do not want to knock back my settings, the game looks so much better with the proper settings.  I am really wondering what specifically is creating the problem and what I might be able to do about it.

My last 3 crash logs: 

https://pastebin.com/7F2qiVfS

https://pastebin.com/540edu9N

https://pastebin.com/D4yCx8Bw

 
Did you overclock anything? If so, put everything back to product advertised speeds (default) and see what happens.

What PSU make / model / max watts output are you using?

Are your drivers / bios / firmware up to date? (motherboard and GPU are most important)

 
I agree with Fox…..there are no errors in any of your logs so it points to an issue with your rig itself. Stress testing your cpu and power supply, running ram diagnostics are recommended. Also making sure that you have Windows managing your swap file. As Fox mentioned, any overclocking should be reset. Check the Event Viewer to see if anything regarding the game crash is mentioned.

 
Nothing is overclocked and the drivers are up to date.  None were changed/updated either.  After horde night, put everything back on ultra and working fine.  It is just horde night.  

My PSU is a Corsair RM750.  I doubt it is a power issue, I have several titles that push this rig harder than 7 days and have had no problems with crashing or anything like that.  

The event viewer does have the crash there but does not tell me much: 

The program 7DaysToDie.exe version 2020.3.14.53691 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 5e4c
 Start Time: 01d84f1bf7e2791e
 Termination Time: 12
 Application Path: C:\Games\Steam\steamapps\common\7 Days To Die\7DaysToDie.exe
 Report Id: 607bcbd5-0ad7-4d11-abb1-d8e5db087719
 Faulting package full name: 
 Faulting package-relative application ID: 
 Hang type: Unknown
 

I have no idea why it states to see if there is more information in the Security and Maintenance control panel, there it says the exact same thing.  This does not tell me anything that I am aware of.  Does it mean anything more to you guys?

 
Last edited by a moderator:
FA_Q2 said:
Nothing is overclocked and the drivers are up to date.  None were changed/updated either.  After horde night, put everything back on ultra and working fine.  It is just horde night.  

My PSU is a Corsair RM750.  I doubt it is a power issue, I have several titles that push this rig harder than 7 days and have had no problems with crashing or anything like that.  

The event viewer does have the crash there but does not tell me much: 

The program 7DaysToDie.exe version 2020.3.14.53691 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 5e4c
 Start Time: 01d84f1bf7e2791e
 Termination Time: 12
 Application Path: C:\Games\Steam\steamapps\common\7 Days To Die\7DaysToDie.exe
 Report Id: 607bcbd5-0ad7-4d11-abb1-d8e5db087719
 Faulting package full name: 
 Faulting package-relative application ID: 
 Hang type: Unknown
 

I have no idea why it states to see if there is more information in the Security and Maintenance control panel, there it says the exact same thing.  This does not tell me anything that I am aware of.  Does it mean anything more to you guys?
Click to expand...
It doesn’t narrow down the problem source but it does confirm that the game is not the source. Personally, I’d start with checking the ram as it’s the easiest to rule in/out. Either run the Windows Memory Diagnostic tool which is already installed on your pc or run Memtest if you have it. I haven’t heard anything bad about Widows Memory tool, I just have more history with Memtest. If your ram checks out, next thing to do is stress your cpu by running Prime 95. There are other programs that other people have recommended in other cases but I’m not remembering at the moment. I believe there is even one that will stress test your power supply.

All this being said, horde night is a major strain on mainly your cpu but also ram and gpu but especially the cpu. Checking to be sure your chipset drivers and motherboard bios are up to date. Run some of these tests and let us know the results.

EDIT: OCCT is the software that stresses the psu.

 
Last edited by a moderator:
As Star69 mentioned... try testing your ram to see if any errors pop up, as the contacts do occasionally lose contact over time due to dirt or sections can just start failing randomly. MemTest86 is free and my preferred tester, though I'm sure others use other apps.

You can also check your game's installation file integrity within steam to see if there's anything unusual going on (especially if you have an outdated mod installed you forgot about)

 
Well, did more testing as you suggested and then did some in game testing and I do not think it is my system.  I think it might be the save.  I started a new save, set the day to 49, my level to 100 and set up a similar defensive base.  Changed game speed to 3 and then ran horde night on ultra rather than high and no issues at all.  Thought it may have been because the map was unexplored so went around making random holes with the digger and a rocket launcher in POIs and all over the ground.  Still no problems.  The base itself was smaller and I think I was on a smaller map but my base is by no means anywhere near what a mid sized POI is.  What about stations?  Are they a significant drain?  Would it matter if I ensured they were not running when Horde night arrived?  Pathing to me might have been a bit simpler too but not by much.  I might replicate the base entirely but I am not sure there would be a good reason for it.

Does the overall map size use more resources than a smaller one when in game?  Does the amount of the map explored matter?  I know there were problems like that in the past but that was back when the map was open ended rather than fixed iirc.  What about damage on the map?  Does the game require more active resources when buildings and other areas are damaged or are they fine when unloaded?

 
Last edited by a moderator:
Ok, how old was your save file? Was it before 20? Are you playing the latest experimental release?

I think different map sizes might use more ram, but otherwise is the same on hardware. Map explored I think increases save file size (I could be wrong on this one though).

 
Last edited by a moderator:
No, save is from not that long ago, less than a week I think.  Not experimental afaik: A20.3 (b3) 

 
Last edited by a moderator:
This definitely surprises me. I’m happy that starting a new game fixed your issue but I haven’t heard of a game-related crash where there is absolutely no hint of an issue in the log and the crash was recorded by the Event Viewer. Just goes to show you that there’s always a first time.

 
Beelzybub said:
This is just a guess but what about Electricity? Were you using it in your base?
Click to expand...
Yes, but that was true in both cases.

My first suspicion was that it was a result of the electrical fencing, those have always been very wonky.  I have not gotten the repair bug back yet so I hope that has disappeared but we will see in my new game.

Star69 said:
This definitely surprises me. I’m happy that starting a new game fixed your issue but I haven’t heard of a game-related crash where there is absolutely no hint of an issue in the log and the crash was recorded by the Event Viewer. Just goes to show you that there’s always a first time.
Click to expand...
Or I am missing something :D

Likely a one off.  The event viewer shows that it flat stopped responding so it does not overly surprise me that it was not in the event log.  I will find out soon enough, I rolled a new game anyway because I play did and, well, I did :(

 
I've always used and abused the limits of electric fencing (stretching the length limits using a few tricks) and have never gotten a crash with the only exception being Alpha 3 which is completely unrelated to this (vertices glitch / too many entities within a loaded chunk... built a massive skyscraper).

My base usually has 3 or 4 layers of fencing (24 - 32 poles) plus 2 going up the ramp.

 
Last edited by a moderator:
Never had them crash me either but have had a lot of bugs with them in the past; wires running off on random directions sometimes stretching a km away, stop receiving damage, transferring damage to another pole, having a single pole receive all the damage from fences in a the chunk even when disconnected and therefore being only the pole requiring repair to keep the entire system up.

They seem to have received a buff of some sort this alpha too, I have 3 fences in my tunnel and those three alone can basically kill everything.  I am essentially 100 percent safe as long as I start the night with a dozen bars and electrical parts.

 
You must log in or register to reply here.
Back
Top