I found the problem.
** This solution is for people that have perflib/perfnet errors when they go in start menu, event viewer, windows, application around the times the game crashed **
It's due to windows superfetch. You have to disable the service. It tries to pre fetch the data based on what it expects you to do, like what games you usually open at time X etc. When you have a drastic texture change happening, like going out of a building, dropping, respawning, spectating, it tries to use the texture data stored by superfetch and fails to do so. Windows perfomance monitor catches the error and terminates the program.
The shittier your computer is, the more often it happens, but it doesnt matter it could happen on any system.
You have to disable superfetch in the services. It might also be called prefetch or sysmain. It's also compltely useless on any modern system and HDD
Google how to do it. You need a small registry tweak.
the tldr if you're tech friendly and on windows 10: (i think it is the same patch but different names on previous versions)
STEP 0: optional: start menu, restore point, create a restore point (in case you dont trust yourself playing with the registry, back it up)
STEP 1: start menu, services.msc, (stop it then disable it), disable superfetch and or prefetch and or sysmain
STEP 2: start menu, regedit, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters
, change the value of the key "enable prefetcher" to 0. (doesnt matter if hexa of decimal 0 is still 0)
STEP 3: reboot your computer, check again in services if the service is still off.
Technically, the responsible for crashing apex is the performance monitor. But I do no recommend turning that one off. If you're really desperate though, it could be the final solution
I ALSO RECOMMEND THE FOLLOWING:
- start menu, task manager, go through that list and turn off or chill out the frequency on all those useless tasks like hourly microsoft office updates etc
- start menu, services.msc, stop and disable windows search
- make sure you DO NOT have apex, origin and easycheat on "run as admin" from trying ideas from this thread. This could make things unstable.
P.S. the FPS cap works because you just use less data from the prefetch. You wont need to pull it as often with a lower cap. It's always a good idea to try that, and lower any texture related graphic options until you get it to work
What SHOULD happen if you had the same error type as i did: you'll get lag spikes when it used to crash, the lag spike when you just know it's gonna crash. But then it doesnt, and 2s later you're back to shooting smoothly
