Aller au contenu

Photo

Lots of crashing on Illium with patch or DLC; stable before


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

#1
TrueThanny

TrueThanny
  • Members
  • 13 messages
On my first couple playthroughs, before any extra DLC came out, I never had any crashes.

Recently, after getting a bunch of the DLC (including Lair of the Shadow Broker), I started another game. 

I've found that it crashes quite often on Illium, usually when entering the tunnel leading to the transportation area.  I have one save right now that crashes consistently after walking a few feet forward from the save point (I developed a habit of saving before walking down that tunnel).  Here's the error information:

  Problem Event Name:    APPCRASH
  Application Name:    MassEffect2.exe
  Application Version:    1.2.1604.0
  Application Timestamp:    4bd611db
  Fault Module Name:    MassEffect2.exe
  Fault Module Version:    1.2.1604.0
  Fault Module Timestamp:    4bd611db
  Exception Code:    c0000005
  Exception Offset:    0010f01f
  OS Version:    6.1.7600.2.0.0.256.1
  Locale ID:    1033
  Additional Information 1:    01bf
  Additional Information 2:    01bf342c2a3a9018ca1b1e44ba5fecdd
  Additional Information 3:    7bdd
  Additional Information 4:    7bdd70dc18e92aafb112222b6e71d745

That offset is the same with each crash, and this one is 100% reproducible.

Fortunately, I think I've already done everything there is to do down that way now, and was heading there only to double-check the stores.

Anyone else have this problem?

#2
yourfat

yourfat
  • Members
  • 1 messages
Im having the same problem, Illium was working fine, then i down loaded "shawdow broker" dlc now it crashs at the same point every time in the tunnel heading to the shipping area

#3
Triand

Triand
  • Members
  • 2 messages
I am Having this EXACT same issue. Around going halfway into that tunnel located under liara's office that game almost ALWAYS crashes.... one of the most annoying things.... and I still can't seem to fix it. and yes, I have downloaded ALL of the DLC.

#4
Triand

Triand
  • Members
  • 2 messages
I contacted EA support about this.. I had them escalate the issue.

#5
NipWup

NipWup
  • Members
  • 53 messages
yes, someone has already posted a temporary solution.. dont remember where to find it...



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

#6
DedoAglar

DedoAglar
  • Members
  • 4 messages
Same problem after installing ShadowBroker.

#7
MarsCraft

MarsCraft
  • Members
  • 2 messages
Same issue


#8
colt205

colt205
  • Members
  • 1 messages
i get this and blue screen after 10 min playing .

page_fault_in_nonpage_area

*** stop:0x00000050 (0xfffffa0003d34270,0x0000000000000001,0xfffff80001c57b72,0x0000000000000007) or was it 1 the last seven , dont remember anymore XD

#9
Cola-Bear

Cola-Bear
  • Members
  • 2 messages
Okay guys, I found a way that works for me to fix it. Now bear with me because when I first heard it I thought "ok this is the stupidest thing Ive ever heard", but it actually worked. What you do is, load whatever game works before crashing, then walk your character right up until the part where you crash (for me in the tunnel under Liara's office), once you're about 2-3 feet away from the "crashing boundary" save your game.

Walk up and the game will crash, deal with Windows then re-load ME2. Load up the save file you just made and I can't believe I've saying this but it runs, and so far completely without incident. I'm not sure if it just loads something differently or if it's a video effect from a different angle but what matters is that it works for a temp. fix. Hope it works for you guys too.
 

*** Update, this is my first time playing through the game and after I got past the afforementioned crashing area, I completed both Liara's initial terminal hacking missions and the dossier on Samara. But seeing how most of you guys are reporting issue after installing the Shadow Broker, Im assuming it had to do with her first mission.
 
I say this because at the end of your first meeting with her, you can say "let's get the shadowbroker" right off the bat without actually completing the opening mission, said mission than appears in your Journal as completed (without giving credits or exp) so I am just making the assumption there may have been some kind of conflict.

Modifié par Cola-Bear, 10 décembre 2010 - 02:15 .


#10
pjarupanich

pjarupanich
  • Members
  • 1 messages

NipWup wrote...

yes, someone has already posted a temporary solution.. dont remember where to find it...

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


Thank you NipWup! I had the same problem but I followed your suggestion and it worked!! appreicate your info!

#11
Freddo01

Freddo01
  • Members
  • 1 messages
 Colabear I swear to god you rock.

Like you I saw your post and thought - dude, that's just retarded but it worked! Just save anywhere near that crash point and you can walk through. Haven't tried to cross back yet but hey at least I can progress in the game now.

Cheers holmes!

#12
NonoNemrod

NonoNemrod
  • Members
  • 2 messages
same trouble with the tunnel... i hope Bioware will find a solution... :(

#13
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
Ive said it before, and I'll say it again. Given that noone can be bothered submitting a proper error report as listed in the "Read First" thread, and just say "Ive got problems here", or worse stills, a "me too", its going to be hard for any solutions to be developped.

An accurate report will help the devs narrow it down to wether its a particular OS version, GPU brand, driver revision or whatever. You wouldnt go to a doctor, tell him you're sick, then refuse to answer any more questions, or refuse to let him look at you would you? No. Same thing applies here. Provide information that can be used in the fault finding process, or you will be stuck with the fault.

#14
TrueThanny

TrueThanny
  • Members
  • 13 messages

Bogsnot1 wrote...

Ive said it before, and I'll say it again. Given that noone can be bothered submitting a proper error report as listed in the "Read First" thread, and just say "Ive got problems here", or worse stills, a "me too", its going to be hard for any solutions to be developped.
An accurate report will help the devs narrow it down to wether its a particular OS version, GPU brand, driver revision or whatever. You wouldnt go to a doctor, tell him you're sick, then refuse to answer any more questions, or refuse to let him look at you would you? No. Same thing applies here. Provide information that can be used in the fault finding process, or you will be stuck with the fault.

You mean like an instruction offset, complete description of the circumstances, and an implicit offer to supply a save game that exhibits the problem consistently?

Honestly, what's the purpose of your response?

#15
IBPROFEN

IBPROFEN
  • Members
  • 370 messages

TrueThanny wrote...

Bogsnot1 wrote...

Ive said it before, and I'll say it again. Given that noone can be bothered submitting a proper error report as listed in the "Read First" thread, and just say "Ive got problems here", or worse stills, a "me too", its going to be hard for any solutions to be developped.
An accurate report will help the devs narrow it down to wether its a particular OS version, GPU brand, driver revision or whatever. You wouldnt go to a doctor, tell him you're sick, then refuse to answer any more questions, or refuse to let him look at you would you? No. Same thing applies here. Provide information that can be used in the fault finding process, or you will be stuck with the fault.

You mean like an instruction offset, complete description of the circumstances, and an implicit offer to supply a save game that exhibits the problem consistently?

Honestly, what's the purpose of your response?


  
  http://social.biowar...6/index/4795299       this is what Bog is talking about that ppl don't know how or just don't want to read.


 edit add* READ FIRST that is stickied.

Modifié par IBPROFEN, 22 février 2011 - 09:11 .


#16
Soltrapax1

Soltrapax1
  • Members
  • 1 messages
Same problem here with illium transport tunnel.

Bioware or Ea you should look into this.

It is ruining the games replay value.

#17
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
Look 3 posts up.

#18
Roguewolfe

Roguewolfe
  • Members
  • 5 messages
This bogsnot1 guy just trolls every post where someone describes a problem. Anyhow, add me to the list of people who crash in that tunnel on Illium.

#19
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
I dont troll, I just dont have time for idiots. You, like the others, have ignored the forum description which states that official tech support is performed by EA, as well as ignoring the "Read First" thread which details how to post a full problem report.
Bugs cannot be fixed until the devs have a fair idea of where to start looking for the root cause of the problem. This could be related to a particular make or model of video card, a driver revision, cound card, CPU, motherboard, etc.
It has also been shown that certain 3rd party applications cause the game to crash. ASUS GamerOSD and SmartDoctor have been responsible for the Weapons Locker Crash. Kapersky Antivirus has been responsible for the game not running at all. Comcast apps have been shown to cause keyboard problems.

Ive said it before, and I'll say it again. Posrt a proper error report, and we might be able to pinpont the problem. If you just rely on saying "me too" on these forums, and dont lodge the fault with EA, then nothing will get done.
Posted Image

#20
Roguewolfe

Roguewolfe
  • Members
  • 5 messages
I've been building my own gaming rigs for 12 years, and I'm fully aware of everything you mention in the above. None of it excuses the attitude that I've seen over and over from you in multiple threads. You're not a Bioware employee, you're just a really snarky user with a chip on his shoulder. Throwing up the PEBKAC picture repeatedly just makes you look like a d-bag. More importantly, you don't contribute to the forums or help anything by acting this way, even though you probably think you're some sort of tech superman.

To the rest of the folks, creating a save a few feet from the crash and then reloading it does let you go through to tunnel just fine. It's an annoying work-around, but it does work.

Modifié par Roguewolfe, 03 juin 2011 - 09:24 .


#21
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
If you were truly aware of everything I had previously stated, then you wouldnt have just thrown up a "me too" response, and would have contacted EA support to get your voice added to those who had lodged a complaint.
For someone who has been building their own rigs for 12 years, you havent been all that keen to share your alleged expertise with your fellow gamers. You also show your lack of knowledge of the very system you have built by proclaiming your continued sufference to this bug. I too have been building my own gaming rigs for years, and yet I have never suffered from this bug.
I also do not hesitate to help out others on this forum when they have problems, yet your silence in sharing your alleged expertise is deafening. Call me snarky and a douchbag if you will, but at the end of the day, you're the one with the problem, and my game is unaffected.

#22
Roguewolfe

Roguewolfe
  • Members
  • 5 messages
An interesting thing about this bug: it only affects new games started with LotSB DLC installed. Game saves in progress when the DLC is installed are apparently unaffected. I can say that with relative certainty because the crash is very consistent, but two of my playthroughs I had going when I installed LotSB did not experience this at all (and no settings changes and only a couple of realtime days between them).

#23
Roguewolfe

Roguewolfe
  • Members
  • 5 messages
An interesting thing about this bug: it only affects new games started with LotSB DLC installed. Game saves in progress when the DLC is installed are apparently unaffected. I can say that with relative certainty because the crash is very consistent, but two of my playthroughs I had going when I installed LotSB did not experience this at all (and no settings changes and only a couple of realtime days between them).

1.1: Playing the game via Steam (Product version 01604.00)

1.2: Here's a full system report:
<Report>
- <System>
  <TimeStamp>20110603T102822.281-08:00</TimeStamp>
- <device0 name="processor">
  <property0 name="clockspeed">3307</property0>
  <property1 name="clockspeed.units">MHz</property1>
  <property2 name="family">6</property2>
  <property3 name="model">42</property3>
  <property4 name="name">Intel® Core™ i5-2500K CPU @ 3.30GHz</property4>
  <property5 name="numcores">4</property5>
  <property6 name="numprocessors">1</property6>
  <property7 name="stepping">7</property7>
  </device0>
- <device1 name="storage">
  <property0 name="filesystem">NTFS</property0>
  <property1 name="letter">C:\\</property1>
  <property2 name="model">OCZ-VERTEX3 MI</property2>
  <property3 name="name" />
  <property4 name="shellType">Local Disk</property4>
  <property5 name="space.free">25011576832</property5>
  <property6 name="space.total">119926681600</property6>
  <property7 name="type">Local Disk</property7>
  </device1>
- <device2 name="storage">
  <property0 name="filesystem">NTFS</property0>
  <property1 name="letter">D:\\</property1>
  <property2 name="model">SAMSUNG HD103SJ</property2>
  <property3 name="name" />
  <property4 name="shellType">Local Disk</property4>
  <property5 name="space.free">964832997376</property5>
  <property6 name="space.total">1000202039296</property6>
  <property7 name="type">Local Disk</property7>
  </device2>
- <device3 name="storage">
  <property0 name="filesystem" />
  <property1 name="letter">E:\\</property1>
  <property2 name="model">OPTIARC DVD-ROM DDU1681S</property2>
  <property3 name="name" />
  <property4 name="shellType">CD Drive</property4>
  <property5 name="space.free">0</property5>
  <property6 name="space.total">0</property6>
  <property7 name="type">CD/DVD Drive</property7>
  </device3>
- <device4 name="memory">
  <property0 name="pagefile.avail">15352324096</property0>
  <property1 name="pagefile.total">17141653504</property1>
  <property2 name="pagefile.used">1789329408</property2>
  <property3 name="physical.avail">6995824640</property3>
  <property4 name="physical.load">18</property4>
  <property5 name="physical.load.units">%</property5>
  <property6 name="physical.total">8571060224</property6>
  <property7 name="physical.used">1575948288</property7>
  <property8 name="virtual.avail">2018942976</property8>
  <property9 name="virtual.total">2147352576</property9>
  <property10 name="virtual.used">128409600</property10>
  </device4>
- <device5 name="display">
  <property0 name="bpp">32</property0>
  <property1 name="driver.distversion">8.17.12.7061</property1>
  <property2 name="driver.friendlyversion" />
  <property3 name="driver.name">nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um</property3>
  <property4 name="driver.version">8.17.12.7061</property4>
  <property5 name="height">1080</property5>
  <property6 name="monitor">Generic PnP Monitor</property6>
  <property7 name="name">NVIDIA GeForce GTX 570</property7>
  <property8 name="refresh">60</property8>
  <property9 name="refresh.units">Hz</property9>
  <property10 name="resolutions">1024 x 768 x 60;1024 x 768 x 70;1024 x 768 x 75;1152 x 864 x 75;1280 x 1024 x 60;1280 x 1024 x 75;1280 x 720 x 59;1280 x 720 x 60;1280 x 768 x 60;1280 x 800 x 60;1280 x 960 x 60;1360 x 768 x 60;1366 x 768 x 60;1440 x 900 x 60;1600 x 1024 x 59;1600 x 1024 x 60;1600 x 1200 x 60;1600 x 900 x 59;1600 x 900 x 60;1680 x 1050 x 59;1680 x 1050 x 60;1920 x 1080 x 59;1920 x 1080 x 60;640 x 480 x 59;640 x 480 x 60;640 x 480 x 72;640 x 480 x 75;720 x 480 x 56;720 x 480 x 60;720 x 480 x 72;720 x 480 x 75;720 x 576 x 56;720 x 576 x 60;720 x 576 x 72;720 x 576 x 75;800 x 600 x 56;800 x 600 x 60;800 x 600 x 72;800 x 600 x 75</property10>
  <property11 name="vendor">NVIDIA</property11>
  <property12 name="vram">1342177280</property12>
  <property13 name="vram.desc">4064 MB</property13>
  <property14 name="vram.units">B</property14>
  <property15 name="width">1920</property15>
  </device5>
- <device6 name="sound">
  <property0 name="driver.name">cmudaxp.sys</property0>
  <property1 name="driver.version">5.12.1.8</property1>
  <property2 name="name">Speakers (ASUS Xonar D1 Audio Device)</property2>
  <property3 name="vendor">ASUSTeK</property3>
  </device6>
- <device7 name="sound">
  <property0 name="driver.name">cmudaxp.sys</property0>
  <property1 name="driver.version">5.12.1.8</property1>
  <property2 name="name">Digital Output (ASUS Xonar D1 Audio Device)</property2>
  <property3 name="vendor">ASUSTeK</property3>
  </device7>
- <device8 name="speaker">
  <property0 name="configuration">Desktop stereo speakers</property0>
  </device8>
- <device9 name="network">
  <property0 name="description">Realtek PCIe GBE Family Controller</property0>
  <property1 name="dhcp.enabled">true</property1>
  <property2 name="dhcp.server">192.168.0.1</property2>
  <property3 name="gateway">192.168.0.1</property3>
  <property4 name="ip.address">192.168.0.101</property4>
  <property5 name="ip.mask">255.255.255.0</property5>
  <property6 name="name">{2F8A3751-41AC-4A50-80D8-CBEC945104A0}</property6>
  <property7 name="type">Ethernet</property7>
  <property8 name="wins.enabled">false</property8>
  <property9 name="wins.primary" />
  <property10 name="wins.secondary" />
  </device9>
- <device10 name="windows">
  <property0 name="buildNumber">7601</property0>
  <property1 name="buildType">Multiprocessor Free</property1>
  <property2 name="caption">Microsoft Windows 7 Ultimate</property2>
  <property3 name="codeSet">1252</property3>
  <property4 name="countryCode">1</property4>
  <property5 name="csdVersion">Service Pack 1</property5>
  <property6 name="defaultSystemCountryCode">US</property6>
  <property7 name="defaultSystemCountryName">United States</property7>
  <property8 name="defaultSystemLanguageCode">en</property8>
  <property9 name="defaultSystemLanguageID">0409</property9>
  <property10 name="defaultSystemLanguageName">English</property10>
  <property11 name="defaultUserCountryCode">US</property11>
  <property12 name="defaultUserCountryName">United States</property12>
  <property13 name="defaultUserLanguageCode">en</property13>
  <property14 name="defaultUserLanguageID">0409</property14>
  <property15 name="defaultUserLanguageName">English</property15>
  <property16 name="locale">0409</property16>
  <property17 name="osLanguage">1033</property17>
  <property18 name="osType">18</property18>
  <property19 name="productType">1</property19>
  <property20 name="servicePackMajorVersion">1</property20>
  <property21 name="servicePackMinorVersion">0</property21>
  <property22 name="userIsAdmin">true</property22>
  <property23 name="version">6.1.7601</property23>
  </device10>
- <device11 name="directx">
  <property0 name="description">DirectX 10.0 (Mar2009) or later</property0>
  <property1 name="version">0.0.0.0</property1>
  </device11>
  </System>
- <versions>
  <exe name="MassEffect.exe">1.02.1604.00</exe>
  <exe name="MassEffectLauncher.exe">1.01.00.15</exe>
  <exe name="MassEffectConfig.exe">1.03.00.01</exe>
  </versions>
- <settings>
- <configfile name="GamerSettings.ini">
- <![CDATA[ [AppCompat]
MeasuredCPUScore=174.670074
CompatLevelComposite=3
CompatLevelCPU=5
CompatLevelGPU=3
GPUVendorID=4318
GPUDeviceID=4230
CPUNumLogicalProcessors=4

[SystemSettings]
BorderlessWindow=False
Fullscreen=True
QualityBloom=True
DynamicShadows=True
LightEnvironmentShadows=True
MaxCharacterCinematicLightingPasses=3
EnableLightEnvSHLights=True
MotionBlur=True
FilmGrain=True
ResX=1920
ResY=1080
Resolution=_1920x1080

Problem Details


1) Nature of the problem: Lockup/crash to desktop (desktop is recoverable in all cases).

2) The problem began occuring after my latest playthrough, and not on my previous 3. It always occurs in the tunnel in Illium under Liara's office which runs between the first and second sections of the city.

3) See number 2. Others in the thread have indicated it's related to the Lair of the Shadow Broker DLC. It would seem that this is probable, since I recently installed that.

4) What steps are involved in replicating the problem? About 100 steps -- from the normandy airlock to the illium tunnel :)

5) I had edited coalesced.ini to change my squadmates weapon loadouts, but I reverted to the native coalesced.ini to see if it was causing the problem. The native .ini crashes just the same.

#24
Oddball1

Oddball1
  • Members
  • 61 messages

Roguewolfe wrote...

An interesting thing about this bug: it only affects new games started with LotSB DLC installed. Game saves in progress when the DLC is installed are apparently unaffected. I can say that with relative certainty because the crash is very consistent, but two of my playthroughs I had going when I installed LotSB did not experience this at all (and no settings changes and only a couple of realtime days between them).

1.1: Playing the game via Steam (Product version 01604.00)

1.2: Here's a full system report:
<Report>
- <System>
  <TimeStamp>20110603T102822.281-08:00</TimeStamp>
- <device0 name="processor">
  <property0 name="clockspeed">3307</property0>
  <property1 name="clockspeed.units">MHz</property1>
  <property2 name="family">6</property2>
  <property3 name="model">42</property3>
  <property4 name="name">Intel® Core™ i5-2500K CPU @ 3.30GHz</property4>
  <property5 name="numcores">4</property5>
  <property6 name="numprocessors">1</property6>
  <property7 name="stepping">7</property7>
  </device0>
- <device1 name="storage">
  <property0 name="filesystem">NTFS</property0>
  <property1 name="letter">C:</property1>
  <property2 name="model">OCZ-VERTEX3 MI</property2>
  <property3 name="name" />
  <property4 name="shellType">Local Disk</property4>
  <property5 name="space.free">25011576832</property5>
  <property6 name="space.total">119926681600</property6>
  <property7 name="type">Local Disk</property7>
  </device1>
