Broccoli error happening over and over

jairusgg

March 29, 2026 00:02

Since the launching of the game, I have been experiencing Broccoli error in almost every raid, even in the loading screen or in the menu. Sometimes 2 or 3 errors in the same raid. It's making the game almost unplayable.

I have tried updating drivers, rolling back drivers, disabling overlays and switching game settings, but nothing seems to work.
This is my hardware:
- CPU: AMD Ryzen 7 7800X3D
- GPU: ZOTAC GAMING GeForce RTX 5080
- MB: ASUS PRIME B650-PLUS WIFI
- RAM: Corsair Vengeance DDR5 6000MHz 32GB 2x16GB CL30
- Monitor: ASUS ROG Strix OLED XG27AQDMG 26.5"

Please help me, I am really enjoying the game but this error makes me die 50% of the games and it's unplayable.

Comments

2 comments

Official comment

Bungie Support
Marathon Support

March 29, 2026 15:25

Hi there,

Error code: BROCCOLI signifies a problem with the detection of the player’s GPU, often due to a driver crash.

To try and resolve this issue, players are advised to keep their Windows version and GPU drivers updated to the most recent version.

If you haven't already, we recommend that you update your graphics card drivers directly from the manufacturer’s website. This will ensure you have the most up-to-date drivers and can help resolve these types of issues.

You may want to try the following steps as well:

1. Enable "Game Mode" in Windows 10 or, if you already have "Game Mode" enabled, try disabling it.
2. If you use EVGA Precision for overclocking, you may want to disable that. MSI Afterburner might be a good alternative to use.
3. In your Settings, cap your framerate to keep GPU usage below 90% to see if this helps.
4. If you have an NVIDIA graphics card, see if the card stabilizes using NVIDIA's temporary debug mode.
5. Some players have reported that a mild underclock for GPU clock of around -100MHz and GPU memory around -50MHzz may help with this issue.
PsychoIan

March 29, 2026 02:40

Same problem.
My hardware is:
7950x3d
5090
And I've checked Windows' log, it's a typical NVIDIA problem “nvlddmkm id 153”.

0

Please sign in to leave a comment.