{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
3/31/2026 8:35:39 AM
1
Full system crash - D2 game launch - Focusrite Scarlett 18i22 on
Hey u all!
[b]For some reason, from one day to the other, my whole pc system crashes down when I launch the game while my audio interface Focusrite Scarlett 18i22 is being used for audio. I'm talking total computer shutdown followed by immediate reboot. [/b]
I run D2 via Steam, so I press on "PLAY", a few seconds pass and then I'm being welcomed by the above mentioned shutdown & reboot.
The game and my computer have been running without problems, no crashes whatsoever, within the last months. And as I said, without any changes to the system, from one day to the other, this problem started to occur.
Only thing I recall doing is updating the software that comes along with the interface.
[b]The shutdown ONLY happens with THIS game, so Destiny 2. It does not happen when running Guild Wars 2 for example. [/b]
Also no other problems whatsoever using the interface for its actual purpose, like recording in Cubase.
[b]Destiny 2 runs perfectly fine as long as the interface is turned off. [/b]
I'm grateful for any new ideas to try.
Since it seems to be a game related problem, I haven't really thought of reinstalling anything except for checking the game files of D2 via Steam.
HELP!
-
Hello there, Thank you for reporting this issue. BattleEye plus Focusrite Scarlett could be the issue Try these steps to see if it can help: 1. Update or roll back the Focusrite driver Go to Focusrite’s website → Downloads → Scarlett 18i22 → grab the latest driver + firmware for your OS. Install, reboot, test Destiny 2. If the problem started right after you updated Focusrite: Uninstall all Focusrite software: Settings → Apps → remove Focusrite Control / Focusrite USB driver. Reboot. Plug the 18i22 back in and let Windows install its default USB audio driver. Test Destiny 2 again. This forces Windows to use its native driver, which typically doesn’t trigger BattlEye issues. 2. Disable the Focusrite MIDI driver (keep audio) Reports show the MIDI driver is the part BattlEye really dislikes; disabling just that lets the audio side work. Open Device Manager. Expand Sound, video and game controllers and Audio inputs and outputs. Right-click any Focusrite MIDI or similar MIDI device entries → Disable device. Reboot and try launching Destiny 2 with the 18i22 on. If that alone doesn’t help, some users fix it by disabling the Focusrite MIDI driver service via command line, which completely turns off MIDI for the 18i22 but leaves audio working; Focusrite and community threads walk through the exact commands. (Search for “Focusrite Scarlett BattlEye MIDI BSOD” for step-by-step instructions.) 3. Use a different default output just for Destiny 2 If you don’t want to touch drivers yet: Right-click the speaker icon → Sound settings. Set Output to your motherboard/headphone output (Realtek, etc.). In Focusrite Control, make sure the 18i22 isn’t the Windows default playback device. Launch Destiny 2. Once in game, you can try switching back to the Scarlett in Windows if it doesn’t crash.
