JavaScript is required to use Bungie.net

Help - Destiny 2

Help us help you.
8/24/2026 7:10:52 PM
0

BROCCOLI & MARMOT Troubleshooting Report

Hi, I have been troubleshooting recurring BROCCOLI crashes in Destiny 2 for quite some time and have documented the entire investigation in the PDF linked above. I initially also experienced MARMOT, but in my case that issue was completely resolved after disabling BitLocker and fully decrypting the affected drives. BROCCOLI, however, continued independently of MARMOT. Before concluding that this was defective hardware, I tried to rule out as much as reasonably possible. Destiny 2 was completely reinstalled three times, repaired/verified through Steam multiple times, and even installed on a different physical drive. I also performed a complete NVIDIA driver cleanup using DDU in Safe Mode followed by a clean driver installation. The RTX 4070 Ti was subsequently tested with the 3DMark Steel Nomad DX12 Stress Test for 20 consecutive runs and passed with 99.0% frame-rate stability, without artifacts, driver resets or crashes. Windows also showed no corresponding WHEA, PCIe or nvlddmkm hardware errors during the investigated Destiny crashes. The most interesting part is the Destiny crash data itself. One minidump contains Destiny's own halt message: “Graphics: device lost or removed. (GPU Device Status:'timeout')” A separate Destiny crash produced a 0xc0000005 INVALID_POINTER_READ / NULL pointer read directly inside destiny2.exe. I am not claiming that these findings definitively prove a Destiny 2 software bug. However, after the troubleshooting documented in the report, I currently have no convincing evidence of a defective GPU, SSD, RAM, PCIe connection or motherboard that would explain why this problem occurs specifically in Destiny 2. The PDF contains the complete troubleshooting summary, system information, storage and memory checks, driver testing and the relevant WinDbg findings. I would particularly appreciate feedback from Bungie on whether BROCCOLI / GPU Device Status “timeout” is currently a known issue or whether the crash data points to something Bungie can identify internally. I still have the original Destiny crash folders and minidumps available and can provide them if they would be useful for further investigation. Thanks for taking the time to look into this.
English
#Help #gameplay

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon