Ce n’est pas ce que vous cherchez ?

Nouvelle publication

Commentaires

4 commentaires
  • Update: This looks to be related to the Scarlett 4i4 device I use for audio. Once I disconnect it, the crash stops happening. I haven't yet successfully launched the game yet, but that seems to be the culprit.

    1
  • Upvoting for visibility. After updating literally everything on my PC for hours, turning off my Focusrite Scarlett 16i16 Gen 4 Audio Interface was the only thing that gets the game to boot. Can the Bungie team please get the BattleEye team to prioritize fixing this?

    1
  • Bumping this. Hard to play a game when having a specific audio device plugged in causes a bluescreen on launch. I also have a scarlet 4i4 that i use to output audio through.

    0
  • Absolutely ridiculous, Battleye causes a BSOD Kernel crash on my PC for using one of the most popular audio interfaces out there. Apparently it causes similar issues if you got your flight/racing sim equipment plugged in. Gotta unplug everything and deal with having crappy audio and no comms.

    This might help some of y'all but still, please keep reporting to Bungie and Battleye

    It seems the issue is specifically the Focusrite's MIDI Driver! You can disable just that, and continue using your interface.

    Steps if you are using a Focusrite 2nd Gen Device (This may work on others, so use the Query to confirm):

    Open Command Prompt (Run as Administrator)

    Confirm the service name exists:

    sc query FocusriteUsbMidi

    Disable it:

    sc config FocusriteUsbMidi start= disabled

    Reboot. Boot Marathon, should boot up just fine.

    To re-enable later:

    sc config FocusriteUsbMidi start= demand
    0

Vous devez vous connecter pour laisser un commentaire.