- <device2 name="storage">
  <property0 name="filesystem">NTFS</property0>
  <property1 name="letter">D:</property1>
  <property2 name="model">SAMSUNG HD103SJ</property2>
  <property3 name="name" />
  <property4 name="shellType">Local Disk</property4>
  <property5 name="space.free">964832997376</property5>
  <property6 name="space.total">1000202039296</property6>
  <property7 name="type">Local Disk</property7>
  </device2>
- <device3 name="storage">
  <property0 name="filesystem" />
  <property1 name="letter">E:</property1>
  <property2 name="model">OPTIARC DVD-ROM DDU1681S</property2>
  <property3 name="name" />
  <property4 name="shellType">CD Drive</property4>
  <property5 name="space.free">0</property5>
  <property6 name="space.total">0</property6>
  <property7 name="type">CD/DVD Drive</property7>
  </device3>
- <device4 name="memory">
  <property0 name="pagefile.avail">15352324096</property0>
  <property1 name="pagefile.total">17141653504</property1>
  <property2 name="pagefile.used">1789329408</property2>
  <property3 name="physical.avail">6995824640</property3>
  <property4 name="physical.load">18</property4>
  <property5 name="physical.load.units">%</property5>
  <property6 name="physical.total">8571060224</property6>
  <property7 name="physical.used">1575948288</property7>
  <property8 name="virtual.avail">2018942976</property8>
  <property9 name="virtual.total">2147352576</property9>
  <property10 name="virtual.used">128409600</property10>
  </device4>
