Restart happens, games settings set to ULTRA, no problem playing a 3 hour gaming session on Eos, with lots of saves, terminals accessed, conversations and loading screens. And Paf! Suddenly, my computer says that it needs to restart to validate the changes (something it didn't do before)! And that my paging file is now 16384Mo big. So when I modified it for the last time, I ticked the box on top "Automatic management of the file for all volumes". The first two times I changed it for the option : managed by system, it didn't work. I had a personalized sized file of between 200Mo and 1024Mo. So when you have it disabled, or with a personalized sized, it can get filled. It basically stores stuff in it that is being used for a running program, but that doesn't need to be put in the much faster RAM itself. Now for the computer illiterate among you, this file is a part of your hard disk that your OS uses as a slower RAM.
Separate paging files can be created, or, in the contrary, be missing from certain volumes, thus creating problems. Two : You have multiple disks, or volumes.
Windows automatically reduces or disables the paging file because of it, because it forces a lot or reads/writes on it, and that wears them down faster than normal drives. You see, The changes to the pagination file size do not always validate upon changing it, especially on Windows 10! This is a recurring issue apparently, and happens for 2 main reasons. A few users had mentioned that it solved their issues so I had tried to do the same. One of the actions I had done was also to resize my memory paging file a few times (the famous pagefile.sys).
Windows 10 64 bits Family Edition (upgraded from 8.1 64 bits Family Edition).Īll of this watercooled (Custom EK Watercooling) 2 separate cooling loops - one for CPU, one for GPU.Īnd while researching the problem, I saw people with GTX 1080 SLIs, which have 8GB of VRAM, so double mine, and still had the same problem. (For Game Library, where MEA is installed) HDD 2To WD RED Server Grade Hybrid Disk with 32MB cache. (For OS, where Origin client is installed) SSD 256Go Samsung 850 Pro. Intel I7-5930k, 6 cores, 3.5GHz, with Hyper threading (overclocked to 4.2GHz).ĪSUS GTX980 STRIX 4GB VRAM (can't remember the precise overclock).ġ6Go RAM (4x4Go) Corsair Dominator Platinum DDR4, at 2166MHz. Ok so first my system specs : they don't matter, but are here to prove a point, which is that your components are not the problem for this issue. Wall of text incoming though, so brace yourselves. So if you are still experiencing this bug, stick around. It happened to me since the start of the trial, and yesterday, I finally solved it. It was often accompanied by a Windows warning pop-up saying that you are running of memory and should close the following programs in order not to lose data.
The game would freeze and force you to kill the game through the task manager. The error message would say that a DirectX rendering error happened due to a lack of memory. It had a tendency to happen while saving, accessing terminals, loading, or cinematics/conversations. One of these pestering insects was a crash that would happen after some time spent playing, regardless of place (Tempest, planet-side, nexus, etc.). Ok, so by now everyone that has actually played the game has realized that there is a few bugs ( cough "few" cough) in Mass Effect Andromeda