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

@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-file-growth 

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.