Forum Discussion
Same exact crash as you.
Running an i7-8700k @ 4.9GHz OC'd and 32GB of GSKILL Trident Z @ 3200 MHz (not OC'd)
crash: { R5Apex: 00000000002F2DCA EXCEPTION_BREAKPOINT: 80000003 } cpu: "Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz" ram: 32 // GB callstack: { KERNELBASE: 000000000008669C ntdll: 00000000000A80CB ntdll: 000000000008FD36 ntdll: 00000000000A468F ntdll: 0000000000004BEF ntdll: 00000000000A33FE R5Apex: 00000000002F2DCA R5Apex: 00000000004C0B56 R5Apex: 00000000004C0F47 R5Apex: 00000000004BF767 R5Apex: 00000000004C1502 KERNEL32: 00000000000181F4 ntdll: 000000000006A251 } registers: { rax = 1 rbx = 0x0000000978303260 rcx = 0 rdx = 4 rsp = 0x000000090115FA30 rbp = 1473 // 0x000005C1 rsi = 0x0000015F2B14A6E0 rdi = 1200 // 0x000004B0 r8 = 0 r9 = 242998 // 0x0003B536 r10 = 447828 // 0x0006D554 r11 = 447828 // 0x0006D554 r12 = 448215 // 0x0006D6D7 r13 = 448215 // 0x0006D6D7 r14 = 1 r15 = 0x0000015AC3F38670 rip = 0x00007FF73CFA2DCA xmm0 = [ [4667748, 0, 0, 0], [0x4A8E72C8, 0x00000000, 0x00000000, 0x00000000] ] xmm1 = [ [22227366, 0, 0, 0], [0x4BA994D3, 0x00000000, 0x00000000, 0x00000000] ] xmm2 = [ [5.2441268, 0, 0, 0], [0x40A7CFE3, 0x00000000, 0x00000000, 0x00000000] ] xmm3 = [ [24478264, 0, 0, 0], [0x4BBAC11C, 0x00000000, 0x00000000, 0x00000000] ] xmm4 = [ [2416850.3, 0, 0, 0], [0x4A138349, 0x00000000, 0x00000000, 0x00000000] ] xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ] xmm6 = [ [2416850.3, 0, 0, 0], [0x4A138349, 0x00000000, 0x00000000, 0x00000000] ] xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ] xmm8 = [ [1904400, 7617600, 17139600, 3.4028235e+38], [0x49E87880, 0x4AE87880, 0x4B82C3C8, 0x7F7FFFFF] ] xmm9 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ] xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ] xmm11 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ] xmm12 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ] xmm13 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ] xmm14 = [ [13.8, 0, 0, 0], [0x415CCCCD, 0x00000000, 0x00000000, 0x00000000] ] xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ] } build_id: 1553899726
No other game crashes like APEX, its getting stupid at this point. RTX 2080ti
crash:
{
R5Apex: 00000000002F2DCA
EXCEPTION_BREAKPOINT: 80000003
}
cpu: "Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz"
ram: 32 // GB
callstack:
{
KERNELBASE: 000000000008669C
ntdll: 00000000000A80CB
ntdll: 000000000008FD36
ntdll: 00000000000A468F
ntdll: 0000000000004BEF
ntdll: 00000000000A33FE
R5Apex: 00000000002F2DCA
R5Apex: 00000000004C0B56
R5Apex: 00000000004C0F47
R5Apex: 00000000004BF767
R5Apex: 00000000004C1502
KERNEL32: 00000000000181F4
ntdll: 000000000006A251
}
registers:
{
rax = 1
rbx = 0x0000001CD61427C0
rcx = 0
rdx = 1
rsp = 0x0000001CDEE0FB50
rbp = 1719 // 0x000006B7
rsi = 0x000001B195DDDA40
rdi = 836 // 0x00000344
r8 = 0
r9 = 40657 // 0x00009ED1
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x000001AF72762D10
rip = 0x00007FF770A12DCA
xmm0 = [ [2303563, 0, 0, 0], [0x4A0C992C, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [10969346, 0, 0, 0], [0x4B276102, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [5.7619042, 0, 0, 0], [0x40B86185, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [13272909, 0, 0, 0], [0x4B4A874D, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [1.8916884e-08, 0, 0, 0], [0x32A27EAB, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [1.8916885e+08, 0, 0, 0], [0x4D3467CD, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [1.9501056e+21, 4.3877375e+21, 3.4028235e+38, 3.4028235e+38], [0x62D36E4E, 0x636DDC17, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm9 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm12 = [ [80000000, 0, 0, 0], [0x4C989680, 0x00000000, 0x00000000, 0x00000000] ]
xmm13 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm14 = [ [13.8, 0, 0, 0], [0x415CCCCD, 0x00000000, 0x00000000, 0x00000000] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}
build_id: 1553899726
- 6 years ago
I'm also using 2x 1080 Ti in SLI although I'm not sure this is really related.
- 6 years ago
just update the drivers on your vieo card. it worked for me
- 6 years ago
I had this issue in the past. I had lowered the texture streaming budget to 'None' in game settings. Game kept stuttering and crashing after that change.
Ideally, your texture streaming budget should be close 80-90% of your GPU memory, otherwise major load goes on on-board graphics in CPU for rendering the game and the game crashes when CPU can't provide enough resources.So, keep your texture budget around that range. Let your GPU do the heavy lifting (the only job it was designed for).
- 6 years ago
@OrioStorm My pc crash behind the last updates, but i didnt have any crash report.. Juste my pc freeze..
- 6 years ago
Same here,yesterday was fine, today 6 out of 6 game crashed. Never had this kind of issue before.
i5-9600k @ 5GHz
RTX 2060 @ 2050MHz
16GB RAM @ 3000MHz - 6 years ago
yep having the same problem
- 6 years ago
Continuing to experience this crash.
This is clearly an issue with the game, and not the Overclocks on 70+ pages worth of crash reports.
Apex Crash - Overclocked/Overheated?
Apex crashed in a way usually caused by a CPU that is overclocked or overheating.
Specifically, the CPU reported that it couldn't execute an instruction it didn't want to execute. More precisely, the CPU's memory controller said it didn't have permission to execute one address, but the CPU's registers said it wanted to execute a different address.
More technical information should be available in "apex_crash.txt" in your Documents folder.
Ctrl+C in this window will copy this message so you can paste it as text.
OK
- 6 years ago
mileswin64 is the error I keep getting, with two no-error crashes.
- 6 years ago
Disable your LEDS in motherboard BIOS should fix it.Give that a try it fixed mine and like 4 other friends of mine
- 6 years ago
{
R5Apex: 000000000029BC3F
EXCEPTION_ILLEGAL_INSTRUCTION: C000001D
}
cpu: "Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 0000000000055447
ntdll: 00000000000AE531
ntdll: 0000000000096606
ntdll: 00000000000AA57D
ntdll: 000000000003FD23
ntdll: 00000000000A96EA
R5Apex: 000000000029BC3F
R5Apex: 0000000000459076
R5Apex: 0000000000459467
R5Apex: 0000000000457CB7
R5Apex: 0000000000459A22
KERNEL32: 0000000000008364
ntdll: 000000000006E851
}
registers:
{
rax = 0x0000025CBEC24F70
rbx = 761 // 0x000002F9
rcx = 761 // 0x000002F9
rdx = 60455 // 0x0000EC27
rsp = 0x00000094A6A58530
rbp = 0x00000094A6A5E8F0
rsi = 51
rdi = 0x0000025E23C88500
r8 = 0x00000094A6A59D28
r9 = 0x0000025CBE946A40
r10 = 943 // 0x000003AF
r11 = 1
r12 = 761 // 0x000002F9
r13 = 0x0000025CBE94EA68
r14 = 0x0000025CBEC24F20
r15 = 0x0000025CBE971B04
rip = 0x00007FF7549ABC3F
xmm0 = [ [-1759.41, 0, 0, 0], [0xC4DBED1F, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [1.9044e+12, 0, 0, 0], [0x53DDB38B, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [-5977.29, 16451.4, 0, 0], [0xC5BACA52, 0x468086CD, 0x00000000, 0x00000000] ]
xmm3 = [ [3.7326241e+12, 0, 0, 0], [0x5459446F, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [3.7326241e+12, 0, 0, 0], [0x5459446F, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [2.789479e+08, 2.789479e+08, 2.789479e+08, 2.789479e+08], [0x4D850342, 0x4D850342, 0x4D850342, 0x4D850342] ]
xmm8 = [ [2.789479e+08, 2.789479e+08, 2.789479e+08, 2.789479e+08], [0x4D850342, 0x4D850342, 0x4D850342, 0x4D850342] ]
xmm9 = [ [6382.9268, 5886.2163, -4263.9609, 0], [0x45C7776A, 0x45B7F1BB, 0xC5853FB0, 0x00000000] ]
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: 1570643705- 6 years ago
my new week of play is start with this error
- 6 years ago
89 minute ban. 5 days in a row of non-stop crashing. Is this a joke? Make it so we can rejoin if we D/C....? This is so * stupid.
- 6 years ago
Hi I focus on Ranked Play, I am now on I think 8 crashes. It forgave the first 6 I think. I now have a second Penalty for 10min.
I thought they can see if you ALT F4 and this is the penalty. Cant you see if it was the game crashed?
Soon I wont be able to play? First I had the Level 500 bug and could not play, now this?
Can EA representative please reply to this?
PC: 9900k, 1080ti, 16gig ram, Win10
ID: Prof_Kong
- 6 years ago
8 Kill 3 Assit in Platinium league and got crash.Well done EA.Do something seriously.
We are facing with this issue for 2 weeks.Fix your god damn game.
I got Penalty and -72 points seriously WTF u doing?There is no feedback from respawn or EA.Give us an INFORMATION at least...
- 5 years ago
mine crashes without any errors as well it happens mid game or late game. 2080 TI OC :/ only happend this week its either the nvidia driver or the new season 4.
- 5 years ago
My game keeps crashing after every 2nd game, its becoming unplayable, the first game runs flawlessly but halfway through the second game I will crash without an error, without the game freezing, all that happens is the game closes down on its own. This is the only game that does this, my specs are i7-8700k and GTX 1080ti, running the game on an SSD, ive tried changing drives from my OS to another, both SSDs, yet to no avail, ive also tried deleting the entire game and reinstalling it, again not working, i see a lot of people are getting this issue, i just hope to god someone can find a way to fix it because it seems like the devs are not even giving any information about these crashes at all.
- 4 years ago
yeah, when they going to fix this piece of * * ? is been over 2 years and still they can't fix it
About Apex Legends Technical Issues
Recent Discussions
- 32 minutes ago
- 50 minutes ago
- 2 hours ago