Death in Nether (Blaze) - Realms Crash

I cannot get any Diagnostics logs to be created by the app. Thankfully at least someone else was able to provide some logs from an iOS device and even on a newer firmware than my own. I will try to post in the logs from my PC when I have time if I can locate them.

I'm not sure if I can provide any diagnostic, but this does also happen on iPad 2, iOS 9.3.5, MCPE 1.0.0. I died in the Nether, and can't reconnect. It gets through all loading messages, and then crashes when it should display me in the Nether.

Same problem on windows 10 but only crashes for the 2nd player on a multiplayer game, my fiance died in the nether and could get back into the realm but can't acces chests/inventory etc. if she does it crashes i exported the world to use on lan and the same happens, copied it to her pc and ran it I joined the world and crashed without loading the world :S

Do note that I'd already died some times in the Nether, before it finally crashed and never let me back in. So this bug is triggered by a death/crash in the Nether, but that is not the main issue, as I'm living (or dying? 🙂 ) proof that you can die some times in the Nether without being locked out.

Exact same situation as Even. I died twice in the Nether, and on the third the game crashed. Haven't played since (despite trying).

I actually think I had died about 2-3 times in the Nether before the crash as well. This almost looks like it is linked to the following: Nether; Death Count in Nether; and Blazes being the cause of death. The last one may be wrong but it seems to be fighting and dying from Blazes generally causes the issue but that could just be a coincidence. Really wish I could provide logs but the game just refuses to create logs upon crash on my iOS device.

Here are some more details to narrow down the bug:

• It is player related! Friends of mine has been playing on the realm after I was shut out, and when I changed to another gamerTag I was allowed back on. So the bug is connected to a given gamerTag

• Not sure if it is Blaze's or Wither Skeletons triggering it, as I've fought both (and died). Most of the times surviving, and able to play again. My final death was within a Nether Fortress

Stuff I tried to remedy the situation:

• Restart MCPE, both just a plain restart, or by wiping it from memory (using the multitask handling of iOS)

• Restart my iPad before restarting MCPE

• Re-installing iPad without installing anything extra, not even the backup of my worlds

• Re-installing iPad including my worlds

None of these actually helped allowing me back on the realm which crashed. All allowed me gameplay in different worlds, but not on the realm. The only thing allowing me back on the realm, was to create another gamerTag and be re-invited to the realm with that new gamerTag.

This is the same bug:
https://bugs.mojang.com/browse/REALMS-258

And my husband is experiencing. No one else on the Realm (yet).
We haven't tried resetting the realm, but have heard back from others who did that resetting it did not fix the problem with the player(s) who crashed in the Nether while fighting Blazes.
BTW, we can fight Blazes just fine (and did to collect 7 rods) and we can die in the nether just fine (and did about 50 times while building a tunnel to our hub) this only happened when he was fighting multiple blazes and a ghast and there was a crash.

Does this issue solely occur on Realms, or is it affecting players on Single player, LAN or over XBox Live?

Mega_Spud,

Please read the Jira Ticket. https://bugs.mojang.com/browse/REALMS-258 There is a lot more information there as well. I wrote "My wife is having the same issue. She was in the Nether fighting and then Minecraft Crashed. She is trying to connect to my Realms server and can no longer connect. If I copy the realm to my desktop and then have her try and get the same problem that she cannot connect"

So it happens any time you try to connect to a game that you were in the Neither.

Moved to the realms section. The developers are aware of this issue and it will be looked into further. I'm also going to point other tickets to this as the parent ticket.

It's been a fortnight since I can not connect to my realm.

This issue seems to be directly linked to Realms and XBL accounts being unable to access the Realm after so many deaths within the Nether. I wish I could give some more info.

Side note:
I really only play PE for Realms so I can use the same world on my PC and phone. But now I have been paying for a service for about 2 weeks that I can't even use. I understand it is a weird bug that is difficult to fix but I don't want to cancel my Subscription if it will delete my world. I just feel like I am paying for nothing when it comes to this. Especially at that steep amount of money for me to just have one world on multiple devices for myself. I don't even use Realms to play with other people. So $10/month for something that doesn't work literally at all for me right now is really irritating. Sorry that that is more or less unrelated to the issue but I had to put it out there.

My son and I becoming so frustrate,we where about to cross the ender portal, we just missed some blaze powder for the last ender eyes, after month of playing and paying, I hope this bug will be fix soon!

Update 1.0.1 just came out. The issue is still occurring on this update on my iOS 10.1.1 (14b100) iPhone 7+.

This happened to me about one week ago, I died in the nether a few times due to Blazes and then Minecraft completely crashed. Since then I am unable to enter that world, either on Realms or downloaded locally.
In this state Realms is unusable, because resetting the world isn't an option due to how much effort has been put into the current world.
When attempting to join the world the client makes nether sounds and then crashes.
Windows 10 Edition, v1.0.0.

Having what appears to be this same issue. On version PE 1.0.1
It crashes out completely with no message when trying to login to the Realm. Only my user account is having this issue. Other users can get in and out. This all started yesterday when I was killed in the nether. Not sure what the difference was because I had been killed there a couple of times before in that same session. During login I see the load sequence:
Locating server
Realms
Syncing pack
Realms
Building terrain
Done!
And then MCPE is gone. We are running on multiple iOS devices. Since a number of users have spent substantial time building in this world we would really like to avoid the "world reset" option if possible.
Any help is greatly appreciated!

Add me to the list with the exact same issue. Two of us were in the realm in the nether, we both died and the game crashed. Since then I am unable to get back into the realm, not even if I download it (it is my realm). My friend, however, CAN still get into the realm as long as I'm not trying to get in. What's interesting is that when he gets in, he spawns with the inventory and XP of MY character, so it's almost like something got crossed between our gamertags... While I do have a backup of the world prior to the crash, which works fine locally, when I upload it to my realm, it crashes again. Furthermore, when trying to reset the realm, it keeps giving me a "failed to reset..." error.

My friend has even tried uploading my backups to his own realm, and there we can get into it individually, but then it crashes if we both try to go in.

Again, this is only directly affecting me. Others can access the realm fine. I mainly play on Windows 10, but the crash is also occurring when I try from PE as well. I really hope there's some kind of solution that doesn't involve losing the whole realm/world.

Exact same issue as above...so do we get our money back?

Both my husband and I, on separate computers and separate accounts are having the issue. I've reset our realms three times because of it. Once his realm, twice my realm. It has been after dying from the blazes in the fortress each time. This last time, we were both one shot at the same time by one blaze, even though wearing enchanted diamond armor. So... something is up with the blazes in fortresses. We didn't find the fortress for two weeks in this last realm world and I was in the nether for hours on end just fine. As soon as we would find, and die, from blazes the crashes and bugs start. Although this last time I could at least get back into the game but opening our inventory causes immediate crash. No message no nothing... just staring at my wallpaper like I was never playing minecraft at all. I have given up trying to go to the nether until this issue is fixed. Currently working on building a castle instead...

Issues known so far

It happens only in the Nether
Generally happens after 1-3 deaths
Almost all cases seem to be in a Fortress
Almost all cases seem to be from Blaze (a few exceptions)
Linked specifically to the account that dies
Happening on at least iOS and Windows 10 running PE 1.0-1.0.1

I'm sorry. I know this is being worked on. But it is getting ridiculous. This is now 2 months worth of Realms I have paid for to not be able to do anything at all. Everyone who has experienced this issue really should be getting their money back in some way because this is crap.

Same. Killed in Nether by a Blaze and game crashed. Now game crashes when loading is 'Done!' only on my account. Can hear Ghasts for a few seconds before crash.

1.0.2 released in the App Store for iOS. Still crashing at "Done" when loading Realms. This is getting ridiculous. I am losing a good chunk of cash due to this issue. Really hope they refund the users getting the error. This is asinine.

I had to create a second account to continue playing hope this gets fixed soon. t

I'm having the same issue. I didn't didn't die in the nether, but the game crashed after multiple blaze appeared. Other players in my realm can log in, but mine shows 'done!' Hear the ghast, then everything shuts down. I've tried logging in from iPhone, iPad, and windows 10 desktop, all crash.

So are you all creating new Xbox live accounts to continue playing?

Does a new account help it? I didnt try that I started a new world

Yes, I created a new gamer tag for my Son, invited him to our realm, and now he can get on and play. Not sure if we just gotta avoid the nether now 😞

I havent had any issues since but haven't died much since!!! Hard to say

Hello,

I've encountered the same issue. Here are my details:

• Minecraft PE for iOS on iPad

• 3 player Realm

• I'm the Realm admin

• First occurred in MCPE version 1.0.1, still happening in 1.0.2

• Issue started when I was fighting multiple Blazes in the Nether. I got hit and the game crashed. Haven't been able able to get back in. The only exception is if I switch the Realm to Creative, I can get in. But as soon as I switch back to Survival it crashes.

• When I log in it says loading, syncing pack with server, done, then the screen goes white and takes me to my iPad home screen.

• The two other Realm players, both on the same home network and wifi, can still access the Realm.

• Twice when I've attempted to get in I got a "global resources" crash error.

Stuff I tried to remedy the situation:

• Restarting MCPE in multiple ways (logging out of Xbox Live, not signing out of Xbox Live, hard reboot of my iPad before launching app, etc.)

