PC MD5 Error (Second Time!)

[eternal biz]

Back around November I encountered my first MD5 error. I play Survival SP splitscreen with my girlfriend. We took over a house and built on it and around it. Had multiple chests full of supplies/food/guns/etc. Lost forges full of all its materials. The house went completely back to day 1 settings.

We decided to move on and rebuild it. We roughly play the game 4 to 6 hours a week. We are on day 50. Playing during the end of the blood moon and the game crashes(which is nothing new). After the crash we restarted the game to find that a new 3 story base I constructed (across from the original house we turned into our own fancy base) with an underground garage and crates of all my guns and ammo are all gone and reset back to day 1 settings. That fancy base we had to rebuild from the first MD5 error, half of it got reset. Chests of all our supplies/campfires/forges/workbenches/sea of wood spikes around the house are completely gone...... basically everything is all gone. It's completely disheartening. We bought this game because we absolutely love it but this MD5 error makes us want to stop playing. We can basically predict a crash because they literally happen every hour. When can this issue finally get fixed? Is there any way to recover whats been lost?

 

[RuttedLightning]

yikes...playing on xbox? Im sure the team is working to try and correct md5's, but until then there are some work arounds that have been suggested that have some success preventing this

 

[Damselx1]

Unfortunately this is still an issue on Xbox and sadly there is no way to get back what was lost, however, there are things you can do to protect yourself.

Some players shut down and clear cache (fully power down for at least 5 minutes) every hour/two hours, depending on the frequency of the crashes.

One player reported that he clears cache then loads up an old save first, so if its going to happen, it happens to his old game, not his current one.

Lastly, there is a player found workaround that requires you to quickly delete your local save, before it is written to the cloud. I understand that you need to be quick with this, and be sure to follow all the steps. As this is an unofficial workaround, it is recommended that you use caution - several players have sworn by this method though. You can find the workaround here:https://7daystodie.com/forums/showthread.php?69218-Possible-work-around-and-or-solution-to-md5-crashes(base-wipes-resets)

The information thread about the MD5 bug can be found here: https://7daystodie.com/forums/showthread.php?50175-Known-Issue-Terrain-Rewriting-(MD5-Issue)

 

[eternal biz]

7

Unfortunately this is still an issue on Xbox and sadly there is no way to get back what was lost, however, there are things you can do to protect yourself.
Some players shut down and clear cache (fully power down for at least 5 minutes) every hour/two hours, depending on the frequency of the crashes.

One player reported that he clears cache then loads up an old save first, so if its going to happen, it happens to his old game, not his current one.

Lastly, there is a player found workaround that requires you to quickly delete your local save, before it is written to the cloud. I understand that you need to be quick with this, and be sure to follow all the steps. As this is an unofficial workaround, it is recommended that you use caution - several players have sworn by this method though. You can find the workaround here:https://7daystodie.com/forums/showthread.php?69218-Possible-work-around-and-or-solution-to-md5-crashes(base-wipes-resets)

The information thread about the MD5 bug can be found here: https://7daystodie.com/forums/showthread.php?50175-Known-Issue-Terrain-Rewriting-(MD5-Issue)

We have the digital version on XB1 which I can't believe I forgot to mention.

Before we bought it we rented the disc base game and even back then the game would constantly crash. Back then we never encountered MD5 we'd only lose mini bikes. We're used to it crashing then just restarting the game back up to continue where we left off no problem. The first MD5 back in November really bothered my girlfriend but not me as much because we were still early on in the game and did lose quite a lot but not so much to where I was like "we'll just rebuild". Now, however, I'm starting to lose interest. It's such an amazing game but this issue is way beyond just an issue and I'm finding it hard to want to return to the game at all.

I've read a little about the work around but since we already started up the game to find that the MD5 had occurred trying the work around is probably too late right?

 

[Damselx1]

7

We have the digital version on XB1 which I can't believe I forgot to mention.

Before we bought it we rented the disc base game and even back then the game would constantly crash. Back then we never encountered MD5 we'd only lose mini bikes. We're used to it crashing then just restarting the game back up to continue where we left off no problem. The first MD5 back in November really bothered my girlfriend but not me as much because we were still early on in the game and did lose quite a lot but not so much to where I was like "we'll just rebuild". Now, however, I'm starting to lose interest. It's such an amazing game but this issue is way beyond just an issue and I'm finding it hard to want to return to the game at all.