- <device5 name="display">
  <property0 name="bpp">32</property0>
  <property1 name="driver.distversion">8.17.12.7061</property1>
  <property2 name="driver.friendlyversion" />
  <property3 name="driver.name">nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um</property3>
  <property4 name="driver.version">8.17.12.7061</property4>
  <property5 name="height">1080</property5>
  <property6 name="monitor">Generic PnP Monitor</property6>
  <property7 name="name">NVIDIA GeForce GTX 570</property7>
  <property8 name="refresh">60</property8>
  <property9 name="refresh.units">Hz</property9>
  <property10 name="resolutions">1024 x 768 x 60;1024 x 768 x 70;1024 x 768 x 75;1152 x 864 x 75;1280 x 1024 x 60;1280 x 1024 x 75;1280 x 720 x 59;1280 x 720 x 60;1280 x 768 x 60;1280 x 800 x 60;1280 x 960 x 60;1360 x 768 x 60;1366 x 768 x 60;1440 x 900 x 60;1600 x 1024 x 59;1600 x 1024 x 60;1600 x 1200 x 60;1600 x 900 x 59;1600 x 900 x 60;1680 x 1050 x 59;1680 x 1050 x 60;1920 x 1080 x 59;1920 x 1080 x 60;640 x 480 x 59;640 x 480 x 60;640 x 480 x 72;640 x 480 x 75;720 x 480 x 56;720 x 480 x 60;720 x 480 x 72;720 x 480 x 75;720 x 576 x 56;720 x 576 x 60;720 x 576 x 72;720 x 576 x 75;800 x 600 x 56;800 x 600 x 60;800 x 600 x 72;800 x 600 x 75</property10>
  <property11 name="vendor">NVIDIA</property11>
  <property12 name="vram">1342177280</property12>
  <property13 name="vram.desc">4064 MB</property13>
  <property14 name="vram.units">B</property14>
  <property15 name="width">1920</property15>
  </device5>
