A17 'stable' constant crashes - suggestions?

[McXtravert]

Since B240 dropped my game has become unplayable.

 

I get constant crashes at random. Sometimes I can go for 5 minutes then *bam* lock and CDT. Other times it can be after a few seconds. Seems no rhyme nor reason to it.

 

I've loaded up old A17 alpha saves, same issue. deleted these then created a new game, same issue. Whatever I try, constant CTD and I'm getting fed up with it. Prior to B240 I had no issues whatsoever so I'm pretty confused.

 

Can anyone help a frustrated player out?

 

My rig is 2700X, RX Vega 56, 16GB ram, installed on SSD, Win10Pro.

 

Thanks.

[TargetPractice]

I'll take a stab. My apologies if I'm telling you stuff you already know/have tried.

 

Please try these, one at a time, and restart your game each time.

1. Make sure you are using the current version - 17.0 (B240) stable as of this writing. If you opted in for the experimental versions, then you probably already know how to check this.

2. Verify local files: Open your Steam library, right-click on 7 days to die > Properties, click the Local Files tab, select Verify Integrity of Game Files. It'll take a while, depending on your setup. Any corrupted or missing files will be re-acquired and installed. If you have any mods or edited xml files installed, they will be overwritten.

3. Verify you have enough free space on whichever drive the game is installed on. I recommend a _minimum_ of 50Gb of free space so that games can write/update files as needed. Fortunately(?), 7D2D keeps most of its updates in your user profile.

4. Verify you have enough free space on whichever drive your user profile is on. 7D2D normally stores its player/map info under (Win10) C:\Users\<UserID>\AppData\Roaming\7DaysToDie\Saves. I recommend a _minimum_ of 100Gb of free space on whichever drive your OS and user profile are sitting on (troubleshooting with too many family members who like to sync My Photos with whatever cloud storage service they use). If you've got a lot of directories under there, consider deleting the old ones and their contents.

5. Try re-running the game with NO OTHER APPS RUNNING. I'm noticing that the latest version of Firefox browser is doing Very Bad Things with memory management and disk access on my box. I normally have Firefox running in the background so I can watch youtube while waiting for night/crafting timer to pass. I've had to be careful this past week, or use Chrome. (This does NOT mean that 7D2D couldn't use a generous optimization overhaul - which various mods and devs have said is on the schedule.)

6. If none of the above applies or fixes it, then it gets harder. Check your OS logs, for example (Win 10) Start > Control Panel > Administrative Tools > Event Viewer (there are lots of other ways to get to this, including click the the little window icon in the lower left and typing "Event Viewer"). Expand Windows Logs > Application, and Windows Logs > System. These may give some clues as to where you can try troubleshooting next. You can also try pulling up Task Manager while 7D2D is running and seeing if there's a RAM or CPU bottleneck (you never know when that AntiVirus software decides to freak out and eat your disk I/O).

 

Please post your results in this thread, as it may help others with similar problems. I hope my recommendations are useful in getting you back to headshotting Z's soon!

[McXtravert]

I'll take a stab. My apologies if I'm telling you stuff you already know/have tried.

 

Please try these, one at a time, and restart your game each time.

1. Make sure you are using the current version - 17.0 (B240) stable as of this writing. If you opted in for the experimental versions, then you probably already know how to check this.

2. Verify local files: Open your Steam library, right-click on 7 days to die > Properties, click the Local Files tab, select Verify Integrity of Game Files. It'll take a while, depending on your setup. Any corrupted or missing files will be re-acquired and installed. If you have any mods or edited xml files installed, they will be overwritten.

3. Verify you have enough free space on whichever drive the game is installed on. I recommend a _minimum_ of 50Gb of free space so that games can write/update files as needed. Fortunately(?), 7D2D keeps most of its updates in your user profile.

4. Verify you have enough free space on whichever drive your user profile is on. 7D2D normally stores its player/map info under (Win10) C:\Users\<UserID>\AppData\Roaming\7DaysToDie\Saves. I recommend a _minimum_ of 100Gb of free space on whichever drive your OS and user profile are sitting on (troubleshooting with too many family members who like to sync My Photos with whatever cloud storage service they use). If you've got a lot of directories under there, consider deleting the old ones and their contents.

5. Try re-running the game with NO OTHER APPS RUNNING. I'm noticing that the latest version of Firefox browser is doing Very Bad Things with memory management and disk access on my box. I normally have Firefox running in the background so I can watch youtube while waiting for night/crafting timer to pass. I've had to be careful this past week, or use Chrome. (This does NOT mean that 7D2D couldn't use a generous optimization overhaul - which various mods and devs have said is on the schedule.)

6. If none of the above applies or fixes it, then it gets harder. Check your OS logs, for example (Win 10) Start > Control Panel > Administrative Tools > Event Viewer (there are lots of other ways to get to this, including click the the little window icon in the lower left and typing "Event Viewer"). Expand Windows Logs > Application, and Windows Logs > System. These may give some clues as to where you can try troubleshooting next. You can also try pulling up Task Manager while 7D2D is running and seeing if there's a RAM or CPU bottleneck (you never know when that AntiVirus software decides to freak out and eat your disk I/O).

 

Please post your results in this thread, as it may help others with similar problems. I hope my recommendations are useful in getting you back to headshotting Z's soon!

 

Thanks very much for that. I'd tried everything suggested including fresh install etc. Still random crash persists.

 

I reviewed the log file from the event viewer and on crash I had the following Application error:

 

Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0x00000000

Fault offset: 0x0000000000000000

Faulting process id: 0x2c0c

Faulting application start time: 0x01d49fc1f03aaa6c

Faulting application path: bad_module_info

Faulting module path: unknown

Report Id: 7c163e74-111d-4f0f-839d-0780b8beee06

Faulting package full name:

Faulting package-relative application ID:

[OzHawkeye]

Make sure to post it in the Bugs thread over here:

 

https://7daystodie.com/forums/showthread.php?101363-Alpha-17-Stable-B240-bug-reporting-thread/page17

 

The more detail, the better, and I'd include the steps you've already taken.