8 réponses à ce sujet

[SayCHeese256]

Yesterday I wanted to do Jacob's loyalty mission (second to last one I'm doing before the reaper iff), so I travelled to Aeia in the Galaxy map, scanned for the distress signal, launched the probe and clicked "Land". Thus the loading screen appeared. However about 3 seconds into the loading screen I heard the windows error sound so (with the loading screen still going) I Alt+tabed out of Mass Effect 2 and, to my surprise, no error message. I went back into Mass Effect 2 and then it presented itself:
"Microsoft Visual C++ Runtime Library"
"Error"
"Program C:\\Program Files (x86)\\Bioware\\Binaries\\Mass Effect2.exe"
"An Unusual error has presented itself..." or something along those lines.
I tried restarting Mass Effect 2...didn't work
I tried restarting my PC...didn't work
I also tried going to Illium, the Citadel, Omega and doing Jack's loyalty mission...they all worked fine, but the moment I went back to Aeia I got the error message again?!?!?
One thing I haven't tried that I should try is reinstalling Mass Effect 2 because I can't seem to be able to find the discs...
Whats going on? I really want to do Jacob's loyalty mission so I can finish the game (for the second time).

BTW, my specs according the config utility:
AMD Athlon™ II X2 250 Processor - 3004 MHz
RAM - 3.99 GB
ATI Radeon HD 4800 Series - 1.00 GB
Speakers (Realtek High Definition Audio) - 6.0.1.6526
Microsoft Windows 7 Ultimate
DirectX 10.0  (Mar2009) or later
MassEffect2.exe - v1.02

Any help is geatly appreciated

[no_subject]

If you can't find the discs how are you managing to play?

[SayCHeese256]

No-CD crack. But how would a slightly modified MassEffect2.exe affect this?

[no_subject]

Quite easily. No-cd exes are often sloppily hashed together and cut out bits of code that should still be there, causing programming errors like the one you're experiencing. I suggest 'finding' your game, registering it with origin and downloading it, then you can play without the disc in the drive.

[SayCHeese256]

I don't want to use up 14GB of my internet allocation so I'll just find the discs and reinstall it. I can accept having to use the discs if it means finishing the game without any more errors.

Modifié par SayCHeese256, 15 avril 2012 - 09:35 .

[UbiSergei]

@SayCHeese256, did you try to update Visual C++ 2005 Runtime Libraries, install Windows updates affiliated with Visual C++ Runtime?

no_subject wrote...

Quite easily. No-cd exes are often sloppily hashed together and cut out bits of code that should still be there, causing programming errors like the one you're experiencing.

Nonsense. Developers don't sophisticate their code and make one big mess, all code sections are separated.

Community members are having same errors with original .exe. It's a shame that people blame patched executables for all problems of a game instead of helping to find a solution.

Modifié par UbiSergei, 17 avril 2012 - 01:22 .

[no_subject]

As someone that used to use patched exe's, (I really couldn't be bothered to sift through all my cases) I am aware that they ::can:: cause problems when the original exe is tampered with. Particularly later variants of Securom that has call functions embedded at several places in the game code. (I am aware that ME2 just uses a CD check though.) I am not one of these people that link all problems to patched exe's, I simply saw the C++ error and thought it might be a programming error in the no-cd patch. ME2 should've installed any necessary libraries on install, but I do humbly admit that reinstalling those libraries in your link will probably fix the problem. We're all here to try and help!

Regards.

[SayCHeese256]

I've started two new games in ME2 since the C++ error, no errors so far. I've found the discs so I'll be reinstalling in the next day or so. If that doesn't work (should work) I'll try manually reinstalling C++, and if that doesn't work...well, we'll think about that if it comes to it.
Thanks for all the help guys!

By the way, all my games that don't use steam (or equivalent) have a patched exe, never had any problems.

[SayCHeese256]

Reinstalling it worked perfectly.
Thanks for the "insight" no_subject and UbiSergei, much appreciated.