7days crashing quite often. Please help.

[tenchikun]

Sometimes this crash occurs in 10 minutes, sometimes it takes a couple hours. Can't figure out what is causing it or how to fix it. The game will just freeze mid swing while mining, shooting, driving or even walking. 

 

System Info:

Ryzen 7

MSI gtx 1660 ti

32gigs of ram

win 10 newest version, up to date, all extras updates included.

Drivers all up to date

Direct X up to date

Logs: 

 

Faulting application name: 7daystodie.exe, version: 2019.2.17.24627, time stamp: 0x5df1e6e4
Faulting module name: UnityPlayer.dll, version: 2019.2.17.24627, time stamp: 0x5df1e859
Exception code: 0xc0000005
Fault offset: 0x0000000000d1a468
Faulting process id: 0x12a8
Faulting application start time: 0x01d730da00a38004
Faulting application path: D:\Program Files\Steam\steamapps\common\7 Days To Die\7daystodie.exe
Faulting module path: D:\Program Files\Steam\steamapps\common\7 Days To Die\UnityPlayer.dll
Report Id: 8717bf55-d92b-49cb-992d-c57c087f86e1
Faulting package full name: 
Faulting package-relative application ID: 

 

 

Faulting application name: 7daystodie.exe, version: 2019.2.17.24627, time stamp: 0x5df1e6e4
Faulting module name: UnityPlayer.dll, version: 2019.2.17.24627, time stamp: 0x5df1e859
Exception code: 0xc0000005
Fault offset: 0x0000000000d1a468
Faulting process id: 0x3230
Faulting application start time: 0x01d730d50e8354db
Faulting application path: D:\Program Files\Steam\steamapps\common\7 Days To Die\7daystodie.exe
Faulting module path: D:\Program Files\Steam\steamapps\common\7 Days To Die\UnityPlayer.dll
Report Id: 9613dc9b-b8ce-4096-a9f0-f26d2e03ed4e
Faulting package full name: 
Faulting package-relative application ID: 

 

Session "dfa2c640-651d-488d-a479-2fd7a7ca6e29" failed to start with the following error: 0xC0000022

 

 

Faulting application name: 7daystodie.exe, version: 2019.2.17.24627, time stamp: 0x5df1e6e4
Faulting module name: UnityPlayer.dll, version: 2019.2.17.24627, time stamp: 0x5df1e859
Exception code: 0xc0000005
Fault offset: 0x0000000000d1a468
Faulting process id: 0x5160
Faulting application start time: 0x01d730c837266a22
Faulting application path: D:\Program Files\Steam\steamapps\common\7 Days To Die\7daystodie.exe
Faulting module path: D:\Program Files\Steam\steamapps\common\7 Days To Die\UnityPlayer.dll
Report Id: ab799268-018c-4f94-b398-43c2ba54bd31
Faulting package full name: 
Faulting package-relative application ID: 

[SylenThunder]

This appears to be an access violation. Which can be caused by a number of things.

 

Ensure that the client is properly excluded from security software.

Ensure that you don't have any RAM issues by running memtest.

Ensure that your hard disk is error free.

Ensure that you do indeed have the latest drivers. (Windows updates will install outdated/broken drivers for LAN, Chipset, and GPU on a regular basis. Always ensure that you refresh all critical system drivers after a Windows update.) 

Ensure that the Pagefile is set to "System Managed". Doesn't matter how much RAM you have, manually locking this will cause issues. It also will not save your SSD. That is a myth.

[tenchikun]

Changed the setting for the Pagefile, We'll see how that goes. Everything else you mentioned has already been done with no errors. And I don't run security software. 

 

[BFT2020]

4 hours ago, tenchikun said:

And I don't run security software. 

 

Now that is scary

[tenchikun]

 

 

It's nothing to be scared about. You don't need security software if you know what you're doing and you're careful. Stay away from bull@%$# sites, scams, ect. I've got 25 years of experience on internet security. Thats not to say I don't have security software, I just don't run it all the time. Especially when i'm playing a game. And of course stay away from the porn sites! 

Edited April 14, 2021 by tenchikun (see edit history)

[Boidster]

1 hour ago, tenchikun said:

And of course stay away from the porn sites!

Now that is scary

[SylenThunder]

2 minutes ago, Boidster said:

Now that is scary

My current record for repair is a wee bit over 850,000 infections.  If they didn't absolutely have to have bank data that couldn't be pulled out by just copying the files, I wouldn't have even attempted it.  Took a couple of days, but I did manage to purge all the infections.  Main source of infection, husband visiting porn sites on a separate profile in the PC.  I left him a little note in his user profile.

[tenchikun]

Well I got to play most of the day but it crashed yet again. Almost thought that was fixed but apparently its still not. Not sure what to do next. 

[meganoth]

Please use steam to validate your game. Even if you have done it already, there were cases where two validations were necessary.

 

Secondly please post the full log (through pastebin or similar), this is explained in a pinned thread in this forum section.

 

Edited April 15, 2021 by meganoth (see edit history)

[tenchikun]

https://pastebin.com/ZEX8xXXf

Validated the game, all is good there. 

Hope this helps some. 

[meganoth]

I found this error message:

 

 

Quote

 

2021-04-14T12:55:07 1785.190 INF Disconnect

Coroutine couldn't be started because the the game object 'XUi' is inactive!

 

 

where you seem to have been thrown out of the game.

 

Then there were two server restarts

 

Then the crash. Was the first event just an unexpected exit and the two server restarts were expected? Why so many restarts in only 10 minutes?

 

The error seems to have happened in unity, so it could be a driver problem. It could also be network-related.

 

I would propose a few experiments:

 

Play on that server but turn down texture size to half. This is just to make sure that 6G is enough for full texture display. Does it crash?

 

