problem apex legend crash with 417.71

by vegetayasuo
Reply

Original Post

Re: Bad_module_info

[ Edited ]
★★ Novice

Finally fixed this stupid bad_module_info crashing issue on my rig. Mine has been crashing since day 1. Crashes nearly every game at seemingly random times. 

 

i5-3570k @ 3.40 GHz (no OC)

R9 Fury 4GB with 1.9.2.1 drivers

Viewsonic XG2401

 

Stopped crashing completely in the past 3 days with the following settings:

Full screen mode

75 FPS cap

Disable fullscreen optimizations

V-sync off

All other graphical settings are high

Message 281 of 466 (1,560 Views)

Crashing with a AMD Radeon(TM) RX 560

★★ Novice
Processor
AMD FX(tm)-6300 Six-Core Processor
 
Video Card
AMD Radeon(TM) RX 560 Series
 
RAM
16 GB
 
Operating System
Windows 10
 
Message 282 of 466 (1,175 Views)

Re: Apex Legends - Crash on Startup or Bad_module fix

★★★ Newbie

Its Probably AMD they need to make a new driver update i have the same thing as you and its really annoying EA PLZ fix UR GAME! ITS BEEN GOING ON FOR 3 WEEKS NOW!

Message 283 of 466 (1,603 Views)

Re: Bad_module_info

★ Apprentice

@5c077y2H077y wrote:

I saw the comment from Blueberry mentioning dual monitors and decided to give it a go. I disabled my secondary screen and just played with the one; and, though I've only been able to play about 2 hours, those 2 hours were crash free.

 

I'm not calling it a fix by any means but could anyone conduct any testing in parallel with my own investigations? I'm somewhat dubious as I doubt only people who use dual monitor set ups are affected, but anything that lets me get in a game is welcome to me. The crash is incredibly random and difficult to replicate, so I reckon someone would need at least 12 hours of stable game time before calling anything a solution. I imagine the random aspect of these crashes is slowing down Respawn's investigations, too.

 

Thanks.


Unfortunately for me this doesn't help, totally unplugged my second monitor so it was just my main one and crashed about mid way through a game after 2 or 3 games

Message 284 of 466 (1,603 Views)

problem apex legend crash with 417.71

★ Novice

HELLO ,sorry for my poor english,i have an problem with apex legend.i have an rtx 2080ti. an i7 8700k overclock 5ghz.ram 3600mhz ddr4

 

.i join to the post the  dxialog.if an personn can help me

i freeze in game and crash.not all time but all the 1-2 games.i freeze all game when i play in 144hz,but with the nvidia contro lpanel i give 60hz locked and i freez not the al lthe game.i crash only o nthis game,i no understand

Message 285 of 466 (1,199 Views)

bad_module

★★★ Newbie

so it's been 2 weeks since i had this problem, sometimes i'm in the middle of a game and suddently an error message appears and says "BAD_MODULE stopped working" or something like that is there any solution to this problem?

i have a core i5 7400 with a gtx 1070 and 12gb of ram

Message 286 of 466 (1,161 Views)

Bad_Module_Info crash

★★★★★ Newbie

So I've been trying to play this game for several weeks now, I rarely make it to the end of any game since I crash ALL THE TIME.

I've tried literally everything, every posted "fix" on google, updated drivers, tried old drivers, reinstalled the game, reinstalled windows, you name it! The only thing that some what works is to cap fps to 60, then I can run a few games between crashes... Not super exciting to play at 60 fps with a 240hz monitor...

According to the event log it's a Bad_Module_Info crash every time.

We are 6 friends playing this and every single one get the same crash, so I would assume it's a pretty big problem.

 

-The first patch you guys released after the game launch fixed the crashes for all of us, played for a few days without issues. After the second patch hit and all updates after that we crash every single game, more or less. Ironic since the second patch was supposed to be the one fixing crashes.

 

