PSA: If you're getting EAAntiCheatService errors

[Mustache man]

My game kept crashing on me while compiling shaders and I found out by having Red Dead Redemption 2 also crash on me multiple times, that I had to increase the amount of Virtual Memory on my hard drive, and in turn seems to have fixed my game crashing with the log in Windows Event Viewer stating: EAAntiCheatService ExitType: 95 (267), which was the most common error I was getting.

It seems as if fixes for problems like this are extremely inconsistent so perhaps try this once you've exhausted most other options.

Before you tweak the amount of virtual memory, make sure you research the recommended amount for the amount of RAM you have and your hard drive can take to not bottleneck or decrease the lifespan of your computer, hope this helps.

[Zatick]

Originally posted by Mustache man:

My game kept crashing on me while compiling shaders and I found out by having Red Dead Redemption 2 also crash on me multiple times, that I had to increase the amount of Virtual Memory on my hard drive, and in turn seems to have fixed my game crashing with the log in Windows Event Viewer stating: EAAntiCheatService ExitType: 95 (267), which was the most common error I was getting.

It seems as if fixes for problems like this are extremely inconsistent so perhaps try this once you've exhausted most other options.

Before you tweak the amount of virtual memory, make sure you research the recommended amount for the amount of RAM you have and your hard drive can take to not bottleneck or decrease the lifespan of your computer, hope this helps.

I don't know why people keep overriding Windows paging settings, especially when they don't understand what it's used for. For the most part the paging file is just increasing the page file address space and doesn't really even get actively used, unless you have insufficient RAM for what's running on your system.

Basically apps request chunks of address space and generally don't use all of what they request, you can see this if you open task manager and go to performance > memory. The "committed" is the amount of address space in use, which fits into your physical RAM plus page file. "in use" is the amount of memory actually used, which should ideally fit inside your physical ram.

I just fired up BF6 to main menu, mem usage 2.2GB, commit 12.1GB. So if you turn your page file off, you need that extra 10GB of commit as physical RAM, otherwise it will crash with memory allocation failed errors. Having the address space pointed to your SSD doesn't bottleneck or meaningfully decrease the lifespan of your computer, it's not memory in active use.

[Zatick]

Set paging file to system managed, problem solved. Windows recommends 4GB for me, but it's currently inflated it to 27.5GB to meet the needs of the commit the apps have made, yet physical RAM usage is 22GB/32GB.

Just let Windows deal with that stuff and increase/decrease the size of the page file as necessary to stop things crashing.

[fecba]

Originally posted by Mustache man:

My game kept crashing on me while compiling shaders and I found out by having Red Dead Redemption 2 also crash on me multiple times, that I had to increase the amount of Virtual Memory on my hard drive, and in turn seems to have fixed my game crashing with the log in Windows Event Viewer stating: EAAntiCheatService ExitType: 95 (267), which was the most common error I was getting.

It seems as if fixes for problems like this are extremely inconsistent so perhaps try this once you've exhausted most other options.

Before you tweak the amount of virtual memory, make sure you research the recommended amount for the amount of RAM you have and your hard drive can take to not bottleneck or decrease the lifespan of your computer, hope this helps.

Was your issue when it was compiling shaders?