Apex Legends Crash no error - PC (apex_crash.txt)

by KaolinAngel_TTV
Reply

Original Post

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

crash:
{
!!!unknown-module!!!: 000000018002E450
EXCEPTION_ACCESS_VIOLATION(execute): 000000018002E450
}
cpu: "Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000FF67A
ntdll: 00000000000A4AF2
ntdll: 000000000008C6D6
ntdll: 00000000000A11FF
ntdll: 000000000006A289
ntdll: 000000000009FE6E
!!!unknown-module!!!: 000000018002E450
}
registers:
{
rax = 0x000000018002E450
rbx = 0x00007FFE77EE9A20
rcx = 16
rdx = 0
rsp = 0x0000008604CBF5C8
rbp = 0
rsi = 16
rdi = 0x000000018002E450
r8 = 0
r9 = 0
r10 = 0x00007FFE824BC884
r11 = 582 // 0x00000246
r12 = 0x7FFE000C
r13 = 0x7FFE0008
r14 = 0
r15 = 0
rip = 0x000000018002E450
xmm0 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm1 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm2 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm3 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm4 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm7 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm8 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm9 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm12 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm13 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm14 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}
build_id: 1575435971
modules:
{
R5Apex: [00007FF6DC260000, 00007FF705025000]
ntdll: [00007FFE82420000, 00007FFE82610000]
KERNEL32: [00007FFE80D80000, 00007FFE80E32000]
KERNELBASE: [00007FFE7F670000, 00007FFE7F913000]
Activation64: [00007FFE4E460000, 00007FFE4E761000]
GDI32: [00007FFE80E40000, 00007FFE80E66000]
win32u: [00007FFE7F980000, 00007FFE7F9A1000]
gdi32full: [00007FFE7F9B0000, 00007FFE7FB44000]
msvcp_win: [00007FFE7F5B0000, 00007FFE7F64E000]
ucrtbase: [00007FFE7F3B0000, 00007FFE7F4AA000]
USER32: [00007FFE82030000, 00007FFE821C4000]
CRYPT32: [00007FFE80380000, 00007FFE804C9000]
MSASN1: [00007FFE7F370000, 00007FFE7F382000]
SHLWAPI: [00007FFE804D0000, 00007FFE80522000]
msvcrt: [00007FFE80FD0000, 00007FFE8106E000]
combase: [00007FFE811A0000, 00007FFE814D6000]
RPCRT4: [00007FFE81600000, 00007FFE81720000]
bcryptPrimitives: [00007FFE7FB50000, 00007FFE7FBD0000]
WINTRUST: [00007FFE7F920000, 00007FFE7F97C000]
gdiplus: [00007FFE756A0000, 00007FFE75843000]
ole32: [00007FFE80670000, 00007FFE807C6000]
MSVCP140: [00007FFE62D70000, 00007FFE62E17000]
advapi32: [00007FFE81550000, 00007FFE815F3000]
VCRUNTIME140: [00007FFE68F30000, 00007FFE68F46000]
sechost: [00007FFE81EC0000, 00007FFE81F57000]
OLEAUT32: [00007FFE80CB0000, 00007FFE80D74000]
SHELL32: [00007FFE817D0000, 00007FFE81EB5000]
cfgmgr32: [00007FFE7F4B0000, 00007FFE7F4FA000]
shcore: [00007FFE80F10000, 00007FFE80FB9000]
windows.storage: [00007FFE7FBD0000, 00007FFE8034F000]
profapi: [00007FFE7F350000, 00007FFE7F36F000]
powrprof: [00007FFE7F300000, 00007FFE7F34A000]
UMPDC: [00007FFE7F2F0000, 00007FFE7F300000]
kernel.appcore: [00007FFE7F390000, 00007FFE7F3A1000]
cryptsp: [00007FFE7F650000, 00007FFE7F667000]
WINHTTP: [00007FFE79AE0000, 00007FFE79BD0000]
IMM32: [00007FFE817A0000, 00007FFE817CE000]
VERSION: [00007FFE7B1E0000, 00007FFE7B1EA000]
bcrypt: [00007FFE80350000, 00007FFE80376000]
dxcore: [00007FFE7DFD0000, 00007FFE7DFF0000]
ntmarta: [00007FFE7E350000, 00007FFE7E381000]
clbcatq: [00007FFE81080000, 00007FFE81122000]
amsi: [00007FFE783B0000, 00007FFE783C5000]
USERENV: [00007FFE7F210000, 00007FFE7F235000]
MpOav: [00007FFE78330000, 00007FFE78376000]
WS2_32: [00007FFE814E0000, 00007FFE8154F000]
webio: [00007FFE79760000, 00007FFE797F9000]
mswsock: [00007FFE7EB00000, 00007FFE7EB67000]
IPHLPAPI: [00007FFE7E810000, 00007FFE7E84A000]
WINNSI: [00007FFE7AAF0000, 00007FFE7AAFB000]
NSI: [00007FFE81070000, 00007FFE81078000]
SspiCli: [00007FFE7F1E0000, 00007FFE7F20F000]
DNSAPI: [00007FFE7E850000, 00007FFE7E91A000]
rasadhlp: [00007FFE7ABA0000, 00007FFE7ABAA000]
fwpuclnt: [00007FFE7A3C0000, 00007FFE7A437000]
schannel: [00007FFE7E5A0000, 00007FFE7E628000]
mskeyprotect: [00007FFE5E750000, 00007FFE5E765000]
ncrypt: [00007FFE7EDD0000, 00007FFE7EDF6000]
NTASN1: [00007FFE7ED90000, 00007FFE7EDCB000]
ncryptsslp: [00007FFE5E8B0000, 00007FFE5E8D5000]
DPAPI: [00007FFE7E6B0000, 00007FFE7E6BA000]
rsaenh: [00007FFE7E670000, 00007FFE7E6A3000]
CRYPTBASE: [00007FFE7ECD0000, 00007FFE7ECDC000]
imagehlp: [00007FFE80EF0000, 00007FFE80F0D000]
gpapi: [00007FFE7DF10000, 00007FFE7DF32000]
cryptnet: [00007FFE7B1B0000, 00007FFE7B1DF000]
AVIFIL32: [00007FFE68F10000, 00007FFE68F30000]
MSACM32: [00007FFE683B0000, 00007FFE683CC000]
WINMM: [00007FFE77ED0000, 00007FFE77EF4000]
MSVFW32: [00007FFE67590000, 00007FFE675B9000]
winmmbase: [00007FFE77EA0000, 00007FFE77ECD000]
COMCTL32: [00007FFE70D00000, 00007FFE70DA9000]
d3d11: [00007FFE7C720000, 00007FFE7C97B000]
dxgi: [00007FFE7DFF0000, 00007FFE7E0DB000]
D3DCOMPILER_43: [00007FFE48A40000, 00007FFE48CAF000]
mileswin64: [00007FFE62CB0000, 00007FFE62D61000]
AVRT: [00007FFE77430000, 00007FFE7743A000]
binkawin64: [00007FFE61E20000, 00007FFE61E56000]
WLDAP32: [00007FFE81130000, 00007FFE81198000]
Normaliz: [00007FFE80FC0000, 00007FFE80FC8000]
bink2w64: [00007FFE5FB70000, 00007FFE5FBE2000]
SETUPAPI: [00007FFE80830000, 00007FFE80CA0000]
HID: [00007FFE7DF00000, 00007FFE7DF0E000]
nvldumdx: [00007FFE710C0000, 00007FFE711AF000]
nvwgf2umx: [00007FFE4E930000, 00007FFE50FCD000]
XInput1_3: [0000000000400000, 000000000041E000]
DEVOBJ: [00007FFE7F0F0000, 00007FFE7F11A000]
EasyAntiCheat_x64: [00007FFE56270000, 00007FFE56339000]
MSCTF: [00007FFE80530000, 00007FFE80665000]
TextInputFramework: [00007FFE693D0000, 00007FFE6946E000]
CoreMessaging: [00007FFE7D330000, 00007FFE7D404000]
CoreUIComponents: [00007FFE76CA0000, 00007FFE76FCA000]
wintypes: [00007FFE7B460000, 00007FFE7B5B3000]
iertutil: [00007FFE72CA0000, 00007FFE72F46000]
mscms: [00007FFE764D0000, 00007FFE7657E000]
ColorAdapterClient: [00007FFE767C0000, 00007FFE767D7000]
Windows.Internal.Graphics.Display.DisplayColorManagement: [00007FFE3DAB0000, 00007FFE3DACA000]
OneCoreCommonProxyStub: [00007FFE69B80000, 00007FFE69BF9000]
OneCoreUAPCommonProxyStub: [00007FFE75850000, 00007FFE75FBD000]
dcomp: [00007FFE7CDE0000, 00007FFE7CFBB000]
dwmapi: [00007FFE7DBA0000, 00007FFE7DBCD000]
MMDevApi: [00007FFE7AC20000, 00007FFE7AC92000]
dsound: [00007FFE568F0000, 00007FFE56989000]
wdmaud: [00007FFE569E0000, 00007FFE56A24000]
ksuser: [00007FFE77F20000, 00007FFE77F29000]
AUDIOSES: [00007FFE7AD50000, 00007FFE7AEAD000]
msacm32: [00007FFE71B30000, 00007FFE71B3D000]
midimap: [00007FFE71650000, 00007FFE7165A000]
Windows.UI: [00007FFE69470000, 00007FFE695C1000]
InputHost: [00007FFE69210000, 00007FFE6932A000]
PROPSYS: [00007FFE79D00000, 00007FFE79DEF000]
XAudio2_6: [0000000065740000, 00000000657CD000]
uiComputer: [00007FFE48510000, 00007FFE4875A000]
napinsp: [00007FFE633C0000, 00007FFE633D6000]
pnrpnsp: [00007FFE62BD0000, 00007FFE62BEA000]
winrnr: [00007FFE70DE0000, 00007FFE70DEE000]
NLAapi: [00007FFE7BF50000, 00007FFE7BF6C000]
wshbth: [00007FFE66A80000, 00007FFE66A95000]
dhcpcsvc: [00007FFE7AA00000, 00007FFE7AA1C000]
secur32: [00007FFE62730000, 00007FFE6273C000]
resourcepolicyclient: [00007FFE7D990000, 00007FFE7D9A4000]
}