I know there is multiple threads about this but there is no real answer from you Respawn/EA, is this something that is getting fixed or should the several thousands of people getting this just uninstall the game? Don't get me wrong, it's a great game, haven't had as much fun in a game for a long time, but the crashes will make people leave in heaps, including myself.

 

Specs:

i5 9600k

1070 ti

z390 gaming h

16gb ddr4

Message 287 of 466 (1,162 Views)

Re: Bad_module_info

★★★ Newbie

So I have had some luck getting this game to run stable by using the +fps_max 80 command line arguments.  Even though my system is capable of running this game at much higher fps, the game becomes seemingly unstable for me at anything past 80 fps. 

I played for a solid 3-4 hours yesterday without a single crash to desktop.  I experimented with the fps and adjusted it to +90 and it crashed on the first game.  I adjusted it back to 80 and no crashes.  This morning I was able to play for another 2-3 hours at +80 and had zero crashes.

I hope this was helpful.

Specs :

i5-6400
RX 480 4gb

Message 288 of 466 (1,324 Views)

Random Crashing

[ Edited ]
★★★ Novice

I posted a Topic yesterday so if you need any other information besides what I am going to say here, check that out.

 

I crash a lot in Apex. I thought there was nothing I could find for reasoning but then I found something in Event Viewer (I checked before but it was an Error which I didnt look at). The same thing comes up for EVERY crash and I will post it below. I crash every 1-3 games if I am with a pre-made team. If I am solo I crash between 1-12 games... sometimes I get lucky and can play 12 matches before crashing, but it will happen.

 

What Event Viewer says EVERY crash:

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: 0x2f7c
Faulting application start time: 0x01d4d1e52b844879
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: 4c7a5b6f-39ed-4ff2-a591-653d7376835e

Message 289 of 466 (1,183 Views)

Windows error report i got after crashing to desktop,might help devs

★★★ Newbie

just posting this here because i really haven't seen someone post something like this about the freeze to crashing to desktop. Don't know if it helps but here it is none the less

Version=1
EventType=APPCRASH
EventTime=131961678791207607
ReportType=2
Consent=1
UploadTime=131961678832014840
ReportStatus=268435456
ReportIdentifier=f68c58fc-b796-49f5-b801-53b8f7a976e4
IntegratorReportIdentifier=6f830adc-09ce-4553-a06b-9e0da361ea30
Wow64Host=34404
NsAppName=bad_module_info
AppSessionGuid=0000128c-0002-0009-1741-935972d2d401
TargetAppId=W:0006c1744d7c180d7ff939cb116540ad415b00000904!00008bca6bbdadaf56f500bf1d8fe6d9393673dfcbe4!r5apex.exe
TargetAppVer=2019//02//25:05:35:36!2a1985b!r5apex.exe
BootId=4294967295
TargetAsId=2147
UserImpactVector=858796848
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=2fa587f61571ffe999423f2b2f32e164
Response.BucketTable=4
Response.LegacyBucketId=120792870519
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=bad_module_info
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=00000000
Sig[3].Name=Fault Module Name
Sig[3].Value=unknown
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Code
Sig[6].Value=00000000
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000000000
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.17763.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=bad_module_info
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17763
OsInfo[3].Key=ubr
OsInfo[3].Value=348
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=8219
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.348.17763.0-11.0.111
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=8127
OsInfo[19].Key=svolsz
OsInfo[19].Value=111
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180914
OsInfo[22].Key=bldtm
OsInfo[22].Value=1434
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs5_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17763.348.amd64fre.rs5_release.180914-1434
OsInfo[30].Key=buildflightid
OsInfo[30].Value=7B76D7C8-0EA8-445C-968B-DFE2552A419C.1
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=RS:2A2B
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=bad_module_info
AppPath=bad_module_info
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=A01ED07A810B640A20A150D57CC9C420
MetadataHash=957071466

Message 290 of 466 (1,143 Views)