Aller au contenu

Photo

ME2 crashing after a few minutes on Vista 64-bit.


  • Veuillez vous connecter pour répondre
6 réponses à ce sujet

#1
Eurhetemec

Eurhetemec
  • Members
  • 815 messages
My ME2 is reliably crashing after a few minutes of being on in Vista 64-bit. It doesn't seem to matter whether I'm in the actual game, or the intro sequence or the motion comic.

The crash is "Mass Effect 2 has stopped working" with absolute no details being provided that I can find.

Here are my PC's stats:

AMD Athlon™ 64 X2 Dual Core Processor 5600+
NVIDIA GeForce GTS 250 w/1gb of memory
4gb of memory (in 2 matched 2gb sticks).
Microsoft® Windows Vista™ Home Premium
DirectX 10.0  (Mar2009) or later
Sound - Speakers (2- Logitech USB Headset)

The config utility claims the game is version 1.02

What's extremely frustrating is that this is the same computer which has 130+ hours played on ME2. The old HDD experienced a mechanical fault, and I lost my saves etc. and I replaced it (with a 1tb unit), and upgraded from 2gb to 4gb of memory (replacing the old memory in the process).

I re-installed ME2, but now it crashes constantly.

Things I've already tried:

Re-installing. I've tried this twice. First I re-installed from Steam (deleting all trace of ME2 from my PC). Then, when the problem continued, I moved the CD key to Origin, uninstalled/deleted everything again and re-downloaded/installed from there. This had no impact on the problem.
Playing with no DLC (didn't bother installing it on re-installs)
Updating my graphics card drivers (have 275 at the moment)
Downgrading my graphics card drivers (tried 253 iirc, as suggested).
Updating my sound card drivers - not possible, nothing to update.
Adjusting my video card settings downwards (no impact - already have a perfect framerate).
Updating PhysX - won't do it, says a more recent version is installed.
Updating the game - Steam version wouldn't do it, Origin version does it, but has no impact on crashing.
Checking heat levels in the PC - Are actually pretty low.
Disabling UAC - no impact.
Making sure virus scanners were off or ignoring masseffect2.exe - no impact.
Running ME2 as administrator - no impact.

At this point I'm totally at a loss for what I should do. This same machine has run this game perfectly before (only HDD and memory are different), with no need for messing around, and does not experience problems with other, more demanding games which might suggest a hardware fault (I've been playing BF:BC2 on stupidly high settings to see if I could get it to crash as part of my testing - I couldn't).

I've searched the archives, but I'm not finding anything comparable - lots of people have crashes on booting ME2, or hardcore bluescreen crashes in specific places or the like. I don't get that. What I get is, after a few minutes of being on, the game stops, and I get a Windows error be-beep and a "Mass Effect 2 has stopped working" message.

Does anyone have any ideas at all?

EDIT - One possible wrinkle is that the ME2 config utility also sometimes crashes. But only sometimes.

Modifié par Eurhetemec, 18 juin 2011 - 03:59 .


#2
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
Only 2 things that spring to mind at themoment are:
Are you running it in XP compatibility mode?
Have you tried MassAffinity to run it? AMD Dual Cores are notoriouos for having slightly differernt speeds in their cores, and that can cause random problems with ME2. Using MassAffinity can help correct this.
http://www.theplaywr...-v0-2-released/

#3
mcsupersport

mcsupersport
  • Members
  • 2 912 messages
If you can try putting the old memory back in, you may have a bad set.

#4
Eurhetemec

Eurhetemec
  • Members
  • 815 messages

mcsupersport wrote...

If you can try putting the old memory back in, you may have a bad set.


It seems unlikely that I have bad set. I've used it for 8+ months with no problems whatsoever, and I've run every test under the sun on it (because I thought the same thing), all of them report that it's perfect.

I have heard rumours that ME2 has difficulty coping with memory on multiple sticks in AMD mobos, though, so if all else fails I'll try taking one out and see if it does the trick (and if it does I will write an angry letter to Bioware lol). If that fails I'll try going back.

Bogsnot1 wrote...

Only 2 things that spring to mind at themoment are:
Are you running it in XP compatibility mode?
Have you tried MassAffinity to run it? AMD Dual Cores are notoriouos for having slightly differernt speeds in their cores, and that can cause random problems with ME2. Using MassAffinity can help correct this.
http://www.theplaywr...-v0-2-released/


I've not tried either of those things, so I'll give them a go and report back.

Thanks both for your suggestions.

#5
Eurhetemec

Eurhetemec
  • Members
  • 815 messages
I tried both those options, then spent six hours digging through these and other forums and trying assorted other tricks (ME2 has a lot of weird bugs!), before finally giving in and trying what mcsupersport suggested, and going back to my old memory.

Which solved the problem.

I don't even know whether to be mad or happy lol.

I guess when I'm done with ME2 for a while I'll put the new stuff back in (it helps performance on some games - no noticeable effect on ME2 though).

Thanks either way! At least I can play now, and ME2 is a hell of a game.

#6
mcsupersport

mcsupersport
  • Members
  • 2 912 messages
Just a note:

I added some ram and found my system wasn't stable anymore, ended up buying some high quality from mushkin and it made a huge difference in stability throughout the system. It is totally possible that your ram has an issue in it, minor but it just happens to hit in an important area of ME2. Depending on how much you care, and how much issue you have in the future you may want to look at replacing it with a better set or brand. Ram like a lot of things seems to get quirky and can cause some interesting issues but not all the time depending on which section is getting used and how.

#7
Eurhetemec

Eurhetemec
  • Members
  • 815 messages
Yeah mine is Corsair and theoretically decent quality (has a warranty etc.), but I'll be keeping an eye on stability when I put it back in.