Hopefully we can get some attention on this, seems to be happening to quite a few people. Ever since Warmind came out we are getting consistent Broccoli errors. each time we get the error the Game hard locks, only way to back out is to CTRL ALT DELETE, task manager, end task. On the Desktop we get the error Broccoli. Can happen a couple times in a row, can happen after playing for a couple hours. Crashes in PVP matches, Patrol on IO, New Mars Strikes, Gauntlet Leviathan, Beginning jumping puzzle in EoW.
i7 8700k / EVGA 1080 TI SC2 / 16GB RAM / M.2 NVME SSD
Windows 10, 1803
These are the supposed fixes I have found and tried on here and reddit
-Setting card to Debug mode in nvidia control panel. (Still Crashes)
-Down Clocking GPU in Precision XOC. (Still Crashes)
-Rolled back to April Video Card Drivers. (Still Crashes)
-Fresh Install of Windows 10 1709, newest driver released on May 24th. (Still Crashes)
-Renamed PrecisionXServer.exe (Still Crashes)
-Set Frame Cap to 72fps. (Hasn't crashed yet) Need to do more testing but this is the last thing I have found to try.
All in all, looks like we might have yet another FPS issue... again
We had the FPS issue with colony, fix was reducing FPS to 72FPS
We Have the Trials going down the purple tunnel issue - Fix is reducing FPS to 72FPS
We had the Mercury Pub Event Man Cannon Issue. fix was reducing FPS
Hope one of these works for anyone that is experiencing this error.
-
Every time I enter this problem occurs after ten minutes of playing (can someone help me my video card is from amd)
-
I have the stupidest fix ever. I turned on Vsync and i can play without problems on 60 FPS ever since. I could potentially get way more fps, but it is capped by vsync. This sucks.
-
Изменено (Matryx): 8/21/2018 4:17:22 AMOnly Fix I know of for this is putting NVIDIA Drivers into Debug Mode! Helping Spread the word to fix this! I know its frustrating. https://www.evga.com/support/faq/afmviewfaq.aspx?faqid=59594 This declocks the OC to stock....GG Bungie you monkeys.... Happened since Warmind update apparently.
-
Изменено (Ryu): 6/4/2018 12:03:18 AMsame problem tried everything above even more like different drivers, scan game, delete cvar file (setting file), ingame graphic from low-high, fps limit 62 (haven't tried 72 but i will). I'm always playing with two friend they have no problems at all (exept this insane long loading screens). First install was on my HDD but the loading screens made me so angry that i moved it to my SSD and loading screens were a bit better. I think from that point my problem start but i'm not sure maybe we all have it on our SSD and the game doens't like to load so fast cuz of console shit or something idk xD Right now i reinstall it on my HDD maybe it works if not i try the 72fps and if it still crashes i'm out of ideas -.- And yes my system is up to date even the st00pid new w10 update that no one likes. EDIT: reinstall on HDD still crash, FPS limit on and FPS to 72 still crash... EDIT2: Fix for me was pretty simple another GPU because my old one had a problem with the fan. Infight with a Hunter (with Orpheus Rig much bling bling) my GPU was at 90C° and my brother found out that Destiny2 thinks that my GPU was 15C° higher because something i don't know anymore. So Destiny thought or told my PC that my GPU was at 105C°. I don't know if this is a fix for everyone but for me it was i played liked 12h today (with some breaks dw) and no crash yesterday no crash either. Maybe it will help some people to find there own fix.
-
I have also the same issues and same gaming rig as you do. I have gone through the same steps except setting the frame cap, which I will try next. Hopefully this shit gets fixed soon.
-
I had the same but I seem to have fixed the problem. Rolled back my EVGA XOC Precision to a version from January. Also I had it running via steam, uninstalled it and re-installed the standalone version and no crashes so far after a lot of testing!
-
Изменено (Desmond The Moonbear): 5/27/2018 12:54:14 PMDid you install the nvidia 397.93 driver? I believe this to be the issue as it's the only driver that I've changed since last playing without crashing. I reverted back to 397.64. Will be checking for stability Edit: After playing a bit, this seems to have fixed my issue
-
According to the Bungie.net help page: 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.
-
Also receiving Broccoli errors. This had started with the latest Destiny 2 update, I would play for 15-20 min get knocked out of the game with a Broccoli error. The only was I was able to fix it was by limiting framed to 72.