I've read a little about the work around but since we already started up the game to find that the MD5 had occurred trying the work around is probably too late right?

Unfortunately, yes. It has to be immediately from what I've read. I you do decide to give another map a go, you could keep the workarounds in mind - players have reported a lot of success with it.

 

[eternal biz]

Unfortunately, yes. It has to be immediately from what I've read. I you do decide to give another map a go, you could keep the workarounds in mind - players have reported a lot of success with it.

That seems like a lot of work with the game crashing every hour. Since we play on my XB1 splitscreen both our gamertags have a save file attached to the game. Would I need to delete both saves or just mine since I'm the main account on the XB?

She's also afraid that trying the work around wouldn't work and permanently lose all our files and progress.

 

[Damselx1]

That seems like a lot of work with the game crashing every hour. Since we play on my XB1 splitscreen both our gamertags have a save file attached to the game. Would I need to delete both saves or just mine since I'm the main account on the XB? She's also afraid that trying the work around wouldn't work and permanently lose all our files and progress.

That I can't help you with as I'm don't know how it works (I'm on PS4, not Xbox). If the answer isn't in the links I gave, hopefully another Xbox player could chip in and answer this for you.

 

[gilean23]

That seems like a lot of work with the game crashing every hour. Since we play on my XB1 splitscreen both our gamertags have a save file attached to the game. Would I need to delete both saves or just mine since I'm the main account on the XB? She's also afraid that trying the work around wouldn't work and permanently lose all our files and progress.

I also play with my wife on XB1 split screen. I believe (but I'm not 100% certain) that you would only need to delete the save for the profile of whichever player the game is saved on (player 1). In our case, I log in first as the game is saved on my profile, so I delete my local save (not my wife's) when we crash. Fully exiting the game hourly has vastly cut down on our number of crashes. We generally only bother clearing cache before starting a session, and maybe once during a long session. If you're willing to spend the time to do a cache clear hourly though, I'm sure that would probably be safer.

ETA: We had 2 MD5's before we started the hourly logouts and local save deletions, and 0 since then. Not sure if that's pure luck, or attributable to all the workarounds, but I'm willing to keep trying the workarounds until they become don'tworkarounds.

 

[wildangel55]

I play on XBox and have had the MD5 error about 17 games. I am to stubborn to give up. When you do a hard reset and delete saved games on your XBox you don’t lose anything of the game. I am finally on level 70 from doing the work around. As soon as the screen goes blank I shut the console off then when I start it up I go to settings and delete all local saved games. That just takes back to the cloud save. Also another tip, very important, don’t store all your stuff in one location or put all your forges workbenches in one place. The error seems to focus on these. Spread them out!!

 

[Clare]

Hi Eternal Biz,

I am sorry to hear you have been effected by the MD5 error multiple times. Unfortunately I do not have an estimated fix time from the team for this issue and it's remaining triggers. However the team are not giving up and are continuing to work on the MD5 errors.

From reading the thread it appears that the information given above is accurate. I understand the workarounds are not ideal and can add to the frustration of the MD5 error, but hopefully these workarounds can help you to prevent further ones.

Thank you Damselx1, gilean23 and wildangel55 for your input and suggestions.

Eternal Biz, if you have any further questions, I will do my best to answer them.

Clare

 

[eternal biz]

I want to thank everyone for their time and helpful input.

Is it necessary to clear the cache for the work around or just delete the saved file then restore it from the cloud?

 

[Lockspur]

I want to thank everyone for their time and helpful input.
Is it necessary to clear the cache for the work around or just delete the saved file then restore it from the cloud?

If I get a crash, I force quit the game, delete the local saves and reboot. Works everytime, and only sets me back about 10-30 in-game minutes. I haven't done a cache dump as my fix always works.

 

[wildangel55]

As Lockspur said I immediately force shut down the console, I used to just wait a few minutes and then start it up go to settings; system; clear local saves; then when it restarts again it will resync with the cloud which in theory has a save from before the crash. However, on my last two crashes (#18 & 19), I noticed that even after I forced a auto shutdown the XBox was still functioning. Turns out even when you auto shutdown if the game was close to a cloud save it will still complete it. So on 18 & 19 I lost parts of base and two minibikes. I did save everything on 4 other crashes on the same game tho by using the work around. It really does work 99% of the time.