JavaScript is required to use Bungie.net

Help - Destiny 2

Help us help you.
Edited by Kingkoofy: 12/14/2021 1:48:17 AM
2

PC: FREEZING / CRASHING: Battleye Engine related

I've struggled with this for a couple days now. Randomly Destiny 2 freezes and crashes, with generally the same Event Viewer message: Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000409 Fault offset: 0x00007ff630944334 Faulting process id: 0x45bc Faulting application start time: 0x01d7f084a82dceae Faulting application path: bad_module_info Faulting module path: unknown Report Id: 8b47129e-bc45-4d45-a72b-75a75af77ba0 Faulting package full name: Faulting package-relative application ID: Now, after trying everything to the extreme of installing a fresh OS on a brand new hard drive, and seeing the other event viewer messages, I think it is Battleye related. I just reinstalled Battleye by doing the following: Go into C:\Program Files (x86)\Steam\steamapps\common\Destiny 2\battleye Double click uninstall_battleye.bat Validate game files Play the game and you should be prompted to reinstall Battleye. Will keep this post updated.
English
#Help #gameplay

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by HIHAHIHO: 12/15/2021 2:10:45 PM
    do you use msi afterburner ? if you do try running msi as admin

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Still no luck. Reinstalls, firewall changes, services changes, steam launch parameters, game settings, overlays, underclocks, nada. Its Battleye. Gonna have to wait until they fix. More events: Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00007ff673b616db Faulting process id: 0x3d38 Faulting application start time: 0x01d7f1633ed110c3 Faulting application path: bad_module_info Faulting module path: unknown Report Id: 70698436-61fa-4b5f-9b16-1926550749af Faulting package full name: Faulting package-relative application ID: Fault bucket 120858127557, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: bad_module_info P2: 0.0.0.0 P3: 00000000 P4: StackHash_0000 P5: 0.0.0.0 P6: 00000000 P7: c0000005 P8: PCH_84 P9: P10: Attached files: \\?\C:\Users\fuers\AppData\Local\Temp\WER26CC.tmp.WERDataCollectionStatus.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER367D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER368D.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER368A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36BA.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_bad_module_info_59ea469c9cde70e5cc5fc8dc983f2f16bebbf3_85207d7d_088c4a57-58e7-4868-8c0f-2a36ee502952 Analysis symbol: Rechecking for solution: 0 Report Id: 70698436-61fa-4b5f-9b16-1926550749af Report Status: 268435456 Hashed bucket: 0758bc351100ecb0a46f1e72d1780692 Cab Guid: 0

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    1 Reply
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon