{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by fr00tl00picus:
6/20/2026 3:47:01 AM
1
Repeated Error Code: Broccoli and Graphics Driver Timeout
I am experiencing repeated error code Broccoli or GPU driver timeout issues when attempting to play Destiny 2 on PC. The crashes are frequent but inconsistent in timing. I have been able to play for upwards of 2 hours without crashes, most frequently I can barely get past 3 minutes without crashing.
I have tried the following troubleshooting steps to no avail:
- Clean driver install in safe mode using DDU program
- Driver rollback to an earlier version
- Disable Anti-Lag, Radeon Boost, and AMD Fluid Motion Frames
- Disabled unnecessary startup applications
My system specifications:
OS: Windows 11 Pro
CPU: Intel i5-9600KF
GPU: AMD Radeon RX 7600
Drivers tested: AMD Adrenalin 26.6.1 and 25.30.1
I have checked other forum posts and found another user who has been experiencing the same issue since before the Monument of Triumph update was released [url=https://www.bungie.net/en/Forums/Post/265263772?sort=0&page=0]but no fix or update to the post was provided[/url].
The game is literally unplayable in an appreciable capacity right now because of these issues. Please help.
First edit: Continuing troubleshooting methods I've seen suggested elsewhere, I have performed a mild underclock of approximately 100MHz for GPU clock speed and 50MHz for GPU memory but this has not fixed the crashing. Additionally, I also attempted to lower my graphical settings in game and capped my framerates, but neither of these had any effect. Lastly, I have tested the game with Windows 11 "Game Mode" enabled and disabled and the crashing persists regardless.
Second edit: The game is functionally unplayable for me with this issue. Any kind of assistance or acknowledgement of the issue would be greatly appreciated.
-
1 ReplyHello there, Thanks for the detailed report. Broccoli is a graphics-runtime / GPU device-loss crash, so this does sound worth a closer look. We have seen internal Broccoli cases before where the crashes were inconsistent, hard to reproduce, and not tied to one single cause. In those cases, the issue could show up across AMD, NVIDIA, and Intel hardware, and the most useful next step was getting crash data and narrowing down any common pattern. Since you already tried the common driver and settings steps, the most helpful details now would be: whether this only happens in Destiny 2 or if any other DX12 games are also crashing whether the crash happens in a specific activity, destination, or menu, or stays completely random whether the crash folder is being generated in your local temp/appdata path after the crash whether Windows Reliability Monitor shows a faulting module when Event Viewer does not a DxDiag whether fullscreen, borderless, or windowed mode changes the crash frequency If you can provide a DxDiag, the crash folder, and any Reliability Monitor faulting-module info, that would help determine whether this is a broader driver/device-loss issue or something more specific to your current Destiny 2 setup.
