Please follow the instructions below, don't be afraid, it looks more complicated than it is.
If there aren't any dump files of ME:
Hi @holger1405
Ok, so I follow the first instructions and it's appear what you say. I save in my Drive and the link it's:
https://drive.google.com/drive/folders/1anYDIv5lIrBW0MhK2H7k9xvvSi61UH4e?usp=sharing
Thanks for your time and your patience
Both the launcher and the game crash with a NULL_POINTER_READ access violation.
That means it trays to access a memory address that is inside the first 64kb of memory and this space is reserved by the OS.
The problem is that this can have many reasons, code corruption, a hardware fault and more.
If you did not do it until now, preform a clean boot , disable your virus scanner and other security software as well as Afterburner or similar software if you use them, and test the Game in clean boot mode.
If that don't helps:
Hi. So I apply the clean boot, and I can access for the lautcher. But when I want to start a game, it's appear a black screen and then I return to the lautcher. It's differente from the first time because I cant even access the lautcher.
I follow the instructions about PowerSheel, but the only thing that put it's Windows does not find no infringement for integrity.
i got something to work for me yesterday, i was trying to run origin through steam so i could use steams DS4 support, and that seems to be what was causing the issue for me, when i just run the game through origin directly it works.
im just using DS4 windows instead.
but also i saw another commenter say after booting up either ME1 ME2 or ME3, just alt F4 the main launcher and the game will boot up, may be worth trying for other people.
This is my first time posting on a forum like this, but I haven't seen anyone else with this error so I'm wondering how to fix it. Whenever I try to launch ME:LE on either steam or origin, it doesn't do anything but open steam to the homepage. I've never even seen the launcher, but it already says I've played for 8 minutes. I've tried everything I can think of: disabling firewalls, running the app as administrator, uninstalling and reinstalling, getting a refund and rebuying, buying the game on origin instead of steam, doing the unicode fix, updating my graphics drivers, and checking forums on the daily to see if there's a new fix to try. I've got a few .dmp files here: https://www.dropbox.com/s/4gu7ctvcree1zfw/CrashDumps.zip?dl=0 and I've attached my computer specs to this message as well.
@Aquacat3965Hi - Try this https://www.nexusmods.com/masseffectlegendaryedition/mods/46
Had exact same problem and this works. Its helped lots of people on here.
It was originally posted about here: https://answers.ea.com/t5/Mass-Effect-Legendary-Edition/Mass-Effect-Legendary-Edition-on-Origin-does-not-start/m-p/10341661#M1785
Did you also tried the custom launcher from dvidebyzero?
It is as said a NULL_POINTER_READ access violation, and I hunt this error basically since launch.
See, a null pointer read is in the most cases a clean as it gets case of a software bug or Hardware (Memory) error, but this games runs for many people and other games run well for people that have the same problem. .
In C++ a NULL_POINTER_READ is defined as "undefined behaviour", meaning that the code can appear to work, and only fails for example on specific system configurations, but that is also unlikely here.
I like to try something:
No drivers expect network drivers are loaded in this mode, meaning the game is rendered in software, so it will take a wile to get to the launcher and so on.
You of course can't play this way, the idea is to find out if a normally loaded driver is causing the error.
To leave the Save environment, just restart the system.
@holger1405
Can't try what you suggested at the moment unfortunately, my network adapter isn't supported in safe mode with networking, because of this I can't log into origin first to launch the game. I'll look around for an Ethernet cable, can't guarantee that I'll find one though.
Origin and the game should run in Offline mode as well, I suggested online mode because it is the easier way.
Thanks anyway!
Than all I can suggest itm is a repair installation or a complete fresh installation of Windows.
The repair installation has the benefit that you can keep your data and applications, but I can't promises that it will work.
The fresh installation should work if there is no hardware malfunction that prevents the game from running.
(The repair installation is normally a save process, but you still should have a backup of your important data!)
On my sister's PC:
dividebyzero's custom launcher comes up when I start the game via Steam/Origin, and when I click ME1, I see the ME1 splash image. Unfortunately, the game never actually starts, the loading process just seems to hang there. We tested this today, letting it go for two hours, and when we came back, the screen still showed the ME1 splash image and a spinning circle.
Her PC meets minimum requirements for the game (eg 8gb of ram, gtx 1060).
At this point, if a patch doesn't fix the issue for her within a week, she's going to have to refund the game.
(btw, she can run Cyberpunk 2077, The Sims 4, and many other games on her pc)
Please create a DxDiag in text file format and post it with your next reply. You can do that with the "Choose file" button at the bottom right corner of the reply window.
@holger1405
Found that cable in the in the legendary "throw every kind of cable you don't need right now" drawer and yes, the game runs in safe mode (tried only ME1 but it does load up, I can walk around and everything)
That is the best drawer you can have. 😉
So, there is a driver on your system that is preventing the game from running.
Unfortunately it is not as easy to narrow down as with a clean boot.
So if you plan on a fresh install anyway, I would suggest that.
Install the Chipset driver first > Restart > Install the Graphic driver > Restart > Test the game.
If it is still working, test after every additional driver you install.
@holger1405
I'll try to keep a log of what I install so if I run into this problem again so I'll be able to narrow it down and post about it (I'll post if it'll work without problems as well), it may take some time though as I plan to pretty much clean the entire PC and my internet is kinda garbage, should do it within this week though.
Hi Holger,
Thanks so much for being an angel for helping out in your own time with this. Much appreciated! EA should hire you! After trying everything, I found my solution and would like to share with you and others who have this issue.
Just a heads up, for those running Sophos Home Premium like I am, I'm just going to provide a link:
This page basically details how - through your local Sophos widget - to set a 'Local Exclusion' for MassEffectLauncher.exe.
Hopefully this helps someone else and spares them a headache!
Thanks @BlackAdder117 !
Updated the OP.
@holger1405
Just launched the game after Windows clean installation, everything works fine now.
That was expected, but is still good to hear. 🙂
Keep us posted if something goes wrong.
What region are you in and what region did you choose?
My Region is Slovakia and i choose Uk
I did change my region on my PC
Hi all, I had a general Sophos related error in that ME LE launcher at large would not start. This was solved by resetting one property in Sophos. However, and this is the reason that I write, reexperienced problems Sophos related when starting ME2 LE , I got a blocking error 'unable to load dbdata.dll' which was not fixable by repairing. I tried repairing three times. The last time, I completely unabled Sophos Home Premium and repaired : the game played again ME2 LE started and ran.
Thank you everyone for your efforts! Enjoy playing Gerard van der Kooij
@ALTBOULI313 indeed, it is on the forum here. I have made a screenshot of it, it is kind of hard to find. This is for the general MELE launcher (so no image at all....).
For the MELE 2 error I disabled the full Sophos to get the result of foregoing the blocking error 'unable to load dbdata.dll'.
So for the lanncher at large you should be ok with just the setting "prevent code cave utilization" as you can observe in the third screen shot (zoom in to the document with + in pdf).
It would seem that disabling Sophos altogether to repair the game files to forego the Mele 2 error should be enough. playing could be with sophos enabled, haven't tested this yet. Succes, Gerard
