Disconnected due to world corruption.

Happens randomly.

Getting the same thing regularly since the 1.13 update. Extremely frustrating.

I've also been getting the same bug. The game seems to pause when loading anything and suddenly I get the same screen. Happens almost a handful of times a night.

Guess I'm not playing on any world I don't want corrupted

Had exactly the same on realms.... well annoying

happens in minecraft dedicated software aswell

this is what is in the console

if this can help at all

it happens every time someone is loading chunks 

NO LOG FILE! - setting up server logging...
[2019-11-08 11:16:53 INFO] Starting Server
[2019-11-08 11:16:53 INFO] Version 1.13.0.34
[2019-11-08 11:16:53 INFO] Session ID aa8fdacd-cd69-4c59-b25e-7ca7ad57812a
[2019-11-08 11:16:53 INFO] Level Name: survival no rules
[2019-11-08 11:16:53 INFO] Game mode: 0 Survival
[2019-11-08 11:16:53 INFO] Difficulty: 3 HARD
[2019-11-08 11:16:56 INFO] Content logging enabled. Writing log to: ContentLog_Friday2019_November_08_11_16_56
[2019-11-08 11:17:08 INFO] IPv4 supported, port: 19131
[2019-11-08 11:17:08 INFO] IPv6 supported, port: 19139
[2019-11-08 11:17:08 INFO] IPv4 supported, port: 19132
[2019-11-08 11:17:08 INFO] IPv6 supported, port: 19133
[2019-11-08 11:17:11 INFO] Server started.
[2019-11-08 11:17:25 INFO] Player connected: littlexavier101, xuid: _______________
gamemode c @a
Set littlexavier101's game mode to Creative
weather clear
Changing to clear weather
time set day
Set the time to 73489000

Unknown command: . Please check that the command exists and that you have permission to use it.