- <device6 name="sound">
  <property0 name="driver.name">cmudaxp.sys</property0>
  <property1 name="driver.version">5.12.1.8</property1>
  <property2 name="name">Speakers (ASUS Xonar D1 Audio Device)</property2>
  <property3 name="vendor">ASUSTeK</property3>
  </device6>
- <device7 name="sound">
  <property0 name="driver.name">cmudaxp.sys</property0>
  <property1 name="driver.version">5.12.1.8</property1>
  <property2 name="name">Digital Output (ASUS Xonar D1 Audio Device)</property2>
  <property3 name="vendor">ASUSTeK</property3>
  </device7>
- <device8 name="speaker">
  <property0 name="configuration">Desktop stereo speakers</property0>
  </device8>
- <device9 name="network">
  <property0 name="description">Realtek PCIe GBE Family Controller</property0>
  <property1 name="dhcp.enabled">true</property1>
  <property2 name="dhcp.server">192.168.0.1</property2>
  <property3 name="gateway">192.168.0.1</property3>
  <property4 name="ip.address">192.168.0.101</property4>
  <property5 name="ip.mask">255.255.255.0</property5>
  <property6 name="name">{2F8A3751-41AC-4A50-80D8-CBEC945104A0}</property6>
  <property7 name="type">Ethernet</property7>
  <property8 name="wins.enabled">false</property8>
  <property9 name="wins.primary" />
  <property10 name="wins.secondary" />
  </device9>
- <device10 name="windows">
  <property0 name="buildNumber">7601</property0>
  <property1 name="buildType">Multiprocessor Free</property1>
  <property2 name="caption">Microsoft Windows 7 Ultimate</property2>
  <property3 name="codeSet">1252</property3>
  <property4 name="countryCode">1</property4>
  <property5 name="csdVersion">Service Pack 1</property5>
  <property6 name="defaultSystemCountryCode">US</property6>
  <property7 name="defaultSystemCountryName">United States</property7>
  <property8 name="defaultSystemLanguageCode">en</property8>
  <property9 name="defaultSystemLanguageID">0409</property9>
  <property10 name="defaultSystemLanguageName">English</property10>
  <property11 name="defaultUserCountryCode">US</property11>
  <property12 name="defaultUserCountryName">United States</property12>
  <property13 name="defaultUserLanguageCode">en</property13>
  <property14 name="defaultUserLanguageID">0409</property14>
  <property15 name="defaultUserLanguageName">English</property15>
  <property16 name="locale">0409</property16>
  <property17 name="osLanguage">1033</property17>
  <property18 name="osType">18</property18>
  <property19 name="productType">1</property19>
  <property20 name="servicePackMajorVersion">1</property20>
  <property21 name="servicePackMinorVersion">0</property21>
  <property22 name="userIsAdmin">true</property22>
  <property23 name="version">6.1.7601</property23>
  </device10>
- <device11 name="directx">
  <property0 name="description">DirectX 10.0 (Mar2009) or later</property0>
  <property1 name="version">0.0.0.0</property1>
  </device11>
  </System>
- <versions>
  <exe name="MassEffect.exe">1.02.1604.00</exe>
  <exe name="MassEffectLauncher.exe">1.01.00.15</exe>
  <exe name="MassEffectConfig.exe">1.03.00.01</exe>
  </versions>
- <settings>
- <configfile name="GamerSettings.ini">
- <![CDATA[ [AppCompat]
MeasuredCPUScore=174.670074
CompatLevelComposite=3
CompatLevelCPU=5
CompatLevelGPU=3
GPUVendorID=4318
GPUDeviceID=4230
CPUNumLogicalProcessors=4

[SystemSettings]
BorderlessWindow=False
Fullscreen=True
QualityBloom=True
DynamicShadows=True
LightEnvironmentShadows=True
MaxCharacterCinematicLightingPasses=3
EnableLightEnvSHLights=True
MotionBlur=True
FilmGrain=True
ResX=1920
ResY=1080
Resolution=_1920x1080

Problem Details


1) Nature of the problem: Lockup/crash to desktop (desktop is recoverable in all cases).

2) The problem began occuring after my latest playthrough, and not on my previous 3. It always occurs in the tunnel in Illium under Liara's office which runs between the first and second sections of the city.

3) See number 2. Others in the thread have indicated it's related to the Lair of the Shadow Broker DLC. It would seem that this is probable, since I recently installed that.

4) What steps are involved in replicating the problem? About 100 steps -- from the normandy airlock to the illium tunnel :)

5) I had edited coalesced.ini to change my squadmates weapon loadouts, but I reverted to the native coalesced.ini to see if it was causing the problem. The native .ini crashes just the same.


I'll tell you what's odd, is that I had this trouble when I had a pair of Visiontek Radeon 4870's. After I pulled them out, got rid of ATI's drivers entirely, and stuck in a pair of MSI GTX 460's, this problem quit. At that time, I was very disgusted with ATI's drivers.

Out of curiosity, what is the heatsink fan on your videocard like, and how many fans do you have in your case. You may want to try running the fan on your videocard or cards at 100 percent using NTune or MSI Afterburner. Next if your case fans have speed selectors set them to 100 percent, if not this can be done in the bios if the fans are hooked up to motherboard connectors for them. It's a possibility, that either your videocard is overheating or some other component, based on your description of the problem. By the way this crashing problem was fixed in the GeForce 270.61 drivers from Nvidia, and you may want to give them a try if you don't have them already.

#25
Roguewolfe

Roguewolfe
  • Members
  • 5 messages
Yeah, you can see in the above I'm running a GTX 570 (asus to be exact with the enormous 3 fan heatpipe) with the the 270.61 drivers. I have zero overheating issues, I monitor temps with EVGA precision and I never go above 53 C while playing (45 C on the CPU). The card should be stable up to 70 C or so, but I never even approach that. I have Corsair 600T case with 2 200mm fans. Overheating is definitely not an issue. If it was overheating, it would randomly happen in other places. This is extremely specific to illium.