JavaScript is required to use Bungie.net

Alerte du service
Destiny 2 sera temporairement mis hors ligne demain pour une maintenance programmée. Cliquez ici pour consulter le statut du serveur Destiny et les mises à jour.

Forums

publié à l'origine sous : Constant Marmot Issues
10/27/2025 1:58:17 PM
3
Hi there, Some users were able to resolve this issue by configuring their audio settings in windows. Please try the following steps: [quote]- Go to Windows > Settings > App Volume and Device Preferences - Verify that Steam is set to default - Launch Destiny 2 - Return to App Volume and Device Preferences - Set Destiny to default - Force close Destiny 2 using task manager[/quote] If you're still getting stuck on the same screen after trying this out, please let us know.
English

Langue du message :

 

Modifier
Prévisualiser

Jouez selon les règles. Prenez une minute pour lire notre Code de conduite avant d'envoyer le message. Annuler Modifier Créer l'escouade Publier

  • I think I resolved the issue, It appears to have been caused by Steam Controller input settings.

    Langue du message :

     

    Modifier
    Prévisualiser

    Jouez selon les règles. Prenez une minute pour lire notre Code de conduite avant d'envoyer le message. Annuler Modifier Créer l'escouade Publier

  • Thanks for letting us know. We'll keep note of that for future players who may encounter this issue. If you run into any further problems, please don't hesitate to open a new thread!

    Langue du message :

     

    Modifier
    Prévisualiser

    Jouez selon les règles. Prenez une minute pour lire notre Code de conduite avant d'envoyer le message. Annuler Modifier Créer l'escouade Publier

  • Modifié par Skoly : 10/28/2025 6:53:21 PM
    Thank you for the guidance regarding the Windows audio settings and Discord overlay. I followed your instructions: ✓ Configured audio settings in Windows App Volume and Device Preferences ✓ Set Steam to default/VB-Audio device ✓ Set Destiny 2 to default/VB-Audio device ✓ Disabled Discord overlay ✓ Force closed Destiny 2 after testing The solution worked initially and the game was able to load to the character selection screen successfully. However, the crashes have now returned. CURRENT STATUS: ---------------- - Crashes have resumed and are occurring frequently - Most recent crashes (October 28, 2025): * 11:25 AM - Application hang at character selection * 11:13 AM - Application hang at character selection * 11:08 AM - Application hang at character selection - Same error pattern: Game hangs/freezes at character selection screen - Requires Task Manager to force-close - Event ID: 1002 - "Application stopped responding to Windows" MOST RECENT CRASH TIMES FOR TELEMETRY: -------------------------------------- Date/Time: 10/28/2025 11:25:43 - destiny2.exe version 41270.0.0.0 Date/Time: 10/28/2025 11:13:31 - destiny2.exe version 41270.0.0.0 Date/Time: 10/28/2025 11:08:13 - destiny2.exe version 41270.0.0.0 Date/Time: 10/27/2025 20:06:23 - destiny2.exe version 41270.0.0.0 (previous day) The audio settings fix appears to have been a temporary workaround that is no longer effective. CURRENT SYSTEM STATUS: ---------------------- - Audio settings: Still configured as instructed - Discord overlay: Still disabled - All other previous troubleshooting steps: Completed - No changes made to system configuration since initial fix QUESTIONS: ---------- 1. Are there any additional steps I should try beyond the audio configuration? 2. Is there a known issue with version 41270.0.0.0 that might require a game update? 3. Could there be another background service or application interfering? 4. Should I try a different audio configuration or device?

    Langue du message :

     

    Modifier
    Prévisualiser

    Jouez selon les règles. Prenez une minute pour lire notre Code de conduite avant d'envoyer le message. Annuler Modifier Créer l'escouade Publier

Vous n'êtes pas autorisé(e) à visionner ce contenu.
;
preload icon
preload icon
preload icon