March 2019
Just noting down some actions that my friend has tried.
So far he has attempted the below actions without any resolution.
Strangely I've only had it crash once, and I've played it quite a bit.
I've attached my dxdiag results in case anyone working on the issue wants to compare DxDiag results with from someone who has only ever crashed once over the period of 45 hours of gameplay.
If you can't fix it soon, please implement a rejoin game feature like PlayerUnknown's Battlegrounds has. PUBG suffered from disconnects back in the day, but at least we could rejoin the session.
March 2019
Literally unplayable
March 2019
EA support was at a loss, if I update my Nvidia driver the game just randomly quits with no error message or warning.... if I downgrade my Nvidia driver I get application error crashes. Maybe 1 in 10 games will go without crashing if I'm lucky.
Anyone have advice? Guess I should just wait until the next major patch... feel like I've been letting a ton of my teams down with this happening.
March 2019
March 2019
Try this new Driver hot off the presses:
https://answers.ea.com/t5/Technical-Issues/Important-Nvidia-Update-419-35-The-HUNG-Fix/td-p/7631857
March 2019
Try updating your windows so we can check its not an outdated windows causing your crashes please
March 2019
I've started smoking again because of this technical issues in APEX. I have almost same PC config as @Vinko1911 and this really grinds my gears. Half of time I planed for gaming I spend on researching how to fix crashes. Other half i spend in random Q's with mongoloid sqadmates. And I'm a noob also. After all, I'm a little bit upset.
I just hope that your next patch won't be about new legends and gun skins.
Kind regards,
Dubravko
March 2019
Found this in event log whenever there is a crash
even origin error reporting also crashs when i try to upload text
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: 0x10d8
Faulting application start time: 0x01d4daded78c2309
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: 0eec0ff1-eee3-4918-a53a-feb40abbdb07
Faulting package full name:
Faulting package-relative application ID:
Version=1
EventType=APPCRASH
EventTime=131970945433051556
ReportType=2
Consent=1
UploadTime=131970945473523737
ReportStatus=268435456
ReportIdentifier=3629a5da-e256-4a2c-b134-557f97e4a748
IntegratorReportIdentifier=0eec0ff1-eee3-4918-a53a-feb40abbdb07
Wow64Host=34404
NsAppName=bad_module_info
AppSessionGuid=000010d8-0001-0060-0923-8cd7dedad401
TargetAppId=W:0006c1744d7c180d7ff939cb116540ad415b00000904!00008bca6bbdadaf56f500bf1d8fe6d9393673dfcbe4!r5apex.exe
TargetAppVer=2019//02//25:05:35:36!2a1985b!r5apex.exe
BootId=4294967295
TargetAsId=469
UserImpactVector=858796304
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.256.48
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=379
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=215
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
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=93132
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.379.17763.0-11.0.115
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32684
OsInfo[19].Key=svolsz
OsInfo[19].Value=465
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.379.amd64fre.rs5_release.180914-1434
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
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=1768287860
November 2019
This issue started happening to me just a few days ago. out of the blue. Prior weeks I had the occasional freeze and close which was strange in itself and rarely happens. But now it will only play the frostbyte into and then close without even starting the game. No server selection, No lobby just crash back to origin?????? any tips?