17 réponses à ce sujet

[roflsaurusrex0r]

1.  What Game is Being Played
a.  Mass Effect 2
b.  Digital Download (Steam)
c.  MassEffect2.exe v1.01

2.  System Details
a. 
Intel® Core™2 Quad  CPU   Q9450  @ 2.66GHz
Clock Speed: 2667 MHz
RAM/Physical Memory: 4 GB
Display Adapter: NVIDIA GeForce 9800 GX2
VRAM: 512 MB
Driver Version: 195.62
Sound Adapter: Realtek HD audio output
Driver Version: 5.10.0.5998

b.
Windows XP Pro x64 (SP3)
DirectX 9.0c

3.  Problem Summary
The game is crashing during launch.  After I downloaded and installed the game it worked for the first three hours or so.  Then, I had a freeze.  When I restarted, I found that the game wouldn't initialize at all and I received a windows error message stating that there was a problem and the app needed to close.  I initially tried restarting, then I tried backing up and reinstalling the game, then I tried reinstalling steam.  None of those work and I'm still unable to launch the game.

*edited to conform to correct posting format

Modifié par roflsaurusrex0r, 24 mars 2010 - 11:12 .

[Gorath Alpha]

Read Chris' instructions and follow them. Number three post at the top here.

[roflsaurusrex0r]

bump

[Doofus42]

What is the error message in your Windows Application event log?



You might want to consider updating the following items:



1. DirectX to Feb 2010 release - download.microsoft.com

2. RealTek Audio - 2.45 was just released

3. Disable nVidia SLI. The 195.62 driver is fairly recent and would not be high on my list to update

4. Chipset drivers



Your use of 64bit XP is a cause for concern. This uses the Windows 2003 server 64bit kernel. I have "heard" that driver support can be less than stellar for this version of XP. But this is pure hearsay on my part. I have no direct experience with XP x64.



What version of the Visual C++ runtimes are insatlled?

[roflsaurusrex0r]

The error message is

Faulting application masseffect2.exe, version 1.1.1599.0, faulting module msvcr80.dll, version 8.0.50727.4053, fault address 0x0001500a.

Microsoft Visual C+++ 2008 Redistributable x-64 9.0.30729.17


I'm doing the updates you recommended and no success so far.

Modifié par roflsaurusrex0r, 24 mars 2010 - 04:12 .

[Doofus42]

The msvcr80.dll is part of the Visual C++ 2005 RTE.



I have both the x86 and x64 versions Visual C++ 2005 installed on my x64 Vista and Win7 machines:

Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update

http://www.microsoft...72-9112bab119c2



I do not have the 2008 version installed.

[roflsaurusrex0r]

I uninstalled the 2008 and I made sure that i have both the x86 and x64 versions from that link.



Same windows error is still occuring

[Doofus42]

Still crashing in the msvcr80.dll module?

[roflsaurusrex0r]

yes

[Doofus42]

My Vista x64 system has 24 msvcr80.dll files on the C: disk. I guess I am just stupid lucky that I am not in DLL hell. Just thinking here. How many of these files do you have installed on your C:?



I am at a bit of a loss right now. It's way too early to do the re-install Windows thing.



This may seem like busy work..... Could you download MemTest86+ CDROM ISO from www.memtest.org, burn a CD, boot to it and let it run a memory test of your system?



Prime95 is also good hardware stress test tool. It will peg the CPUs at 100% utilization so you would need to closely monitor your CPU temps. RealTemp works well for this.

[roflsaurusrex0r]

It looks like I have 9 instances of msvcr80.dll



My hd is partitioned and the OS is about the only thing on C: so reinstalling Windows isn't a big deal if it comes to it.



I also should point out that every other game I've tried, original Mass Effect (also on Steam), DA:Origins, Quake 4, etc all work fine. I'm really at a loss here.



I'll try running Prime95 (I have no burnable CDs and I have no desire to go buy any) but I'm a bit confused what it will accomplish.

[Doofus42]

Mainly this would verify that you don't have a memory problem.

Almost all PCs have 8bit memory with no form of error detection nor correction. So if a memory cell gets stuck on a 1 or 0, there is no way to detect this other than running a program like memtest86+ that will write, read, and compare all memory locations. An error is detected when the data written to memory does not equal the value read. I have had memory go bad in the past and memtest86+ is the tool I use for memory testing.

Memtest86+ is what I run when a computer starts acting "flaky" with random failures. Also if the failure is in the high memory address you may only rarely access it.

Modifié par Doofus42, 24 mars 2010 - 05:43 .

[dwx84]

Its a shame that things have come to such as pass as this but here we go:

Firstly, for you Direct2Drive people I have a solve (for me anyway and hopefully you too) at the end of this brief rant.

 To begin, its actually rather incredible that between two multi-million (and low billion) organizations (BioWare/EA, and Direct2Drive.com) seemed to have played bull-poop hot potato on this one, saying "its your problem" to eachother and leaving the customer in the middle.

 Heaven forbid someone spend five hundred dollars ($500), or maybe a few grand, and figure out the issue with your heavy hitting franchise game worth at least tens or even hundreds of millions of dollars. To BioWare/EA, Heaven forbid you invest in smooth technical synergy with major online game sellers like Direct2Drive, the wave of the future in case you didn't know. No, I take it back, we all feel like spending a bunch of time and running down to the store then having a fat game collection taking of space in our homes, with boxes and manuals and running the risk of physical injury from kids. No thank you sir, I will download it and keep track of my account info via and handful of different methods, requiring either a small peice of paper, a flash drive, and a kilobyte of space of my hard drive.

Incredible.

For my fellow D2D users a quick fix is this:

I was on the verge of giving up and had shook my fist angrily in the air more than once and almost, Almost, cried out in complete exasperation at this point. Between the download (10gb), life, work, and and it constantly telling me after a few lengthy 10gb re-installs "The game cannot launch because of a misconfiguration. Please reinstall your game and try again" (AWC.dll)... then searching the net for advice and it not working for me there either, though it steered me to the "binaries" folder in the ME2 master folder I managed to launch the game eventually. 

In the binaries folder, furiously clicking wildly on all the EXEs in anger, I found my fix.

Run the 114kb EACoreServer app and then quickly run the 16,038kb MassEffect2 app. 

Hopefully it works for you.

Apparently EA can't be bothered to fix this. Having grown decadent in their success they prefer to stagnate and enter their own version of Gibbon's The Decline and Fall of the Roman Empire. Too much bureaucracy perhaps that graduated with management credentials but no gaming credentials.

[Bogsnot1]

You necro a thread, only to post a rant, and a fix that was discovered long ago?
Bravo, sir, bravo.

[dwx84]

Well a handful of searches, and then some more with some quotation marks here and there yielded no fix. Re-installations holding my breath did not help.I took it on myself to spare anyone else with a similar problem -honest customers spending good money and finding themselves on the brink of exasperation- the time reading long threads and maybe opening a DOS prompt for the hell of it. While we're at it why not a hex editor that God knows how to use?

And as far as the fix goes, its a dubious one. Myself I did not see within an hour of trouble shooting and searching the fix after a great deal of anger at why my legitimately purchased product did not work. Understand as well that most people will begin, like me, with Google, and not with http://social.biowar.../index/1882961.

So yes, my good man, the Dwarf with a fiery beard and upset countenance for his picture, probably wielding a mighty hammer as befitting your proclivity, you can call me out for my "necro" thread but at the end of the day someone else with a similar problem will hit the end of the thread arrow and reach my solution, though it has been added by someone else according to you (and I believe you there).

[Bogsnot1]

Did you think to look in the Tech FAQ?

[dwx84]

You know what Bogsnot1, it's all my fault. Its all my fault that I worked and earned money, paid taxes, contributed to society, bought this game legitimately, and then got screwed by a technicality that I couldn't solve after searching Google and the net. I then worked hard again and provided the solution and called out the parties involved who made the process so arduous. Then you came along. Thankfully you are here, with the benefit of hindsight, to pick on me and point out my shortcomings since it makes you feel like such a big man. I missed specific things. You are here to tell me how I failed, with your mighty hammer and fiery Dwarven beard. Thank you. Thank you for helping me see what I did wrong, you, who have absolutely no first hand experience about what has led me to be on this board in the first place. Thank you, for correcting me.

[Bogsnot1]

You're welcome.

FYI

Mass Effect 2 PC Technical Support (Spoilers Warning) This forum is for fans and owners of Mass Effect 2 on the PC to assist each other with technical questions. Official game support is provided by Electronic Arts, but fans are encouraged to try to assist each other here.

Now you know where to turn to when you have difficulties in future. Have a pleasant day.