PC Crashes with green slime then corrupts the save game!

B

blackbirdsd

Refugee
Ive been playing for a while now and have had consistent PC crashes whenever I have green slime shot at me.  PC just restarts.  Its not an overheat issue as I play for hours up until i see the green slime.  Rarely the green slime does not crash the pc but 99% of the time.  When I go to to load the game again the save game is corrupted.  I have an I9 core and a 7900xtx.   

 
PC issue that only happens when green slime in 7days to die are shown?  No other issue with pc no other issue with any game and no issue with 7 days to die except when green slime shows up.

 
blackbirdsd said:
PC issue that only happens when green slime in 7days to die are shown?  No other issue with pc no other issue with any game and no issue with 7 days to die except when green slime shows up.
Click to expand...


1. No other game taxes your hardware like 7 Days does. This is due to the heavy calculations for structural integrity, navigating AI is an ever-changing fully 3D Voxel landscape, and the I/O required between storage and RAM for the live world data. If your hardware has a weak link, this game will find it where no others will. Even stress test and benchmarking software might not trigger it, but the game will.

2. No clue what "green slime" even is, but sounds like it's probably a GPU issue.

3. When your PC "crashes" 95% of the time it is a Windows BSOD. (Blue Screen of Death)   The error for the BSOD is displayed while Windows writes the crash data to a log on your computer. With newer PC's this can happen so fast you don't see it, and it appears the computer simply reboots.  The details are available in your system log, and you can disable the automatic restart to get a view of the error code.

You came asking for help. You are getting information from an expert. You can choose to heed the advice, or ignore it.

 
So I have zero lag and high frame rates.  I lowered the settings and played for a couple hours and once again when the zombie with the mutated head sprays the green slime, pc restarts.

Jugginator said:
I'm willing to bet it's a gpu driver issue, amd is sorta notorious for those. Try reinstalling, maybe using DDU
Click to expand...
Do you mean reinstall the game?  If so, I have done that.  What is DDU?

Thanks

 
I did some testing and so far I found my pc doesnt crash if I am only using 1 stick of ram.  Ive tried both sticks of ram in the A2 slot and both dont seem to have the issue but when I put the second stick in slot b2 then it crashes when the mutated head spits the green slime.  I tried running with and without XMP.  I have 2 sticks of 16gb gskill ram DDR4-3200 CL16-18-18-38 1.35v.  Doesnt seem to be a fault of the ram but maybe a bios setting I am unaware about.  Any help would be appreciated.  Thanks

 
blackbirdsd said:
I did some testing and so far I found my pc doesnt crash if I am only using 1 stick of ram.  Ive tried both sticks of ram in the A2 slot and both dont seem to have the issue but when I put the second stick in slot b2 then it crashes when the mutated head spits the green slime.  I tried running with and without XMP.  I have 2 sticks of 16gb gskill ram DDR4-3200 CL16-18-18-38 1.35v.  Doesnt seem to be a fault of the ram but maybe a bios setting I am unaware about.  Any help would be appreciated.  Thanks
Click to expand...


