77 réponses à ce sujet

[MosyM80]

Doesn't work for me, I mostly get my crashes during combat.

[Y2DAZZ]

Used to crash quite often for me, but I did as the OP suggested, updated my Graphics card and turned off the Online tab stuff and it allowed me to play for about 4 hours with no problems, until just now when it crashed.



Tried what another poster suggested of forcing DX9 and it just made the screen lag and crash almost instantly, however I have the Steam version of the games.

[Jaesic]

Ya, I don't particularly recommend forcing lower modes; though it's not a bad idea to do the runtimes update as was suggested to ensure the full backwards compatibility of dx11 is there. If you don't have those .dll's installed, forcing dx9 mode won't actually do you any good... because if those files aren't present, it's going to fail (which may be the exact reason you crashed immediately when you tried this).





Also, remember when you're trying to isolate a problem that you do one thing at a time. This gives you a clearer picture of what exactly you changed that caused a difference. That'll let you report better info back here, which will help Bioware correct the real cause of the problem so we don't have to keep using work-arounds.



For those having issues in combat especially around AoE spell results... have you tried shifting texture type? maybe there's an issue with the particular bit texture that you're using with your graphics card (this can happen even when your drivers are up to date and you have a high end card)... anti-aliasing level is another adjustment that you should try a couple settings on. Strangely enough, in some cases, I've actually had better results from a higher AA setting than a lower one (Age of Conan was like that for my system).

[Mustang68jd]

Tried the -dx9 tag, and it crashes randomly to desktop the same as usual. Tried reinstalling Dirextx components, seems to run smoother, but crashes. Tried running in SLI, out of SLI, using different nVidia drivers (on 195.62 for 280M nVidia mobile cards at the moment) and it crashes. Tried the affinity core fix on quad machines -- it still crashes and is unplayable on only one core. I've reinstalled C++ runtime components, crash. I'm getting to the point that it must be the game that has poor, flawed programming. Running it on Vista 64.

[IC_MCMXCII]

try this http://social.biowar...8/index/1835264 you have nothing to lose

[Y2DAZZ]

Bump.



I noticed a few people posting new topics on the front page whom are having the same problem.

[Sionnach22]

I've also started getting crashes after installing the v1.03 patch. My screen goes blank, my HP monitor tells me it's going to sleep and the computer no longer responds. I have to reboot using the power button. I have an HP Pavilion A6152n with Windows 7 64-bit. It does have Realtek HD Audio as mentioned above, with the latest driver reported by Windows Update. The video card is an NVidia GeForce 8600GT, with driver version 196.21.



The crashes have always happened during a cut scene, for what it's worth. I've started to replay DAO with a second character and the crashes have happened in Ostagar and in the Elven areas before that.

[Jaesic]

