20 réponses à ce sujet

[hedstones]

Ok, so I downloaded the Mass Effect 3 demo and it starts up fine until it gets to the title screen in which the message pops up "Origin is no longer running, Mass Effect 3 demo will now close."

Origin doesn't close, and is still running... I tried repairing, reinstalling, restarting the computer and making sure origin is running in administrator mode... I get the same error.

So I decided to try running Battlefield 3. It opens Battlelog, but won't connect to any server for multiplayer, and just sits there saying "Initializing" when trying to run campaign.

Same issue when logged into my account or my roommates.

Is anyone else having issues with Origin? Or how do I fix it?

(btw, was working fine earlier today as my roommate was able to play the ME3 demo before I got home from work)

Modifié par hedstones, 15 février 2012 - 04:24 .

[hedstones]

Ok... so for some reason it's working on my laptop but not on my desktop...

I notice when loading ME3 the Origin icon shows up in the bottom right corner, does not do this when starting up on my desktop

[thetricia]

I've been having a similar problem. Oddly, Dragon Age II works perfectly fine, but the demo won't launch for me - all I get is a black screen and a loading circle - and now ME2 won't launch either. It just vanishes every time I try to play it.

[Myseria]

I'm having the same problem. Whenever I launch the demo, it closes Origin. Battlefield 3 also closes it now, but worked just fine yesterday. 

Modifié par Myseria, 17 février 2012 - 07:39 .

[Thomas Abram]

Hey everyone,

We're currently looking into this but we need your help. Can you launch your Task Manager (ctrl+shift+esc), go to your processes and let me know if you see multiple Origin processes running (with the same name) when launching the game. Thanks!

[Drasynd]

Edit: Post removed.

Modifié par Chris Priestly, 19 février 2012 - 09:12 .

[Myseria]

After restarting my computer, it worked just fine.

[Stardozen]

The same thing is happening to me aswell, can't seem to get it working

[MrWahd]

Edit: Post removed.

Modifié par Chris Priestly, 19 février 2012 - 09:12 .

[target_drone]

Well it depends if it works better than the demo for him. No point in me buying ME3 since it won't start on my PCs with this "Origin (EA) is no longer is running" nonsense, so I've gotta agree - unlink ME3 from Origin before release!

[karlpopper]

A problem i'm having with Origin at the moment is when I tried logging into Origin yesterday it said ''The origin network could not be reached. Please check your network connection and try again.''

I uninstalled it yesterday, tried logging in again, same message. Okay, maybe it's the fact that EA is overwhelmed by all the new players logging into ME3 multiplayer so I gave it a day and it still doesn't work.

Oh and yesterday I was able to log onto Origin but the ME3 demo wouldn't work properly so I attempted to uninstall the demo and the computer crashed.

Modifié par karlpopper, 18 février 2012 - 01:27 .

[Maestr055]

I had this problem on my Desktop, there are no other instances of Origin running.
However, I "installed" Origin by copying the Origin folder (and ME3 demo) from another computer (I have very slow internet) and then just running Origin.exe.
Re-installing Origin from the installer fixed the problem.

[ColJay]

Is this something to do with 64bit OS and running the 32bit origin program. If ME3 does something as basic as "look at running processes for Origin.exe" then it's likely to fail if it failes to check the *32 part also. This is really an annoying bug. Any progress from EA?

[Gyroscope]

 I'm trying to start the game but the only thing happening when i'm clicking mass effect 3 demo is that the origin window with "starting mass effect 3 demo" pops up and then nothing when it dissapears.
I've tried repairing and restarting the game, and I can play bf3 without any problem.

[Furtled]

ColJay wrote...
Is this something to do with 64bit OS and running the 32bit origin program. If ME3 does something as basic as "look at running processes for Origin.exe" then it's likely to fail if it failes to check the *32 part also. This is really an annoying bug.

If it is a 64bit issue you can download something called CFF Explorer and try changing the .exe file to run 64bit; I did something similar to get the UE of DA Origins to stop crashing every five minutes. Mind that was a memory problem I was fixing, so not sure if that'll solve this problem or how Origin will react.

If you do try it make a back-up of the .exe file first, use at your own peril etc.

Modifié par Furtled, 19 février 2012 - 08:19 .

[Dominus]

I've been having this problem and a discussion was made before on it which can be found here. Joe reccomended trying the new drivers, but it hasn't removed the effect yet.

Has any consistently successful solution been found yet? I'd rather not have to wait for the inevitable steam version, but that may have to be the only option if this continues.

[Dominus]

Regardless, the platforms aren't dissapearing anytime soon. I'm a mass effect fan, but I've no intention of buying a game that isn't able to work due to a malfunction with Origin. However, that's not really the main discussion in this topic. It's about finding out what the root of the issue is, and how to root it out.

From what I've read so far, solutions have been across the board: Reinstalling origin, removing firewalls, rebooting windows, etc. If nothing is fixed by Launch day, I'm going to have to just wait for the steam one(or rent the game instead).

[ColJay]

 OK - i finally got this all to work.

Had to re-install Origin, but also - had to check my env variables. I had directed %temp% to "E:\\".

This stopped Origin from installing properly, and thus ME3 was unable to work out it was running.

I then set %temp% and %tmp% to "E:\\temp" and hey presto installed correctly. Looks like having an extra backslash there was the issue. I'd read earlier people were having issue with running temp in a RAMDisk, I'm guessing this is the same issue. Bad coding on EA's part if that's the case, simple check for a backslash before implimenting would have saved a lot of hassle.

hope this helps some folk.

Thanks

Col