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

Hey @OrioStorm,

Could you please take the time and check my crash log? I have an i7 9700k oced to 4.9ghz and it is stable in any stability or stress test I have done. Played alot of games since I have it and I had no problems until now. apex_crash.txt is attached.

@scrawny633 it looks like an overclocking issue, since the instruction address that failed to execute doesn't match the instruction address that it wanted to execute.

00007FF60000201B -- this is the address that it complained about executing in the EXCEPTION_ACCESS_VIOLATION line

00007FF68D4F22FF -- this is the address that it should be executing from the RIP register

If you know hex, you can see that some of the bits that are 1 in RIP are 0 in the address it complained about.

We had common crashes like this due to overclocking (on Intel only) before we changed the instructions used to do a particular calculation. I recommend dropping your OC by 0.1 GHz and see if Apex is stable.

Stress tests can prove that your overclocking is unstable, but they can't prove that your overclocking is stable. In other words, they show you don't have problems in their tests over the time period the test runs, but they don't prove that you won't have problems under ANY workload over ANY timeframe.

This is a fundamental limitation of science, by the way. Experiments can prove a theory is WRONG if the results don't match predictions, but the fact that they do match doesn't prove that a theory is RIGHT. For example, Newtonian physics were experimentally verified for centuries, until experiments proved them wrong in the late 1800s / early 1900s (or so), and then we had to develop relativistic physics and quantum mechanics.

So, it's good to run stress tests to test your overclocking, but the fact that the tests are stable doesn't mean that you won't have problems due to overclocking. The program that fails doesn't even have to be particularly stressful; it just has to hit on a sequence of instructions and memory reads such that one stage of the CPU pipeline somewhere doesn't finish before the next stage starts.

@OrioStormThanks for the quick reply and the science lesson :D
I will reduce my clock speed then. Fortnuately I can do this with AI Suit, so I dont have to restart my PC every time.

think i may have found a solution without lowering clock speed on cpu. Ive had a stable clock of 4.20 ghz for about 3 months now and randomly got the "missing"/"bad" module crash. I claim no part in finsing this, i simply want to share it with others. what i was told to do is the following;

First, you will need to navigate to the installation folder. The easiest way to do this is right-clicking the desktop icon - > Properties -> Open File Location. Once the folder is open, you will need to find r5apex.exe, which will likely be already highlighted.

Right-click r5apex and click Properties. Navigate to the Compatibility tab and find the Disable Fullscreen Optimisation option. Check the box next to it, save and exit. The next time you launch Apex Legends it might run in windowed mode, but you should be able to safely change to fullscreen in Apex Legends' in-game options.

this is directly copy and pasted from https://www.altchar.com/games-news/588830/apex-legends-pc-crash-on-launch-bad-module-info-fixes so please check it out if it was useful to you.

today crash without apex_crash.txt , engine error 

BSoD today hapen ☹️

Another BSoD atikmdag.sys today :/

I test my computer in prime95, window mdsched.exe , 3Dmark, Intel(R) Extreme Tuning Utility, and all test pass, no problem ,no BSOD, only Apex crash ☹️

Im reinstall AMD drivers and dont help 

Me too i have amd processor with graphicas vega  8... I  cant play one game without crash or BSOD... I updated all my drivers, install, uninstall, update windows, BIOS... Its amazing if they dont repare those bugs they will lose a lot of people who can play i think.

I have solution for this BSOD ,  I had to reduce my Mhz on RAM

I have 2x8GB XMP 3200Mhz but if I set to 2800Mhz game dont crash any more.

Strange...

All my other game and benchmark work fine even on 3460Mhz  

crash:
{
atidxx64: 000000000003FEC7
EXCEPTION_ACCESS_VIOLATION(read): FFFFFFFFFFFFFFFF
}
cpu: "Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000FFBCA
ntdll: 00000000000A4AB2
ntdll: 000000000008C676
ntdll: 00000000000A119F
ntdll: 000000000006A229
ntdll: 000000000009FE0E
atidxx64: 000000000003FEC7
atidxx64: 00000000007D791F
atidxx64: 00000000007CC0A9
atidxx64: 000000000096EBF4
KERNEL32: 0000000000017BD4
ntdll: 000000000006CE71
}
registers:
{
rax = 0x810000012B9A3867
rbx = 0x000002884020F1C0
rcx = 0x000002884020F1C0
rdx = 0x000002884020F1C0
rsp = 0x0000008966A9F750
rbp = 0
rsi = 0
rdi = 0
r8 = 0x00000289E215EE68
r9 = 0x00000289E215EE60
r10 = 0
r11 = 1
r12 = 0
r13 = 0
r14 = 0
r15 = 0
rip = 0x0000028814D8FEC7
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: 1565932929

crash:
{
atidxx64: 00000000007CD91A
EXCEPTION_ACCESS_VIOLATION(read): 0000000000000000
}
cpu: "Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000FFBCA
ntdll: 00000000000A4AB2
ntdll: 000000000008C676
ntdll: 00000000000A119F
ntdll: 000000000006A229
ntdll: 000000000009FE0E
atidxx64: 00000000007CD91A
atidxx64: 0000000000131D41
atidxx64: 0000000000132B29
atidxx64: 0000000000131C11
atidxx64: 0000000000131613
atidxx64: 00000000001384EC
atidxx64: 000000000001F227
atidxx64: 000000000001F2E2
atiuxp64: 000000000000DE69
d3d11: 000000000002474F
d3d11: 0000000000025018
dxgi: 00000000000052D9
dxgi: 0000000000004F24
dxgi: 00000000000199DF
dxgi: 00000000000188CB
dxgi: 000000000000464F
RTSSHooks64: 000000000002CDDB
R5Apex: 00000000003FD2A3
R5Apex: 000000000029EEF6
R5Apex: 00000000003DA18F
R5Apex: 000000000045997D
KERNEL32: 0000000000017BD4
ntdll: 000000000006CE71
}
registers:
{
rax = 0x000001455DBE1980
rbx = 0
rcx = 0x0000014568E48240
rdx = 0x0000014574BB6FC0
rsp = 0x0000003C8266D970
rbp = 0x000001455DBE1980
rsi = 1
rdi = 0x0000014568E48240
r8 = 0x0000003C8266DA00
r9 = 16
r10 = 0x0000014536B08970
r11 = 0xFFFFFFFFF68BCD1E
r12 = 16
r13 = 0x0000003C8266DA00
r14 = 0x00000145364D8308
r15 = 0x0000014574BB6FC0
rip = 0x00007FFAF3ADD91A
xmm0 = [ [1.2, 0, 0, 0], [0x3F99999A, 0x00000000, 0x00000000, 0x00000000] ]
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: 1565932929

Two crashes in 4-5 games...