Yes, just a reminder that there ARE several potential fixes in this thread. If you're new to the thread please don't just announce that you have the same problem (especially if you're just going to complain about the programming or Bioware in general). This thread is not a bug reporting thread. Looking to get feedback on whether a work around that has worked for some of us, happens to work for you.



So... those of you who recently posted, have you tried disabling the recommended settings (Autosave and the Online Profile options)?

[Jaesic]

IC_MCMXCII wrote...

try this http://social.biowar...8/index/1835264 you have nothing to lose

Actually, I disagree with you there. This is something that applies only to a very limited number of people for a commonly occuring problem. IF the crashes had anything to do with the difference between 64 and 32 bit architecture/programming, those of us who are running with older machines would not be experiencing the problem. Now... that doesn't mean there aren't issue that you can resolve with that fix... but you should be very clear up front that its a fix for a very particular sub-set of problems and users. Even if it does fix some type of crash... there's no guarantee they aren't also experiencing the crashes caused by problems that apply to many others.

[Melisenta]

Jaesic wrote...

IC_MCMXCII wrote...

try this http://social.biowar...8/index/1835264 you have nothing to lose

Actually, I disagree with you there. This is something that applies only to a very limited number of people for a commonly occuring problem. IF the crashes had anything to do with the difference between 64 and 32 bit architecture/programming, those of us who are running with older machines would not be experiencing the problem. Now... that doesn't mean there aren't issue that you can resolve with that fix... but you should be very clear up front that its a fix for a very particular sub-set of problems and users. Even if it does fix some type of crash... there's no guarantee they aren't also experiencing the crashes caused by problems that apply to many others.

Quite frankly I do not understand what you disagree with... Yes the problem indeed is widespread. But it's not like we are discussing here what fix is right and what wrong. IC_MCMXCII was just trying to help, just like you. And might I add his fix did solve the CTD issue for me ( at least I am able to play for 1-2 hours, instead of 5-15 minutes, more testing today). So uhm... yeah... I disagree with you here:wizard:

[Obode]

What I want to know Is, Why the hell has this problem not been addressed ? It seems like a obvious Nr.1 on the Hotfix list.. tried the various advices in this thread, made no diffrence what so ever.



Never had this issue before installing 1.03.. now it happens every 5 mins.. Its totally unacceptable that this problem has not been resolved since this patch of horrors was released.

[TolaGarf]

I seem to have fixed the CTDs by going from 4x AA to only 2xAA.

[Allroy]

Never had a crash with DA:O, played with the original version. Installed Awakenings and I can't even play the darn thing. Crashes CONSTANTLY. Tried all solutions in this thread. Updated all drivers. Still crashes all the time. Annoying.

[Terrifyer]

Jaesic wrote...

Yes, just a reminder that there ARE several potential fixes in this thread. If you're new to the thread please don't just announce that you have the same problem (especially if you're just going to complain about the programming or Bioware in general). This thread is not a bug reporting thread. Looking to get feedback on whether a work around that has worked for some of us, happens to work for you.

So... those of you who recently posted, have you tried disabling the recommended settings (Autosave and the Online Profile options)?

As a person who has suggested one of the said "fixes", I strongly suggest to simply wait for a fix from BioWare. The 1.03 patch is bugged, severely bugged. It is so bugged it resembles one of those new darkspawn cockroach monstrosities from Awakenings. So unless you feel like reinstalling the game without the 1.03 patch, my advice is to put this game on the shelf until BW removes their head from their anal cavity.

I apologize for being crass, but this is quite possibly the worst release ever from BW from a technical standpoint. It's very disappointing to see a company of BioWare's standards roll out an expansion with such an unstable patch, especially AFTER they had a stable version of the original game to begin with.

Then again, this is what happens when you allow EA to put their hands on your product. Shameful.

[TheEightman]

Surango wrote...

20thcenturyghost brought up an interesting point in a different thread. This game was originally deigned on DirectX 9. Yet Win7 and Vista run on DX10/11 have you tried installing the end user runtimes? www.microsoft.com/downloads/details.aspx

Instructions:


Make a folder and call it DX on your desktop.
Download the
file, when you run it, it asks for a destination path to extract the
files. Use the folder you just made.
Go into the DX folder and find
the setup utility and follow its instructions from there.

It doesn't say you have to restart afterward, but it's probably a good idea to do so either way. When you're done, you may delete the DX folder.

if you need to find out what version of DirextX is on your computer, go to Help and Support from your star menu and type in directx and you'll see a link that says. "What version of DirectX is on your computer?" Let this run a diagnostic and you'll know for sure. If you let it connect to the internet, it says it will also check your drivers.

I was having the CTD during battle problem after upgrading from WinXP 32-bit to Win7 64-bit.  While playing on XP (even after patching the game to 1.03) I never had any problems whatsoever.  Then, after installing Win7, reinstalling the game, and re-patching to 1.03 the game crashed mid-battle after only 30 minutes or so of playtime.  This happened to me twice in a row during the same battle.

I followed Surango's above instructions and just got done playing for about 4 hours with no crashes or freezes.  Hopefully (fingers crossed) this has resolved my problems. If you were having the same problem as me and haven't already tried this for yourself, I would definitely recommend giving it a shot.  Thanks, Surango!

[Jaesic]

Melisenta wrote...

Quite frankly I do not understand what you disagree with..

What I disagreed with was the nonchalant attitude, that there was nothing to lose. There's a great deal of difference between toggling off ingame settings and changing external/OS settings or recompiling the executable version of the game. I've seen suggestions that involve changing the code of the game... neither of those things are good ideas to offer someone who's just looking for a quick solution. Even if they are perfectly accurate in being solutions (a good example of this is the fix that's been posted for lockpicking... completely logical and probably the exact change that BioWare will end up using... but not something I'd casually recommend to someone who isn't a programmer). You're not going to break your game (or computer) by changing the autosave setting... some of these other things CAN have an impact on far more than playability of one game... especially for someone who doesn't really understand what they're doing and just changing options because someone else said its a fix.

Fortunately, it WAS a fix for you. And you knew what you were doing in following it. Not every player reading this forum/thread is going to be in similar conditions.

[Sionnach22]

I installed the February 2010 DirectX redistributable updates as suggested by Surango and added -dx9 to the program shortcut. I've played several times since for an hour or more and have not had any more crashes during cut scene dialog.



Thanks for the help. I'm keeping my fingers crossed... I'll report back if the crashes (full lockup, blank screen) re-occur.

[Surango]

It's a shame so few have reported in. From the looks of other threads though it seems DX is helping people with a retail version of the game and turning off the online options is helping folks with a digital version.

Modifié par Surango, 24 mars 2010 - 05:55 .

[Jaesic]

Sionnach, I'd be interested in hearing if you were able to run without the -dx9 added into your shortcut now that you have the updates installed. If you have the time to experiment.

[Sionnach22]

Jaesic, I'll give it a try without the -dx9 tonight and report back.

[Valsung]

Tried the -dx9 tag and installing the DirectX end-user runtimes, no such luck. I also tried the online options changes, no such luck there as well.

[sohryu621]

Game crashes as soon as I cast any kind of spell combo or overlap AoE spells. Had the options disabled before reading this thread.

System specs

AMD Phenom II x3 720 BE (not overclocked)
Corsair DDR 2 800 8G
Sapphire 4850 512M
Creative XIFI xtremegamer
Windows 7 Pro 64

All drivers are up to date.

Never had any probelm with 1.00 except for loading time gradually increasing, yet Awakening is simply unplayble for me. Guess I'll just continue playing Supreme Commander 2 and DoW 2 Chaos Rising.

Modifié par sohryu621, 24 mars 2010 - 12:37 .

[Jaesic]

Sohryu, have you tried the Direct X method yet? Many people with the AoE spell crash seem to be getting resolution to them by using that.

[Uebelkraehe]

I'm running DA:O on Windows XP and an A 64 X2 - no Problems with stability at all until 1.03 but now the game crashes frequently. That's why i can't really believe the problem is about DX11 or Phenom/Core xy CPUs...

[Sionnach22]

The crashes started again despite the dx9 switch and the DirectX update. I'm sorry to say that I uninstalled Dragon Age, re-installed and patched up to 1.02a. I'll lurk here and wait for a proper patch.