Okay, so, to preface this, I have done all of the following: [b]Reinstalled Destiny 2 on my console. Cleared my Xbox Cache Rebooted my router Hard reset my router. Tried my account on a completely different Xbox/Internet connection at a friend's house. Used other accounts on my own Xbox successfully and consistently.[/b] The following scenarios are happening consistently on this account (And this account alone): On attempting to log in, before/after character selection screen, the rotating class symbols in the bottom right corner freeze and the console hangs with a repeating singular thudding audio sound. If this does NOT occur, the following two scenarios will occur: I successfully load in to a character, I attempt to load in to a location: This leads to one of two scenarios' If I successfully load in, I can attempt to load in to an activity (I've specifically been using The Quarry Legendary lost sector to test this, however the same results have occurred in strikes.) 9 times out of 10, I will get a very long loading screen which results in Newt error code, sometimes this can not be cancelled out of (Can't press 'B' to close) and when I can, a persistent black screen once again occurs for several minutes until finally I recieve a 'WATERCRESS' error and I'm booted to the title screen. Attempting to relog after this almost always results in a crash. After much frustration and attempting everything I can to remedy this (Over the space of two days, issues having started at reset) with no result, I tried a different account. This account can consistently play without any issues whatsoever, no conflicts, no Newt, no Watercress, no crashes, no extra long load screens. Leading me to believe that the only thing this could be is an isolated account error, and part of me wonders if it's a stuck account flag failing to load/be removed correctly following on from Trials. I'm exceptionally frustrated with this problem, and any response from a developer would be sorely appreciated, as I've tried every reasonable solution possible, only to discover that the problem appears isolated to my account (Prince Aoi) and there's nothing I am able to do. Thanks for your time.