Forum Discussion

Re: Bad_module_info

Just throwing in my DxDiag, as well as my userbenchmark if it helps at all. I've tried nearly every driver from 388 to 417 with no luck, still getting bad module info in my event viewer. I ended up throwing windows 7 onto a second drive and haven't had any major issues so far, although it's too soon to tell since i've only played a few games.

12 Replies

  • Rippthrough's avatar
    Rippthrough
    7 years ago

    I have the same thing, tried different gpu drivers, various compatibility modes, disabling audio, reinstalls, etc - nothing seems to fix it.

    HOWEVER - it happens far more often when I'm chatting on Discord than when I'm not. Almost every game vs every 10 games. So it may be audio subsystem related.

  • Vinko1911's avatar
    Vinko1911
    7 years ago

    In my case, my screen freezes for couple of seconds and then the game crashes to desktop.

    I tried disabling unused audio outputs with not much success... It was fine for a day and it started again

    When I check Event Viewer it also shows "Bad module"

    Spoiler
    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: 0x00000000
    Fault offset: 0x0000000000000000
    Faulting process id: 0x1cf4
    Faulting application start time: 0x01d4c2d60f7dbd42
    Faulting application path: bad_module_info
    Faulting module path: unknown
    Report Id: 580f0ff0-9d37-4b8a-b339-887ea802b3c1
    Faulting package full name:
    Faulting package-relative application ID:

    Jesus, crashed 2/2 games now...

    First when was about land from spawining ship, second one when my teammate collected my banner

  • The game crashes without visible error for me. I previously played a full game (22min), Then a super short game crashed while landing. This happens constantly I can play one or two games then Apex crashes to desktop with no visible error. Has happened since I downloaded the game Sunday. I'm getting the bad module info in event viewer. 

    This is the latest one:

    Started game 7:05 - End Game 7:08 - Graphics froze and closed Apex landing on the mountains south of the Armory. Bad Module at 7:07:55
    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: 0x00000000
    Fault offset: 0x0000000000000000
    Faulting process id: 0x10c0
    Faulting application start time: 0x01d4c398cc51b9e5
    Faulting application path: bad_module_info
    Faulting module path: unknown
    Report Id: 09571111-80fc-4ea8-bf0e-7e56de9dcaa0
    Faulting package full name:
    Faulting package-relative application ID:

    • Have the Application Crash Log, attaching dxdiag.
    • IGO_Log.Origin_3428 shows some warnings at the start of the game
    • All but active sound is disabled, and have the latest AMD Drivers for my GPU 19.2.1
    • Latest Windows Updates
    • Running Origin and Apex as Admin with disabled full screen optimizations
    • I've also cleared Cache and Reinstalled the Game and Origin Client

    Performed the following prior to game to continue troubleshooting.

    Disabled all non microsoft services
    Disabled all start up options except AvastAV and Steel Series Mouse SW
    Restarted
    Updated Avast AV, Restart
    Made exceptions for All Origin, Apex, and EasyAnticheat folders in AppData, ProgramData, Program Files x86.
    Added Apex, Origin, and Apex Legends (all entries) to communicate through private and public in Windows Defender Firewall.
    VRAM is set to 5888MB
    Advanced performance options is set to Applications
    Ran Update on Game
    Ensured Enabled Origin in game was turned off
    Enabled Logging in Origin

    Game Graphic Settiings

    - Borderless Window, have tried all options several times
    - 16:9
    - 1920*1080
    - FOV 90
    - V Sync Disabled, have tried triple buffered as well
    - Anti-aliasing TSAA
    - Texture Streaming budget 4GB, have changed to 6GB same result
    - Anisotropic 4x
    - All others except Model Detail(High) on Disabled or Low

    PC Specs:

    Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz - Running stock speed

    16.0 GB DDR3 2300 Gskill Mem

    Realtek High Definition Audio - onboard on ASUS MB

    Radeon RX 580 Series 8GB Mem

  • 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: 0x00000000
    Fault offset: 0x0000000000000000
    Faulting process id: 0x37c8
    Faulting application start time: 0x01d4c3a81372af15
    Faulting application path: bad_module_info
    Faulting module path: unknown
    Report Id: 15aa8461-6f88-42ab-a12f-ed66f21b3e8b
    Faulting package full name:
    Faulting package-relative application ID:

    this is my error report from the event viewer
    The crashes just keeps happening no matter how i tried of the fixes found by community, this this to be addressed real quick by respawn.
    My PC specs:
    i5-4430 stock speed with decent cooling around 40-50C in game
    AMD RX570 4GB around 60C ingame
    16GB DDR3 RAM
    win 10 pro.ver 1089

  • Bheshie's avatar
    Bheshie
    7 years ago

    Here is mine

    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: 0x00000000
    Fault offset: 0x0000000000000000
    Faulting process id: 0x2744
    Faulting application start time: 0x01d4c3a7658b58e7
    Faulting application path: bad_module_info
    Faulting module path: unknown
    Report Id: 944e3b1e-cd49-4ae0-9bd1-560529977fb4
    Faulting package full name:
    Faulting package-relative application ID:

  • Patch has been released, maybe this will fix our issues. version 3.0.1J1585

  • Didn't fix it for me either

    Some more info: 

    Its installed on a SSD, so the speculation that it might be hdd related doesn't seem very likely. This error has apparently popped up for people in other games that have easyac implemented so I wouldn't at all be surprised if that is where the fault lies.

  • smt923's avatar
    smt923
    Rising Traveler
    7 years ago

    I am still crashing post update, but bad_module_info is no longer appearing in my event viewer, I don't really get any errors there now, the game just crashes without much of a hang at all

  • Name der fehlerhaften Anwendung: bad_module_info, Version: 0.0.0.0, Zeitstempel: 0x00000000
    Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
    Ausnahmecode: 0x00000000
    Fehleroffset: 0x0000000000000000
    ID des fehlerhaften Prozesses: 0x2434
    Startzeit der fehlerhaften Anwendung: 0x01d4c3dfef47438b
    Pfad der fehlerhaften Anwendung: bad_module_info
    Pfad des fehlerhaften Moduls: unknown
    Berichtskennung: 425efa6e-be6c-43d2-9784-c83aee7610cb
    Vollständiger Name des fehlerhaften Pakets:
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

    This my error code.

    Specs:

    I5 6500
    8GB RAM
    ATI R9 380X with the current driver version 19.2.1
    Win 10