Community Manager
@InVyUI wrote:Hello, EA-Community.
I found a fix for myself and hope this could also help others who are experienced the issue with the "random crash without error (bad_module_info)".
This could just affect people with an overclocked processor!
If you have no experience with overclocking, you should probably wait until there's an official fix.
After I tried literally everything to fix the issue with random crashes without error (bad_module_info) from Apex Legends, I found something in the "System" log from the Event Viewer.
Image from the Event Viewer window:
Spoiler
The "Processor APIC ID" is not always the same number (it's also 0, 4 & 6 sometimes).
After I found this log, I've searched with google for a solution and found a answer from a user who said that this will go away by trying increasing the vCore (Core Voltage) from the processor.So I increased the vCore value (via BIOS) from 1.245 to 1.300 and since I did this there were no log about this anymore.
What has it to do with Apex Legends?
After increasing the Core Voltage of my processor, I also get no new logs about the bad_module_info and the game isn't crashing anymore.
It seems like Apex Legends takes a lot of power from the processor and it needs more voltage to run stable.
You also have this issue?
Check if you also have this log, if yes, you probably need to increase the Core Voltage of your processor, which might be improves the stability of Apex Legends.
Look into your Event Viewer, go to Windows Logs → System and search for "WHEA-Logger" by pressing CTRL + F.
Normally my PC runs stable at 1.245 vCore, Apex Legends is the only one game which needs a higher Core Voltage to run stable (at least for me).
I've never experienced this issue in any other game before and they all running stable at 1.245 vCore.
Maybe required informations:
Spoiler• OS: Windows 10 Pro (Version: 1809, OS Build: 17763.348)
• Mainboard: ASUS Z170 Pro Gaming (BIOS version: 3805 - up to date)
• Processor: Intel® Core™ i7-7700K (4x 4.80 GHz OC @ 1.300 vCore, Delidded)
• Graphics Card: ASUS ROG Strix OC GeForce® GTX 1060 (6 GB VRAM, Driver version: 419.35)
• Memory: Corsair Vengeance LPX DDR4-3000 (2x 8 GB; 16 GB @ 3.000 MHz XMP OC)
• Monitor: BenQ XL2411Z (24", FHD, 144 Hz, 1ms Response Time)I hope this could help a few of you.
THANK YOU, THANK YOU, THANK YOU, !!!
I was investigating the same thing for the last days and was thinking the same - to increae the vcore a bit to see how it will handle. I was sure my build was stable, and wasn’t suspecting the CPU, but in fact that was the reason for my crashes! Btw, for me it was about 0.1 vcore more, 0.05 didn’t work. I’m on adaptive voltage, 9700k, 5ghz and now I can enjoy my build without crashes! Thank you for sharing!
Coming back to you with an update:
Increasing vCore did nothing, unfortunately. I started increasing by increments of 0.05, ended up to 1.41 vCore. Game still crashed.
There is no way my CPU is not stable at those voltages, especially when I tested it on 1.34 vCore for about a month before playing any games. Just wanted to make sure if that's the issue here, but it's not.
But I've made another test. Since I'm using z390 board, I tested with the Intel turbo boost technology and the board's MCE (multi core enchancement). This is the factory overclock the board and the CPU provides for those of you who don't know.
I increased the maximum - 4.9 Mhz on the intel turbo boost (maximum mhz the I7 9700 comes with) - the game then crashed.
I lowered to 4.8 mhz - game crashed.
I lowered to 4.7 - game crashed.
I then revereted to the stock value, which is 4.6 - this is the stock overclock the board's MCE + intel turbo boost provide for my processor - and boom - no crashes.
So the conclusion here is that this kind of crash in not related to stability and increasing voltages (there is not way the automatic voltage on the board is not stable, since it always provide more voltage than the processor needs), but to CPU Mhz in some way. I'm not sure how is this related to the DirectX and the game engine itself, since I'm not a game developer, but the issue is 100% connected to the CPU. This could be also related to a windows update as well.
Nevertheless, this is an issue RESPAWN must fix, since I'm not getting those kind of crashes in other games.
I will monitor and let you know if I get any crashes with the stock OC.
Below is my spec:
Windows 10 latest update, 1809 build
i7 9700K
RTX 2080, drivers 419.35
Mobo: Z390 Aorus Elite
32GB Ram, 3200Mhz
Reading these most recent posts about voltage is what fixed it for me. I too am overclocking an i7 8086k from 4.0 to 5.0ghz set to all cores. I had kept my voltage lower at 1.198 for a while since it was stable in every app/ stress test before playing apex. however, apex uses avx2 instructions which need an offset in the bios when they are in use as they address significantly more power to your cores. so either vcore needs to go way higher or you tell your cores to run on a -2 or -4 offset (effectively -200 or -400mhz) whatever runs best.
I remember touching these AVX offset settings a long time ago. turns out they were okay, set to -2, so I went with upping my voltage a bit. I went up slowly, experiencing the same crashes to desktop every game or every other game until settling on 1.225 which now for 10 games has been stable. I'll update as well after 20 or 30 to see if it remains the same.
I guess this is the first AVX2 instructions use game i've played because nothing ever gave me any sweat at the lower, cooler voltage. Increasing it did see my load temps hitting 55C vs. 48C from before. I just like to run my hardware as cold as possible at all times. Anyway, thanks to whoever noticed this first and started trying to troubleshoot it in relation to the types of errors being shown in event viewer.
I can actually start playing the game now! :D
some more info:
I run the game 1920x1080, with gsync on in nvidia control panel, vsync disabled in-game. FPS capped to 238fps using RTSS. Video settings set to low for everything. Texture streaming set to 2GB. Model quality set to High. Framerate is about 125-150 when flying and once landed caps to 238fps.
Operating System
Windows 10 Pro 64-bit Version 1803 (OS Build 17134.590)
CPU
Intel 8086k Core i7 @ 5.00GHz at 1.225v 55 °C
Coffee Lake 14nm Technology
RAM
32.0GB Dual-Channel Corsair Dominator Platinum PC3200 @ 1600MHz (14-14-14-34)
Motherboard
ASUSTeK COMPUTER INC. ROG MAXIMUS XI HERO (WI-FI) (LGA1151)
Graphics
ROG PG258Q (1920x1080@240Hz)
ROG PG278Q (2560x1440@144Hz)
NVIDIA GeForce RTX 2080 Ti XC Hybrid (EVGA) @ 2040mhz boost clock 38 °C
GeForce Drivers 419.35 WHQL
Storage
1863GB Samsung SSD 860 EVO 2TB (SATA (SSD))
1907GB Micron\_1100\_MTFDDAK2T0TBN (SATA (SSD))
931GB Samsung SSD 960 EVO 1TB (m.2 PCI-E x4 (SSD))
Power Supply
Seasonic PRIME SSR-1000PD 80+ Platinum 1000W
Optical Drives
No optical disk drives detected
Audio
Sound BlasterX AE-5
Mouse
Logitech G305 Wireless
Keyboard
Corsair K65 RGB
AIO Cooler
Corsair H110i GTX
Printer
Brother HL-L2360D series laser
Network/Wireless devices
Intel Ethernet Connection I219-V
Intel(R) Wireless-AC 9560 (disabled)
Bluetooth enabled (onboard)
Notable software running in the taskbar: Corsair iCue, Greenshot, 1Password, Samsung Magician, Sound Blaster Connect 2, NVIDIA Control Panel, Color Sustainer (icc color profile keeper software), Display Fusion Pro, Logitech Gaming Software, Discord, Riva Tuner Statistics Server, EVGA Precision X1 - all up to date versions.
I tried too up my voltage on my I5 6600 aswell. Upped it from 1.050 in jumps of 0.05 to max 1.300. It didnt change anything for me, the game still had crashes on a regular base. Also feelsbad too make these changes, Im quite sure its not good for your system too mess around with Vcore amping.
Seriously, i have never crash that much on a game
It just go back to desktop without any error.
Fix that * please
@kwerbias wrote:Reading these most recent posts about voltage is what fixed it for me. I too am overclocking an i7 8086k from 4.0 to 5.0ghz set to all cores. I had kept my voltage lower at 1.198 for a while since it was stable in every app/ stress test before playing apex. however, apex uses avx2 instructions which need an offset in the bios when they are in use as they address significantly more power to your cores. so either vcore needs to go way higher or you tell your cores to run on a -2 or -4 offset (effectively -200 or -400mhz) whatever runs best.
I remember touching these AVX offset settings a long time ago. turns out they were okay, set to -2, so I went with upping my voltage a bit. I went up slowly, experiencing the same crashes to desktop every game or every other game until settling on 1.225 which now for 10 games has been stable. I'll update as well after 20 or 30 to see if it remains the same.
I guess this is the first AVX2 instructions use game i've played because nothing ever gave me any sweat at the lower, cooler voltage. Increasing it did see my load temps hitting 55C vs. 48C from before. I just like to run my hardware as cold as possible at all times. Anyway, thanks to whoever noticed this first and started trying to troubleshoot it in relation to the types of errors being shown in event viewer.
I can actually start playing the game now! :D
some more info:
I run the game 1920x1080, with gsync on in nvidia control panel, vsync disabled in-game. FPS capped to 238fps using RTSS. Video settings set to low for everything. Texture streaming set to 2GB. Model quality set to High. Framerate is about 125-150 when flying and once landed caps to 238fps.
Operating System
Windows 10 Pro 64-bit Version 1803 (OS Build 17134.590)
CPU
Intel 8086k Core i7 @ 5.00GHz at 1.225v 55 °C
Coffee Lake 14nm Technology
RAM
32.0GB Dual-Channel Corsair Dominator Platinum PC3200 @ 1600MHz (14-14-14-34)
Motherboard
ASUSTeK COMPUTER INC. ROG MAXIMUS XI HERO (WI-FI) (LGA1151)
Graphics
ROG PG258Q (1920x1080@240Hz)
ROG PG278Q (2560x1440@144Hz)
NVIDIA GeForce RTX 2080 Ti XC Hybrid (EVGA) @ 2040mhz boost clock 38 °C
GeForce Drivers 419.35 WHQL
Storage
1863GB Samsung SSD 860 EVO 2TB (SATA (SSD))
1907GB Micron\_1100\_MTFDDAK2T0TBN (SATA (SSD))
931GB Samsung SSD 960 EVO 1TB (m.2 PCI-E x4 (SSD))
Power Supply
Seasonic PRIME SSR-1000PD 80+ Platinum 1000W
Optical Drives
No optical disk drives detected
Audio
Sound BlasterX AE-5
Mouse
Logitech G305 Wireless
Keyboard
Corsair K65 RGB
AIO Cooler
Corsair H110i GTX
Printer
Brother HL-L2360D series laser
Network/Wireless devices
Intel Ethernet Connection I219-V
Intel(R) Wireless-AC 9560 (disabled)
Bluetooth enabled (onboard)
Notable software running in the taskbar: Corsair iCue, Greenshot, 1Password, Samsung Magician, Sound Blaster Connect 2, NVIDIA Control Panel, Color Sustainer (icc color profile keeper software), Display Fusion Pro, Logitech Gaming Software, Discord, Riva Tuner Statistics Server, EVGA Precision X1 - all up to date versions.
UPDATE!!! :
After about 12 hours of playing I can say I fixed it for good. The game doesn't crash when I'm on 4.6 Ghz (stock OC). Thank you for sharing the AVX info, I didn't know that. The upcoming days I will test with a avx offset to see if I can manage to hit higher frequencies.
This is a game engine specific, which needs to be fixed, unfortunately.
I can now say 100% that this kind of crash is a CPU related issue. Took me a month to figure it out...
Community Manager
