9 réponses à ce sujet

[MechaPants]

I haven't been able to get the steam version to run on win7 64 bit. Launching the game shows a loading cursor for 3 seconds and then nothing. If I check the task manager I see a mass effect 2 process that has 0 cpu and stays at 6,500k but otherwise does nothing.

Anyhow... I saw a Bioware post from Micheal Gamble:

A few helpful users (as well as EA support) have come up with a number of troubleshooting options:

Solution:
1) Open windows file search
2) Type "EAAccessInstaller.exe" and locate the file on your hard drive
3) Open a command prompt and cd to the directory of EAAccessInstaller.exe
4) Type the following command:

EAAccessInstaller.exe /s /dir "C:\\\\Program Files\\\\Electronic Arts\\\\Mass Effect 2\\\\binaries"

(With the appropriate path to the ME2 binary directory).

If that still doesn't work:

1) Go to the ME2 directory, binaries subfolder.
2) Open the EACore_App.ini file in a text editor
3) Make sure that the paths to activation.exe are correct

If that _still_ doesn't work, you can examine the log file to see if there's any indication there of what's going wrong.

On Win XP, the log files live in: C:\\\\Documents and Settings\\\\All Users\\\\Application Data\\\\Electronic Arts\\\\EA Core\\\\logs
On Vista/Win7, the log files live in: C:\\\\Program Data\\\\Electronic Arts\\\\EA Core\\\\logs

Any how I tried to try those things but EAAccessInstaller.exe isn't anywhere on the harddrive (at least not from win7 search) and C:\\\\Program Data\\\\Electronic Arts\\\\EA Core\\\\logs doesn't exist.

Maybe that's a problem with the install? Should these be missing? Where can I find the logs?

[MechaPants]

bump

[Jack Lamden]

The EA Access related steps aren't valid for the Steam build.



EA Access is for all of our non-Steam Digital Distribution PC builds.

[zacrobmer]

Did you validate your steam game cache?

[Phonzo]

i had this issue briefly when steam attempted to launch the launcher which for some bizarre reason wouldn't launch.



Have you tried launching the .exe directly? Its' under steamapps\\common\\mass effect 2\\binaries\\MassEffect2.exe along those lines and then see if it crashes. (it might not be under binaries just under \\mass effect 2 but i am to lazy to look

[Kevin Lynch]

The very first time I launched the game, I had the same issue (I have Win7x64, too). I found that the problem was that it appears to be attempting to do a configuration scan (not necessarily; it's just a guess, since I had the same issue with DA:O). I temporarily ran the MassEffect2Launcher.exe as an administrator, let it do its thing (ran the config program myself from within the launcher), and I've not had the problem re-appear since, even though I'm no longer running as an administrator.

That .exe is in C:\\Program Files (x86)\\Steam\\steamapps\\common\\mass effect 2

Doesn't hurt to try.

Modifié par Kevin Lynch, 02 février 2010 - 11:23 .

[MechaPants]

Alright here's the full description of the steam problem I'm having:


When I try and run ME2, (through the launcher, through steam, or directly running the exe), the cursor changes to a waiting cursor for about 5 seconds. Then it goes back to normal but the game doesn't launch.


When I open the task manager I see process called “MassEffect2.exe *32”. That has 0 CPU and is using around 6,500 K. The amount of ram varies from 6,000K to 6,700K.


Also after installing ME2, EVERY other bioware game I own on steam started doing the EXACT same thing these include : ME1, DA:O and KOR. The only difference was the amount of ram shown in the task manager (ME1 and KOR were about 5,000K).

I also own ME1 on DVD. If I remove the steam version and install the DVD version ME1 runs fine(as long as I install the 1.02 patch).

The DA:O character creator also runs fine even though that game will not.

I'm not exactly sure but I think this all started happening when I installed ME2.


Here are my system specs:


Win7 Home Premium 64 bit (upgraded from vista home 64)
Asus P6TD deluxe motherboard
ADI AD2000B onboard sound running sound max drivers
Core i7 920 (not overclocked)
12 gigs of ram
2 x Geforce 285 in sli (196.21 drivers)
SATA 500gb HD
Kaspersky Antivirus (I've tried "pausing" protection and turning it off entirely)
Running through a d-link hardware router

here's what I've tried so far:

1) Re-validating files
2) Running Steam as Adiministrator
3) Turning off UAC
4) turning off virus protection
5) runing as admin without uac, and no virusprotection
6) renaming openal.dll
7) reinstalling openaldrivers
8) removing physX drivers and installing them from theredist dir
9) made sure all network ports from the readme wereopen and routed to that machine (as well as the steam ports)
10)disabled sound from the launcher
11) disabled my onboard soundfrom the device manager
12) setting it to windowed mode
13)turning all the options down in the launcher
14) turning all theoptions up in the launcher
15) setting steam, the launcher, andthe game executable to run as admin
16) rebooting(always)
17)removing any other game disks from my dvd drive.
18) Uninstalling steam and all steamgames then deleting the steam directory and reinstalling steam and Mass Effect 2.



Looking at the process in Process
monitor shows the last started processes include:





CreateFileMapping
C:\\Windows\\SysWOW64\\pnrpnsp.dll





RegQueryValue
HKLM\\System\\CurrentControlSet\\Control\\SQMServiceList\\ SQMServiceList




RegQueryValue
HKLM\\System\\CurrentControlSet\\Services\\Dnscache\\DnsCache\\ShutdownOnIdle

Modifié par MechaPants, 03 février 2010 - 05:58 .

[MechaPants]

Is there a way to attach files? I was going to post my Process Monitor dump. If anyone from Bioware wants to look at it or any other information I can send it.

Modifié par MechaPants, 03 février 2010 - 06:22 .

[MechaPants]

bump, also tried running with the computer in my router's "dmz" which is supposed to disable the firewall.

[MechaPants]

bump, also tried removing tages that was installed for antoher game. No effect.