been playing andromeda again for a few days. there are no bex64/c000005 related errors in dxdiag any longer after turning off Force randomization for images (Mandatory ASLR). sfc and dism report nothing wrong. game runs today. so I went into windows security and removed the exception for the game. game crashed again with the on screen error on our end msg, dxdiag with the new andromeda.exe error attached.
If I understand correctly, you added an exception for "MassEffectAndromeda.exe" in the "Program Settings" section of the "Exploit Protection Settings" and then turned off "Mandatory ASLR" additionally?
(BTW, the default setting for "Mandatory ASLR" is deactivated, not activated.)
After that the game was ruining.
And now you removed the exception in the "Program Settings" and the game is not running anymore?
Did you also activated "Mandatory ASLR" again?
Is "Data Execution Preventive, DEP" activated?
there are no bex64/c000005 related errors in dxdiag any longer
I can see an BEX64 buffer overflow error in your DxDiag from Yesterday?
the default global system setting is Force randomization for images (Mandatory ASLR) is on. it has been on since 2021 when I got this win 11 desktop. I last played the game in Dec 2023 and the game worked then. I recently tried to play and all I could get was the error on our end msg. UNTIL I add an exception and turned Force randomization for images (Mandatory ASLR) OFF for this game. if I remove the exception the game wont work. DEP is ON and I did not add an exception for this game. THe BEX64 error fromyesterday was from when I removed the exception to generate the error in dxdiag. the ASLR is again OFF now and I just ran the game successfully,
So, to get the game running, you only created the Mandatory ASLR exception for "MassEffectAndromeda.exe" in the "Program Settings" section, without deactivating "Mandatory ASLR" globally. Is that right?
If yes I just would leave it at that.