• Installing 1.0.2 update

• Deleting Minecraft app from my iPad and reinstalling it and my worlds

Hope this helps.

Sandra

I have this issue (or similar):
1. Crash when hit by blaze (didn't die)
2. In a fortress
3. In a 3 player realm
4. Version 1.0.2.
5. I can't log on the realm, it crash after I hear 2 second of nether sounds on the "Done'" screen.

I just attempted to download the world
It downloads offline fine
The game crashes when loading the offline version of the world as well
I thought maybe I could at least open offline but apparently not
This was attempted on v1.0.2 on iOS 10.1.1 (14b100) iPhone 9,2
This Realms world was created in v0.16.x if I remember correctly
This crash only existed after v1.0

Damn. i was hoping to find a solution. My friend and i play on realms 1.0.2 or maybe 1.0.3 and he died and cant login anymore or use the world in any way.
not on his phone or pc... does someone know a workaround?
The server costs money and we seem to not be able to play together now in this world.

There is no workaround other than make a new account and log in then avoid the Nether at literally all costs basically meaning never see the End. Myself and a few others here have tried a lot of different ideas and nothing seems to work.

But the bug still exists on v1.0.3 and there is no way to fix this other than suck it up. I am pretty sure even creating a new world doesn't fix the issue but I am not sure.

Did you try changing to creative and peaceful?
maybe that works?
I cant cause its my friends realm and he is raging right now

I have tried Peaceful but it does not work. I have not tried Creative as to allow me to still get achievements as I am an achievement hunter. I honestly can't say there is really anything else left that we can do to fix the issue. Only idea is to make another account and just add that account into the server list and play that way and avoid the Nether at all costs.

And I really don't feel like this is being worked on at all and it makes me question if this is even really a place to report bugs. Like there hasn't really been anything opened to the public about them being aware of the issue and looking into it. It just seems like this is an issue that they don't care about because they are still making money off of the people who are sitting and paying hoping for a fix one day. I am seriously considering cancelling my payments until the bug is acknowledged and fixed but I am afraid of losing my world. I put a LOT of work into it and don't want to have to start all over again.

My report, titled "Windows 10 nether Realm crash when open inventory or chest" is not a duplicate of this. Can you please re-open my report?

On Windows 10 in the Realm, my game crashes when I open my inventory or try to open a chest. I can check my inventory in PE. This happens in the Overworld as well as the Nether.

I was hoping this might be fixed in 1.0.3, but it still happens. Minecraft is completely unplayable if I can't access inventory.

Hi Tom,

I've experienced that issue too, but there's an easy fix. It's because you have got a Wither Skull in your inventory. If you die/kill yourself, you're inventory will empty and the problem is fixed. You'll obviously lose the skull, but at least you can play!

PB

I have had exactly the same issue last night. I was playing with my daughter on a realm in the Nether, fighting blazes in a nether fortress. She plays on a iPad4 mini, and I play on a Windows 10 edition on a paid realm. My game froze, and she saw me dropping out of the game. Now I cannot join the realm game anymore from my Windows 10 edition or a pocket edition.
The crash report says this:

"
Version=1
EventType=MoBEX
EventTime=131311837306901538
ReportType=2
Consent=1
UploadTime=131311837307113462
ReportIdentifier=d71e7499-ef5e-11e6-9c18-74d02b9402b3
IntegratorReportIdentifier=81e8702f-20e8-4477-90c6-9fee2bb5d2a2
NsAppName=praid:App
AppSessionGuid=00002540-0003-0027-5dd9-09776b83d201
TargetAppId=U:Microsoft.MinecraftUWP_1.0.312.0_x64__8wekyb3d8bbwe!App
TargetAppVer=1.0.312.0_x64_!2017//02//03:23:35:30!0!Minecraft.Windows.exe
BootId=4294967295
Response.BucketId=56bbb3e1ddd01510d29f067fa25464d6
Response.BucketTable=5
Response.LegacyBucketId=133460149662
Response.type=4
Sig[0].Name=Package Full Name
Sig[0].Value=Microsoft.MinecraftUWP_1.0.312.0_x64__8wekyb3d8bbwe
Sig[1].Name=Application Name
Sig[1].Value=praid:App
Sig[2].Name=Application Version
Sig[2].Value=1.0.3.12
Sig[3].Name=Application Timestamp
Sig[3].Value=589513c2
Sig[4].Name=Fault Module Name
Sig[4].Value=ucrtbase.dll
Sig[5].Name=Fault Module Version
Sig[5].Value=10.0.14393.0
Sig[6].Name=Fault Module Timestamp
Sig[6].Value=578997b5
Sig[7].Name=Exception Offset
Sig[7].Value=000000000006d5b8
Sig[8].Name=Exception Code
Sig[8].Value=c0000409
Sig[9].Name=Exception Data
Sig[9].Value=0000000000000005
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=c0e1
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=c0e1a5fa30ad6558b5ff8633c356bc3f
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=cfab
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=cfab75bfb70cf4b11e6028018bc1b652
UI[2]=C:\Program Files\WindowsApps\Microsoft.MinecraftUWP_1.0.312.0_x64__8wekyb3d8bbwe\Minecraft.Windows.exe
LoadedModule[0]=C:\Program Files\WindowsApps\Microsoft.MinecraftUWP_1.0.312.0_x64__8wekyb3d8bbwe\Minecraft.Windows.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[5]=C:\WINDOWS\System32\sechost.dll
LoadedModule[6]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[7]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[8]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_47.dll
LoadedModule[9]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[10]=C:\WINDOWS\System32\combase.dll
LoadedModule[11]=C:\WINDOWS\System32\user32.dll
LoadedModule[12]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[13]=C:\WINDOWS\System32\win32u.dll
LoadedModule[14]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[15]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[17]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[18]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[19]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[20]=C:\WINDOWS\SYSTEM32\XINPUTUAP.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\gamingtcui.dll
LoadedModule[22]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.24123.0_x64__8wekyb3d8bbwe\vccorlib140_app.DLL
LoadedModule[23]=C:\WINDOWS\System32\shcore.dll
LoadedModule[24]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.24123.0_x64__8wekyb3d8bbwe\MSVCP140_APP.dll
LoadedModule[25]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.24123.0_x64__8wekyb3d8bbwe\CONCRT140_APP.dll
LoadedModule[26]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[27]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[28]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.24123.0_x64__8wekyb3d8bbwe\VCRUNTIME140_APP.dll
LoadedModule[29]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[30]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[31]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\CRYPTBASE.DLL
LoadedModule[33]=C:\Windows\System32\Windows.Devices.Enumeration.dll
LoadedModule[34]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\BiWinrt.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\deviceassociation.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\twinapi.appcore.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[39]=C:\Windows\System32\DevDispItemProvider.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[41]=C:\Windows\System32\WinTypes.dll
LoadedModule[42]=C:\Windows\System32\Windows.ApplicationModel.Store.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\WINHTTP.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\Cabinet.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\webservices.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[47]=C:\Windows\System32\Windows.UI.Xaml.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\Bcp47Langs.dll
LoadedModule[50]=C:\Windows\System32\Windows.UI.dll
LoadedModule[51]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[52]=C:\Windows\System32\ActXPrxy.dll
LoadedModule[53]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[54]=C:\WINDOWS\system32\CoreUIComponents.dll
LoadedModule[55]=C:\WINDOWS\SYSTEM32\rometadata.dll
LoadedModule[56]=C:\Windows\System32\MrmCoreR.dll
LoadedModule[57]=C:\WINDOWS\System32\profapi.dll
LoadedModule[58]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispiwu.inf_amd64_b67dc924fff8de6d\nvwgf2umx.dll
LoadedModule[59]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[60]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[61]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[62]=C:\WINDOWS\System32\msctf.dll
LoadedModule[63]=C:\WINDOWS\System32\Shell32.dll
LoadedModule[64]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[65]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[66]=C:\WINDOWS\System32\shlwapi.dll
LoadedModule[67]=C:\WINDOWS\system32\nvspcap64.dll
LoadedModule[68]=C:\WINDOWS\System32\ole32.dll
LoadedModule[69]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[70]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[71]=C:\WINDOWS\system32\nvapi64.dll
LoadedModule[72]=C:\WINDOWS\SYSTEM32\windows.ui.core.textinput.dll
LoadedModule[73]=C:\WINDOWS\SYSTEM32\TextInputFramework.dll
LoadedModule[74]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[75]=C:\Windows\System32\Windows.UI.Immersive.dll
LoadedModule[76]=C:\WINDOWS\system32\DataExchange.dll
LoadedModule[77]=C:\WINDOWS\SYSTEM32\dcomp.dll
LoadedModule[78]=C:\Windows\System32\OneCoreUAPCommonProxyStub.dll
LoadedModule[79]=C:\WINDOWS\SYSTEM32\dwrite.dll
LoadedModule[80]=C:\Windows\System32\Windows.Globalization.dll
LoadedModule[81]=C:\WINDOWS\SYSTEM32\msftedit.dll
LoadedModule[82]=C:\WINDOWS\SYSTEM32\globinputhost.dll
LoadedModule[83]=C:\WINDOWS\SYSTEM32\NInput.dll
LoadedModule[84]=C:\WINDOWS\SYSTEM32\d2d1.dll
LoadedModule[85]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[86]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[87]=C:\Windows\System32\Windows.Graphics.dll
LoadedModule[88]=C:\Windows\System32\twinapi.dll
LoadedModule[89]=C:\Windows\System32\threadpoolwinrt.dll
LoadedModule[90]=C:\Windows\System32\Windows.ApplicationModel.dll
LoadedModule[91]=C:\Windows\System32\Windows.Storage.ApplicationData.dll
LoadedModule[92]=C:\Windows\System32\Windows.Networking.Connectivity.dll
LoadedModule[93]=C:\Windows\System32\Windows.Media.Speech.dll
LoadedModule[94]=C:\WINDOWS\SYSTEM32\msvcp110_win.dll
LoadedModule[95]=C:\WINDOWS\SYSTEM32\RemoteNaturalLanguage.dll
LoadedModule[96]=C:\WINDOWS\SYSTEM32\urlmon.dll
LoadedModule[97]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[98]=C:\Windows\System32\msxml6.dll
LoadedModule[99]=C:\WINDOWS\System32\Speech_OneCore\Common\sapi_onecore.dll
LoadedModule[100]=C:\WINDOWS\SYSTEM32\MMDevAPI.DLL
LoadedModule[101]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[102]=C:\WINDOWS\SYSTEM32\wininet.dll
LoadedModule[103]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[104]=C:\Windows\System32\speech_onecore\engines\tts\MSTTSEngine_OneCore.dll
LoadedModule[105]=C:\Windows\System32\speech_onecore\engines\tts\MSTTSLoc_OneCore.DLL
LoadedModule[106]=C:\WINDOWS\SYSTEM32\DPAPI.dll
LoadedModule[107]=C:\WINDOWS\SYSTEM32\tokenbinding.dll
LoadedModule[108]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[109]=C:\WINDOWS\system32\mswsock.dll
LoadedModule[110]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[111]=C:\WINDOWS\System32\NSI.dll
LoadedModule[112]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[113]=C:\WINDOWS\SYSTEM32\userenv.dll
LoadedModule[114]=C:\WINDOWS\SYSTEM32\profext.dll
LoadedModule[115]=C:\Windows\System32\rasadhlp.dll
LoadedModule[116]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[117]=C:\WINDOWS\system32\schannel.DLL
LoadedModule[118]=C:\WINDOWS\SYSTEM32\mskeyprotect.dll
LoadedModule[119]=C:\WINDOWS\SYSTEM32\ncrypt.dll
LoadedModule[120]=C:\WINDOWS\SYSTEM32\NTASN1.dll
LoadedModule[121]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[122]=C:\Windows\System32\cryptnet.dll
LoadedModule[123]=C:\Program Files (x86)\EMET 5.5\EMET_CE64.DLL
LoadedModule[124]=C:\WINDOWS\system32\ncryptsslp.dll
LoadedModule[125]=C:\Windows\System32\Windows.Gaming.Input.dll
LoadedModule[126]=C:\Windows\System32\deviceaccess.dll
LoadedModule[127]=C:\Windows\System32\rmclient.dll
LoadedModule[128]=C:\Program Files\WindowsApps\Microsoft.MinecraftUWP_1.0.312.0_x64__8wekyb3d8bbwe\fmod_WSA82_X64.dll
LoadedModule[129]=C:\WINDOWS\SYSTEM32\MFPlat.DLL
LoadedModule[130]=C:\WINDOWS\SYSTEM32\MFReadWrite.dll
LoadedModule[131]=C:\WINDOWS\SYSTEM32\RTWorkQ.DLL
LoadedModule[132]=C:\Windows\System32\DDORes.dll
LoadedModule[133]=C:\Windows\System32\DefaultDeviceManager.dll
LoadedModule[134]=C:\Windows\System32\Windows.Media.Devices.dll
LoadedModule[135]=C:\WINDOWS\SYSTEM32\AVRT.dll
LoadedModule[136]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[137]=C:\Windows\System32\CryptoWinRT.dll
LoadedModule[138]=C:\Windows\System32\Windows.Security.Authentication.Web.Core.dll
LoadedModule[139]=C:\Windows\System32\usermgrproxy.dll
LoadedModule[140]=C:\Windows\System32\vaultcli.dll
LoadedModule[141]=C:\WINDOWS\system32\directmanipulation.dll
LoadedModule[142]=C:\Windows\System32\XblAuthTokenBrokerExt.dll
LoadedModule[143]=C:\Windows\System32\XblAuthManagerProxy.dll
LoadedModule[144]=C:\WINDOWS\system32\napinsp.dll
LoadedModule[145]=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule[146]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[147]=C:\WINDOWS\System32\winrnr.dll
LoadedModule[148]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[149]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
LoadedModule[150]=C:\Windows\System32\OneCoreCommonProxyStub.dll
LoadedModule[151]=C:\Windows\System32\WinRtTracing.dll
LoadedModule[152]=C:\WINDOWS\SYSTEM32\webio.dll
LoadedModule[153]=C:\Windows\System32\Windows.Networking.dll
LoadedModule[154]=C:\WINDOWS\SYSTEM32\FirewallAPI.dll
LoadedModule[155]=C:\WINDOWS\SYSTEM32\Windows.Networking.HostName.dll
LoadedModule[156]=C:\WINDOWS\SYSTEM32\fwbase.dll
LoadedModule[157]=C:\Windows\System32\certenroll.dll
LoadedModule[158]=C:\WINDOWS\SYSTEM32\certca.dll
LoadedModule[159]=C:\WINDOWS\System32\WLDAP32.dll
LoadedModule[160]=C:\WINDOWS\system32\mlang.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=MoBEX
AppName=Microsoft.MinecraftUWP_8wekyb3d8bbwe!App
AppPath=C:\Program Files\WindowsApps\Microsoft.MinecraftUWP_1.0.312.0_x64__8wekyb3d8bbwe\Minecraft.Windows.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=BA6062A8EC45C6C15729AFC60375788F
MetadataHash=-601156801
"

Is there any chance I can recover my account? Any idea when this will be fixed?

Erwin

This same issue impacted two players on my Realm. They were hit by blazes near a spawner in the nether and their clients immediately froze/crashed. Whenever they try to log onto the realm using either PE or win 10 edition (v 1.0.3) their client crashes. Everyone else is still able to log in just fine. We see them log in for about 5 seconds, then they disconnect.

I changed the realm into Creative mode. They were able to log on successfully then. I had them move out of the nether and they destroyed all items in their inventory and that they were wearing. After I switched back to Survival the issue persisted. We may end up resetting the realm so everyone can play again.

Can you try in 1.10.3?

Update for me on Windows 10: v1.0.3 - I had let my realm expire and decided to renew it with the latest update. To my surprise, I am actually able to enter the realm now! BUT, something is still not right. My character shows no health icons (only the food icons), and I can't die! Progress, but still need some bug fixing apparently. I am not going to risk going into the nether yet on my other realm.

I tried on 1.0.3 on Windows 10 and it still crashes on startup. When I copied the the realm offline, I can start in creative mode, but I cannot kill myself from the commandline.
If you want I can upload the offline realm, it is ~100 Mb.

Erwin

Trying to enter my Realms game in 1.0.3 on PC caused my entire PC to freeze, needing a reboot. None of the other accounts in my Realms are affected, and can all still play as normal.

TMO

After dying in the Nether, I am unable to access inventory by pressing "E" or clicking to open any chests on Windows 10 v1.0.3, 10 player realm (I am the owner). Both actions cause screen to freeze, then entire app shuts down. None of the other people with realm access are affected. I can access realm using Minecraft PE and play normally. I can play other realms and single player games normally.

This is still happening for me. My partner just paid to open a realm and we uploaded a copy of the world there, only to find that now, it crashes for both her and myself, which is different to previously where the bug only affected myself.

Thanks again for all the useful comments. Sorry this issue is ongoing. As stated earlier the developers are aware of the issue and it is being looked in to.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki

I just had this same issue... I died in the nether (via blaze). 4 days later, I went back into the nether and found my items were still there. I picked them up and could not access my inventory. I have noticed SEVERAL bugs. Most having to do with redstone, and loading in and out of the game. In my opinion, it is incredibly irresponsible to charge money for a server when there are game breaking bugs. Once again, I am giving you money, and now i can't play what i am paying for.

Is there anyone here who can provide any indication when this issue is going to be assigned and/or progressed? even better, when it is expected to be resolved?
I have to renew my realm-account soon, and at this point in time I am planning not to do so.
I also want to claim back the last 2 months of my realm subscription, as it has been unused for this period.
Anyone has a clue?

Erwin

I am in the same boat as Erwin, however mine has been over 3 months (I think going onto month 4). I really hope that if this issue is resolved we will have some kind of reimbursement. Even if it is only something as simple as free Realms time and not actual return in money. I wish I could provide more info for the issue because I used to play my world daily and now I can't play it at all and I play it in all my down time in between things I am doing so now I have hardly anything to do at all in my little between times. This issue is pretty extreme and for it to have been this long before we even heard again about the issue being worked on at all is pretty screwed up. There is a large number of people paying for something they cannot even use and that is just asinine. I am sorry, I hate being that guy but it is getting really irritating now.

Edit: Spelling errors

Sames as others. FIX THIS ASAP! Might as well cancel my realm and claim my money back.

This shit is killing our progression. No one wants to go into the nether because they do not want to have to restart the realm. What is the progress on this bug? Why is this taking so long to fix? A bug like this should have been fixed within a week. Its a Critical bug that does not allow players to play on their realms without resetting. That needs to get fix and fixed 3 months ago.

I don't know about everyone else, but I have not had any issues since 1.0.4 on the Win 10 PC version. My friends and I have gone into the nether several times. No issues thus far. I even purposefully allowed several blazes to spawn and hit and kill me. No issues.

Again, I don't know everyone else's experience, but for me at least, so far so good!

I am the owner. I had the same issues previously, and I ended up opening a second realm. After the 1.0.4 update I went back into my original realm and it was working fine again. That's where I tried to reproduce the bug again, but could not. That's why I'm thinking they've definitely done some work on this, though I haven't seen/heard if it's officially resolved. I still take backups of my realm every time before I play, just in case.

First, it is not owner-only. My husbad was one of the first to experience this crash and still can't play because of it. He is not the realm owner.

Secondly, as I noted many months ago in the original report, I went into the Nether during the same time as he, both with other players and alone, and I had about 50 deaths. We were tunneling long range and looking for others' nether portals to hook into the base. We died via blazes several dozen times....And I never had this bug occur...And really, neither did my husband until about his 100th death or so....Indeed, since it no longer mattered if I could play the realm or not (since our whole point of our family having it is so we can play with my husband who works far away) I've been coming and going into the Nether during this entire time, and dying, even by Blazes while collecting rods.....I'd still be rather hesitant to declare it won't happen. I'll wait until my 200th death, or 300th, or maybe I"ll never truly believe that it IS fixed and I will always enter the Nether with trepidation and a kind of sad hopelessness...I don't know.

All I know is, that the realm is useless to me, my daughter, and my husband, as we can no longer play with him....EVEN if the realm owner can delete it all and start again, he won't, because it's half a year's worth of building by all of us, and there's only three of us, my brother (who owns the realm) and his kids outnumber us.

Just tried to connect again on my Android tablet, running v1.0.4. It got to the "Done" screen of the load before crashing.

I've gone into the Nether and the Blazes just sat around and didn't attack me. I've fought the Blazes once also. I have not died to a Blaze attack, and I'm not about to risk my surviving account to test it and find out. 🙂 I've no desire to restart this world if I can help it.

iPhone 7+ iOS 10.2.1 PE Version 1.0.5 still crashes. Log link below:

https://ghostbin.com/paste/y77bs

Cameron Jackson,

when I got this bug I did not die either. I was together with someone else near a blaze spawner though. 1.0.5 still crashes with me on Windows 10 PE and IOS.
The other account did not get bugged, so it seems I picked something up in my inventory which caused my game to crash.
This seems to be inline with some of the other bugs.
I very disappointed that this has not even been assigned. Maybe we should do some voting on this issue.

Erwin

Still crashing when logging in to Realm, on version 1.0.5.

I have just issued a complaint with Mojang to request my money back. In the process I looked into the stats on bugs.mojang.com, and this bug has by far the most votes. I am a bit surprised this was not addressed in the latest patch.
When I export the game from the realm I can load it as a local game, and it will crash instantly in survival.
When I switch the local game to creative I can enter the game, but it crashes when I look into my inventory.
This suggests there is something wrong with an item the account picked up. It should be easy to fix the inventory check on loading the game, and erase anything that makes the game crash. That will still crash the game when the culprit item drops and moves into the inventory, but at least we can continue to play.

Erwin

Erwin

I'm new here and have a similar issue with the Nether (2 computers and 1 tablet in 2 different households)... and by mistake, I posted this in the Pocket Edition/W‌indows 10 section. Should I repost in Realms?

MCPE-20807 Entering Nether Portal crashes game/cannot get back into game
In our realm, my son's character entered the nether portal and it crashed the Minecraft program to desktop. Now when he starts minecraft and clicks the realm button, it starts loading but then freezes and that's it. Can't get in. We tried destroying the portal, recreating the portal, uninstalling the game, reinstallng the game, updating video drivers.
So then I tried to go through the nether portal and the same thing happened... it crashed the Minecraft program to desktop. Now when I start minecraft and click the realm button, it starts loading but then freezes and that's it. Can't get in.
There is no error message, it just freezes and crashes to desktop. This started happening for us yesterday, March 31 late evening mst.

Thanks Cameron Jackson. I may give your suggestion a try as it is my realm. I have voted for this as I feel it is an issue that should be given priority with the number of people who pay for a realm.

Spend insane amounts of time imagining, constructing, and enjoying a world. A world I pay to sustain, with real $ and product usage, and the best answer we can get after half a year is..... open ticket. I am disheartened at a lack of disclosure, product support, and in general execution. This issue is a known issue. An issue that could not have passed proper testing without a sign of occurrence prior to launch, and yet in good faith Mojang is selling this product to millions of people. Could anyone at all explain to me the bug, how to avoid it, and lastly when can a paying customer reasonably expect to get full use of the product actively being "sold" to me and my fellow blockheads around the world?

Not sure if it is related to time of day. My son and I experienced this at different times but both were in the mid-to-late evening. My issue has nothing to do with dying in the Nether, but is due to something crashing the game while the character was still in the Nether Portal. For whatever reason it must corrupt the character because everyone else can still log into the Realm and play, although we have Destroyed the Nether Portal and posted signs to not enter one. This is why I feel not being able to get back into the realm (my own issue and the other ones I have read here) has something to do with crashing/dying while in the Nether.

I was told to download the realm, and see if I could access it as a single player game. I could download it but it would still not load even as a single player game. I was then told the only solution is to Reset the Realm. I have not done this as the others can still play and I am hoping this issue will be fixed before my subscription runs out. My husband has signed up for Realms and so we play there now.

One thing I may have noticed - I don't think I've seen any complaints about this happening in a personal game, not in Realms. Does anyone know of this happening not in a Realms server?

TMO

This has happened to me once in a single game as well as on the Realms server in both cases I either deleted or reset the map. For awhile on my Realms server I logged in under a separate account

I have had the same blaze bug on a personal game. However when a personal game crashes it reverts back to the last autosave which is anywhere between 30 seconds and 2 minutes ago as far as I can tell. In this autosave the fatal event has not happened yet and you can continue to play from there. In the realm it does not revert back to the autosave, and that is why the account becomes corrupted. I suspect it has something to do with a dropped item from a blaze which crashes the client game engine, and which is stuck in the inventory of the account. This would explain why people who play on their personal servers don't experience this problem.
Thinking about it a bit more, I think I could create a situation where this would happen on a personal server. If you keep a primary account to start the game, and then play with a secondary account from a different ipad/pc/client, it would experience the same problem. Maybe someone can test this?

Erwin

With realms the server doesn't crash, it's the client which crashes, and in our case it keeps crashing.
I have experienced multiple crashes near 2 blaze farms on my local game, but because it reverts back to a little before the game crashed, I never experience the problem. I think a 2nd user on my local game will actually experience exactly the same problem. My 8 year old daughter isn't too much of a daredevil to go blaze hunting though. The thought of her losing her account also scares her.

Yes, it works. You do also have to have cheats enabled to enter the code.

I am logged in and playing under my own account again.

As a side effect of switching to Creative and enabling Cheats, either one of them alone means you can never again gain Achievements on this server. A small price to pay for being able to play again, imho.

TMO

Where did you find those instructions Cameron? I don't think I saw them in the release notes. It's great it is fixed, but seems strange to me that we have to follow those steps for something that is "fixed".

The new version fixed the issue for me. I didn't follow any of the advice here regarding creative mode, etc, just connected to the realm and it worked. Thanks for the fix, Mojang team.

On Windows 10 Edition, I can walk around in my realm in 1.0.6, but when I switch to my inventory it crashes instantly. when I open a chest it does not crash though.
I have taken a copy from the realm to experiment on my home pc and I think I have found the cause of the issue.
on my home server, in survival everything works still the same as in the realm. as soon as I go to my inventory the game crashes. I have let myself die, and then I can go to my inventory, however as soon as I pickup my armor the game crashes instantly. I guess if you don't want to lose the achievements, it is best to unload all your inventory into a chest, die in a safe place, which you can later flood with lava to get rid of the cursed armor items.
I suspect the developers tried to put some nice 'blaze burning' state on our beloved armor items which crashes the game because it got half implemented in the software. (I tried dying in water, it did not resolve the issue with the armor.
The current patch solves the issue of a crash on startup which allows you to actually die and get rid of the items, however it doesn't fix those items.

Erwin

The new update did not fix my issue. My character must still be corrupted, caught in the Nether portal forever. 😞

Thank you, Mojang developers! The issue has been resolved in my Realm.

Hi Cameron... I believe both my son's character and my character are stuck in the Nether Portal as that is when both of us experienced the game crash. I have no idea whether the character actually made it through the portal or not.

Since that time, we cannot log into the Realm. It gets to the purple Building Terrain screen and then freezes. The other 7 players in the Realm see the message that says we have logged into the Realm, but we never get into the Realm as the purple Building Terrain screen is where it freezes on both of our computers.