Oh, yeah that's one of four things, one being very unlikely.

  • You have two mismatch sticks of ram (the manufacture date is very important here, as ram is made in... "bins", anything from that bin is the same, but the same exact stick of ram made out of another bin may not be the exact same and won't work together because of that. If you bought them as a pair, it's not this. If they both don't run together anymore without XMP on, then it's likely not this
  • The stick that you took out is dying. You can swap your first stick into slot b2 and see if it runs
  • The slot on the motherboard is failing (very unlikely but possible)
  • The memory controller on the CPU is aging and not able to handle two sticks of ram at set speed. Since it does it without XMP, unlikely, but potentially it's failed to the point where it can't handle two sticks at the same time period

I have been there done that with ram sticks, it's complicated heh

Seems like you narrowed it down though, good thinking! 

I'd start with the stick of ram that seems good. Put it in the slot you took the other one out, run it, run it under XMP, see if it crashes. If it doesn't, take the potentially bad stick and put it in the slot the other potentially good stick is in and test. If it doesn't crash then too, then you know it's not the ram anyway.

If your ram is pretty old, you can try upping the voltage. I do not suggest going high at all, and I would suggest doing research (if your ram is RIPJAW, then we have the same, it handles 1.4, but again, different bins different silicon, so they won't be exactly the same). Increments of +0.05 are common to try. As they age, they might need more power to be stable, but, you can also reduce the power, but you will need to reduce the CL and timings. This is where things get stupidly complicated, and I only suggest it if reading books worth of stuff about ram timings sounds interesting to you 🤣

 
Jugginator said:
Oh, yeah that's one of four things, one being very unlikely.

  • You have two mismatch sticks of ram (the manufacture date is very important here, as ram is made in... "bins", anything from that bin is the same, but the same exact stick of ram made out of another bin may not be the exact same and won't work together because of that. If you bought them as a pair, it's not this. If they both don't run together anymore without XMP on, then it's likely not this
  • The stick that you took out is dying. You can swap your first stick into slot b2 and see if it runs
  • The slot on the motherboard is failing (very unlikely but possible)
  • The memory controller on the CPU is aging and not able to handle two sticks of ram at set speed. Since it does it without XMP, unlikely, but potentially it's failed to the point where it can't handle two sticks at the same time period

I have been there done that with ram sticks, it's complicated heh

Seems like you narrowed it down though, good thinking! 

I'd start with the stick of ram that seems good. Put it in the slot you took the other one out, run it, run it under XMP, see if it crashes. If it doesn't, take the potentially bad stick and put it in the slot the other potentially good stick is in and test. If it doesn't crash then too, then you know it's not the ram anyway.

If your ram is pretty old, you can try upping the voltage. I do not suggest going high at all, and I would suggest doing research (if your ram is RIPJAW, then we have the same, it handles 1.4, but again, different bins different silicon, so they won't be exactly the same). Increments of +0.05 are common to try. As they age, they might need more power to be stable, but, you can also reduce the power, but you will need to reduce the CL and timings. This is where things get stupidly complicated, and I only suggest it if reading books worth of stuff about ram timings sounds interesting to you 🤣
Click to expand...
Thanks for the quick reply.  Both sticks seem to not have an issue if placed separately in A2.  But when either ram is in A2 and B2 then that is what seems to make the pc crash possibl.  I believe I bought the ram together in one package.  They are Ripjaws F4-3200c16D-32GVK.  When I had both sticks in I would either run at 2100 or 3200 with xmp but havent tried 3200 without xmp (not sure if its possible).  I havent noticed any issue with other games its just that stupid mutant in 7 Days to die for some reason.  Another thing I forgot to mention is almost always, when the pc crashes and reboots, the it wants to load optimized bios settings or it wont boot.  But after doing the default I can run XMP and restart the pc with no prompt to load optimized defaults.  

Thanks again for your help.

 
blackbirdsd said:
Thanks for the quick reply.  Both sticks seem to not have an issue if placed separately in A2.  But when either ram is in A2 and B2 then that is what seems to make the pc crash possibl.  I believe I bought the ram together in one package.  They are Ripjaws F4-3200c16D-32GVK.  When I had both sticks in I would either run at 2100 or 3200 with xmp but havent tried 3200 without xmp (not sure if its possible).  I havent noticed any issue with other games its just that stupid mutant in 7 Days to die for some reason.  Another thing I forgot to mention is almost always, when the pc crashes and reboots, the it wants to load optimized bios settings or it wont boot.  But after doing the default I can run XMP and restart the pc with no prompt to load optimized defaults.  

Thanks again for your help.
Click to expand...


Hmmm. Weeeeel if you want to get hugely technical about it, all XMP does is load the first... 5 or 6 timings, voltage increase, and the clock increase. The lower the timings, the more power it needs, the higher the clock, the higher the power. The clock speed is pretty easy to achieve, but the timings are a whole other level and the cpu, motherboard, and both ram sticks need to be in constant sync. So, you absolutely can just try loading it up in 3200, increase the voltage to 1.35v, and leave the timings all at default. CL is the biiiiig one you want, but even that also relies on timings being certain numbers... it's a mess of stuff you need to study and look up lol.

This game and CSGO (CS2 now) are great for finding bad ram timings. Most games don't use that much ram compared with us, and if they do, they don't hammer ram like we do. There is a TON of work being done on the data in ram, so there is an exponentially increased chance of hitting something bad. When memory has something bad in it, your system will reboot itself to save itself since it will cause cascading failures (everything in your system runs on ram, so that's why it does it).

Honestly, the cop vomit could just be numbers that happen to push the timings over the limits. 

Don't forget to check for a BIOS update too

And you're welcome, I absolutely do not mind at all :)

 
Last edited by a moderator:
Just noticed something interesting.  When the big head mutant guy spits, my pc has a quiet beep each time he spits.  Usually the first spit crashes the pc but I disabled XMP and ran it at 3200 and he spit 3 times at me and each time the motherboard beeped.  the third spit crashed the pc.

Would be nice if I can remove that ■■■■ character all together so I can play this game. LOL

 
blackbirdsd said:
Just noticed something interesting.  When the big head mutant guy spits, my pc has a quiet beep each time he spits.  Usually the first spit crashes the pc but I disabled XMP and ran it at 3200 and he spit 3 times at me and each time the motherboard beeped.  the third spit crashed the pc.

Would be nice if I can remove that ■■■■ character all together so I can play this game. LOL
Click to expand...


The motherboard beep is very interesting. It would be something I'm not aware of, I've only known beeps to happen on boot when a failure happens as a beep-code. Hmm. May want to look up beep codes for your motherboard model, but be specific to look up beeps while the pc is running.

You can try your ram at complete default except the voltage (set the voltage to 1.35). If it runs, bump up the frequency by a few steps and keep going until you either hit 3200 stable or you crash.

You can also increase the timings by +2 (leave CL alone, the first number, should be 16 or 18 by default) as well during this, if you hit crashes. 

You can look up what your ram/etc should be set to timing wise, but a good rule of thumb is keep the evens even and the odds odd.

Actually... look into spread spectrum. Most call it something or the other, it's EMI related, so I'd look it up for your motherboard. It's something that usually doesn't do anything at all but it can make ram timings unstable

 
@blackbirdsdJust wanted to let you know that I brought this up since you're not alone; there are some ideas that could be done to make it less taxing, it will take some time to make sure it's done correctly, so absolutely no time frame at the moment, but we're hoping to work something in to make it less taxing on aging/dying hardware to hopefully help.

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