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
Commenti
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.
Accedi per aggiungere un commento.