Destiny 2 PC Issues: Crashes/Freezes/Plum Error After Reinstall & PC Reset
Platform: Steam (PC)
OS: Windows (fresh reset)
Initial Issue (pre-reset): After fresh Destiny 2 reinstall:
Launches fine initially.
Crashes out during 2nd mission or shortly after.
Won't relaunch properly via Steam (hangs/closes improperly).
After PC restart: Freezes at Character Select screen (characters don't load, "Destiny unresponsive").
Post PC Reset + Reinstall:
Plum Error (BattlEye anti-cheat flag).
BattleEye Launcher hangs ("BattleEye starting..." stuck indefinitely in Steam).
Finally launches to Clan screen / Orbit Welcome ("Welcome to Destiny 2! Press Enter to open text chat"), but completely frozen – no inputs work (Enter, ESC, mouse/keyboard unresponsive). ALT+TAB/ALT+ENTER sometimes fails.
Ongoing: BEService.exe can't be stopped (Error 1061 in services.msc/CMD: "The service cannot accept control messages at this time"). Only 1 drive available (can't relocate install).
Everything I've Tried (in order, multiple PC restarts/Steam verifies after each):
CategorySteps TriedInstall/Files- Full Destiny 2 reinstall via Steam.
- Verified integrity of game files (multiple times).
- PC full reset (Windows reinstall) + fresh D2 install.BattleEye- uninstall_battleye.bat as Admin (D2 folder).
- Deleted BattlEye folders (D2 + C:\Program Files (x86)\Common Files\BattlEye).
- CMD Admin: taskkill /f BEService.exe etc. + sc stop/delete BEService (Error 1061).
- Manual BEService start in services.msc (failed).Cache/Shaders- Deleted %localappdata%\DestinyPC (didn't exist post-reset).
- Deleted %appdata%\Bungie\DestinyPC\prefs\cvars.xml.
- Steam shadercache (1085660 folder).
- %temp% cleared.Overlays/Input- Steam Overlay OFF.
- Steam Input disabled.
- Discord/NVIDIA GeForce/Xbox Game Bar/Afterburner overlays OFF.
- Launch as Admin (Steam + D2).Graphics/Drivers- GPU drivers clean reinstalled (DDU in Safe Mode, latest Studio Driver).
- Launch options: -d3d11 -nohwc -windowed -USEALLAVAILABLECORES (tested variants).System- Windows Defender real-time OFF + exclusions (D2/BattlEye folders).
- Firewall allow (D2.exe/BEService.exe).
- Visual C++ 2015-2022 (x64/x86) reinstalled.
- DirectX End-User Runtime.
- Pagefile expanded (16-32GB).
- Controller disconnected.Other- DIM checked ornaments/items (ruled out MIDA/Marathon).
- Event Viewer checked (Destiny2.exe errors noted).
No bans/cheats – fresh PC, no VPN/remote tools. Game launches to frozen chat screen now, but unplayable. Need help getting stable launch past Orbit!
[Attach: DxDiag.txt, MSInfo32.nfo, Screenshots of Plum/Steam hang/Chat freeze, Event Viewer errors]
Thanks! 🚀
-
3 Replies**Update – February 07, 2026** Hey, quick update on my ongoing issues (Plum / Character Select freeze / occasional Marmot after verify/restart). Since my last post: - I managed to launch the game **once successfully** and played for a short time (reached in-game, no immediate crash). - After restarting the game (to test stability), it went back to **Error Code PLUM** (BattlEye query timeout) or freeze at Character Select screen (characters don't load, game unresponsive). - Verified files again → completed, but Plum returned right after. - Deleted %temp%\Destiny 2 folders (the main cache thing) multiple times – no DestinyPC folder ever appears in %localappdata% (which seems normal if it never fully loads). - Tried setting BEService to "Automatic" in services.msc and sc config BEService start=auto. - Disabled all non-Microsoft services / autostart items in msconfig (including other launchers like EA/Ubisoft/Epic). - Ran DISM /Online /Cleanup-Image /RestoreHealth + sfc /scannow again. - Switched launch options around (-d3d11 -windowed -safe etc.). - Headset/external USB disconnected during tests. - GPU drivers clean reinstalled (DDU in Safe Mode) → latest Studio Driver. - No change – still loops between Plum after restart/verify and freeze at char select. **No DxDiag/MSInfo32** – PC crashed/hard froze when trying to save DxDiag (happened twice, even in Safe Mode attempt). The fact that it **worked once** (briefly playable) gives hope it's not hardware/Ban related, but something with persistence after restart (BE service? Steam config? Cache not building?). Planning next: Try Epic Games version to rule out Steam completely (will report back). Any ideas on why it works once then dies on restart/verify? Or specific Event Viewer codes to look for (I see Destiny2.exe errors but no clear pattern yet)? Thanks for any new suggestions!