PC
PLATFORM: Steam
SYSTEM INFO:
CPU: AMD Ryzen 5 5600X
GPU: NVIDIA GeForce RTX 3080
RAM: 16 GB DDR4-3200
GPU Driver Version: 32.0.16.1742 [Released 09/30/2026]
OS Version: Windows 11 23H2 (OS Build 22631.7652)
ISP Provider/Speed: 150Mbps UP / 170 Mbps DOWN
Connection Type: LAN
DxDiag: https://pastebin.com/jRgS5tTd
ISSUE:
Destiny 2 throws Error Code BROCCOLI and crashes when I attempt to travel through the transition/loading zones around the Lost City landing zone inside the Pale Heart.
The error appears to be strongly correlated with traversal speed and rapid changes in movement direction while crossing zone boundaries. Sprinting, bunny-hopping, or otherwise moving quickly through affected transitions frequently triggers the crash, while walking slowly or pausing during the transition has allowed successful traversal. The crash most frequently occurs when transitioning from the Lost City to the Arbor of Light/Lost City Outskirts, and then next most frequently for Lost City-to-The Landing. Notable minority crashes include the Speaker's Chamber (also near the landing) and the The Landing-to-The Refraction loading zone.
Fast-travelling directly into the Landing (even if from the Lost City) does not appear to trigger the issue.
Normal gameplay, including extended sessions elsewhere in Destiny 2, does not appear to be affected.
REPRO STEPS:
Method 1: Speed
Launch Destiny 2
Select the Pale Heart.
Transmat to the Lost City landing zone.
Move towards The Landing or the Lost City outskirts at speed. Burst Glide b-hopping, other skating, or simply sprinting while Amplified count, and of course Sparrows.
Cross the transition point (where the Zone Title appears and then fades out)
ERROR OCCURS: game may freeze during or shortly after the transition and display Error Code BROCCOLI. Sound continues.
Method 2: Runback
Select the Pale Heart.
Transmat to any landing zone.
Move towards any other zone via the connected paths.
Cross the transition point (where the Zone Title appears and then fades out)
Immediately double back and return to your original zone.
ERROR OCCURS.
EXPECTED RESULT:
The player should be able to cross between adjacent loading zones at any normally supported movement speed, including sprinting and other movement abilities, without triggering a GPU timeout or terminating the game/ Rapidly reversing direction during a zone transition should likewise not cause the game to freeze or crash.
LINKS: N/A, sorry :(
NOTES:
During the bug Destiny 2's graphics freeze while the game audio/music continues. This includes NPC barks like Fallen chittering and such. The game subsequently displays Error Code BROCCOLI and exits to the desktop.
Windows itself remains responsive, and other desktop applications continue functioning normally. There is no accompanying system-wide black screen or reboot.
However, following the crash, Steam can remain stuck displaying "Stopping." Multiple Destiny-related processes, including destiny2.exe, the BattlEye launcher, and Bungie Error Handler, have remained active for me. Manually terminating destiny2.exe is required to complete shutdown/be able to relaunch the game through Steam.
Windows Reliability Monitor records a LiveKernelEvent, Code 141, corresponding to a GPU execution timeout. Windows Event Viewer also records an NVIDIA kernel-mode driver error (nvlddmkm, Event ID 153) at the time of the crash. These errors coincide with the observed Destiny 2 crashes in time, though of course I can't be sure.
The crashes are not correlated with total gameplay duration. They have occurred both shortly after launching Destiny 2, and after extended periods (6+ hrs) of otherwise normal gameplay.
No other Patrol Zone seems to have this issue since I tend to speed through them all and have not experienced this error in those zones.
-
Hi there, Thanks for reaching out! As you know, Error code: BROCCOLI signifies a problem with the detection of the player’s GPU. This often occurs due to a driver crash. To try and resolve this issue, players are advised to keep their Operating System and Graphic 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: [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 card, 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]