Hello. You may want to review our [url=https://www.bungie.net/en/Help/Article/46853]BROCCOLI[/url] article for more information about this issue.
If that doesn't help, here are a few suggestions some players have found to resolve this issue:
[quote][b]1[/b]. Enable "Game Mode" in Windows 10 or, if you already have "Game Mode" enabled, try disabling it.
[b]2[/b]. If you use EVGA Precision for overclocking, you may want to disable that since it doesn't play well with Destiny 2. MSI Afterburner might be a good alternative to use.
[b]3[/b]. In your Settings, cap your framerate to keep GPU usage below 90% to see if this helps.
[b]4[/b]. If you have an NVIDIA graphics cards, see if the card stabilizes using [url=https://www.evga.com/support/faq/afmviewfaq.aspx?faqid=59594]NVIDIA's temporary debug mode[/url].
[b]5[/b]. Some players have reported that a mild underclock for GPU clock of around -100MHz and GPU memory around -50MHzz may help with this issue.[/quote]
None of the following helped. and since your article about broccoli error code only suggests to keep the drivers and systems update its not really helpfull. It seems more like a crucial either gpu or cpu error that is caused by something happening while the map is about to be loaded cuz it happens everytime in the same exact way. It would be helpful for your team to actually check that bug cuz it renders the game literally unplayable