43 réponses à ce sujet

[Bogsnot1]

After spending some time going back through older threads detailing this problem, the one common denominator is that it only seems to be affecting 64bit versions of Vista and Win7. This is purely based on those who have actually included their system specs in theior reports, which is a measly 20% at best, but its enough to give an indicator. Noone has reported this error with either 32 or 64 bit versions of WinXP that I have been able to track down.
This leads me to beleive that the problem is inherant with the 64 bit versions of those 2 operating systems, wether its the 64-32 bit translation layer, DirectX10 or 11 interfering with the DX9.0c configuration, UAC issues, or possibly even just the naming convention of the program files directory. I dont run either of those systems, so I cant test out any theories as to the exact cause. If you feel like being a guinea pig, I can definately give you a few things to try.

DirectX:
Have you installed any games recently which installed DX10 or 11 as part of its installation procedure? If so, download and reinstall DX9.0c from Microsofts website in case the DX10/11 setup buggered up the DX9 configuration.
http://www.microsoft...&displaylang=en

Naming Convention/Translation Layer:
It could be possible that the inclusion of (x86) in the Program Files directory name, in particular the brackets, might not be recognised as valid characters by the ME2 configuration, and during times of excessive read/write activity, the translation layer is not able to keep up, and passes the data request straight through, causing an invalid character command and subsequant crash.
I freely admit I could be talking out of my arse about this, as, like I said, I dont have either Vista or Win7 to play around with. I do know, however, that Microsoft is not exactly reknowned for creating stable operating systems that perform as they should.
Bypass this by doing a custom installation, where you do not install the game into the Program Files (x86) directory, but create its own directory without any characters that ould be considered invalid.

If neither of these work, let me know and Ill go back to the drawing board.
Out of curiosity, have you disabled UAC completely, or just fire it up as admin. Also, I assume you have installed and run it in XP compatability mode?

[Kamisori Hanzo]

I am having this problem, exactly as described by the posters above. I didn't have problems before, but now with Lair of the Shadow Broker installed, my game crashes when going through the load tunnel underneath Liara's office on Illium. I'm able to work around it by saving just before entering the tunnel, then after crashing and loading from the save, the crash doesn't happen.

Here is my system info:

Processor: Intel® Core™ i7 CPU 970 @ 3.20GHz
Clock Speed: 4204 MHz
Physical Memory: 11.9 GB
Display Adapter: ATI Radeon HD 5900 Series
VRAM: 1.00 GB
Driver Version: 11.4
Sound Adapter: Speakers (ASUS Xonar DS Audio Device)
Driver Version: 5.12.1.8
OS: Microsoft Windows 7 Home Premium
DirectX Version: DirectX 10.0 (Mar2009) or later

@Bogsnot1
I run all my games from a second HDD, using a directory named "Games", so the path to my ME2 executable is "D:\\Games\\Mass Effect 2\\..." That would rule out the x86 program file directory as a problem. I also have UAC disabled. I can try those other things.

[Bogsnot1]

Do you have Anti Aliasing enforced on your video card for ME2?
Do you have any ASUS software loaded (apart from audio drivers)? I ask this because it has been found that GamerOSD and SmartDoctor can cause problems elsewhere in the game, and wondering if they have an audio suite that could be causing further problems.

[Kamisori Hanzo]

Yes, you hit on the problem in your first question. I was just returning to post that I had found my problem. I was forcing AA in my video driver settings, and when I reset to default settings, it doesn't crash. Specifically, I was using the "Morphological Filtering" setting in Catalyst Control Center. If I disable that, the crash disappears. I can even still force AA, so long as Morphological Filtering is unchecked.

Thanks for the help.

[Bogsnot1]

Thank you very much for the feedback, now we actually have a potential fix to let everyone know about who is having this problem. I'll contact the author of the Tech FA (Kloreep), and get him to add it in.
Thanks again.

[Kloreep]

