mass effect: andromeda won't launch

@PhAse-Shifter-nz

NP, but please also try to run it from your Admin account.

ME:A won't run from the admin account either ☹️ I've tried repairing the runtimes in the ME:A folder, no go. All of my installed runtimes seem to be up to date. 

Here are the runtimes from both the admin and standard accounts.

I took this from a program called AppCrashView, not sure if it helps.

Version=1
EventType=BEX64
EventTime=131785359641862033
ReportType=2
Consent=1
UploadTime=131785359643667237
ReportStatus=268435456
ReportIdentifier=0a01afb1-2c4b-4c78-82cf-193d655e6b24
IntegratorReportIdentifier=ab9535f7-e1e9-4dd0-bb4d-ef5ba217248a
Wow64Host=34404
NsAppName=MassEffectAndromeda.exe
AppSessionGuid=00004050-0001-0087-a408-ee0c1632d401
TargetAppId=W:0006c03f842b703466c36178c064c8eac37400000904!0000175fa5a826e9f796fc99c5e57a1622756019268f!MassEffectAndromeda.exe
TargetAppVer=2017//07//19:16:04:01!4829c01!MassEffectAndromeda.exe
BootId=4294967295
ServiceSplit=2171076944
TargetAsId=863
IsFatal=1
Response.BucketId=405df458358c34b936f8cf596e6a53c3
Response.BucketTable=5
Response.LegacyBucketId=1655300846070158275
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=MassEffectAndromeda.exe
Sig[1].Name=Application Version
Sig[1].Value=1.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=596f82f1
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_a38e
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Offset
Sig[6].Value=PCH_18_FROM_ntdll+0x000000000009AA04
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=0000000000000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.17134.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=5129
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=a38e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=a38eda4264ca4c2e952b13799f3c5656
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=16d5
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=16d5b84b43edbe1adc9fbf0af3d892ed
UI[2]=D:\Origin Games\Mass Effect Andromeda\MassEffectAndromeda.exe
LoadedModule[0]=D:\Origin Games\Mass Effect Andromeda\MassEffectAndromeda.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[4]=D:\Origin Games\Mass Effect Andromeda\Core\Activation64.dll
LoadedModule[5]=C:\Windows\System32\CRYPT32.dll
LoadedModule[6]=C:\Windows\System32\ucrtbase.dll
LoadedModule[7]=C:\Windows\System32\MSASN1.dll
LoadedModule[8]=C:\Windows\System32\WINTRUST.dll
LoadedModule[9]=C:\Windows\System32\msvcrt.dll
LoadedModule[10]=C:\Windows\System32\RPCRT4.dll
LoadedModule[11]=C:\Windows\System32\advapi32.dll
LoadedModule[12]=C:\Windows\System32\sechost.dll
LoadedModule[13]=C:\Windows\System32\USER32.dll
LoadedModule[14]=C:\Windows\System32\win32u.dll
LoadedModule[15]=C:\Windows\System32\GDI32.dll
LoadedModule[16]=C:\Windows\System32\gdi32full.dll
LoadedModule[17]=C:\Windows\System32\msvcp_win.dll
LoadedModule[18]=C:\Windows\SYSTEM32\MSVCP120.dll
LoadedModule[19]=C:\Windows\SYSTEM32\MSVCR120.dll
LoadedModule[20]=C:\Windows\System32\SHELL32.dll
LoadedModule[21]=C:\Windows\System32\cfgmgr32.dll
LoadedModule[22]=C:\Windows\System32\shcore.dll
LoadedModule[23]=C:\Windows\System32\combase.dll
LoadedModule[24]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[25]=C:\Windows\System32\windows.storage.dll
LoadedModule[26]=C:\Windows\System32\shlwapi.dll
LoadedModule[27]=C:\Windows\System32\kernel.appcore.dll
LoadedModule[28]=C:\Windows\System32\profapi.dll
LoadedModule[29]=C:\Windows\System32\powrprof.dll
LoadedModule[30]=C:\Windows\System32\FLTLIB.DLL
LoadedModule[31]=C:\Windows\System32\IMM32.DLL
LoadedModule[32]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[33]=C:\Windows\system32\rsaenh.dll
LoadedModule[34]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[35]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[36]=C:\Windows\System32\imagehlp.dll
LoadedModule[37]=C:\Windows\SYSTEM32\gpapi.dll
LoadedModule[38]=C:\Windows\System32\cryptnet.dll
LoadedModule[39]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[40]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[41]=C:\Windows\System32\NSI.dll
LoadedModule[42]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[43]=C:\Windows\SYSTEM32\winmmbase.dll
LoadedModule[44]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[45]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[46]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[47]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[48]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[49]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[50]=C:\Windows\SYSTEM32\DSOUND.dll
LoadedModule[51]=C:\Windows\SYSTEM32\WTSAPI32.dll
LoadedModule[52]=C:\Windows\System32\WS2_32.dll
LoadedModule[53]=C:\Windows\SYSTEM32\dbghelp.dll
LoadedModule[54]=C:\Windows\SYSTEM32\dbgcore.DLL
LoadedModule[55]=C:\Windows\System32\PSAPI.DLL
LoadedModule[56]=D:\Origin Games\Mass Effect Andromeda\amd_ags_x64.dll
LoadedModule[57]=C:\Windows\System32\ole32.dll
LoadedModule[58]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[59]=D:\Origin Games\Mass Effect Andromeda\AnselSDK64.dll
LoadedModule[60]=C:\Windows\SYSTEM32\DINPUT8.dll
LoadedModule[61]=C:\Windows\SYSTEM32\MFPlat.DLL
LoadedModule[62]=C:\Windows\SYSTEM32\RTWorkQ.DLL
LoadedModule[63]=C:\Windows\SYSTEM32\inputhost.dll
LoadedModule[64]=C:\Windows\SYSTEM32\wintypes.dll
LoadedModule[65]=C:\Windows\SYSTEM32\CoreMessaging.dll
LoadedModule[66]=C:\Windows\SYSTEM32\CoreUIComponents.dll
LoadedModule[67]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[68]=C:\Windows\SYSTEM32\WSOCK32.dll
LoadedModule[69]=C:\Windows\SYSTEM32\USP10.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17134
OsInfo[3].Key=ubr
OsInfo[3].Value=165
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=183
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=145821
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.165.17134.0-11.0.75
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16313
OsInfo[19].Key=svolsz
OsInfo[19].Value=232
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180410
OsInfo[22].Key=bldtm
OsInfo[22].Value=1804
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs4_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17134.165.amd64fre.rs4_release.180410-1804
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=BEX64
AppName=Mass Effect: Andromeda
AppPath=D:\Origin Games\Mass Effect Andromeda\MassEffectAndromeda.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=73709B9E299F2087E791C8A0E67EB99D
MetadataHash=1515902358

