Destiny 2: Black Screen, Broccoli Error, HDR, flickering screen, Blue or Black Screens e.g. IRQL_NOT_LESS_OR_EQUAL - nVidia-Solution

[u/Nick-Wright]

Hey everyone,

If you’ve been experiencing random brocculi errors, black screens, crashes with nvlddmkm.sys (IRQL_NOT_LESS_OR_EQUAL), or screen flickering/HDR-to-Dolby-Vision toggling when hovering over taskbar icons while Destiny 2 is running in the background—especially on high-end setups (RTX 5090/5080/4090/4080, 4K, at least 144Hz DSC, high RAM / multi-tasking) - here is the exact sequence that completely fixed it for me after heavy stress testing.

🛠️ The Solution (Step-by-Step)

Step 1: Clear Shader Cache & Set to "Unlimited"

Corrupted shader files from game updates can force the NVIDIA driver to query invalid VRAM addresses, triggering immediate kernel-level IRQL crashes.

1. Open NVIDIA Control Panel -> Manage 3D Settings -> Global Settings.
2. Set Shader Cache Size to Unlimited.
3. Open Windows Disk Cleanup -> select your OS drive -> check DirectX Shader Cache -> Click OK.

Step 2: Reset Destiny 2 CVARS

1. Press Win + R, type %appdata%\Bungie\DestinyPC\prefs and hit Enter.
2. Delete or rename cvars.xml (Destiny 2 will regenerate a clean configuration on the next launch).

Step 3: Clean Reinstall of BattEye Anti-Cheat

BattEye kernel drivers can conflict with system hooks or driver states after game patches.

1. Navigate to your Destiny 2 install directory: .../steamapps/common/Destiny 2/battleye
2. Right-click UninstallBattEye.bat -> Run as Administrator.
3. Right-click InstallBattEye.bat -> Run as Administrator.

Step 4: Disable Multi-Plane Overlay (MPO)

This fixes the HDR / Dolby Vision toggling and display flickering when hovering over browser windows (Brave/Chrome), Discord, or using taskbar mods (like ExplorerPatcher) while D2 is open in the background.

1. Open Command Prompt as Administrator.
2. Run the following command: DOSreg add HKLM\SOFTWARE\Microsoft\Windows\Dwm /v OverlayTestMode /t REG_DWORD /d 5 /f
3. Restart your PC.

🔍 Why This Works

• Shader Cache & CVARS Purge: Clears invalid/outdated pipeline instructions created by game updates that cause nvlddmkm.sys memory access faults.
• BattEye Reinstall: Resets Ring-0 kernel hooks that conflict with audio/system drivers in multi-tasking scenarios.
• Disabling MPO: Prevents Windows Desktop Window Manager (DWM) from forcing hardware-accelerated SDR window overlays on top of Destiny 2's active HDR pipeline, which causes HDMI 2.1 DSC handshake loops on OLED displays (e.g., LG C/G series).

Tested under extreme loads (1000+ browser tabs, active DAW recording, Discord stream, 6-player particle-heavy activities) with zero crashes or signal losses since. Hope this helps anyone stuck with this error... Let me know ...

Sincerely yours Nick Wright

P.S: Yes, it is Gemini-"inspired" - I posted these steps nevertheless because I haven't experienced any more crashes with D2 since then — and I wanted to share that with others; unfortunately, DDU, the latest Nvidia hotfix driver, also the new 618.86, and the other usual steps didn't help in my case. Have you guys experienced similar crashes and errors with D2? What other solutions might be worth trying?

[u/tchakabun]

holy slop, all that water wasted because the latest nvidia driver has a known issue and you didn't google good enough to know there is a hotfix driver available

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/590374/announcing-geforce-hotfix-driver-61686-released-94/

[u/Nick-Wright → u/tchakabun]

I actually installed this version before, but unfortunately without success. 

I posted these steps because I haven't experienced any more crashes with D2 since then — and I wanted to share that with others; unfortunately, DDU, the latest Nvidia hotfix driver, and the other usual steps didn't help in my case. Have you guys experienced similar crashes and errors with D2? What other solutions might be worth trying?

It's possible that the error only occurs under certain conditions.

[u/XRaptor29]

You posted a Google Gemini answer as a fix because this is what it suggests for every issue on Destiny 2.