Results 1 to 9 of 9

Thread: "bad-module-info has stopped working"

  1. #1
    New Member Cupidhead Gugus294's Avatar
    Join Date
    Aug 2016
    Posts
    6
    2
    Level completed: 25%, Points required for next Level: 376
    Achievements:
    Repped! Third Class 1 year registered 1000 Experience Points
    Rep Power
    0

    "bad-module-info has stopped working"

    Every time I've tried to launch Smite for the last few days, my game initializes and immediately gray-screens. A window comes up saying "bad-module-info has stopped working", and my only option is to close the program. It happens when I try to launch Paladins as well, so I'm assuming it's something wrong with all of Hi-Rez's games. I have reinstalled the game, my graphics drivers, Windows, Steam, and the Hi-Rez Installation Service and ran the Hi-Rez Diagnostics Tool and found no problems with anything. I also validated the integrity of my game files through Steam, re-ran the prerequisites, changed to windowed mode in the config files, lowered my monitor's resolution, and ran the game in safe mode. Nothing has worked. What else can I do? I've only had this problem with Hi-Rez Games, nothing else.

  2. #2
    New Member Cupidhead BlacKklight's Avatar
    Join Date
    Dec 2017
    Posts
    1
    1
    Level completed: 3%, Points required for next Level: 388
    Rep Power
    0
    I have the same issue, Hirez please fix !

  3. #3
    New Member Cupidhead BaneOfEarth's Avatar
    Join Date
    Dec 2017
    Posts
    2
    1
    Level completed: 7%, Points required for next Level: 373
    Rep Power
    0
    My game randomly crashes at after varying amounts of game play. Bad-module-info stopped working.

    Date & Time Message Type Detail Source Process Thread ERROR_CODE CHARACTER_ID PLAYER_ID LEADER_CHARACTER_ID LEADER_PLAYER_ID MAP_GAME_ID MAP_INSTANCE_ID CLAN_ID GAME_EVENT_ID CHAT_CH_TYPE CHAT_CH_ID ACCOUNT_ID HANDLE MATCH_ID MATCH_QUEUE_ID
    22-12-2017 22:42:27.641 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.641 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.641 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.641 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.642 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.642 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.642 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.642 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.642 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.642 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.642 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.642 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.643 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.643 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.643 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.643 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.643 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.643 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.643 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.643 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.655 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.655 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.655 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:27.655 Invalid mesh assembly id given: 28 3 8 Unknown 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:33.501 Connected to 50.7.13.251:9000 0 8 Unknown 560 7116 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:34.754 Thread ended: PackSession 3 8 Unknown 560 7116 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:34.754 CPackSocket PackThread exit 3 4 Unknown 560 8092 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:34.754 Thread ended: PackSocketIO 3 8 Unknown 560 8092 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:34.807 Connected to 50.7.13.251:9000 0 8 Unknown 560 12352 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:42:38.464 Overwolf# - Loaded gameevents dll 0 8 Overwolf 560 11400 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:44:04.216 Thread ended: PackSession 3 8 Unknown 560 12352 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:44:04.216 CPackSocket PackThread exit 3 4 Unknown 560 9684 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    22-12-2017 22:44:04.216 Thread ended: PackSocketIO 3 8 Unknown 560 9684 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    End

    #-----------------#
    2017-12-22_03.46.35 - PID 11764 - THR 8000
    System started

    #-----------------#
    2017-12-22_07.26.38 - PID 23148 - THR 11732
    System started

    #-----------------#
    2017-12-22_07.36.42 - PID 14600 - THR 236
    System started

    #-----------------#
    2017-12-22_08.02.52 - PID 18456 - THR 6028
    System started

    #-----------------#
    2017-12-22_08.06.53 - PID 5468 - THR 21552
    System started

    #-----------------#
    2017-12-22_08.14.17 - PID 8912 - THR 528
    System started

    #-----------------#
    2017-12-22_10.24.31 - PID 12452 - THR 23840
    System started

    #-----------------#
    2017-12-22_21.03.22 - PID 27600 - THR 24144
    System started

    #-----------------#
    2017-12-22_21.30.39 - PID 8096 - THR 12880
    System started

    #-----------------#
    2017-12-22_21.32.49 - PID 2692 - THR 10556
    System started

    #-----------------#
    2017-12-22_21.38.25 - PID 2684 - THR 8916
    System started

    #-----------------#
    2017-12-22_22.29.58 - PID 6676 - THR 7952
    System started

    #-----------------#
    2017-12-22_22.42.03 - PID 6676 - THR 4960
    Abnormal termination triggered by abort call

    #-----------------#
    2017-12-22_22.42.24 - PID 560 - THR 11400
    System started

  4. #4
    New Member Cupidhead BaneOfEarth's Avatar
    Join Date
    Dec 2017
    Posts
    2
    1
    Level completed: 7%, Points required for next Level: 373
    Rep Power
    0
    Almost 1000 views already, by far the highest on the front page!!! Can anyone address this obviously big issue people are having!?

  5. #5
    Junior Member Cupidhead YoMamaIsSoooo's Avatar
    Join Date
    Oct 2017
    Posts
    19
    1
    Level completed: 65%, Points required for next Level: 142
    Achievements:
    3 months registered 250 Experience Points
    Rep Power
    0
    Quote Originally Posted by BaneOfEarth View Post
    Almost 1000 views already, by far the highest on the front page!!! Can anyone address this obviously big issue people are having!?
    you talk as if hirez even reads these.

  6. #6
    New Member Cupidhead SportsDog's Avatar
    Join Date
    Dec 2017
    Posts
    2
    1
    Level completed: 4%, Points required for next Level: 386
    Rep Power
    0
    I AM having the same issue plz fix it hirez i only have this issue with smite

  7. #7
    New Member Cupidhead SportsDog's Avatar
    Join Date
    Dec 2017
    Posts
    2
    1
    Level completed: 4%, Points required for next Level: 386
    Rep Power
    0
    I AM HAVING THE SAME issue it is costing me tp and is not letting me play plz fix it only happens in smite

  8. #8
    New Member Cupidhead SMircetic's Avatar
    Join Date
    Jan 2018
    Posts
    2
    1
    Level completed: 4%, Points required for next Level: 384
    Rep Power
    0
    Same issue here, it is related to the latest Windows Creator update, if you can roll back that should fix it.

  9. #9
    New Member Cupidhead DreadMz's Avatar
    Join Date
    Oct 2015
    Posts
    3
    3
    Level completed: 40%, Points required for next Level: 420
    Achievements:
    1 year registered 1000 Experience Points
    Rep Power
    0
    Quote Originally Posted by SMircetic View Post
    Same issue here, it is related to the latest Windows Creator update, if you can roll back that should fix it.
    So I have a possible solution to you all, worked for me atleast. All I had to do was disable windows own real-time protection(just google how you can do it if you don't already know). I even disabled cloudbased protection just to be sure.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •