TL;DR
To fix Error Code Broccoli in Destiny 2: This error indicates a GPU driver crash. The most effective fix is to disable any GPU overclocking using MSI Afterburner, or by enabling “Debug Mode” in the Nvidia Control Panel. Additionally, players should perform a clean installation of their graphics drivers, cap their in-game framerate, and verify their game files via Steam or Epic Games. Lowering graphical settings to prevent GPU overheating also resolves the issue.
If you’ve just been abruptly booted from a Grandmaster Nightfall or an intense Crucible match with a screen screaming “Error Code: Broccoli,” you are definitely not alone. It’s one of the most frustrating interruptions in Destiny 2, but don’t worry—it’s entirely fixable.
In this guide, we’re cutting through the tech jargon to give you the exact steps to fix Error Code Broccoli and get your Guardian back into the action.
Stay calm, Guardian. We’ve got the fix for the Broccoli crash.
What is Error Code Broccoli in Destiny 2?
According to Bungie’s official documentation, Error Code Broccoli means there has been an issue detecting the player’s GPU (Graphics Processing Unit). It usually points to a driver crash, a GPU overclocking instability, or a sudden timeout where your graphics card stops communicating with the game.
Why the Broccoli crash happens
Top 7 Proven Fixes for Error Code Broccoli
Run these in order. Most players are back in the game by step two or three, so there is no need to do all of them unless the crash is stubborn. Launch the game and play for a few minutes after each fix to see if it sticks.
1
Clean reinstall your GPU driver
This is the single most effective fix. Download the DDU tool (Display Driver Uninstaller), boot into Safe Mode, wipe your current driver completely, then install a fresh driver from NVIDIA or AMD. A clean wipe clears the corrupted files that a normal update leaves behind.
If the crash started after a recent update, install an older stable driver instead of the newest one. Many players report the broccoli code vanishes the moment they roll back.
2
Force DirectX 11
Destiny 2 can run on DirectX 12, but DX12 is where a lot of broccoli crashes live. Forcing the older DirectX 11 path is stable for most cards. On Steam, right click Destiny 2, open Properties, and in the launch options box add this line:
-force-d3d11
3
Disable fullscreen optimisations
Find the Destiny 2 application file, right click it, open Properties, then the Compatibility tab, and tick Disable fullscreen optimisations. This stops Windows from layering its own frame handling on top of the game, which can break the GPU link and throw broccoli.
4
Turn off every overlay
Discord, GeForce Experience, Steam, Xbox Game Bar and MSI Afterburner all inject overlays into the game. Any one of them can trip broccoli. Disable them one at a time, or all at once, and test. Overlays are the second biggest cause after drivers, so do not skip this.
5
Delete the corrupt graphics config
A damaged settings file can feed bad values straight to your GPU. Press the Windows key and R, type the path below, and open the Bungie folder. Find the cvars file and delete it. The game rebuilds it on next launch, so you will just need to set your graphics options again.
%appdata%
6
Clear the shader cache and verify files
Clear the DirectX and OpenGL shader cache from Disk Cleanup, then verify the game files through Steam or the Epic launcher. This rebuilds any shaders that compiled badly and replaces any game file that went missing, both of which can surface as broccoli.
7
Check temperatures, overclocks and hardware
If nothing above holds, look at the hardware. Reset any GPU or memory overclock to stock, including XMP or EXPO profiles on DDR5 kits, since unstable memory is a known broccoli trigger. Watch your GPU temperature during play, and if the card is old and the crashes spread to other games too, the card itself may be on the way out.
Error SP-POST-4003-1002 ZEE5 Fix: Quick Working Solutions for Mobile, TV and Web
Frequently asked questions
What does error code broccoli mean in Destiny 2?
It means Destiny 2 lost contact with your graphics card. Bungie treats this as a GPU detection failure, and the trigger is almost always a graphics driver that crashed, went stale or installed badly.
What is the fastest fix for the broccoli error?
Add the launch option -force-d3d11 in Steam to push the game onto DirectX 11, then disable Discord and GeForce overlays. That combination clears the crash for a large share of players in under five minutes.
My broccoli crash started after a driver update. What should I do?
Roll the driver back rather than updating forward. Use DDU to wipe the current driver, then install the last build that worked for you. Several recent NVIDIA releases set off a fresh round of broccoli crashes, and a rollback fixed it for most affected players.
Is error code broccoli caused by a bad graphics card?
Usually not. It is almost always a software or driver issue. Failing hardware is the least common cause. Suspect the card only if the crashes also hit other games, persist after a clean driver install, and you have already reset any overclock.
Does deleting the cvars file delete my progress?
No. The cvars file only stores your local graphics settings. Your characters and progress live on Bungie’s servers. Deleting it just resets your graphics options, which the game rebuilds on the next launch.
Does the broccoli error happen on console?
Broccoli is a PC error tied to graphics drivers, so it shows up on PC. Console players get different Bungie codes for crashes. The driver and overlay fixes here apply to PC players on Steam, Epic and the Microsoft Store.
The short version
Error code broccoli is a graphics card crash, and the cause is nearly always your driver. Start with a clean driver reinstall, force DirectX 11, and switch off your overlays. That trio fixes it for most people. If the crash held on through a recent driver update, roll back instead of pushing forward, then work down to the config and hardware checks only if you have to.
Once the GPU link is stable, broccoli stays gone. Save this checklist, because the next driver wave tends to bring it back, and now you know exactly where to start.
Did this guide save your flawless run? Drop a comment below and let us know which fix worked for you!
Pingback: Easy Fix for Gemini Error 1099 | "Something went wrong (1099)" - Seminarsonly.com