Re: Bad_module_info

@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.

@EA_Blueberry I've set FPS to 45, played for almost an hour of play time before bad_module_info crash, monitoring GPU and CPU usage at below 50% at all times.  GPU dropped to 0% as the game froze then spiked to 100% as it told it it had crashed.

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: 0x337c
Faulting application start time: 0x01d4d375d6134d6c
Faulting application path: bad_module_info
Faulting module path: unknown
Report ID: 03b846b3-74c7-47d8-bd59-1f9ac6d89ac3
Faulting package full name:
Faulting package-relative application ID:

PC Specs

I9 9900k no OC

RTX 2080ti no OC

Asus Formula z370

Team Group 8 pack DDR4 set to 3000mhz 

Installed on C drive M.2 Samsung NVME. 

Logitech G910 and G305

Tried

1. Unticking enable Origin in game for Apex Legends.
2. No overclocking GPU and CPU.
3. Going to Apex folder a changing the r5apex.exe properties compatibility to ticked "Disable full-screen optimisations".
4. Windowed and fullscreen.
5. Played with the game settings.
6. GPU Driver 417.71 (did help alot with the DX Hung and DX remove errors)
7. Crying

Nothing worked. 

Just adding my voice to the list.

I experienced this error MANY times during my first 5 hours of playtime. I tried standard troubleshooting methods such as updating drivers and Windows Updates, as well as the solutions I found in the forums like setting the .exe to disable screen optimization. 

Nothing worked. 

Nothing work I litteraly tried everything, need a fix 

im still experiencing this DUMB issue, like the rest of us.

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: 0xe4c
Faulting application start time: 0x01d4d3bdb6744be2
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: 31711942-487b-42d7-954b-e883d92bbdb0
Faulting package full name:
Faulting package-relative application ID:

Hey all,

I'm afraid I don't have an update to share from the team around this at the moment, but I combed through this discussion on the Apex subreddit and found some steps others mentioned that worked for them for this bad_Module_info error. I was hoping you can give these a try and report back on whether you had some success with them. Please include a DxDiag too if they did or didn't work.

Here are some of the comments I found:

"Try turning off Volumetric Lightning. No bad_module since - for me." (that's found within the game's video settings)

"Are you running VSYNC? I changed mine down one step from Triple (unsure of name) and have never had a crash since. May be worth a look.

https://www.reddit.com/r/apexlegends/comments/axratq/nvidia_driver_41935_for_apex_legends_fixes_dxgi/ehx43fi"

"People who are getting bad_module_info crashes try this:
Open in-game overlay (Alt+Z)
Stop any recordings you have enabled
Disable in-game overlay from GeForce Experience
This reduced the crashed drastically for me. Hope it helps you guys as well.
Edit: Btw. The crash to desktop without error message is most likely the bad_module_info crash which you can check from the Windows Eventviewer"

"for amd user with FX-6*** series cpu, there a fix that work for me
step 1 - open apex legends
step 2 - open windows services by searching "services" using the windows home button
step 3 - stop windows audio endpoint builder (its near the bottom)
step 4 - start windows audio (its right above audio endpoint builder)"

Same problem here :

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: 0x1f68
Faulting application start time: 0x01d4d4530875747e
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: 9faadc7a-ded1-4329-9616-8ece0f74f3dd
Faulting package full name:
Faulting package-relative application ID:

@Prozacel 

Can you try the steps I posted above and include a DxDiag please?

@EA_Blueberry 

"Try turning off Volumetric Lightning. No bad_module since - for me." (that's found within the game's video settings)

I have always had this disabled.

"Are you running VSYNC? I changed mine down one step from Triple (unsure of name) and have never had a crash since. May be worth a look.

No, I've also tried enabling it and it still crashed. on all Vsync settings

People who are getting bad_module_info crashes try this:
Open in-game overlay (Alt+Z)

I have all overlays disabled, even hardware acceleration disabled on Chrome/Discord etc

"for amd user with FX-6*** series cpu, there a fix that work for me

I have an Intel i3 8100

Attaching my Dxdiag

@EA_Blueberry 

List of things I have tried.

1. Installing an older version of Windows 10
2. Installing a multitude of different drivers
3. Changing all video settings
4. Disabling all Amd optimized features for game
5. Disabling / Enabling Vsync - Disabling/Enabling Freesync
6. Eac restart service , Low priority Etc
7. Disabling Full screen optimization
8. Running as Administrator (literally everything)
9. Changing Cpu priority
10. Capping my Fps at 75
11. Installing Apex on a different SSD
12. Cleaning my Ram after a crash
13. Playing in a different Resolution, both windows and Apex
14. Playing in a different Refresh Rate
15. Downloading all the drivers for my Motherboard from Gigabyte
16 . Manually uninstalling and reinstalling all the Microsoft redist packages to the latest one.
17. Running everything on Low / off
18. Running everything on High/On
19. Default settings in Apex
20. Playing in Fullscreen / Windowed / Borderless
21. Disabling Windows firewall
22. Disabling all Anti-Virus software

I'm sure there are another 30 random things I've tried but still open to suggestions. Hopefully this can be patched soon.

I will say this, before i upgraded my graphics card from an Nvidia 1050ti to this Rx580 i wasn't crashing nearly as often (but i was still crashing) not enough where i didn't dump a ton of money into this game.

I have no problems running any other games or problems with crashes, this includes Titanfall 2

@LethalDF  Same for me, I've the rx580 8gb and tried everything, nothing work. I did a lot of research and seems like it's a problem with version v1709 of windows 10. Sry for my bad english

@smt923 

Are you able to update to Windows 10 1809 to see if you experience crashes on that version?