JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Trick Nor Treat: 8/29/2021 2:00:26 PM
0

At Wit's End

When I started playing Destiny 2 on my new Xbox Series X late last season, I would occasionally get a Marionberry error during startup of game as soon as I would 'Press A To Play'. Quitting game and restarting game would eventually overcome error. Since start of this season, Marionberry occurs everytime I start game and quit/restart no longer overcomes error. Sometimes, either a restart of Xbox or router will get me past the error. No other game on this Xbox has network issues; console passes all network tests in Settings; and Destiny 2 experiences no issues on my Xbox One X. Console is hard wired to network. What I've tried thus far: 1. Powered down console and all network devices, then powered up one at a time starting with modem, then router, then switches, and finally the console. 2. Turned off UPnP, forwarded all ports used by Xbox. 3. Uninstalled Destiny 2 and re-installed. As of now, the only way to get into the game is to restart console and/or router 1 or more times. Once I get into game, I can quit and restart game without error, but once I turn off Xbox (Instant On), the error returns next time I try to start game. I'm at wit's end as to what else to try. I've played Destiny for thousands of hours since 2015. This is so annoying that I now have to spend 15-20 minutes restarting equipment whenever I want to play.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon