Re: Bad_module_info

@Sicketor 

Try setting the Easy Anti-Cheat priority to low.

1. Launch the game.
2. Open Task Manager by typing CTRL + ALT + DELETE
3. Go to Details tab>Find Easy Anti-Cheat program and right click>Set priority to low.

Can you get back to me with the results?

@EA_Blueberry  i will try it today and notify you, but i think its much broader problem because it affects alot of players

Low priority EAC crashed first game almost immediately. One of the fastest crashes I've had yet actually. Crashed the game after that, and the one after that, all quite quickly. The crashes are random but if anything this seems to have made the crashes worse.

@EA_Blueberry no working.. crashed at my first game=[

Ok just wanna clear out some doubts : No matter which OS your playing on , it doesnt fix anything. error went from '00000x000 r5apex' error thing ( in windows 8.1) to a simple no error crash or 'bad module info' crash on windows 10.

I tried the game on 3 different driver versions ( AMD) and also tried two different GPU : no change
i tried the game with EVERY possible video setting you can set from the lowest quality ( even 4:3 at 1024x768) to the highest my i can with my monitor (1400x900) and still no difference , still crash. 

Doesnt seem to be AMD only related as my friend using a GTX cant play the game either

I also tried the game without the new  windows 10 update (last one from 2017) AND with ALL new updates : no changes. still crash

I feel like theres just nothing we can do  . I feel like its on YOU guys , EA games.

playing the game with NOTHING running in background doesnt change anything also

I actually had less crash when playing with dual-monitor while i was watching a stream on twitch, with everything open on my pc ( discord , google etc etc) 

Its not like the game wasnt running fine , its very smooth capping 144fps all the time , no bugs , no lag just this random BAD MODULE INFO every game 

I give 1 more week if its not fixed until then im not going to reinstall this game. its actually frustrating cause i really like playing it.

Windows 10 x64

Asus R9 370 GDDR5

8go RAM

AMD FX-6300

I have tried literally everything. All videos, all tutorials, all forums, everything.

There is nothing that we as player can do to avoid "bad_module_info" error.

@EA_Blueberrywhy is so dificult to fix this? I'm a game developer and if you want any help to make a hot fix.

And to be honest, this topic have 25 pages of players with the same problem, and only on page 24 you guys came sayng "set to low priority the Easy Ant Cheat" ... like, really? At least say "WE DONT KNOW WHAT IS THE PROBLEM". Be more carefull with your players, becase we still are here but we wont be here forever. Fortinite is there waiting we back with no crashs and with no moderators to say "set to low priority the Easy Ant Cheat" what offcourse is NOT the problem.

Explain to us why this problem exist and WHAT we can do to avoid.

Thanks.

Windows 10 x64

32g RAM

AMD RX 580 8G

To everyone thats having these super annoying crashes, i've spoken with support multiple times and they told me this: "We are aware of this issue and our responsible team is working on it". I'm also experiencing these crashes very often but i've found some hope knowing that they are working on it.

Yh, "they are awere of issue", so what? It did not start a few days ago, It's been like that since the game launch(FGS it's not a minor bug!). Ehhh, I'm slowly convinced myself that it's time to quit this game. Shame, bcs besides that issue its really good game. 

My config:

CPU: i5 6500

GPU: RX 480

SYS: WIN 10

Btw I've tried to run this game on laptop with GTX and it didn't crash during 3h of playtime(fps was terrible though).

Been experiencing Bad Module Info and crashes every game.

I am running a i5 4670k, RX480 4GB and 16GB DDR3 RAM.

I have tried everything to fix this issue and nothing worked until I used this command in Origin: +fps_max 60 -novid -borderless window

Another rule is no Alt Tabbing, I have not crashed in over 30 games easy.

I have a 144hz monitor and previously FPS was fluctuating from the 100-144 range. Now it is always at 60 and never drops below, no crashes... yet.

I use Discord also.

Hey all,

This is still being investigated and we appreciate you hanging in there with us on it. We've seen some player report positive results by setting their Origin status to invisible and disabling all notifications within their Origin client's application settings.

Can anyone that's currently experiencing this error try it while playing without any overlays? This way we can test to see if there is any link to friends or notifications.

I've had Origin's overlay off for the past week or so and have had consistent crashes every few games for the whole time, like a lot of other posts it probably does help for some people but it's not helping me, I've tried basically every single fix posted on these forums and nothing has helped, there was a small update just now and since then I've crashed every game, even the 'bad_module_info' event has returned and it wasn't there before, below is that and an up to date dxdiag:

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: 0x1334
Faulting application start time: 0x01d4ce06ad3ffbcf
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: ffe7309b-5374-4bd1-86fa-4ef3101f0edc
Faulting package full name: 
Faulting package-relative application ID: 

I think that problem is sound related.. There are a lot of fixes for this problem, and one is helping with like 80% of people here. Ive got crashes since launch, after verifying my game files everything worked fine for 3/4 days and then it crash again. So I decided to try another fix from YT. Disabling Windows Audio when game is in "Click to Continue" stage and then turning it on again FIXED problem for entire day I will test if game is working today also. 

@EA_Blueberry I just attempted disabling all notifications in origin, going invisible, and disabling overlays. This did not work for me. Crashed upon landing.

EDIT: This is my situation in more detail if you need it:

https://answers.ea.com/t5/Technical-Issues/Apex-Legends-Crash-To-Desktop-Without-Error-Message/td-p/7534887

Event Viewer Log:

Blueberry,

I opened Origins and added "+fps_max 60 -novid -borderless window" to the properties for Apex.  I made sure my Radeon Settings have "Use Application Settings" set wherever possible.  All of my graphical settings are at set to the lowest, and 1080 resolution.  I disabled all notifications in Origins.   I disabled Origins In-Game using the option within the Origins client application.  I set my status to invisible.  I played 1 game (~8 minutes) without crashing, then crashed within 5 minutes of my second game.  There was no crash message and I don't know how to check event log.  I usually get either a blank crash or bad_module_info crash.

It seems that I don't have any link to friends or notifications.

GPU: Radeon rx 580 8gb

CPU: AMD FX-6300

OS: Windows 10

it seems that us amd users suffer from that much more then the nvidia counterparts.. wonder if its really a gpu problem =[

i tried everything.. keep crashing and there isnt solution for that

Feels like it's getting worse and worse for me, I have seen two types of crashes now, a completely silent, no error no event log crash one that almost always happens during the drop/landing, as well as bad_module_info crashes while a decent way into the game, running an i5 and AMD rx460, as always, latest dxdiag is included

@EA_Blueberry_ any new

We are crashing.... T_T this is so sad...

For me it occurs a 100% when i stand next to care packages while they drop. Lifelines and the map drop, both of them. But it also crashes in other situations. I think that wasnt mentioned here before, just wanted to throw that in.

I moved the game to my SSD (which also REMOVED all the things like admin mode, compatability mode, etc) and it felt good for a while, no crashes, I started crashing again but it's now only bad_module_info crashes again, so I actually think some of these 'fixes' people are recommending are junk and making these crashes worse for some of you guys, if bad_module_info for intel & amd can be fixed I'd have no crashes

Alright, I am not certain this will work for everyone, but my friend, who has a 480, was crashing ALOT and could not play the game for more than 5 minutes without crashing and receiving this error. After we made these changes, he never crashed again tonight!

We did 3 things that seemed to fix it. Keep in mind: I am posting this right after we finished playing because I understand your frustrations and I am just trying to get some info out there if it helps you.

1. Set your refresh rate (this varies based on your monitor, so at your discretion) AND max fps with launch options. So something like:  -refresh 75 -dev -console +fps_max 0
   • Now I can't say that line will work 100% percent, but if it doesn't remove the fps_max command and input it manually in the developer console in the game. (Sorry if that seems cloogy, but I am speculating based on experience with Source Engine. Look up a video if that command doesn't function because this might be the most contributing factor in making this work and I am purely a layman.)
2. We played on Brazil servers. (He swears this isn't a factor, but I am including it anyways in case it was.)
3. There is speculation that as soon as you match-make, don't hit any button or key until you are landing and your POV has fully switched from Third-person to First-person. I saw a noticeable improvement in his game's longevity here, but it could have easily been coincidental as we only did this in 3 games.

Guys, I truly hope this works for you and you are able to enjoy the game. If anyone has any questions PM me or if it worked for you, RE-POST IT! 

----------------------------------------------------------------------------

(EDIT)

Upon getting more information about this from my previously affected friend and testing it with some other people that were experiencing similar problems, you need to LIMIT your max fps. Blueberry's post below is more accurate as to what you should attempt to do to remedy this. One thing to take note of is that you are limiting your frames, I do not reccomend that you guys limit your fps to 30. I would recommend that you measure your in-game fps and knock it down in 10% increments until it is stable.

---

ttv/MaverickOnPC

---

@MaverickonPC-TV wrote:

Alright, I am not certain this will work for everyone, but my friend, who has a 480, was crashing ALOT and could not play the game for more than 5 minutes without crashing and receiving this error. After we made these changes, he never crashed again tonight!

We did 3 things that seemed to fix it. Keep in mind: I am posting this right after we finished playing because I understand your frustrations and I am just trying to get some info out there if it helps you.

1. Set your refresh rate (this varies based on your monitor, so at your discretion) AND max fps with launch options. So something like:  -refresh 75 -dev -console +fps_max 0
   • Now I can't say that line will work 100% percent, but if it doesn't remove the fps_max command and input it manually in the developer console in the game. (Sorry if that seems cloogy, but I am speculating based on experience with Source Engine. Look up a video if that command doesn't function because this might be the most contributing factor in making this work and I am purely a layman.)
2. We played on Brazil servers. (He swears this isn't a factor, but I am including it anyways in case it was.)
3. There is speculation that as soon as you match-make, don't hit any button or key until you are landing and your POV has fully switched from Third-person to First-person. I saw a noticeable improvement in his game's longevity here, but it could have easily been coincidental as we only did this in 3 games.

Guys, I truly hope this works for you and you are able to enjoy the game. If anyone has any questions PM me or if it worked for you, RE-POST IT! 

---

ttv/MaverickOnPC

---

Thanks for sharing that, @MaverickonPC-TV 

A player in another discussion about crashes post this workaround that fixed the bad_module_info error for them.

Crashing with no error discussion: https://answers.ea.com/t5/Technical-Issues/Apex-legends-crashing-without-error/m-p/7600584/highlight/true#M27470  

---

@Morlynes  wrote:

Hello everynyan.

I had bad module info all Apexlife. Every game is crashed. I tryed everything and don't help me. I gave up but then I decided to try this.

1. Disable second monitor by "Windows" + "P". Only main monitor. (i think it's not main problem).

2. Origin game setting: +fps_max 35. Change min settings in game(my settings is low-medium, I changed it after I tryed low settings) and turn off vsync.

(I don't know what exactly works out of these two points. I did all points)

And it works for me. you can up your +fpx_max to 25, 45, 60,80,100...I change it to 45.

+fps_max 60 doesn't work for me and i changed it to 45 again.

As I understand GPU must work lower 100% in my PC.

Now I can play 5-7 hours without crashes. I don't played longer.

I hope it can help someone.

Sorry for my English.

My PC specs:

Win 10 x64 Pro
CPU: Intel 3450 3.1Ghz
RAM: 6 GB 3DDR RAM

VIDEO: AMD HD 6970 2GB

Motherboard: MSI h61m-p31/w8

Thanks for attention.

---

Hope this helps alleviate some of the pain for those experiencing this. We don't have any updates to share right now on the status of this error but it's still being investigated.