@PhAse-Shifter-nz

It is very later here, and I need to have a closer look at this, will come back to you in the late afternoon, (My time)

@PhAse-Shifter-nz

Well, the error is basically the same. Bex64 with an access violation code: (0xc0000005)

The problem is that this access violation code can have many trigger.

Malicious software, overprotective security software, boot sector problems, Interference with other programs, VC++ errors (We should have ruled that out) memory problem, (Unlikely if the error only occurred in one application) and more. 

What I did saw is an "CLR20r3" error related to the "Corsair.Service.exe" this error point to a NET Framework problem.

1. Please download this MS Net verification tool.
2. Press the Windows key abd "R" at the same time.
3. Copy "appwiz.cpl" (without the quotes) into the new window > hit ENTER
4. In the "Programs and Features" window click on "Turn Windows features on or off"
5. Look which Net versions are installed. (and include them in your next post)
6. Check these versions with the tool you downloaded.
7. Let us know the result. 

Also, run the Windows System File Checker Sfc /scannnow and post the concluding message.

Some of my troubleshooting on BEX64 indicates a few possibilities also. Some people say a A BEX error is a “Buffer Overflow Exception”, "This error is typically raised when Microsoft Windows detects that a programs tries to put more data than possible in a region of memory.

DEP is also mentioned a bit but exclusions can't be added for 64bit apps such as ME:A.exe and this was never an issue in the past so I'm not sure it's that. 

The MS Net verification tool seemed to verify all of the installed NET Frameworks on my PC with success. I've lost the log file but it was very long. I've attached a screenshot of installed NET frameworks on my machine:

@PhAse-Shifter-nz

---

@PhAse-Shifter-nz wrote:

Some of my troubleshooting on BEX64 indicates a few possibilities also. Some people say a A BEX error is a “Buffer Overflow Exception”, "This error is typically raised when Microsoft Windows detects that a programs tries to put more data than possible in a region of memory.

DEP is also mentioned a bit but exclusions can't be added for 64bit apps such as ME:A.exe and this was never an issue in the past so I'm not sure it's that. 

 

---

Yes, BEX refers to “Buffer Overflow Exception” and "64" to 64 bit. It is also right that it is part of "DEP" (Data Execution Prevention), which should prevent malicious code from being exploited via a buffer overrun.
The only way to disable "DEP" for a 64bit executable would be to disable it system-wide.

But that would most likely not solve the problem because the same protection would catch a buffer overflow that is not created by malicious code, but because of a system internally problem, and this is what happens here imho.

So shutting down "DEP" would not fix the problem, but only move it to a different level, and that could lead to a system crash.

There is also no DLL mentioned under P4 (faulty module), but "StackHash_a38e". That means that no approved module could be fetched.

The NET installation is as it should be, according to your screenshot.

Did you run SFC /scannow?

No issues with the SFC /scannow... Damn this seems really tough to fix! 

I may try re-installing Visual C++ 2015 because that one won't let me run a repair on it and it's the install of it since 03/05/18

@PhAse-Shifter-nz

Actually, that should have been done before.... 🤔

https://answers.ea.com/t5/Technical-Issues/mass-effect-andromeda-won-t-launch/m-p/6963071/highlight/true#M18209

Any ideas on what's left to try? 🤨

@PhAse-Shifter-nz

Did you reinstalled VC++ 2015? (And the other runtimes from the link I send you?)

Do you have VC++ 2017 on your machine?

I have to read this thread again, I have time for it tonight.

From add/remove programs I clicked uninstall for both VC++ 2015 x64/x86 where it gave me the option to repair so I chose that instead of completely uninstalling. I suppose I could try a complete uninstall/reinstall... Don't have VC++ 2017...

@PhAse-Shifter-nz

Do everything that follows in your admin account: 

If you did not reinstalled VC++ 2013, 2012, and 2010, do it. (reboot after any package)

Install VC++, you can find it here and here.  > reboot > Repair the game again > test.

If it don't works:

Preform a clean boot again > Go offline > Look if Origin is working in offline mode > if yes disable your Anti-Virus software and your Firewall > test.

If that also don't helps, create a new Windows user account (Administrator) > reboot > Logon to the new account > Test.

@holger1405

Did you mean to reinstall all VC++? Steps taken:

I fully uninstalled VC++ 2015 X64 and X86 and reinstalled. Ran repair, same BEX64 error.

Performed clean boot, went offline, same BEX64 in offline mode...

Turned off Windows Defender and Firewall, same BEX64.

No difference in a new administrator account either... 

BTW running repair seems to reinstall the VC++ redistributes anyway... 

Well I give up... When does the Windows Fall update drop? I somehow don't see this being fixed without a Windows reinstall. Sigh. 

@PhAse-Shifter-nz

---

PhAse-Shifter-nz  schrieb:

Did you mean to reinstall all VC++?

 

---

Yes, a complete fresh installation > uninstall > reboot > Install > reboot.

If it still don't works after that, I would suggest a in place upgrade of Windows 10.

That is a repair installation that will keep your data and files programs intact.

Note: You still should make a complete backup of all your important data on the system drive.

Here is a video tutorial from MS, you can find written guides with google.

@holger1405

Success my friend!! The in place Windows upgrade repair has fixed it! ME:A is working again.. But what did the upgrade repair fix?? Will we ever know?

@PhAse-Shifter-nz

Good to hear! 🙂

---

PhAse-Shifter-nz  schrieb:

But what did the upgrade repair fix?? Will we ever know?

---

Probably not, unless somebody else finds the problem on his machine and post the fix.

In principle, this was a new installation of the operating system.

Debugging this problem without physical access to the system is very complicated, to say the least.

@holger1405

Yep played the game last night. 🙂

I guess the in place upgrade might point to some OS file corruption or perhaps some configuration that was disagreeing with ME:A. The in place upgrade takes about 15 mins and is minimally disruptive so quite an easy fix for anyone who faces this issue at some stage. 

Cheers!

@PhAse-Shifter-nz

---

PhAse-Shifter-nz wrote:

Yep played the game last night. 🙂

---

👍

---

@PhAse-Shifter-nz wrote:

I guess the in place upgrade might point to some OS file corruption or perhaps some configuration that was disagreeing with ME:A. 

---

True, but that this is a Windows problem was pretty clear from the beginning.

I would still suggest that, if you someone has the same problem, try the previous steps, like SFC /scannow with previous repair of the store, and the VC++ installations before the in place upgrade.

---

@holger1405 

True, but that this is a Windows problem was pretty clear from the beginning.

I would still suggest that, if you have the same problem, try the previous steps, like SFC /scannow with previous repair of the store, and the VC++ installations before the in place upgrade.

---

Ok will do but hopefully this won't happen again! 

Now I can finish the ME:A finale. 👍

@PhAse-Shifter-nz

No need for you to do it.🙂

It was for people that have the same or a similar problem. (Should have worded it better, sorry)

A failed VC++ installation will not wreak the system, a failed in place upgrade might very well do.

It absolutely infuriates me that over three years after this post first started EA is still as incompetent as ever. I started replaying the entire ME saga a month or so ago and have gotten through ME, ME2, and ME3 with no problem (none of them require Origin - bought the old CDs/DVDs way back when). I launched ME Andromeda the other night just to check my settings, let Origin do it updates (major mistake), shut down the game, and now it won't launch. Per the majority of the posts I am re-installing/re-downloading the game - which is going to take the better part of 3 hours.

And just a comment for al of the MS haters out there, I'm running Win 10, did not do any updates to the OS, and the game launched fine before the Origin update. This is an EA issue and they are probably loving the fact that so many people are pointing the finger at MS.

This thread makes one thing abundantly clear - EA does not give a tinker's damn about its customers. Once they have your money you are on your own and they are laughing all the way to the bank. I hate this company with a bloody passion.

Replying to my own post - DOH!

The truly sad part about all of this is that I would really like to have gotten the ME: Legendary copy of the games slated for release this Spring, primarily for the upgraded graphics and game play enhancements to ME. The problem is that EA will undoubtedly tie it to Origin which will just screw the pooch. Besides, it's nothing more than a money grab anyway. I can get the improved graphics - minus all of the headaches - over at Nexus. I'm sure there is a special place in Hell reserved for people at companies like EA.

So, here we are 2 hours 40-couple minutes later and the game has been re-downloaded/re-installed and it launches without a hitch. Gee, who'd have thought?

This is not a .NET issue. This is not a Visual C++ issue. This is an EA/Origin issue!

But don't worry; EA won't feel bad if you search dozens of user groups and gamer help posts. In fact, they love that you do that because then they don't have to pay for professional customer service personnel. They get your money then they get you to provide free help for all of the people who can't play the game because EA is a bunch of losers who love sticking it to their customers.

Happy Gaming!

😉

So was it just a reinstall that got it working? I've already tried to uninstall and reinstall once, so I guess I'm out of luck then?

I agree though. EA doesn't care. Do you know how many time an EA tech has successfully resolved an issue of mine? Zero. I've never had a successful interaction with EA support.