30 réponses à ce sujet

[Lucasian]

Like so many others, this game crashes about 75% of the time a spell is cast, and all I can find on this forum are five+ month old threads about this problem.

So really, that's it then? A broken game with no further support?
I just want to finish my game without crashing. Is there anything to be done?

It's sad that it got to this, though. How the mighty have fallen.

Ah well, at least I can let my tiny voice be heard when DA2 and ME3 come out: guess who's money you're not getting, EA/Bio.

[lizzbee]

All I can suggest is what worked to resolve most of my spell-related crashes before I installed patch 1.04: upgrade your .NET framework to version 4. It worked quite well for me with 1.03, even in Awakening, but 1.04 broke everything all over again.

[JackM]

Without any information about your computer, it's really difficult to help you. Please, give the following information:
- Windows version
- RAM
- CPU
- Graphic card and drivers
- Audio card and drivers

Have you updated DirectX with the latest version available here? Do not forget to select the language appropriate to your version of Windows.

Have you also updated .NET Framework with the hotfixes and new versions available on Windows Update web site?

If the version of PhysX currently installed on your computer is newer than the version supplied with DA:O, could you try to uninstall this version and resintall the DA:O version?

[Gorath Alpha]

Lucasian wrote...

Like so many others, this game crashes about 75% of the time a spell is cast, and all I can find on this forum are five+ month old threads about this problem.

I just want to finish my game without crashing. Is there anything to be done?

If you are only making a nonspecific comment / rant / venting about anything, without any request for advice, take it to Off-Topic.  If it's 1.04 that you want to ask for fixes to, Nathan will be back tomorrow.  Phrase your comments into some sort of question that can actually be dealt with here, by the residents of the forum, plus Nathan.  In the meanwhile, if you must run Windows 7, you should forget about DLCs and expansions requiring patches 1.03 / 1.04 -- you can uninstall, the game, and then reinstall, but stop with patch 1.02A

I see that someone else is trying to turn this around for you also.  He obviously types a bit faster than I do.  Here are Chris Priestley's Fill in the blanks instructions, slightly paraphrased from his ME-2 sticky:

Chris Priestly wrote...

Hello (BW game) fans.

This forum is for fans and customers of (Bioware Games),  to share help and to assist each other with technical issues.

Please remember that official game support for (this game) is by Electronic Arts.

If you have a BW Game for PC issue, official support can be found through EA Customer support here:
http://support.ea.co...y=0&p_redirect=

Please try to help one another with problems, but remember the best way to ensure accurate support is to contact the official support provided.  (Edited by G. here: When you want to pose a question for your fellow game players,  these are the basics previously laid down.)

1.  It’s important to identify which product is experiencing the problem.

  a.   Is it the console version or the PC version?  (Edit: Most of this is strictly applicable to the PC version.)

  b. Media: physical disk or digital download (and which vendor)
 
2.  System Details

  a.  Processor / Core count / Core Speed / Main RAM Amount                                              

  b.  Display Adapter / VRAM / Driver Version (just saying "latest drivers" doesn't help -- Edited: only ATI / nVIDIA cards are supported)                                                  
 
c. Sound Adapter / Driver Version

  d. Operating System (& service pack if applicable)

  e. Direct X Version

3.  Problem Details

  a.  When it comes to problem details, think about the five basic questions: Who? What? When? Where?  Why? Okay, so “Who?” doesn’t really apply here, but the others do.

  b.  What?
What is the nature of the problem that you’re seeing?

  c.  When?  When does the problem occur? Every time you engage in a particular action or only after so many hours of play?

  d.  Where? Where does the problem occur? Is the problem localized to a particular planet or does it occur everywhere?

  e.  Why? As much as possible, can you isolate the problem to a specific set of steps?

If you follow these guidelines, and provide the requested information when posting, it will increase the likelihood that someone will be able to help you diagnose the problem and find a solution.

Please report issues, after checking these steps, in new threads.

That's the sort of thing the other gamers can look at to try to help you, if you actually want any help here. 

Modifié par Gorath Alpha, 16 août 2010 - 11:47 .

[Lucasian]

Gorath Alpha wrote...

If you have a specific comment / rant / venting about anything, without any request for advice, take it to Off-Topic.  If it's 1.04 that you want to ask for fixes to, Nathan will be back tomorrow.  Phrase your comments into some sort of question.

Then let me go ahead and copy/paste it for a third time, just for you, "Is there anything to be done about the crashes?" Which, by the way, are so widespread and apparently without a specific cause, I can ask this without including any information about my own system! Ah, how the lazy reign!

Though it's interesting to note that despite the 'lack of a question', you gave me advice anyway. I wonder, is this irony or a paradox? Or both? Surely something to consider! 

Anyway, I've got five different tips to sort through; will post results later!

[Lucasian]

Not to forget, thanks for the advice so far; and if there's anything else, please, keep them coming.

[lizzbee]

Lucasian wrote...
Though it's interesting to note that despite the 'lack of a question', you gave me advice anyway. I wonder, is this irony or a paradox? Or both? Surely something to consider! 

The very model of a Salarian scientist?

[Crunchyinmilk]

if you must run Windows 7, you should forget about DLCs and expansions requiring patches 1.03 / 1.04 -- you can uninstall, and then reinstall, but stop with patch 1.02A

Every thread of this type has 'them', and this time I get to be 'them':

I haven't seen any sign of this frequent crashing issue and I'm running w7(64), steam install of DAO patched up to 1.04 with Awakening, WK, RTO all enabled and completed without issue (other than that damn starmetal meteorite never falling). I'm playing an Arcane Warrior and Morrigan is there too, firing off lots of spells.

I got my first crash 30 hours into a new DAO game when teleporting through Redcliffe. No doubt my own fault because I was abusing the teleport mod which stresses the sequential level loading. I've had a grand total of two application crashes in the whole play through.

What manner of beast (machine) can accomplish this stable play through? A year old macbook pro with a measly 9600M video card. Running at medium graphics/high textures/no anti aliasing/1440x900...

At a guess, do a hard disc check and be sure your DAO content is defragmented, use iobit's gamebooster to defragment individual folders on your system. 1.04 seems to have changed level loading/streaming/flushing. Speedy access to files is a must.

[Quels]

The game is still extremely flawed and you should be prepared to make crazy homemade fixes and workarounds to just about anything imaginable depending on your system.

There are problems with items, quests, conversations, skills, abilities, spells, ram usage, cpu usage, internet connections, dlc ... you name it and there is trouble in this area too

Luckily the game is so good that it's worth the trouble, imo, but I can easily understand why many players give up before actually getting startet,

[jess879malagant]

I agree that this game crashes about 75% of the time a spell is cast. I also recently got a GTX 240. I intend to try casting spells in game with the game running at its lowest settings. I will let you know how it goes.

[samix132]

Lucasian wrote...

Like so many others, this game crashes about 75% of the time a spell is cast, and all I can find on this forum are five+ month old threads about this problem.

So really, that's it then? A broken game with no further support?
I just want to finish my game without crashing. Is there anything to be done?

It's sad that it got to this, though. How the mighty have fallen.

Ah well, at least I can let my tiny voice be heard when DA2 and ME3 come out: guess who's money you're not getting, EA/Bio.

How this game got all those good scores in reviews if this game is so badly broken?! I would like to get performance patch to get fps i should get. I stopped playing after lotharing because i couldn't take no more how this game runs. It's weird though that i didn't run into any crashes,bugs or anything else. Just poor performance.
So i hear you man! I'm also frustrated because this.
Vista 64bit
Hd 5770 1gb
Core 2 quad 9400 2.6ghz
4gb ddr2
Asus p5ql se (integrated realtek)

[JackM]

@samix132:
Check this thread.

[Lucasian]

What didn't work:



- updating.NET Framework

- using PhysX included with DA:O

- updating drivers (it was only one month old to begin with, so meh)

- setting it to XP/Vista compatability



Ah well

[JackM]

Still no details about your computer setup.

[bartoni33]

Lucasian wrote...

What didn't work:

- updating.NET Framework
- using PhysX included with DA:O
- updating drivers (it was only one month old to begin with, so meh)
- setting it to XP/Vista compatability

Ah well

I feel your pain. I have done all of those and more and still no positive result.

Looks like we must face facts and admit that BW/EA/whoever dropped the ball on this one. I think it's safe to say they do not have ANY idea what is wrong with this game or how to fix it. Reminds me of the "MMO" Mortal Online, devs with no clue crapping out fail patches while saying "it's your fault not ours"! While I will NEVER buy another DA game again I shall be looking forward to ME3/TOR though. What a waste...

[samix132]

bartoni33 wrote...

Lucasian wrote...

What didn't work:

- updating.NET Framework
- using PhysX included with DA:O
- updating drivers (it was only one month old to begin with, so meh)
- setting it to XP/Vista compatability

Ah well

I feel your pain. I have done all of those and more and still no positive result.

Looks like we must face facts and admit that BW/EA/whoever dropped the ball on this one. I think it's safe to say they do not have ANY idea what is wrong with this game or how to fix it. Reminds me of the "MMO" Mortal Online, devs with no clue crapping out fail patches while saying "it's your fault not ours"! While I will NEVER buy another DA game again I shall be looking forward to ME3/TOR though. What a waste...

I'm in the same boat as you guys. Last game i'll buy from BW is Me3 and thats that. Tried ABSOLUTELY every possible thing i read anywhere and contacted five times customer support and used like 50hours or more in internet to find answers. I really REALLY were looking forward to this game especially when they ¨lowered¨ their system requirements. Well this game just gave me PLENTY OF FRUSTRATION and cost me 60e but it isin't end of the world. End of the world is if DIABLO 3 HAS THIS KIND OF PROBLEMS!!!!

[JackM]

I'm in the same boat as you guys. Last game i'll buy from BW is Me3 and thats that. Tried ABSOLUTELY every possible thing i read anywhere and contacted five times customer support and used like 50hours or more in internet to find answers. I really REALLY were looking forward to this game especially when they ¨lowered¨ their system requirements. Well this game just gave me PLENTY OF FRUSTRATION and cost me 60e but it isin't end of the world. End of the world is if DIABLO 3 HAS THIS KIND OF PROBLEMS!!!!

Before you give up, try the following:
  1. Install the latest Catalyst driver version (10.7)
  2. in CCC, set Anti-aliasing and Anitropic Filtering to Application controlled. Set Catalyst AI to Standard and disable Adaptive Anti-aliasing.
  3.  if you want to enable VSync in-game and regain 5-15 fps, you can force Direct3D Triple Buffering using an external application like RadeonPro. Note that this application also allows you
to activate Anisotropic Filtering to enhance the aspect of textures as there is no in-game setting for it.

Modifié par JackM, 16 août 2010 - 08:00 .

[lizzbee]

Lucasian wrote...

What didn't work:

- updating.NET Framework
- using PhysX included with DA:O
- updating drivers (it was only one month old to begin with, so meh)
- setting it to XP/Vista compatability

Ah well

I'm getting the impression that there's some other random weirdness that Win 7 users experience.  Do you have integrated audio?  I've heard a lot of our mutual crashing problems might be related to that, though I'm damned if I'm ready to dump any more than $70.00 to maybe fix a problem.  Dedicated sound seems stupid if you play wearing headphones.  The .NET update worked for me, until the current abomination of a patch not only destabilized the game after the Landsmeet, but glitched many of my characters' dialog.  Apparently, one of the current patch's "upgrades" was a few tweaks to the game's audio.  I'm curious to see what the crashing commonalities are.

So far, from what I've gathered on the forums, it's:

Windows 7, both 32 and 64 bit
probably integrated audio
and the problem affects both Nvdia and ATI users similarly  (my own card-- 9800GT, 1GB)

[Eldingo01]

I don't know whether anyone with an Nvidia card has tried this before, but I found that the game stopped crashing so much for me by going to the Nvidia control panel and forcing the Physx to use the CPU instead of the Graphics card.



I don't know what effect this will have on performance for some as it will move more processing onto the processor.



I only have 1 graphics card in there, so maybe the PhysX was overloading it a bit, especially during the large spells.

[JackM]

Eldingo01 wrote...

I don't know whether anyone with an Nvidia card has tried this before, but I found that the game stopped crashing so much for me by going to the Nvidia control panel and forcing the Physx to use the CPU instead of the Graphics card.

I don't know what effect this will have on performance for some as it will move more processing onto the processor.

I only have 1 graphics card in there, so maybe the PhysX was overloading it a bit, especially during the large spells.

This seems like a good hint. Maybe you should post it on other threads with nVidia users complaining about frequent crashes.

[bartoni33]

Eldingo01 wrote...

I don't know whether anyone with an Nvidia card has tried this before, but I found that the game stopped crashing so much for me by going to the Nvidia control panel and forcing the Physx to use the CPU instead of the Graphics card.

I don't know what effect this will have on performance for some as it will move more processing onto the processor.

I only have 1 graphics card in there, so maybe the PhysX was overloading it a bit, especially during the large spells.

Does PhysX happen during cutscenes? Because that's where myself and others are having issues. Turning off PhysX is one thing I haven't tried yet.

[ANDY5151]

Eldingo01 wrote...

I don't know whether anyone with an Nvidia card has tried this before, but I found that the game stopped crashing so much for me by going to the Nvidia control panel and forcing the Physx to use the CPU instead of the Graphics card.

I don't know what effect this will have on performance for some as it will move more processing onto the processor.

I only have 1 graphics card in there, so maybe the PhysX was overloading it a bit, especially during the large spells.

gonna give this a shot when i go back to 1.04 and awakening in this playthrough.  How would you go about doing this..the only option I have in the control panel is to enable or disable physx.

Modifié par ANDY5151, 17 août 2010 - 03:33 .

[jess879malagant]

Does using Nvidia control panel and forcing the Physx to use the CPU instead of the Graphics card solve the problem of frequent crashes.

[flagondotcom]

One thing that helped stability for me on WinXP but is also applicable to Vista and Win7: If you have > 2GB physical memory, the game won't use it by default. There is a free download "CFF Explorer" that can be used to edit the binary headers in the daorigins.exe file (make a backup copy first, of course!) and there is at least one thread on this forum about how to do it. On WinXP 32-bit, there's a change to boot.ini needed as well, but Win7 and 64-bit OS variants shouldn't need any "hints" about using all physical memory.



It might not help for those who primarily are having crashes for cutscenes and spells with specific visual effects, but it's a fairly simple fix and probably worth a try if other things haven't worked.



As to how the game got such good reviews with so many bugs and crashes? I can only guess that the video cards in the reviewers' systems were closer to what BW used for testing. I'm playing on two separate older NVidia cards with 256MB memory, and since applying the "use more memory" fix above I'm having almost no crashes. Good luck.