Re: Mass Effect Andromeda directX crash

@UltrasonicOwl

Since there are a variety of different kinds of DirectX error messages, yours (anyone other than the author of the OP here) must be based on exactly the same circumstances, the same error, and you must look up and follow exactly the same solution as solved the problem for that member. 

For meone or more of the following combined solved it, though I don't know which step:

- installed nvidia driver v382.05

- set/increased virtual memory size manually 1024 - 24576

- changed aspect ratio in game from "1080p auto" to "custom"

- set aspect ratio to "75"

- set shadows to "medium" almost everything else is on "high"

- set game from "fullscreen" to "borderless windowed"

Previously before Tempest on the station i got crashes in every 5-15 minutes,

Now I have played for like 3 hours+

I hope it helps you guys!

I have been closely following whatever "progress" has been made on this issue, and thus far none of the recommended solutions seem to resolve the immediate crashing with this game.

I mean, "unplayable" is a term that is often throw around loosely these days, but this is legitimately unacceptable.

The game crashes before I can even get into the settings to make adjustments.

This issue has now officially been occurring for the last three NVIDIA driver updates (at least for me).

Specs:

MSI Gaming X 1080's in SLI.

5960x @ 4.5GHz.

32GB of RAM.

Windows 10 (not the Creator's Update).

I noticed that someone had underclocked their GPU, and while that might have resolved it for them, unfortunately I don't have the same luck.

Obviously, we shouldn't HAVE to even tinker to this degree to prevent the game from crashing minutes later.

I digress, but clearly I'm not the only one here who has been expressing concern for more than a month now.

I've tweeted numerous times with screenshots, tagging their official Facebook, Twitter, etc. showcasing the errors on various occasions to no avail.

My concern now is that it seems I'm given no choice but to refund the game, as thankfully each time the game has crashed while testing; it hasn't even been more than an hour of in-game time.

Truthfully though, I haven't had a game in recent years do anything quite like this... and as I'm sure you can tell by my response here, it's a major bummer to say the least.

Fixed for me with the following changes (don't ask me which one did it):

- 1.06 patch

- AMD driver 17.5.1

- xfire manually enabled

- limited frame rate to 59 via user.cfg

- latest windows pattches, but not creator's edition

Edit: that only enabled me to play the game at all. I still get the error but after maybe half an hour of gameplay. I also did the following: "but try to lower the graphical senttings and deactivating VSYNC, Triple Buffer and HDR in Video options". I also set the folloing options in user.cfg:

WorldRender.MotionBlurQuality 0
WorldRender.MotionBlurMaxSampleCount 0
WorldRender.MotionBlurEnable 0
WorldRender.MotionBlurForceOn 0
WorldRender.MotionBlurFixedShutterTime 0
WorldRender.MotionBlurMax 0
WorldRender.SpotLightShadowmapEnable 0
WorldRender.SpotLightShadowmapResolution 256
WorldRender.TransparencyShadowmapsEnable 0
WorldRender.LightTileCsPathEnable 0

It ain't that pretty anymore but at least it is playable:

System: 

AMD 8320, ie the bare minimum

2xR9 285 2 GiB

12 GiB RAM

---

@madhiding wrote:
Upgrade your ram to 64Gb, set the pagefile to 0. You will get the best performance as possible.
Or set pagefile to 32GB to increase Andromeda's abnormal high memory needs.But this will decrease performance especially in Tempset.

---

Upgrading the RAM to 64GB is unrealistic, even for most gaming enthusiasts. I have a pretty strong rig, and I was only able to budget for 16 GB (2x 8GB DDR4). The only way to get 64 would be to have 4x 16GB, and 16GB singles only seem to exist for DDR3, which are hard to find unless you know exactly what you're looking for. No game, even at max settings, has ever recommended anything over 16GB, to my knowledge.

---

@madhiding wrote:
Well, this game does. Let me tell you how this game uses so much ram than anyone ever expected.
1. I reply to Bruzur because his spec is 1080 SLI, this is for 4K resolution.
2.High resolution comes with a high virtual memory committed. Normally is 11GB committed virtual memory in Mass Effect for a single card to transfer to Vram. SLI will double the size resulting a whopping 22GB committed virtual memory.
3.Mass Effect program itself also has a high 8GB committed virtual memory for ram to use.
4.These two types of virtual memory cannot exceed actual physical ram memory plus page file size. This sucks because you have still a lot ram left but cannot be used and you already uses 30GB virtual memory.
5.If you set pagefile to 0, you will get best performance in cutscene and Tempest because they need fast swapping files, but the game will crashes soon or later.
6.If you set pagefile to 32GB then you lag in various cutscene and stutter the hell out of Tempest because suddenly increase 1GB swap file to pagefile is hard for SDD or HDD.
7. I use 1080Ti SLI at 5120x2160 DSR with max setting except no AA. I tested this game myself and it happens every time. Using process explorer you can see Mass Effect easily reach 22-23GB private bytes and it's own 8GB bytes.
8. You can test the explanation yourself to see if it matches your experience. And the game sucks anyway especially in memory management.

---

I also have mine in SLI for 4K (I'm using GTX 1070s though), and so far I've managed to get pretty decent results with most of the game with 16GB RAM and no more than ~10GB of page file. The only slow down happens in the Tempest, which seems to happen even with the larger page file size.

Will they fix this memory problem and HDR? Can I get a refund even if it's passed the timeframe? I'm trying to play at 4K with 2 1080Ti but I don't have 40gb of spare SSD place to Pagefile it.

It's so ridiculous. WOW TOTAL FAIL. I've never seen a so poorly coded game.

@nickson5 wrote:

Will they fix this memory problem and HDR? Can I get a refund even if it's passed the timeframe? I'm trying to play at 4K with 2 1080Ti but I don't have 40gb of spare SSD place to Pagefile it.

It's so ridiculous. WOW TOTAL FAIL. I've never seen a so poorly coded game.

---

If you have 2 1080Ti's, then you shouldn't need 40GB for the page file size. I'm using 2 1070s, and I can get away with about 10GB of page file size on the core drive. If you're trying to get Max settings AND have 4K, then you need to readjust your expectations. We're not quite there yet with current games (you'd need a ridiculously expensive rig to try). We are only in the birth of games built to acknowledge the existence of 4K, it's going to take a while before it all settles out, and the developers get comfortable with the new technology. You also have to factor in the fact that Frostbite wasn't originally intended for this kind of stuff, so to even have a functioning game at all is a small miracle in itself.

This actually worked for me, i've tried everything, even reinstall windows, and nothing the i tried this and actually work, thanks