Hello, I was hoping someone could help me regarding this error code i started receiving yesterday evening: Error Code Broccoli
Everything was working Monday night when i was playing and after reset last night the game will crash either at the loading screen, if not when i click on a destination in the game. I received a Windows pop up stating "Graphics runtime detected a crash or loss of device. For more information, visit help.bungie.net and search for error code: broccoli"
After look into this from Bungie's forums, it states "BROCCOLI errors indicate there has been an issue detecting the player's GPU and are commonly caused by a driver crash.
To attempt to mitigate this error, players should always ensure that their Operating System and Graphic Drivers are up-to-date with the latest version."
These are some of the things I've tried from other players who have experienced the same event. However, the majority of these events are from 2018 so I'm unsure where to go next.
1. Ensured OS & Drivers were up to date.
2. NVIDIA control panel debug mode
3. Checked integrity of the Destiny 2 files on Steam
4. Uninstalled and reinstalled Steam
I've tried other games on my Steam account and they all work, please help.
-
3 RepliesHi. Thanks for your report. You may want to review our [url=https://www.bungie.net/en/Help/Article/46853]BROCCOLI[/url] article for more information about this issue. If that doesn't help, here are a few suggestions some players have found to resolve this issue: [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 cards, 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]