The crash happens a few moments after the autosave icon disappears. The autosave begins a few seconds after I load the world. The game completely crashes to the Xbox home screen once autosave is complete. Also, when I attempt to exit and save immediately after loading the map – before the autosave icon appears – the game will crash anyway to the Xbox home screen after a few moments of the "Saving World" message
I am able to travel a short distance before the game crashes while the autosave icon is present. The distance I traveled with the autosave icon flashing is saved but not the distance I travel moments before the crash
I am able to use items and eat food while the autosave icon is present. I cannot after the icon disappears moments before the crash
I noticed a few glitches happening days prior to the current issue. First, on rare occasions I would break a block and instead of the "breaking animation" it would just disappear. Then a quick moment later the breaking animation would happen, and I could pick up the block. The time I was playing just before the crashing, this was happening maybe every 4th or 5th block.
This is a very old survival world, about 8 years, ~230 Mb. This is the only problem I've ever had with it, and it has survived every update.
I have no mods except the "natural texture pack" that came standard with the game, which I've used since I started. I do not use any of the "experimental content" that's available. I didn't do anything different or change any setting.
I have a superflat creative world that does not crash which is also very old. I also loaded up a random survivor world from 2017 that does not crash either. New worlds do not crash. This one map is the only one that crashes.
I've tried clearing my Xbox's cache by holding down the power button for 5 seconds. I've uninstalled and reinstalled the game.
Minecraft was on my external hard drive, and I tried moving the game over to internal storage to see if that would help. It didn't. The same crash is occurring
I have tried playing the game offline. The same crash occurs
Is my world corrupted? Is this unfixable? What's making me the most upset is that I didn't do anything differently.
Any help would be very appreciated.
Comments 6
I'm not too sure. When the crash started happening, I was around 1000 blocks away from my base. Over the course of about 20 crashes, I was able to run back to my base. It's still crashing. If it's still crashing despite me being away from any ticking block, I can't see that being the problem.
My world that I have since 2017 is exactly the same problem. Do you know if the mojang has already commented on this?
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Is this still an issue in the latest version? If yes, can you please add it to the affected versions (or mention it if you are not the reporter)?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
This is the structure ticking bug. If you have a generated structure with a ticking block near by. it will crash the game.