Unknown command: . Please check that the command exists and that you have permission to use it.
[2019-11-08 11:21:04 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.13.0.34
OS: Windows
Server start: 2019-11-08 11:16:53 Eastern Standard Time
Dmp timestamp: 2019-11-08 11:21:04 Eastern Standard Time
Upload Date: 2019-11-08 11:21:04 Eastern Standard Time
Session ID: aa8fdacd-cd69-4c59-b25e-7ca7ad57812a
Commit hash: cc7008ca5cfe93c1c6753f6efecaa2af6d6f1f1f
Build id: 3308413
CrashReporter Key: 4c33f784-9908-3834-a2f6-26bb9dfb83ef

Crash
[2019-11-08 11:21:04 INFO] at class std::_List_iterator<class std::_List_val<struct std::_List_simple_types<struct std::pair<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const ,int> > > > std::_Hash<class std::_Umap_traits<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,int,class std::_Uhash_compare<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,struct std::hash<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > >,struct std::equal_to<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > > >,class std::allocator<struct std::pair<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const ,int> >,0> >::erase<class std::_List_iterator<class std::_List_val<struct std::_List_simple_types<struct std::pair<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const ,int> > > >,void>[class std::_List_iterator<class std::_List_val<struct std::_List_simple_types<struct std::pair<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const ,int> > > >] (UnknownFile:?)
at bool Minecraft::update[void] (UnknownFile:?)
at void ServerInstance::_update[void] (UnknownFile:?)
at void ServerInstance::startServerThread[void] (UnknownFile:?)
at bool SPSCQueue<class std::function<void >,512>::inner_enqueue<0,class std::function<void > >[class std::function<void > &&] (UnknownFile:?)
at unsigned int std::_Pad::_Call_func[void *] (UnknownFile:?)
at beginthreadex (UnknownFile:?)
at BaseThreadInitThunk (UnknownFile:?)
at RtlUserThreadStart (UnknownFile:?)

Thats exactly what im getting too! And it actually seems to happen the more chunks you load. Just started with 1.13

We are having the same issue. Our family has been working on our realm for 3 years! Kids are crying. Is it really gone? Is it time to stop paying for a realm?

This is also happening on the Bedrock Dedicated Server.

Many communities are experiencing this same issue. The host will see an error indicating it is our of space, and players will see an error saying the world is corrupt. There is already a bug report higher up in the priority list. You can help draw some attention to it by voting for it & adding any additional details you may have. 
https://bugs.mojang.com/browse/MCPE-32501

So this just happened and I seem to have lost my world I've been working on for over 2 years. Did that really just happen? Is this issue really being ignored? Am I done playing this game for good? Can we get an answer from a mod or ANYONE?? I am.. really kind of.. upset right now. 

I originally posted this to the Minecraft Forum, and I'll be throwing my entire story here so that hopefully this issue can get attention and traction.

This is going to be a rather long read, so I'll include a TL,DR near the end.

My close friends and I have been working on a survival anarchy/build-your-own-civilization Minecraft world for a little under a year. We started the map in March of 2019, and had been making pretty steady progress on our world until sometime near the end of October, leading into November. We stopped playing for a while as an update had made our game feel sluggish, view bobbing was all sorts of messed up, and our resource pack had stopped working. That, along with the fact that we were running out of things to do, made the 7 of us temporarily lose interest in our map.

Recently (mid-December), my buddy west side 233 and I updated our Minecraft games to the latest version, and hopped back on the world to see if the game felt more stable, and to our surprise, it truly did. The view bobbing had been fixed, and the game no longer felt as slow as it did before. I then went out using my Elytra West to go and generate new terrain with the intent of finding bee nests so I could relocate some of them to our island. As I was flying around, my screen was filled with a pink and black checkerboard pattern, and I saw a line of text that read "Disconnected due to world corruption. Try reopening the world or restoring it from a previous backup". I figured this may have had something to do with the fact that I was generating new terrain, and was just a one-time occurrence, and I reopened the world and headed home. This was the first time I had ever seen this error. Over the course of the next following days, we kept receiving the error, and still continue to get it to this day.

We have seen this error countless times now, and we are struggling to find any causes. Sometimes, it seems the simplest of things could force the world to close and hit me with the "World corruption" error. From the many many times that this has happened, we have not yet found any sort of pattern. There have been times where simply opening a chest will force-close the world, and other times where we can be flying around having a blast, and all will be fine.

As one of my buddies put it, it seems to be "consistently inconsistent" with how the world closes.

The game generally can run for about 15-40minutes before needing to be re-opened, or else I run the risk of the game telling me the map is "corrupted". However, there's been times where the game can run for hours without being "corrupted".

That's a problem, as I tend to go AFK, and allow my friends to use the map as a small little server while I'm gone.

I've gone ahead and compiled a little video, showcasing just exactly what happens a little bit before, and right as I get the error. Obviously, the video doesn't show anywhere near all the occurrences, or else the video would be 40minutes long. Here's the link: https://www.youtube.com/watch?v=mx4uvt1YQkw&feature=youtu.be

Things to note that should be taken into consideration:
-Map size is currently around 1.3GB
-Map did not have any resource packs active during the time of the errors (all packs disabled, only active pack was the default one)
-Map has been copied around 10 times (I make a copy whenever a big event occurs, ie; mass migration, massive project, the End prep etc.)
-During the video, only the host (me) sees the checkerboard pattern as the game closes, every other player sees a blank dirt texture

Things I have tried to resolve/isolate the issue:
-Reinstall Minecraft (remove app data and everything, resync worlds)
-Opening other worlds to see if it's an isolated issue with that particular map (it is)

TL,DR: Our survival map that we have collectively spent over 600 hours building, keeps randomly closing ever since the most recent update, and we receive the following line of text. "Disconnected due to world corruption. Try reopening the world or restoring it from a previous backup". We have put up with this error for as long as we could, but it's just so darn inconsistent and irritating, it makes it hard to do anything fun/risky without the risk of the game closing due to supposed "corruption".

As I used to routinely make backups of the world, I would be happy to restore it from a backup, only if the most recent backup wasn't so darn far behind...

It would be nice for the 7 of us to be able to enjoy our map again, and for this issue to finally be resolved.

This issue relates to the storage issue that occurs in Windows 10 edition.
Because a conflict occurs during the World Save process of Server Host, "Wolrd Corruption" occurs in multiplayer.

https://bugs.mojang.com/browse/MCPE-32501

Larry, thank you for adding to this. You should ask your friends that you play with to vote and/or comment on here as well. Every voice helps man. 

Same issue. Just stared with last update.

what I also have noticed is that if I’m riding a horse, I lose the horse, saddle, armor,  when the game is restarted.

i have a creative world that is approaching 1gig, so I have been grinding for about a year with my girl. She is gonna loose it one day, kill me over this, so it’s a matter of life and death. #savemysurvivalass

Still affecting 1.14.20. Still no acknowledgement from Mojang. 

This is still happening to the game and it's terrible. Having to keep track of back up saves just in case and if one isn't made losing hours of progress is such a turn off for the game. How is this just being ignored? Just an acknowledgement about it even if there is no immediate solution would be nice. But might not play anymore if I can't even keep my game running.

If you have a copy of the world available, you might like to upload a copy of it for investigation.

• On Windows 10 you can use the Export world feature.

• On Android or iOS you need to use a file explorer to navigate to Device storage > games > com.mojang > minecraftWorlds

• On Xbox or Switch the only way is to upload it to a Realm, and then download the world on Windows 10 or Android/iOS. (Please do not purchase a Realms subscription just to provide a world to us - but if you have a Realm already this may be a viable option if you wish to do so.)

If the world is larger than 10MB you can upload the world to OneDrive or a similar file sharing site, and then share the link.

If I can figure out how to upload my PS4 world I'll do it. I also think that Larry should upload his world if possible as he seems to get the error as least as much as I do if not more. 

I've had this happen as well, multiple times, when on windows 10. For me it happens on larger worlds (around 1gig) and flying around fairly fast to load chunks/travel places.

My husband is still getting this all the time. I get it too but don't play as often as it drives me mad. It's happened to him when just opening a chest! We're on Xbox and don't have a realm so can't help I'm afraid. So far, when it's crashed, he's lost multiple mine carts and boats and even a pet dog. It may have also caused the loss of a cat - really frustrating stuff.

Jay, here is the link to a copy of my world.

https://mega.nz/#!t7QCyI6D!ExqdL5v88APC_bH-4tNWzAILZqib1yXPVP9l01bU6cM

For those affected, could you please mention whether this is happening in a local or a multiplayer world, or on a Realm?

I run a multiplayer server using BDS.
I assume that WORLD CORRUPTION is caused by STORAGE ISSUE (https://bugs.mojang.com/browse/MCPE-32501)

For info - mine is local world, Xbox one and under 1Gb. My husband's is local world, Xbox one and 3.7Gb. His crashes more often but he plays more often (I get too frustrated with the crashes to play as much as I used to). On a good day he might get a couple of hours before the pink and black 'checkerboard' appears. Sometimes it's only half an hour.

It's a local PS4 world. According to the PS4 the file weighs in at 1.04 GB. It can happen whether I'm playing alone or with someone. Sometimes it happens after playing for a couple of hours. A couple of times I've had it happen seconds after loading in. The game doesn't always crash out after the error. I can usually click the ok button and then the game will either freeze forever causing me to force quit or it will freeze for a few seconds and then crash. Since the last update, crashes in general are less frequent; so now it tends to freeze at the "Disconnected..." screen and I have to force quit. It also may or may not be worth noting that I've never gotten the checkerboard version of the screen only the dirt screen with the message. Altho this could just be because I use texture packs and the error might be causing only the global resource pack to fail.

It's great to see some movement on this. I miss my survival world as I have stopped playing completely. It's not fun to play a game when you're filled with anxiety the entire time, waiting for the next world corruption to hit at any second. 

Like Christopher, I use a texture pack. My husband doesn't. Next time mine crashes I'll check if I get the checkerboard (I can't remember as I haven't played for a while). My husband definitely gets the checkerboard or a general pink and black random pattern. I can't imagine that those of is who've posted here are the only ones with this problem, I suspect that other people don't know where to report it or can't see the point. That or they've given up playing.

Found a way to upload my PS4 world (No realms on PS4). I hope this can help Mr. Wells and his team. The download link: https://www.mediafire.com/file/eenphwcoobrhhch/BedrockWorldPS4.zip/file

I don't remember where I was the last time I logged out tho. You should load in at one of my bases I just don't remember which one.

I noticed something strange while uploading that. My PS4 tells me the world file is 1.04GB but when you look at that file it will read as 1019.19MB which is just UNDER 1GB (GB is 1024MB). That's strange that the PS4 is reading the file size incorrectly. I checked in the Minecraft application and MC shows the world as 1019 MB as well. Idk if that's relevant but at this point I'm throwing pretty much everything at the wall.

I am in a single player world on Xbox one. The file size is 1.5 GB. It won’t crash if I stay in a relatively small area. As soon as I start to travel, it crashes. 

I wish I hadn’t downloaded the hot fix. Crashes ALL the time. Started a new world because I decided to download a clean version and start again hoping that would help but no. Haven’t even built a base and yet I cannot get further than just exploring a temple approx 1000 x 1000 from spawn. IOS on a brand new iPad. So frustrating.

Been experiencing this since the last update. PS4 world, primarily in multiplayer. World will randomly close with “Disconnected due to world corruption.” First time it happened I could reload the save, the second time the world became corrupted. The error happened once when I entered the nether, and again when I opened a shulker box.

Also noticed the file size is frozen at 572 mb, no matter how much I explore or build it will stay at this file size.
Not sure how I would upload the save (a non-corrupted backup of it, that is) because it’s on PS4.

The way I uploaded mine was to transfer the save files from system storage to a USB drive, transfer that to a PC and then upload it. I've noticed the file size not changing as well. I've noticed a couple of weird things around the file size actually. 

If anyone has access to the current beta please check and see if this is still an issue. Some are reporting success with MCPE-32501 in the new 1.15 beta. Incase these issues are linked it would be a good idea to test if this issue (MCPE-55137) is still occurring. I'm on Ps4 so no beta access for me. Thanks guys. 🤞🤞

Is it just us or have the crashes become more frequent in the last 24 hours? My husband was playing last night (about 12 hours ago here in France) and it started crashing every 10 minutes or so. Plus, when he went through a new portal from the Nether it crashed and he was sent underground (in the main world) and no corresponding portal appeared. He's now stuck in an unknown area (having got above ground) trying to find his way back to an existing property (having originally walked 4 full maps in the wrong direction!). It's also 're-drawing' parts of the Nether again. Where he's mined out and built rail, the tunnel and all railtrack have vanished and he's had to dig through and re-lay new track (this happened once before a few months ago). The game is rapidly approaching the point of being unplayable (I rarely play at the moment as it's so frustrating).

I don't play anymore because of this corruption bug so I can't comment on the crashing. However, your husband's issue with the nether resetting sounds like pretty typical chunk corruption. We see that a lot on realms.

I'm on Xbox One and started getting these crashes today. After I login to my local world, it crashes within a few minutes. I've tried removing the local data, uninstalling and reinstalling the game, and copying the world file. Still crashes and says disconnected due to world corruption.

Do you have beta access or is this 1.14.30?

I'm on 1.14.30.

MCPE-32501 was supposedly fixed in 1.15.0.53 and some people believe our issue here is a duplicate of that one. If anyone has beta access would you mind reporting back here whether or not this error is still occurring in 1.15.0.55?

I’ll having this issue on my multiplayer survival game. Not on my creative game.

Please vote on the issue if you haven't already. 

I also have this issue recently but i can join and play normally but if i quit and save and join again then there is a 60% chance of the disconected message appaered and crash, sometimes happend and sometimes wont and i play solo on ps4, this basically is a Huge bug that should be fixed months ago, i cant even play and i payed for a game which doesnt work how so destructive bug exist? And no i cant upload my world because i dont have a computer right now.

Attempted to load up my realm server today, got this same exact error code. Running version 1.14.3, its a new realm so the file size is 67mb and does not come close to cap.

running vanilla with no mods.

The same thing happens to me on android and I can't play on my own realm or with my friends in their worlds.

This issue has been popping up frequently on my multiplayer survival world on PS4 (1.14.41). The world currently sits at 1019MB's. Running the standard game with mod packs. Hope any of this helps.

That's interesting. In the game on ps4 my world sits at 1019MB as well and never changes. In the ps4 system storage however it reads as 1.04GB and never changes. Others have noticed inconsistencies around their file sizes as well. Just strange. 

This is still present on Bedrock 1.14.60 (playing on PC). I and many others had assumed this was related to MCPE-32501, but that was finally fixed in yesterday's update.

I had the same issue yesterday (2020.04.16.) after the update. I play on ps4 and my friend on xbox one and when he join my world the issue come in. Before the update we dont notice anything like this.

Please vote if you aren't doing so. I see a lot of new comments get posted over time but the vote total does not go up accordingly. Please vote to push this issue higher in the priority list. It's really a shame this is still being reported after yesterday's patch. I guess this was separate after all. Please VOTE.

Thanks for your patience while we try and get this resolved. If anyone else would like to provide a copy of their world save that might help us get to the bottom of the issue more quickly.

• On Windows 10 you can use the Export world feature.

• On Android or iOS you need to use a file explorer to navigate to Device storage > games > com.mojang > minecraftWorlds

• On Xbox or Switch the only way is to upload it to a Realm, and then download the world on Windows 10 or Android/iOS. (Please do not purchase a Realms subscription just to provide a world to us - but if you have a Realm already this may be a viable option if you wish to do so.)

If the world is larger than 10MB you can upload the world to OneDrive or a similar file sharing site, and then share the link.

Thanks Jay. Were you able to download Larry and my worlds? The download links should be in the comments from the beginning of February. Also check out Larry's compilation video of this bug in action. The link is also in the comments from the 20th of January.

So I’m new to this thread. Just had my world corrupted last night. Posted my complaint on the site and was brought here. So the question I gotta ask is, what’s next? Is this something that can be fixed, or are our worlds gone forever?

Same question. I'm a ps4 player. Are we forgotten on this or is there any hope for us too ? 

Everyone that is having this issue please upvote this. This is one of the worst bugs I’ve ever encountered out of the the 8 or 9 years I’ve been playing Minecraft.

Ah, yes.  The dreaded "Pink Checkerboard Screen of Doom."  I've been enduring this for weeks now.  I'm on PS4 and it seems to happen whenever my world exceeds 2GB in size.  It gets even worse when another player joins the world and travels more than 1500 blocks away from my player.  Even after the player stops joining, the world just crashes more and more.  I've tried deleting and reinstalling my world from online storage.  I've gone into saved game data and deleted corrupted data(when I can find it, sometimes it doesn't show up.)  I've even gone into PS4 safe mode and rebuilt my database.  Nothing seems to help.  And eventually, if this time goes like the last time when I ended up having to delete a world and start over, it will probably crash more and more until I just can't open the world at all.  I'm honestly about to quit this game for good.  Losing all that work and time invested is seriously playing with my emotions....

UPDATE:  The last world I lost made it up to 2GB before it corrupted.  However, I looked at the world I'm currently having issues with, and it seems frozen at 1019.0MB.  My backup copy registers the same size, and I've added a considerable amount of data since then, I'm sure.  I'm noticing that's a recurring theme in the comments.  Again, it makes no difference now if players join or if I'm playing alone.  It also makes no difference if I'm online or offline.  I may be able to play for hours before the crash, and sometimes the game crashes seconds after I open my world.  I've started playing my world in creative mode instead of survival.  It doesn't seem to be crashing in creative mode, so far.  I'll update if this changes.
Meanwhile, I'll try to get my world data forwarded to the experts.  PS4 won't support less than a USB 3.0 drive, and I don't have one.  It's gonna take a few days to order one.  I'm not going to the store for it, because, you know, Wuhan Plague.

UPDATE 2:  Nope.  It crashed in creative mode, too.  Just now.  It immediately got the Pink Checkerboard Screen of Doom as soon as the world opened.  Then I tried to open it again and got the Dirt Screen of Doom with the message, "There was a problem loading this world."  Oh dear, that's exactly what happened with the last world.  Eventually my world would never advance further than that screen and I wasn't able to open it at all.  I'm gonna lose this world.  Shucky darn.

Hello Jay!

The same problem occurred to my Realm today. I host a server on Minecraft windows 10 edition, on Realm. The game updated today to 1.14.60 version, then when i tried to open the server it came with the message "Disconnected due to world corruption. Try reopening the world or restoring it from a previous backup". I mention that before the update, my friends were playing normally on server. 

I attach a link with a copy of the world. I hope everything will be fixed. Thank you!

https://1drv.ms/u/s!AlzLSlQ3ZJdjggIw4D8M9_Qiukjz?e=6adpFJ

How is this not fixed yet, or at least the most important issue.

I don’t even know if the mods and bots on this site can even respond to us but us PS4 players seem to be getting shafted on this issue. We’re losing out entire worlds. If there’s anyone actually reading this. Please give us some form of hope. That there’s someone trying to fix this. Some human who can confirm that once this is fixed, our worlds would come back. 

First, this is not a PS4 exclusive issue. It affects all platforms. Read thru the comments. There are even a couple of posts from the project lead, Jay Wells. 

Second, I know this isn't the answer you want, but you're just going to have to learn to be patient. Some of us have been waiting for a fix since December, some longer. Not to be an apologist but this is the version of minecraft that is developed over several rather varied platforms. Also with the nether update and its bugs they are probably feeling the crunch from Microsoft. Bug fixing for this game sometimes takes a long time. The related issue, MCPE-32501, was reported in April of 2018 and was just fixed last week. Someone is now reporting that it's broken again in beta. There was a period of about a year and a half where multiple ender dragons would spawn during the dragon fight making it basically impossible to progress without the /kill command. My point is, buckle up; this could be a long ride. I spent some time being mad like you but it just doesn't help. This will eventually be fixed. It's just a shame it can take so long. 

Right there with you, Jesus.  I'm having this problem on PS4 as well, and also losing entire worlds.  But the game is buggy in general.  It seems the updates often lead to other problems, and they drop a lot of updates on us.  It doesn't help, either, that the bugs take a long time to fix.  I mean, there's a lot of them, and they have to fix them all.  We're in a queue here.  There are other bugs in line ahead of the one we're experiencing.  But make no mistake; if there's a shafting going on, it's not a discriminatory shafting.  The Bedrock codebase is on multiple platforms.  This means the good news is, when they fix this bug on Switch and Xbox One, it'll probably be fixed on PS4, too.  Again, we all share the same codebase.

If only there’s someway to get some confirmation telling us that we’d get our worlds back after we eventually do get an update. My world that I’ve been sharing with friends since long before bedrock. 

I don't think anyone can make that promise. The point of fixing this bug is so that, going forward, it doesn't happen anymore. Did you have your world file actually corrupt? Can you load in at all? Sometimes when this bug hits it corrupts the world but the other half of the time you can restart and reload but it will eventually happen again. If the world is actually corrupt then the only way to fix it is to use 3rd party software on a pc to rebuild the file. You may have to revert to a backup. Many of us on here have had to do that numerous times now, myself included. Sorry I know there is no good answer with a bug like this. It sucks and ruins the game. Hopefully it's days are numbered given how hard they're pushing for bug fixes with this update. 

^^  Inconvenient as all-get-out, but true.  😞  But hey, as long as I can get a world at some point in the future that won't do this stuff, I could live with starting over one more time.  My current seed is kind of crappy anyway.  All the cool stuff like jungles, badlands and woodland mansions are SO far away that I have to teleport to them or literally spend all day trekking.  My last seed was way cooler.  It was littered with woodland mansions, and every kind of biome was reasonably close.  I even stumbled across two fossils and a stronghold within 3000 blocks of where I spawned!  I was really, really ill when that world corrupted.

I can't help noticing that now that my world keeps crashing, the hotfix news screen listing all the fixed bugs(that I oddly didn't have) shows every time at startup.  I used to only see hotfix notifications once.
You know what would be nice?  I'd like to be able to revert to the version that didn't cause problems for me.  As a PS4 user, updates download and install whether I want them or not.  I'd really like to be able to have the choice of installing them, or at least be able to uninstall them if they cause me more problems than they solve.

So, fellow concerned players, I've been thinking some more about this, for those of us who have awesome worlds at stake and don't want to lose them permanently.  Of course, there's no guarantee that fixing the bug will fix our worlds.  But I'm pretty sure the more corrupted they get, the less likely they are to be successfully salvaged.  I'm also pretty sure the more we continue playing them, the more corrupted they are getting.  Bearing those two circumstances in mind, perhaps, for now, the best thing to do is for us to quit playing those worlds until this bug is fixed.  Take the intervening time to check out some new seeds; you might find one even better than the one you got.  Or use your current seed to create a fresh world, if there are things you would have liked to have done differently.  We have two directions we can go after that:  We can decide to not get too committed to our new worlds and move on to a new seed once the file size reaches 1019MB.  Or, we could possibly use this opportunity to create a useful tool for helping our Mojang techs.  Play with multiple players, play on local networks, play across different platforms with your new worlds; see if you can reproduce the bug and make them crash.  If we can discover some common denominators with this bug, it might actually help it to get fixed faster.  But we should probably leave our current worlds alone if we want to maximize the chances of being able to save them.
Just some thoughts, for what it's worth.  If nothing else, it's something to do.  Because time drags when you're nonessential and under stay-at-home orders...  🙂

tried restarting a few worlds myself and the result is the same and even found an awesome seed that had a zombie village, warm ocean and even a jungle biome at spawn, sad it's likely going to go away like the rest of my worlds, dunno might look to other games on mobile in place til it gets patched

Can everyone having this issue instead of commenting...can you please upvote this issue. Mojang obviously hasn’t gotten the attention needed to fix the issue. I see there are far more comments than upvotes on the bug and that is worrying. Really the only way for this to get fixed is if we upvote the bug instead of commenting on it

What Ian said!  It's far simpler to upvote than comment.  So if you have to pick one, vote on this issue so Mojang will address it!
Joe, did you find a trend with all the worlds you restarted?  Any common denominators?  Can you upload them so the Mojang gurus can examine them?

only common elements I see is when I save and quit my game off my app, I can only guess the issue might be centered around the save function at least on my end

Any similarities in the file sizes when your worlds start crashing, Joe?  I've found on my most recent world, the save file size is frozen at 1019MB and won't increase no matter what I do.  There's no warning that I'm running out of space, and there's still plenty of room on my HD anyway.  The file size just stops changing and the world starts crashing.  I've started a new seed to see if I it crashes again when I reach 1019MB.

most my files have been in size was around 75 MB  but size doesn't seem like a factor to my worlds like the save data

Same thing! It hapenned on my Realm as well a couple weeks ago. You start playing normaly and five minutes later it disconnects you... My friends and I deduced that it wasnt going to get better... We gave up, hopefully it doesnt happen to you guys.

Just got this today on my Realm. Happens immediately when logging in. Cannot play on my Realm at all. Error is "Disconnected due to world corruption" and "Try reopening the world or restoring it from a previous backup".

Running Bedrock 1.14.60 on Windows 10. Was logged in earlier today with another player who was using an older iPad running iOS 12. They logged out first and I continued to play. Then I logged out. When I tried to log back in later I get the error as soon as I should be appearing in world. Same error every time I try to log in.

I tried downloading a copy of the world to my PC and running it locally. It was only 49MB big, so not a large world. First time I tried to load the local copy it gave the same error. The 2nd time I tried locally it put me in the world at the World Spawn point and I had no inventory. I opened an Ender Chest and it was completely empty as well. So uploading that copy back up is not a good option. Looked like the world state was fine, but my player state got erased – at least on the local copy.

Right before logging out I had just killed a pillager patrol. I picked up their loot, ran inside and logged out. Since it's a realm the realm file is available to Mojang and/or Microsoft for debugging. Contact me for details.

Gonna be another useless comment here since there are a lot of these anyways. Just wanted to say that since the last time I saw this we doubled on votes maybe more but still nothing. This is already a 6 months old thread and nothing. So I'll assume it's all over for my world. A big thank you to the staff who do nothing and release updates for the ps4 every couple months now. The bots seem to do a lot more here in this site. Not to mention I see bugs that can wait since the game can still be played even if they are not getting more attention than the bug that stops you from playing the game. Sincerely shove it.🖕

          I got this on my realm this morning. It was fine last night and now neither I or my friends can join. This is only on my realm and not on any of my friends. So sad to see that this doesn't have a resolution. This is a big loss for us. We have been playing in this realm for months and months. I don't know how they are going to handle it when I tell them we just have to wait for Mojang to fix it. Especially because we play on bedrock which is usually the last platform to get updates. If this isn't in the update after the nether update (which we still haven't gotten on bedrock) I won't know what to say.

EDIT: my friend's dad found a way to fix it and fixed it. I will ask how and post that when i know

There is at least one report that this can be fixed by removing texture packs from the Realm. If anyone else can try that and confirm whether or not that works, it might be helpful.

Makes no difference for me. Happens with texture packs and without. Happens with zero packs even installed.

Edit: This is a single player world, not a realm. This was never a Realms specific issue. 

My Realm had no texture packs to begin with when it got that so I can't remove them. What did sort of work for me was to download the Realm and run it locally. The first time it gave the exact same error. Then I ran it again locally and that time it let me in but all my stuff was gone, even what was in ender chests. Uploading it back to the Realm saved the map but lost all my stuff. Not really a fix and probably doesn't work for every case of this corruption. But worth a try if you are out of ideas.

Before I begin, I'd like to list some criteria of my situation to help troubleshoot and coordinate the issue. I play on Bedrock Edition, with an original model PlayStation 4. I sometimes play by myself, and sometimes two of my friends play as well. I have never used a texture pack with this world. This is not a Realm, as Realms are not yet available on Bedrock for PlayStation. My world size is dormant, and stuck at 953.1 megabytes, and has not changed ever since I encountered this issue over one month ago. My storage capacity has plenty of space, and I began to encounter this bug briefly after the release of the 1.14.60 hotfix.

Similarly to many reports, this glitch triggers randomly. I may encounter this glitch several times upon struggling to load up the world. Other times, it will not trigger at all. I also believe this issue to be triggered by loading chunks, hence all the initial reports referring to the usage of elytras. Usually, I am able to play my world by myself if I travel modestly without loading too many chunks. Other times, the world will instantly corrupt upon loading into the game. Whenever I try to invite a friend to play with me, the world will give me the corrupt message immediately upon their arrival into the world. I believe that when my friends try to join, the game has to keep track of too many chunks at once, and in response, stops functioning.

The conditions of this glitch are ludicrous. Not only my own, but so many magnificent worlds and hundreds of hours of playtime have been unreasonably lost due to this game-breaking issue. Minecraft is a game about exploring. The worlds we play every day should keep their promises about being infinite. Why should we be given the facade that we can explore and play to our hearts' content, when we can only explore a certain amount before our worlds give up on us?

It's a shame that this large of a thread has gone completely overlooked and unnoticed by Mojang. I understand that things are hectic and bustling due to the imminent arrival of the Nether Update, but there needs to be attention given to a glitch that has been rampant and destructive for over six months that causes worlds to become nearly unplayable.

For those who are new to this thread, I highly urge you to upvote. There is still time to get this issue noticed by Mojang before the arrival of the Nether Update. Please upvote and tell your friends about this.. and maybe all of our lost worlds will see the light of day again. Thank you for reading.

Please understand that the bug tracker is not a forum for commenting / feedback on how bugs are fixed. It's purpose is to gather information that will assist the developers in reproducing the problem and getting those bugs fixed. Adding extra comments does not help, and in general they are not forwarded on to the developers, but they do make it harder to find the important information. So, please do not comment on bugs unless you have something helpful to add that has not already been said. The best way to get attention is to "vote" for the bug.

One forum for discussing bugs is the Mojira discord: https://discord.gg/rpCyfKV

This has plagued my world as well the last few weeks. The temp fix so far has been to Rebuild the Database by turning off the PS4 and going into Safe Mode. But sometimes this fix does not work. I've lost a few versions of the world indefinitely, as they fail to load. At this point I have about 9 different saves in this world, some are very far in the past, most are recent. Most of them do not work, but I keep them around in case they'll work after a Rebuild. They do occasionally work after a few tries. If I get in, I'm usually fine. I've only been kicked out due to corruption twice after being in the world longer than a minute.

But now I have no motivation to build anything, because I don't know when this version is going to self-destruct. It feels like every backup is just a ticking time bomb.

For context, my Creative World and its backup have had no issues, and I created a new Survival world that I've built in for a few days (but nothing major) - and this world has had no issues either. Just my most important world is affected.

PS4 player and I have this issue as well.  My world got to about 600MB and will consistently corrupt at various times for unknown reasons.  If I delete the local save files (not the world) sometimes it will load back up but Minecraft will reload as if it is the first time (voice assist comes on, re-sync Microsoft account & etc.).  A couple times I've had to delete the world and start again from a backup or download it from the PS4 upload file.  I basically can't explore or do much more in the world because of the corruption/crashing.  I need to do some end busting but I'm afraid of making the world any bigger.  There is plenty of space on the PS4 harddrive.  Very frustrating.  Please fix!

This issue occurred for us in our realm about a week ago.  We thought we would wait for the update to see if that resolved the issue.  It hasn't. 

I'm not super happy paying for a service monthly that clearly has no resolution, and since it appears to have been ongoing for over six months, is anyone able to advise of this issue is actually going to be fixed or do we just have to start again?

Just had this occur today on Bedrock version 2.08 in Survival mode with a bonus chest enabled.  I did notice that when I'm at the homescreen it still says I'm in version 1.16.1 so no idea what's going on there. Was in the middle of the first night in a village just standing in a house.  The screen came up and said "Disconnected due to world corruption...", looked exactly like the 2nd to last photo in original post.

2.08 is just the build version on ps4 because of the way they rolled console edition into Bedrock. Ignore that number. The latest version of Minecraft which you are playing is 1.16.1. With that said, yes this bug is alive and well in the current version. I think this is just a permanent feature of Minecraft now. On a brighter note, this bug is solely responsible for getting my FFXIV sub reactivated. I forgot how much I enjoyed that game. Square Enix says thank you for the business. 

This is happening to my Realm.  It will work for a few minutes or a few hours. Then shut down and list the world has been corrupted and to restart or restore a backup.  I have restored several backups and lost several hours of building.  I play on windows 10 bedrock edition.  It seems to happen more on portals to or from the Nether, but happens anytime as well.  

I pulled my world out of beta and it seemed to fix itself so maybe you guys can move your world into beta, wait for the main version to catch up amd then leave the beta

On PS4 I deleted Minecraft, reinstalled it, and continued in that world using a backup that hadn't been corrupted yet. I was cautious at first and didn't do anything time consuming or that I would be angry about losing. For about 2 weeks I played more and more, always backing up my save. Then one time when I saved and created a backup, BOTH were affected the next time I tried to get in and I lost about 20 hours of work. Having no update on this is extremely frustrating.

There is no point continuing to play Minecraft at all if you can't trust the game to operate correctly. It's a corruption time bomb.

"A corruption time bomb." Yes Paul, that is EXACTLY what it feels like and it's the reason I don't play anymore. Usually this bug occurs during gameplay but sometimes it will let you save and quit with no error only to find out that the world corrupted the next time you load in. It makes the game unplayable for me and I can't tell you how much I wish Mojang would prioritize this.

My realm continues to give me a corruption error message every time any player logs in, even after I restore the realm to a back up. The message is immediate upon logging in; we get no play time at all. The message reads "Disconnected due to world corruption / Try reopening the world or restoring it from a previous back up" with a dirt texture behind white text.

I paid for this game and the realm subscription for my little sister and we have had it less than a month. I am extremely disappointed that she has lost all of her progress and I am very hopeful for a fix – fast.

Edit: We play on Windows 10 Bedrock

Just a friendly reminder for anyone that is new to the ticket: ALWAYS remember to upvote the issue by clicking "vote for this issue" on the upper right of the page. The more votes this gets the higher it moves in the priority chain. Always vote. 

Still occurring 

This is occurring for our bedrock realm created by an Xbox user.  Our workaround consists of restoring to a backup, but that file gets corrupted shortly thereafter, consistently losing game progress. Slightly troubling that a ticket with this level of gameplay impact has been in "Community Consensus" status for the better part of a year without the ticket even being moved to "In Progress".  Are devs planning to look at this so that their players can return to the game without fear that their time will be wasted?

Don't bother with man. Being here waiting and all I see Mojang do is update meaningless stuff while a game breaking issue like this gets ignored for a year or more already. Upvote cause it's good to see the numbers raise but don't expect much.

Same problem on  my Main save on ps4

Xbox one s.   World is 1.3gb.  Error occurs when travelling / loading existing chunks... started happening a long time ago.  World basically unusable...   any updates please?

Still happening to me on Ps4, I have no idea what to do, it's my main world with a lot hours put into it

Nothing you can do except keep backups. I have about 7 rotating backups of my world because of this. If you get this message during gameplay try clicking on "OK" and then waiting for it to eventually go back to the title screen. Restart the game/client and try to load in again. You may be able to resume playing (maybe). However, if you're getting this while you're trying to load into the world, like in the screenshot above where it shows the nether update background with the black and pink squares where the loading bar and tips should be, that means your file corrupted the last time you saved and quit. That save is toast and you'll need to go to a backup. It really sucks but that's what we deal with now. Worlds around a gig or larger tend to become unstable in Bedrock Edition.

It happened to me I was running somwhere my sister was trying to join she get so laggy when she dose join as I get laggy if I join someone else 

I have found something strange when finding out the reasons for those corruptions. When applying packs, packs render many corrupted resources or missing ones, probably due to some weird save issues that the client or servers are trying to find. It will either crash or put you on the same screen shown above in those screenshots being "Disconnected due to world corruption. Try reopening your world or restoring to a previous backup." I'm not sure if it is based on those resources alone that it keeps on doing that corruption or chunk related data related to the level.dat files. 

From what I can conclude, primary resources seem to corrupt at times, which could happen randomly. The world can save, and not even correctly save. It is possibly due to huge worlds. I have never experienced this before, recently now twice with two separate worlds. It is essential to use backups, from what I have now learned. I do dearly wish they can come up with a bugfix shortly.

Prevent your worlds from being above 1GB. It seems it is relevant from what I have seen that Bedrock cannot fully get those resources, especially at its peak. That means to limit your exploration and continuously, after saving the world, back it up. I have learned this the hard way twice, and it is heartbreaking, mostly if it happens on Christmas Eve and on your birthday (both of which DID happen).

For now, we'll have to wait and see how Mojang will fix the data corruption. Please keep yourselves in check and have a nice day!

P.S. If you want me to send in screenshots, I could do so, but it will take up much of my time, so doing so will take a while.

UPDATE: I found more possible reasons and notable changes while working on the same world that kept getting corrupted after time and time. The constant crashing that your world gets occurs after an extended period, and the higher storage the world is, the worst it will get. Due to this, you are going to experience what is called a "resource crash." These crashes happen due to the source code or resources that cannot load due to inexplicable reasons. That means resources that were trying to load will possibly corrupt after constant crashes. Even after periods of loading the world after crashing, those crashes will later be consequential. They will perhaps corrupt your world due to saving issues, due to those resources and variables being no longer available. If your world disintegrates, then reset the data on Windows 10 using the replacing level.dat  method. However, this is not preventable on console (namely PS4).

The resources after backing up will continue, but after some time, the world will eventually corrupt regardless of backups and successive playthroughs. What happens is because of those crashes and the limit bedrock holds. Even when using a copy of the leading world, it is doomed to corrupt, so copies are not the solution. However, it is best to save a copy in your backup over time. Ensure you still have the main world, as it is the primary source for all of your copies when accessing due to corruption. If that world corrupts, your copies will no longer work. 

Large worlds overall have this issue primarily. Regardless of trying to go back and getting things done, Minecraft prevents you from even playing the world. It is the most game-breaking bug caused due to those crashes, and the game needs stable fixes to do so. I do not fully know what causes these crashes, as they happen at random. If any developer is reading this, please address this immediately, as this could happen to anyone's world. It tells us that the game is incredibly broken internally and unstable.

In conclusion, if you have a multiplayer world. PLEASE tell everyone not to explore very far, regardless of any event. If you are playing solo, this is regarded to you as well. DO NOT attempt to go far. That will increase the size of your world. If you are a host of a realm, this could happen to your domain as well, but it will be less frequent. The crashing could happen at random, even while you are AFK (I have crashed multiple times from just being AFK in one spot). Limit your exploration, stay relatively close and not too far from each other in your worlds. If you want to keep your world alive, try your best to limit your world size.

If you are planning to explore, make sure whatever that event is, such as woodland mansion hunting, that you are prepared and not to get sidetracked. You may want to limit how far those mansions are. Do not go regularly exploring unless you want the right spot for your house.

Simple Rundown: Minecraft Bedrock, after frequent resource error crashes, will consequently prevent your world from running and will not be accessible. Your world will no longer save those resources that are either corrupt or missing. Once you do not see that "Saving" screen, it means your world is now corrupted. Follow the instructions above if you want to prevent it as much as possible.

So I tried minecraft again for the first time in over a year.  Created a new infinite world and as soon as I spawned I paused it to go make breakfast.  Come back 10-15 mins later and this is what's on the screen.  I hope Mojang fixes this soon.

Still affecting the current version. 

Affects 1.16.230.50

Affects 1.16.220. Also happens with a Bedrock Dedicated Server

Affects 1.17.10 too.

You can have corrupted Minecraft, because you can have full memory.

Still happening with the current version of bedrock...

Just had this happen on my Realms server, a friend logged on and was at the world spawn with an empty inventory, so they ran back to town and was looking at the chicken farm they were building, then got kicked out with this error.  Now none of us can get into the world at all and always get this:

sins updating the Bedrock Dedicated Server from 1.17.30 to 1.17.32 we have a crash like this at least once a week.

we have tried to update to 1.17.40 in the hope it will be fixed but it is still happening.

sever specks:

os: ubuntu 18.04

cpu: intel xeon 8 core prosessor at 3.4ghz

ram 16gb

sorage :  2 ssd's raid 1

world size: over 26,9gb

update 11/feb/2022: we try a backup form before 1.17.30 and jump update to 1.18.2 i locks like its running stable for now

Happens in 1.18.0 realms

Hi Mojang support. So this issue was created 2+ years ago with no apparent progress/fix/roadmap/update?.  My situation is I have a world built with my son over around 2-3years on an XBOX ONE S which is 1.3GB in size for which this issue occurs. We have upgraded since to an XBOX SERIES S but we have no way of transferring the world to the new console, so its basically abandoned - we get the messages 'failed to sync data', then 'the world has not fully synced or has been corrupted. ...'. So, the ask is for Mojang to help out its customers by providing a way / tool to fix corrupted worlds, allowing for them to be played / migrated again.  So instead of focusing on skulk sensors, perhaps try to fix the long term issues that exist in the game first? and provide customers with transparency over what progress is being made? .... please and thank you.

@will roberts 

you can try the "mcc tool chest" 

https://mcctoolchest.weebly.com/

@wertie    thanks for that... however what would be great is if Mojang could supply an in-game tool to help resolve this type of issue... ie something like a defrag/compression/healthcheck utility for your worlds. Using third party apps is time consuming and even trying to connect to the XBOX file system from a PC is a non-trivial task

1.19.40 - Xbox One Series X -  1.3gb world - Bug happens every 20mins or so, followed by "Failed to Sync due to low memory" (with 300gb free!)... World saves, so after failed sync, i can exit the game, reboot the game and the world loads in 10secs in before the crash (luckily nothing lost).

Keep back ups, but afraid to remove game data from Xbox due to sync failure.

Please look into this Mojang, I've lost multiple worlds over the years due to crashes and "sync" failures.

The bug still occurs in 1.19.40. Deleted chunks near my spawn and reset others to different biomes. Nothing was destroyed and am able to import the chunks form old backups. This should be fixed

I researched about these kind of bug reports, and I saw that most of the bug reports that are related to this are on Console for some reason. 

I got a question really, does this happen on Windows or on iOS since I play on those platforms? I once loaded a world that was like 3.6GB large on my windows and nothing happened, but I am still curious if it still happens.

 And also, what file size would it be for a world in order to corrupt like this? I guess over 1-2GB but I am not sure about it.

Please reply and answer my questions.

I have a survival world which is 245.9MB, do you think that this bug will happen to my world?

If my world is 500MB, which is double my current survival world size, will this bug happen?

Also, how do you reproduce this bug? 

Please reply

I think this bug happened because in 1.13, Minecraft changed the level format for Bedrock and Java, and it might have bought some bugs with it including this one. 

And remember how MCPE-32501 bug got fixed, but then the same thing happened again (which is this bug report), I think Mojang is currently now trying to fix this bug completely and prevent it from happening ever, ever again so that's why it is still not resolved, this bug is like 3 years old. It might take a several years and even till 2030 for this bug to get fixed COMPLETELY, but of course, it won't be a 'won't fix'.

1.19.51 confirmed. Mid-flight was given pink checkered screen while my friend saw a plain dirt screen. My wife and I have played on this world since March 2019. We chose it from the biome selector for survival, Badlands. Currently back up but worried because our world is so old, will this happen when we travel and uncover new chunks. Also getting another error with world download. Will update on that tracker.

Echoing the last comment, v 1.19.51 confirmed.  After travelling 7 thousand blocks via elytra, I was in the middle of mining packed ice when I got the "disconnected from world" message with the bright checkboard screen. I can only imagine after reading the other comments, that this has to do with world size (currently sitting at 885.5MB). While I can still get into my world with no issues, I'm absolutely reserved about making any more progress if it's just going to end up crashing. How has it been 3 years and still no fix for this bug? 

Possible Cause and Fix Found (for PC)

My computer had faulty memory when the corruption occurred (failed memtest64 with over 50k errors). Replacing it seemed to have fixed this issue as i have experienced no new world corruption in any of my worlds. You can check for this yourself by running Windows Memory Diagnostic. If the test detects hardware issues then you might need to buy new memory (RAM) or contact the manufacturer for a warranty claim.

I don't know any possible fixes on consoles or mobile devices since their memory cannot be altered

World got Corrupted over almost 1 years. Cause over November 2023.

Relate to MCPE-62153.