- MASS EFFECT ANDROMEDA MODS CTD INSTALL
- MASS EFFECT ANDROMEDA MODS CTD DRIVER
- MASS EFFECT ANDROMEDA MODS CTD 64 BITS
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).
MASS EFFECT ANDROMEDA MODS CTD DRIVER
Changed the games settings, and profile settings in the NVDIA configuration panel to nearly every combination possible.Īll of the above, to still have the problem, even with the new NVDIA driver that released, and the main game instead of the Access Trial.īy that point, I was legit with my mouse cursor over the confirm refund button.īut I decided to give it a last go, because why not.Restarted my computer at least a dozen times (thank god for SSDs and fast start times).Desintalled ROG Game first (because apparently that was a problem).Reinstalled VCRedist C++ with the ones (3 of them) in the game directory (Once).Reinstalled DirectX with the one in the game directory (2 times).
MASS EFFECT ANDROMEDA MODS CTD INSTALL
- Reinstalled my graphics drivers, with clean custom install (3 times).
- Then after the 3rd crash in one play session, I started to do some research.Īnd after a week of trying to fix the problem, this is what I had done: The first time it happened I was like : "Hmmm : strange but expected, I mean this is the Access Trial, and come on : it's EA we are talking about here." The only thing lowering the settings did was delaying the moment before it happened. The problem happened at the following settings low, medium, High, Ultra, and automatic. Your hardware is not the problem: the most it will impact is the performance and FPS of the game depending on the settings you put the game at.
MASS EFFECT ANDROMEDA MODS CTD 64 BITS
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