14 réponses à ce sujet

[Bengi010]

This is probably my 3rd or 4th time through this game and I have never had any problems previously. Now, during the fight with Gaxkang in the Unbound quest, my game will crash to the desktop every time, this has happened consistently the last 6 times I've tried it.  I doubt it's my system all the game required specs are exceeded, and like I said I've already played through before without an issue.  Is it possible this one part got corrupted somehow?  And if so how do I fix it?  So far I haven't had trouble anywhere else.

[Kastagir]

Many have reported that certain spells, such as Mana Clash, now crash the game when used in combat under the 1.03 version. This is likely what is happening in this situation.

[BarakIII]

I'm having the same issue. The game crashes everytime at about the point he gets to about 1/4 health. I only recently bought the game and have the 1.04 patch.

[stuka1000]

1.04 appears to have made the game a lot less stable. I too get crashes during various combats. Also crashes everytime I try to use an acid flask etc.

[Zrasis]

I had the same issue, i must've tried a dozen times. So I thought that, maby it's a problem with the graphics. I tried two different graphic cards (Ati Radeon HD 4770 and a 5850) same issue tho. Upgraded to catalyst 10.7 (from 10.6), no change.



Finally I fought it while making sure that I was looking into the wall the whole fight, pausing before i turned to look at Gaxkang, for managing characters or whatnot. The fight went without a glitch.



So, unless it was pure luck then some of its spell effects was crashing the game, No idea.. Fight's done and over with...

[Kastagir]

The 1.04 update addressed "several memory leaks" and has made the game more stable for some people, allowing them to finish the expansion. However, nothing in the patch notes suggests that these spell-related crashes were even looked at, let alone investigated or a fix attempted. That said, you can expect the exact same behavior in this regard as you observed in 1.03.

If you are still playing in Origins, there really is no benefit to installing 1.03 or 1.04 as they break several mechanics of the base game and only allow access to newer DLC. As of yet, Bioware has not made any promises to address these issues, or any of the other problems introduced by the 1.03 or 1.04 updates. In fact, they have not even acknowledged their existence.

[Paul_Rocks]

Did you ever manage to finish the fight? I'm now having exactly the same problem. I get Gaxkang to about 1/4 health and the game just crashes, doesn't seem to matter what I'm doing at the time - it's most annoying.

[awpdevil]

Changing the camera view killed that crash for me. As soon as the fight starts, pause the fight and go into the dungeon crawler view (the over head view). It may or may not work for you, but I have an ATI card as well.

[ANDY5151]

same scenario with the fight against the fire demon that drops Yusaris. I tested it about 6 times and twice I got a crash. Both times the crash happened when an AOE effect was triggered. The first time when he spawned and that cleanse like effect happened and second when a mage casted a fireball and it exploded.

[Zrasis]

Paul_Rocks wrote...

Did you ever manage to finish the fight? I'm now having exactly the same problem. I get Gaxkang to about 1/4 health and the game just crashes, doesn't seem to matter what I'm doing at the time - it's most annoying.

Yes, just make sure that you set the camera view so that you cannot see Gaxkang's spell effects. Keep the game paused whenever you have to "look" at it.

[Paul_Rocks]

Hmm, last time it crashed I was looking in the opposite direction but it's possible I could see the aoe spell surrounding me. I'll give it another go tonight, thanks for the advice.

Modifié par Paul_Rocks, 10 août 2010 - 09:17 .

[Quels]

It's probably a dual, triple or quad core problem where it's not registered correctly and cause ctd when using certain spells or being in certain areas.

This seems to be the major problem for most users with a lot of CtD

Something that Bioware needs to fix but shutting down the cores that are not registered by Bioware makes the game stable (in my case)

[Paul_Rocks]

Thanks for the all help guys. I went with awpdevil's approach and it worked fine 1st time.

[MeganHunter]

An old topic, but unfortunately I find myself there now. Was 1.04 the last patch Bioware ever made? I'm starting to feel like a whiner, but I have to remind myself if a game keeps giving me quests impossible to finish, I really do deserve my money back. I've been playing this for a week and I don't think I've ever come across a buggier game in my life, for any genre or console. That's not exactly a contest a company should want to win.

[Gorath Alpha]

There's just barely a question in what appears to mostly just be a rant. The alltime winner for bugs was either Daggerfall, from Bethesda, or a version of Pool of Radiance newer than the original Gold Box Game.

There is probably, finally, going to be a real 1.05 patch. IMO, the last patch as an actual repair for bad Beta testing was 1.02a. After that, they only did enough in the way of a patch to keep you from using this or that DLC or expansion if you didn't have it, and 1.03 was as likely to cause new problems as it was to fix anything.

Meanwhile, if the thread you attached this to was the newest you could find, I think it was better left in the graveyard.