Tanner L Chamberlin
Assigned
Reported
Comments
Hey, my Minecraft folks...I'm adding to this thread for a few reason. First off, I just want to bump the thread, as I've had this issue since Summer of 2020 (approx.) off and on, with mixed chances of if it happens when I'm playing multiplayer connected to a friend's game (hosted on their Xbox One), a Realm we have, a split-screen game on my own Xbox One, or a single-player game (which is the least frequent of the culprits). Looking back, almost all of them may have happened on a 4K TV, so I'll try the 1080p resolution trick and see how things play out!
Secondly, to expand on the issue, I notice a lot of my crashes have been coupled with moments where I interact with my Xbox menu overlay, even if I'm just opening that menu to see the time or some crap. Statistically, if I join an Xbox Live Party before joining a server, I've seen more crashes than if I wait to join a party afterwards. Since 1.16.2, however, I'm even getting some weird chugging from doing that, which sometimes results in a freeze and then the hard crash/reboot. It may be anecdotal evidence, but it bears mentioning.
Third, I'm the only person in our group of 5-7 players that logs in to these various hosts that uses an Xbox One X, as everyone else has either the original model or the Xbox One S, and all are in good working condition and kept up to date on updates.
Lastly, far be it from me to know how something like this really happens in lines of code, hardware/software errors, etc., as this isn't my forte in life...I just enjoy the byproduct of it 🙂. However, this repetitive crashing to a black screen seems vaguely similar to the Fallout 76 and Borderland 3 issues where the Xbox One would turn itself off to protect itself from overheating. I don't know what ended up being the fault on BL3's end (as that's still an ongoing issue when I join co-op games), but with Fallout it apparently was an issue of the game forcing your CPU/GPU to spool up to 100% temporarily when loading assets, even something as simple as your P.I.P.B.O.Y., and it would panic to save itself and shut down. This often was accompanied by an error message after saying basically, "I shut down so as not to damage myself due to overheating," which you would expect a machine to do in other cases of heat danger...but when my Xbox One crashes, it instantly reboots itself ~75% of the time (instead of, you know, staying off to cool down) and has yet to warn me about overheating. So, that would signify that either an overheat isn't being detected, the threshold isn't passed, an error is causing the message/protocol to not initiate, or it's an entirely different sort of SYS_ERROR or similar dump (kind of like a seizure).
Updating my status as of Caves & Caverns Pt. 1 update for Bedrock edition, Xbox One X console. I'm still having the crash where my system will freeze and then shut off completely, with a 50/50 chance that it starts itself back up immediately. (I haven't been able to tell if the auto-restart is part of the crash error or part of the connected devices, like a wireless controller or a headset, trying to reconnect and forcing the system to turn back on.)
As with before, turning my graphic settings to 1080p instead of 4k UHD has (anecdotally) prevented a crash every time I've tried it since 1.17 released.