This is going to sound crazy, but I'm almost certain that I have a consistent and reliable fix for my frequent broccoli errors (driver timeouts): [b]Run "Heaven Benchmark 4.0" before starting up Destiny[/b] Crazy, right? But roughly 95% of the time that I start up Destiny I will have a crash within 15 minutes. Running Heaven first has fixed the issue 100% of the time for me. I doubt this is specifically about Heaven Benchmark, but is probably more about how another engine initializes the AMD or DirectX drivers. Every single time that I start Windows now, I run Heaven Benchmark as the very first thing I do and I will then have absolutely no problem with Destiny after that. This fix has been for about 2 weeks now. Meanwhile, I have had ongoing broccoli issues for about 5 months. My setup: i9-9900K. No CPU overclocking. 32GB @ 3200Mhz AMD Sapphire RX 5500 XT 8GB Windows 11 144mhz ultrawide 3440x1440 I am actually running the GPU overclocked at the moment with a 10% max frequency boost. No under-volting, no VRAM tuning (~1786 Mhz). Junction temp does sometimes hang out at around 70C, but that seems fine. GPU stays at 99-100% utilization for game activities. I get an average of 78 fps on a 3440x1440 ultrawide with a 90% render resolution. vsync off. Freesync on. No frame cap. Medium quality. Radeon chill on (75/140) I typically quit Heaven after about 5 seconds of running it and then launch Destiny. If I start up Windows and do not run Heaven, I am almost guaranteed to get a crash within 15 minutes. As another test, I didn't run Heaven this morning and dropped into the Throne World patrol, killed about 4 ads and then it crashed. More often the crash will happen by the second public event. Court of Thorns and Dares of Eternity were always almost guaranteed to crash shortly after starting. My troubles might easily be attributed to a slightly overwhelmed GPU (because of the ultrawide), but this fix seems to solve the issue. I've tried so many different things over the past 5 months and nothing was 100% reliable. I've switched back to Windows 10. Tried countless AMD driver versions. Disabled my RAM XMP profile. Disabled my second display. Reduced display resolution to 1920x1080. Disable Steam overlay. Full uninstall of drivers. Driver only installs of AMD Adrenaline. Empty render caches. Resizable BAR on & off. Too many things to list them all. If anyone from Bungie is tracking broccoli errors on 5000 series GPUs, or if anyone has this problem, this seems to be a strange but reliable fix and maybe a clue to that cause of these errors.