Bungie Answered
Error Code Broccoli crashing on Dire Marsh Only
Disclaimer: My Windows 11 install and graphics drivers are ALWAYS updated to the most recent version (AMD Windows Driver Version
32.0.23027.2005). Rolling back the drivers to each of the three previous versions does not reduce the frequency of crashes. I have verified that the game is using the discrete graphics card.
Crashes are happening on the Dire Marsh map only, sometimes as quickly as 30 seconds into a round. GPU is an AMD Radeon 7900 XTX. Relaunching and reinstalling the game does not reduce the frequency of crashes.
0
Comments
Hi there,
Thanks for reaching out. I understand you're encountering the error code BROCCOLI. I'm sorry to hear of this, as I can imagine the impact this may have had.
Thanks for confirming you’re on a 7900 XTX with up-to-date drivers and that you’ve already tried rolling back your driver. Since this is only happening on Dire Marsh, please try the following:
Turn off overlays and extras
Try a different graphics API / settings profile
Check for any overclocking / undervolting
Verify game files and Windows integrity
sfc /scannowTry a different resolution and refresh combo
Update: Disabling Steam, Discord, and AMD overlays (I am not aware of any others that would be running) allowed me to run 5 games on Dire Marsh in one session. Upon starting another session the next day, I crashed again at about 22:00 into the round.
I do not have an option to switch graphics APIs.
Fullscreen is enabled and V-Sync is already disabled. I will attempt to play with all settings on Low.
Update: This is, without a doubt, related to Lockdowns. 10 matches in a row, triggering Lockdowns or being in a match where a Lockdown was triggered has caused a broccoli crash within 60 seconds. Reloading into the match does not "clear" this, and I can expect to crash again within 60-90 seconds even if no further Lockdowns are triggered.
Physically reseating my GPU has not affected the issue. Crashes still happening when Lockdowns are triggered.
Hi there,
Thank you for the additional details.
There are two more small things you can test on the AMD side:
In AMD Adrenalin, temporarily turn off any “extra” features while testing Dire Marsh (Lockdowns in particular):
Radeon Anti-Lag / Anti-Lag+
Radeon Chill
Radeon Boost
Enhanced Sync
Any per-game tuning profile for Marathon (set it back to default for now)
Make sure there’s no active overclock or undervolt, even mild “automatic” ones. Run the card at completely stock settings while testing Lockdowns.
If the game is still consistently crashing on Dire Marsh during Lockdowns after that, please reply with:
Your PC Launcher
Your region/time zone
The approximate local date & time of your most recent BROCCOLI crash on Dire Marsh
Whether a Lockdown had just started or was active, and what you were doing at that moment (fighting enemies in the zone, just entered it, etc.)
All of these AMD extras have been turned off the entire time. Card has been on stock voltage and power settings since the initial testing round.
Launcher: Steam
Region: US East/CST (UTC-5:00)
Most recent crash: 16:41:47 CST (+/- 30 seconds). Lockdown was NOT active, I had just loaded in to a new game of Dire Marsh (Sponsored) and was walking across the skybridge west of Intersection. No enemies were active.
Additional Broccoli crash in that same (reconnected) match at 16:48:45 (+/- 30 seconds). Lockdown not active, I had just deactivated my Thief X-Ray visor in Maintenance after killing a squad. No enemies active.
New game: Crashed at around 19:09:55 immediately upon activating Thief grapple next to the Anomaly. No lockdown active, no enemies alerted. Link to crash screenshot:https://media.discordapp.net/attachments/439065704184938496/1494097310299459795/image.png?ex=69e15e0d&is=69e00c8d&hm=b0367b83754fe8a4140f951197527a5c46378ec8475845f886b4e7b2a3014798&=&format=webp&quality=lossless&width=1601&height=902
Reconnected and crashed again at 19:12:15 while placing an ammo crate at Bio-Research. Both players and UESC were firing weapons at the time. Link to crash screenshot: https://media.discordapp.net/attachments/439065704184938496/1494098249408319538/image.png?ex=69e15eed&is=69e00d6d&hm=abc69519d1f80aeac8ee7c5f26f9a1243c556716f85d607994bb7c0936266071&=&format=webp&quality=lossless&width=1604&height=902
Hi there,
Both of those screenshots are inaccessible.
Could you re-upload them to a free image hosting site such as imgur and post the link here?
Photos can be viewed at https://imgur.com/a/MCeVOIv
Hi there,
Could you provide us with a copy of your DxDiag so that we can take a deeper look as to why this is still happening? You can copy and paste it over one PasteBin and provide us with the link.
If you don't know how to get your DxDiag, please follow these steps:
• Press (Windows Key + R) to bring up the Run dialog box, enter this command “dxdiag” without quotation marks.
• Click on “Save all information”.
• Copy the text and use PasteBin.com to paste the information. Please don't use Google Drive or Dropbox.
• Create a link and post it in this thread.
DxDiag paste visible at: https://pastebin.com/RkqGGD0u
Four Dire Marsh games successfully completed today (on the standard playlist), each 20+ minutes. A Lockdown was triggered in one but it was far away (Greenhouse, while my team spent the whole game at Maintenance.)
Hi there,
Thanks for the DxDiag.
From what we can see, the BROCCOLI errors in Dire Marsh look like your graphics card driver is briefly crashing under load and then recovering, which shows up in-game as this error.
To try to stabilize things, please run through these steps in order:
Turn off overlays and Windows HAGS
In Windows, go to Settings → System → Display → Graphics → Default graphics settings and turn Hardware-accelerated GPU scheduling Off, then restart your PC.
While testing, please fully disable:
Steam overlay
Discord overlay
AMD Adrenalin overlay / ReLive / Instant Replay / performance overlay
Xbox Game Bar (Settings → Gaming → Xbox Game Bar → Off)
Clean reinstall your AMD graphics driver
Download the latest WHQL “Recommended” driver for your RX 7900 XTX from AMD’s website (avoid “Optional”/beta drivers).
Uninstall your current AMD driver from Apps & features (or use the AMD Cleanup Utility if you’re comfortable with that).
Reboot, then install the freshly downloaded WHQL driver and leave all GPU settings at their defaults (no undervolt/overclock/Anti-Lag+ profiles, etc.).
Lower GPU load in Marathon (just for testing)
In the video settings, set the overall preset to Low, apply, and restart the game once.
Cap your frame rate (for example to 120 FPS) instead of running fully uncapped.
Make sure V-Sync is Off and set shadows / volumetrics / post-processing to Low or Medium.
(Optional) Slightly reduce GPU power in Adrenalin If you’re comfortable using AMD Adrenalin:
Open Performance → Tuning, enable advanced controls, and set a small power limit of about -10% or reduce the max GPU frequency by 5–10%.
Do not apply any manual undervolt; just a small power/frequency reduction to help stability.
Simplify your display setup
Temporarily unplug any second monitor and play only on your main screen.
Turn HDR Off in both Windows and the game while testing.
Test and report back details if it still happens
After doing the above, please run one longer session in Dire Marsh (20–30 minutes).
If you still get a BROCCOLI error there:
Note the exact local time when it happened.
Steps 1-3 and 5 completed.
Entered a Dire Marsh (Sponsored) game and completed all 3 levels of Lockdown and exfiltrated successfully after 24 minutes. Will attempt a few more.
Four consecutive completed Lockdowns successfully, all 20+ minute matches. Will now try enabling my second monitor.
A few days of stable performance on all settings low with second monitor disabled. Then a crash just now 12:47:47 P.M. CST. No lockdown, was looking at Anomaly effects from Quarantine roof.
Please sign in to leave a comment.