Cool, thanks for experimenting Kamisori.

Anyone know what the Nvidia equivalent of Morphological Filtering would be? Do they call it the same thing? Or do they even have an equivalent?

Modifié par Kloreep, 25 juin 2011 - 06:29 .

[Kamisori Hanzo]

I don't think Nvidia has an equivalent of Morphological Filtering (MLAA). I would be interested to see if the people who experience this crash with Nvidia cards are also forcing AA. Maybe one of them could try doing some experimentation with their settings.

[huntsman35]

I played mass effect 2 on the xbox first, and just recently thought I'd play it on PC as well to compare as it was quite cheap. Imagine when I start crashing and come on here to check I find this has been a bug that was first reported 7 months ago and they never fixed it. So lame. To be honest I prefer it on the xbox anyway having played through half of it on the PC. Yes, its graphically nicer, but some of the things are so much worse on the PC (planet scanning, use of NPCs abilities that sometimes use wrong ones and more).

Guess I'll have to put up with the bug and constant crashes on illium for now, but gee its poor work. Either that or I remove the addon till I'm done with the rest of the illium quests.

[mcsupersport]

^ are you here for help or just to complain that the xbox is better??

IF you want help post some specs of your computer, most of the "crashing" issues are either computer specific or as Bogs stated earlier Win7 computer related and thus not an officially supported operating system of the game.......

[Bogsnot1]

@huntsman35: Given you have absolutely no games registered on your profile, and appear to have registered just today to whinge, leads us to assume you are a pirate, and as such deserve no support, and every single bug you encounter.
By all means, register yourgame, prove me wrong, and a full apology for calling you a pirate will be forthcoming. Otherwise, sod off and annoy someone else.

[Kamisori Hanzo]

It looks like I spoke too soon. I just had the crash on Illium in the tunnel under Liara's office again, even with AA disabled completely in Catalyst Control Center. It seems that sometimes it happens and sometimes it doesn't, which led me falsely to blame the anti-aliasing.

[Bogsnot1]

Back to the drawing board I suppose. I should be getting a Win7 box later this week to test it out on, so hopefully I'll be able to fnid something thats causing it.

[Darksei]

So far I am suspecting that it is the Dynamic Shadows. I turned that off and the crashing stopped. This has been consistent on several loads. The issue manifested in the same exact spot. I actually looked at the floor and it was roughly the exact same spot along that hallway. With dynamic shadows off, it worked like a charm. Turn it on? Crash city.

[RiGoRmOrTiS_UK]

I'm having this exact same problem as well. I can confirm it doesnt happen on an old save; but happens on all new playthroughs. whether I force AA or not.

Windows 7 64-Bit, i7 920 and 2 x GTX-460's in SLI. (275.33 Drivers)

[Bogsnot1]

Have you tried it without dynamic shadows like Darksei has found to fix their problem?

[ToTheKing]

Awesome, disabling dynamic shadows worked here too for that stupid hall on Illium.

Bogsnot, 9 months later, you and your ilk are still annoying as hell. Big thanks to the folks who came up with a practical solution so the rest of us could get on with the gaming.

[prettz]

I just ran into this problem and read this topic. I found that it well not crash if I can get the door closed behind me before I hit the spot that crashes.

[Firen Drakendorf]

I tried disabling dynamic shadows, saving right before the crash and waiting for the door to close. I'm guessing it's the dynamic shadows, but I'm not willing to isolate the problem. I turned dynamic shadows back on after I passed that tunnel.

[darkronnie]

NipWup wrote...

yes, someone has already posted a temporary solution.. dont remember where to find it...<br />
<br />
somthing like.. before you enter the tunnel turn off your dynamic shadows in your video options and walk (not run) through the tunnel and you should be fine... turn back on your shadow options once you are through.. note it will crash both ways if you come from the other direction... sometimes you can get away with just walking but it is almost guarenteed if you turn your shadow options off

this worked for me:lol: