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

[TTvMike_Nitrate]

My game crashes and it either tells me my steaming budget is too high (I have gtx 1060 6b) and i have my steaming budget set to 2gb and it says my pc has 128tb of virtual memory. The other crash text i got told me there was more info in the apex_txt

---------------------------
Apex Crash - Out of Memory
---------------------------
Apex crashed because it ran out of memory.

The most common causes of this are:

• "Texture Streaming Budget" is too high in your video settings. Lowering this can help.

• All other programs plus Apex combine to use too much memory. Quitting other programs can help.

• Your Windows page file is set too small. Increasing the page file size can help. (The page file lets Windows move less important memory to disk until it's needed again.)

TECHNICAL INFORMATION:
• Apex was using 3.0 GB of physical memory.
• Apex was using 6.8 GB of virtual memory.
• Apex failed to allocate 2.0 MB of memory.

• Your PC has 16.0 GB of memory physically installed.
• Your PC has 128.0 TB of virtual memory (with the page file).
• After Apex exited, your PC memory load is about 64%.

Ctrl+C in this window will copy this message so you can paste it as text.

---------------------------
OK
---------------------------

[OrioStorm]

@TTvMike_Nitrate, the apex_crash.txt indicates that the OS failed to allocate 2 MB for streaming a texture from disk.

The most likely cause in your case for running out of memory is that you had one or more other programs running that were using most of your memory (64%). A common cause of this is having lots of tabs oben in your web browser; on my machine right now, the web browser is using 36% of my memory that's in use, my various copies of Visual Studio for programming use 40%, and everything else uses the last 24%.

If you open Task Manager (shortcut key Ctrl + Shift + Escape), make sure that you've selected "more details" at the bottom, and click on the "Memory" column of the "Processes" tab, you can sort your programs by memory and see where all that memory is going. You can also see a summary over time of memory and CPU usage and other things on the "Performance" tab.

Freeing up more memory before running Apex should not only keep you from running out of memory as you play, but it is likely to also get you better performance, since it will avoid swapping memory to disk. Swapping memory to disk is likely to feel like frequent hitching in the game, or low/stuttering frame rate.

Now, with 128 TB of virtual memory, I would expect the OS would never fail to allocate. So, I decided to ask the internet why this could happen! I found this article: https://support.microsoft.com/en-us/help/4055223/memory-allocation-errors-can-be-caused-by-slow-page... 

I think that's a likely culprit. It seems highly unlikely that you actually have 128 TB of virtual memory available, because then your Windows page file would be using 128 TB of hard drive space, and that's a bit insane (you couldn't use that 128 TB for anything else). So Windows probably reports 128 TB of virtual memory since it has permission to grow the page file as needed. However, that article says that Windows may not be able to grow the page file fast enough, and that can cause programs to run out of memory. That would explain what happened in your case.

I'm going to research whether there's anything we can do to mitigate this problem. However, since that article by Microsoft says that Microsoft's compiler runs into this problem on Microsoft's operating system, I'm not too hopeful that we can find a solution that Microsoft couldn't.

[OrioStorm]

@yLewis7PT, it looked like your game tried to read past the end of an array. I've posted a bug to our internal database for another programmer to look into how that might happen. Thank you for your report!

[Nem3sis_XVI]

Played this game on 15/07/2019 and won two games out of 4. On 16/07/2019 my game started to crash and gave this bug report. Can anyone help me up on this.

[Anonymous]

Repair Easy Anti Cheat service

I will do this.

Repair Apex Legends

I have done that multiple times already.

Delete Origin cache

I will do this but I have just recently installed Origin (maybe it is caused by Beta version).

Updating Graphics drivers

I have the latest one.

Fix corrupt system files

I will run this.

FPS locking

I have it locked to 72fps.

Turn off overlays

I have everything disabled except Nvidia Shadowplay - which I use.

Ingame settings

I have everything on lowest possible settings.

Overclocking

I have stable clocks (OC but tested for many hours) it is possible that it is a cause but I won't downclock my cpu just for one game.

Disable full-screen optimization for Apex Legends

I have already done that.

Change EasyAntiCheat.exe priority to Low

This seems like strange workaround, also I don't want to do this each time I start a game.

M5 Gaming bios

I have already got latest version since it came out.

Thanks for these suggestions !

[IntuitiveGerbil]

For me it was toggling Shadowplay for Nvidia cards. Turning it off, running the game, restarting, turning it on, then starting the game again confirmed the issue and resolved it. This was after I had tried the following:

• Repair
• Reinstall
• Uninstalling all unrelated C++ Redistributables and reinstalling related ones (ones found in the Origin folder)
• Trying the +fps_max 60/144/100 fix
• Disabling antivirus
• Updated GPU drivers
• Running DISM (Windows 10) to fix OS issues
• Disabling Origin overlay
• Reinstalling Origin
• Repairing EAC
• Reinstalling EAC for Apex
• Running both EAC and Apex as admin
• Disabling Discord/Discord overlay

My game would Crash To Desktop as soon as the intro movie played and the first loading icon displayed in the bottom right, so I couldn't test out other things like toning down Texture Streaming settings (probably could have done it through my GPU control panel though). Only thought about trying to disable Shadowplay from user @Anonymous's reply. Hope this manages to help someone when they stumble upon this thread.

[xNo_Ragrets]

Could you please help me with my errors.  Have been crashing almost every game since the update.  Here is the last error log I received, thanks.

crash:
{
ui: 000000000007E6AF
EXCEPTION_PRIV_INSTRUCTION: C0000096
}
cpu: "AMD Ryzen 7 1700 Eight-Core Processor "
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000EBF30
ntdll: 00000000000A3167
ntdll: 000000000008B5E6
ntdll: 000000000009F7DD
ntdll: 000000000000D856
ntdll: 000000000009E70E
ui: 000000000007E6AF
R5Apex: 00000000002FBB50
R5Apex: 00000000002FC728
R5Apex: 0000000000456666
R5Apex: 0000000000456A57
R5Apex: 00000000004552E7
R5Apex: 0000000000457012
KERNEL32: 0000000000014034
ntdll: 0000000000073691
}
registers:
{
rax = 0x0000019BBC8339E8
rbx = 120
rcx = 0x0000019BCF15D810
rdx = 0x00007FFEDD2E7620
rsp = 0x00000051F735D110
rbp = 0x00000051F735D210
rsi = 0x00007FF76E607DA0
rdi = 0x0000019BCF15D870
r8 = 0x0000019BBC8339D8
r9 = 0x00000051F735D0E0
r10 = 0x0000019BBC8338D8
r11 = 4
r12 = 8
r13 = 0
r14 = 0x0000019BCF15D810
r15 = 0x0000019BF4DC7B20
rip = 0x00007FFEDD1AE6AF
xmm0 = [ [0.49000001, 0, 0, 0], [0x3EFAE148, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [0.50999999, 0, 0, 0], [0x3F028F5C, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm3 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm4 = [ [-0, 0, 0, 0], [0x80000000, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [-1, 0, 0, 0], [0xBF800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm6 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [0.49000001, 0, 0, 0], [0x3EFAE148, 0x00000000, 0x00000000, 0x00000000] ]
xmm9 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [1, 1, 0, 0], [0x3F800000, 0x3F800000, 0x00000000, 0x00000000] ]
xmm12 = [ [0.5, 0, 0, 0], [0x3F000000, 0x00000000, 0x00000000, 0x00000000] ]
xmm13 = [ [48, 48, 0, 0], [0x42400000, 0x42400000, 0x00000000, 0x00000000] ]
xmm14 = [ [18, 0, 0, 0], [0x41900000, 0x00000000, 0x00000000, 0x00000000] ]
xmm15 = [ [60, 60, 0, 0], [0x42700000, 0x42700000, 0x00000000, 0x00000000] ]
}
build_id: 1562876448

[OrioStorm]

@xNo_Ragrets, that's an odd one. The exception is "EXCEPTION_PRIV_INSTRUCTION", which means that a user program tried to execute one of the few instructions that is only allowed to execute for the operating system (as a security measure).

However, the instruction that it complains about isn't a priviledged instruction. In fact, it must have executed that very same instruction a few cycles earlier without any complaints, with nearly the same destination address.

....

00007FFBDEF6E68A movss dword ptr [rdi+00000000000002A8h],xmm0       <--- this nearly identical one worked
00007FFBDEF6E692 call qword ptr [rsi+00000000000000A0h]
00007FFBDEF6E698 movaps xmm1,xmm9
00007FFBDEF6E69C lea rdx,[00007FFBDF0A7620h]
00007FFBDEF6E6A3 mov rcx,r14
00007FFBDEF6E6A6 mulss xmm0,xmm8
00007FFBDEF6E6AB subss xmm1,xmm0
00007FFBDEF6E6AF movss dword ptr [rdi+00000000000002ACh],xmm1      <--- this gave the "priviledged" crash
00007FFBDEF6E6B7 call qword ptr [rsi+0000000000000090h]

.... 

So, the most likely cause of this crash is that your CPU malfunctioned, which is usually caused by overclocking or overheating.

[IntuitiveGerbil]

Okay after a day the crashing is back, I've gone ahead and done a reinstall of Windows because why not. No luck. Here's the only crash log I have since Apex doesn't want to generate new ones now. Guess it's back to Titanfall for now  

[OrioStorm]

@IntuitiveGerbil unfortunately that crash is from an old build. Fortunately, we've fixed that crash (which only happened on exit), I think since the start of season 2. It's hard to remember which patch fixes which bugs!

If the game quits without generating an error message or a crash text file, I think that probably means the GPU is what crashed. Unfortunately, I don't know of any way to find out when that happened to give a user-friendly error message, or to give us or the GPU maker any info. The OS has hooks that let you respond to a CPU crash, which is how the apex_crash.txt works.