Message 961 of 1,214 (2,354 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

Roll back your driver to 430.64 if you want something stable for now. You have to use the 430.64 driver which can be found with a google search. I have zero crashes with this driver , however you will only be able to get 100-140 FPS using it for some reason.            

 

 (430.64-desktop-win10-64bit-international-dch-whql)

Message 962 of 1,214 (2,312 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

Well, there is this slight problem that the driver you mentioned, doesn't exist for my gpu! I am also getting weird freezes for some reason...

Message 963 of 1,214 (2,272 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★ Novice

How is it possible that a game is STILL in such a broken state? Reddit is full of people with complains:

https://www.reddit.com/r/apexlegends/comments/edxocz/apex_legends_dxgi_errors/

https://www.reddit.com/r/apexlegends/comments/dq7scx/dxgi_error_device_hung_rtx_graphics_card/

https://www.reddit.com/r/apexlegends/comments/ddb8ge/still_getting_dxgierrordeviceremoved/

https://www.reddit.com/r/apexlegends/comments/en01ot/tired_of_trying_to_find_a_fix_for_dxgi_error/

https://www.reddit.com/r/apexlegends/comments/enyiaj/dxgi_error_device_hung/

https://www.reddit.com/r/apexlegends/comments/er4zie/dxgi_error_still_causing_me_to_not_being_able_t...

https://www.reddit.com/r/apexlegends/comments/enx1wr/dxgi_error_device_hung/

https://www.reddit.com/r/apexlegends/comments/eh1ywh/anyone_having_issues_with_random_crashes_and_bl...

https://www.reddit.com/r/apexlegends/comments/du7q4v/why_is_this_still_in_the_game_0x887a0006dxgi/

https://www.reddit.com/r/apexlegends/comments/eowyhy/new_update_dxgi_issues_curbed/

 

juuuust only a FEW from last month only. I wouldn't be even mad when I hadn't paid for the battle pass. Never again. Those random crashes totally ruin the experience. I can play all my other games for hours without a single crash on my freshly installed Windows 10 computer. The only solution that worked for me was roll back the driver from * OCTOBER. No can do. (RDR2 won't launch with that). I even underclocked my GPU because I thought there could be a problem with Apex and factory clock speeds. Nope.

 

Please sit together with Nvidia and solve this *. This is a joke for a renowned company like Respawn and EA. Thanks.

 

Ryzen 5 3600. RTX 2070 Super. 16GB DDR4RAM. MSI B450-A Pro Max.

Message 964 of 1,214 (2,047 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

[ Edited ]
★★★★ Novice

https://answers.ea.com/t5/Technical-Issues/Season-3-Zeel-s-Troubleshooting-in-depth-Guide/td-p/83066...

 

 

I tried tried 1) Clean Booting and 4) Apex Priority from that list which actually let me run the current driver with no crashes.  

Message 965 of 1,214 (2,043 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★ Apprentice

sir, do you have any fix for "DXGI_ERROR_DEVICE_HUNG".

 

i cant play the game anymore, i constantly getting this error.......

 

I have Attached Dxiag file

Message 966 of 1,214 (1,903 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

[ Edited ]
★★★ Novice

Joining bandwagon ... It's becoming a huge problem now that Ranked will start to ban people who quit midgame, which also means people who crashed. This needs to be fixed.

 

* Crashes started to occur 3 weeks ago, didn't have any problem before.

* It's the only game that crashes my setup.

* Intel 9900k, Asus Gefore 2080 Ti Strix, 32 gb RAM, SSD drive. So it's not a memory issue. All drivers up to date.

* It occurs at very random moments, may it be inmatch, or during a transition from char select to match.

* I tried a lot of things, like reducing Texture streaming, running in Admin mode, excluding Apex folder from Antivirus, disabling windows defender, etc ... No change.

 

So I opened the dump in Apex/Crashpad/db with Visual Studio, and it says :

 

Process Name: r5apex.exe : XXXX\Origin Games\Apex\r5apex.exe
Process Architecture: x64
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information: Not Present

System Information
------------------
OS Version: 10.0.18363
CLR Version(s):

Modules
-------
Module Name Module Path Module Version
----------- ----------- --------------
r5apex.exe XXXX\Origin Games\Apex\r5apex.exe 1.0.0.0
ntdll.dll XXXXWindows\System32\ntdll.dll 10.0.18362.418
kernel32.dll XXXXWindows\System32\kernel32.dll 10.0.18362.329
KERNELBASE.dll XXXXWindows\System32\KERNELBASE.dll 10.0.18362.535
Activation64.dll XXXX\Origin Games\Apex\Core\Activation64.dll 5.2.4.66

(etc ...)

Message 967 of 1,214 (1,714 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

Try updating to the latest Nvidia driver that was just uploaded yesterday. Been very stable for me. Good luck

Message 968 of 1,214 (1,707 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★ Novice
@SUPER_DOPE_55 Yes I already updated thx
Message 969 of 1,214 (1,696 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★ Novice

I turned off ingame Origin overlay, and ran smoothly without any crash for 2 hours. Will see if stable.

Message 970 of 1,214 (1,677 Views)