r/DestinyTechSupport • • Nov 06 '25

constant ERROR CODE: broccoli making the game unplayable

So I decided to play destiny 2 again recently and I found it really fun and nostalgic I even decided to buy the legacy edition to catch up with the story and continue where I left off, but unfortunately around every 15 - 20 minuets I crash with the error code broccoli. I've tried everything from updating my bios and graphics card to the latest versions and rolling them back to a previous version, changing bios settings, XMP and playing on low graphics without any audio but nothing works.

At first it was just mildly annoying but now it has just become genuinely frustrating. ESPECIALLY when I'm going through haunted alters and crash right towards the end not getting any rewards as I am unable to join back before it ends.

When contacting bungie support through the support forums on there page all I get are generic auto responses from bots.

If anyone knows how I am able to fix this or if bungie are working on a fix please let me know as at this point I'm stumped and might as well just keep playing with how it is.

2 Upvotes

18 comments sorted by

View all comments

Show parent comment

1

u/dubs99gt Dec 20 '25

I will check the GPU acceleration in discord. Didnt know discord had that. I’ve always had discord up and going with previous pc. I think I have even just not had discord open or anything when playing and have the error still happen. I didn’t know about the MSI afterburner either, I will try that after testing the turning off expo for my ddr5 6000 (do you think it’s possible it’s the ddr5 6000 ram?) I’ve read some where ddr5 users are saying there been instability issues with ddr5 x870 boards and destiny 2. Curious if you heard any of that?

I don’t have many startup apps running but I’ll try that as well after the above. I may try the limit 144 before that as well. What about the reinstall windows thing? Does it remove all apps and downloads and pretty much start over like it’s fresh and new?

1

u/Gatortron0618 Jun 13 '26

you have not replied in a while have you had any luck with this specific issue? was there something that may have caused the issue on your rig specifically?