Next: Play a local game and check memory and GPU mem usage from time to time. Does it happen there? Do you see memory increasing constantly? I know, you have @%$#loads of RAM, but just to be on  the safe side

 

If it does happen in a local single player game, post that logfile. Being on a server can muddy the waters if it hasn't anything to do with server/client stuff.

 

If it does not happen, ask the server owner if he uses any mods. Ask what he sees in his log when you crash.

 

[tenchikun]

here is another pastbin from a crash today. https://pastebin.com/up6e3hyC
There were a few server restarts that day so just in case that's from when that happened i'm providing another output log. 

Edited April 15, 2021 by tenchikun (see edit history)

[tenchikun]

here is one from horde night. I want to say I have 3 more of these within 5 minutes of each other. I kept crashing hard at that time. https://pastebin.com/zvizX2ed This is from last night.

Edited April 15, 2021 by tenchikun (see edit history)

[tenchikun]

Just logged in and was going to change the texture resolution and moved around a little and it crashed almost immediately. https://pastebin.com/JejH5EhP

 

[tenchikun]

This is from playing single player. Went a long time before it crashed, was starting to think it wasn't going to crash but here it is. https://pastebin.com/f6BV47Uu

 

[Boidster]

On 4/14/2021 at 11:09 AM, tenchikun said:

And I don't run security software. 

 

The security software you're running says otherwise! 🙂

 

C:\Program Files (x86)\Kaspersky Lab\Kaspersky Total Security 21.2\x64\antimalware_provider.dll:antimalware_provider.dll

[tenchikun]

WTF, it's not running though! I even eliminated it from startup and rebooted right after. 

 

So Kaspersky must be running background without showing in services. 

 

 

and that's the cause of the crash?

Well either way, exclusions have been made for all games. One can only hope that this was the issue. 

Edited April 15, 2021 by tenchikun (see edit history)

[Boidster]

Sorry, I was only poking a little fun. I don't know at all that that one DLL is the cause of your crashes, though my impression is that Kapersky is not highly regarded in general. Just for troubleshooting, it might be worth it to try uninstalling it temporarily. And look closely at your process list before firing up 7D2D in case something else has burrowed in.

Edited April 15, 2021 by Boidster (see edit history)

[SylenThunder]

23 minutes ago, Boidster said:

Sorry, I was only poking a little fun. I don't know at all that that one DLL is the cause of your crashes, though my impression is that Kapersky is not highly regarded in general. Just for troubleshooting, it might be worth it to try uninstalling it temporarily. And look closely at your process list before firing up 7D2D in case something else has burrowed in.

Well after you get in trouble for using your software to steal data from the NSA, it's hard to come back from it. (Which may not have actually happened the way they initially thought. That's a funny one.)

 

In any case, disabling security software fully is typically not possible without completely un-installing it from the system. This is by design due to too many of the viruses we used to write simply disabling the software so they didn't get detected.

 

Also in regards to the several server restarts. There was a known issue where logging out of a server, and logging into a server without exiting the client could cause a memory leak. It was advised to fully exit the client when switching servers, or re-logging in a disconnect situation.  I know work was being done to fix this issue, but cannot recall off the top of my head right now if it was actually resolved in one of the recent updates.

 

 

Something I do find interesting in your logs is the inconsistent amount of RAM allocated. One log is averaging 10GB, and another is only averaging 5-6GB.  The tail end of the logs lead me to believe that it is still an access violation issue though.

[tenchikun]

1 hour ago, SylenThunder said:

The tail end of the logs lead me to believe that it is still an access violation issue though.

And what would be the cause for this?

Seconds into loading into the game it just crashed! https://pastebin.com/aJK6gGtP

[SylenThunder]

1 minute ago, tenchikun said:

And what would be the cause for this?

Mostly the things I listed already. Security software, RAM issue, HDD issue, permissions issue. Stuff like that.  Could just be some other software getting in the way too. Like how Citrix Workstation will randomly kill the client because of how it handles GPU data. Or how nearly every experimental has an issue with the overlay from MSI Afterburner.

 

These things are harder to track down, but usually can be discovered eventually.

[meganoth]

8 hours ago, tenchikun said:

And what would be the cause for this?

Seconds into loading into the game it just crashed! https://pastebin.com/aJK6gGtP

A security software like Kaspersky has two parts, one part is running like any normal program on your PC, a second part is injected deep into the bowels of your operating system. If you prevent the normal program from running you have just disabled the user interface, the serious heavy lifting should still be working as (un)intended.

 

Without an official uninstall utility from Kaspersky you won't get rid of the software (and more paranoid people might even believe not even that will get rid of it 😁 )

 

Not saying that is the cause, but like SylenThunder said, anti-virus software HAS to be resilient against removing it.

[tenchikun]

Ok, fresh new install of windows, updated fully, all drivers downloaded and updated. All I got on here right now is steam, discord, battle.net, star trek online, outriders, and 7d2d.  jumped into game, started mining and crashed to desktop, no error, no popup, nothing. Here is a pastebin for that. https://pastebin.com/gkKX2bT4

[tenchikun]

So forcing Direct x 10 seems to have solved my problems. It seems to be running stable now for over an hour. 

 

Spoke too soon, the game just crashed again

 

[SylenThunder]

1 hour ago, tenchikun said:

Ok, fresh new install of windows, updated fully, all drivers downloaded and updated. All I got on here right now is steam, discord, battle.net, star trek online, outriders, and 7d2d.  jumped into game, started mining and crashed to desktop, no error, no popup, nothing. Here is a pastebin for that. https://pastebin.com/gkKX2bT4

When you took all of these steps, did you also exclude the client from Windows Defender?