17 réponses à ce sujet

[GPA_Nemesis]

Just a curiosity, when looking at crash threads, I see a very large portion of uses with these issues are those running 64-bit versions of Windows XP, Vista, or 7.  I'd like to see if this is a trend, as it may help the coders identify the issues quicker and easier.

So please, if you are crashing, just note your OS here, along with whether it is 32 or 64 bit.

Thanks,
-Xerek

[Wormrose]

32-bit here.

[sarx8172]

I'm running a 64-bit, and I only crash when I excessively spam large spells. i.e. having 3 mages in party, simultaneously casting large spells like mana clash and inferno, tempest, blizzard, as well as a warrior casting holy smite. Usually makes me just lag slightly, but occasionally causes me to crash. Not that big of a deal for me, but for some others it can have significant impact. That effect was not present before patch 1.03/Awakening for me, but I'm not sure which one is the culprit since I got both of those at the same time.

So essentially, the same issue as mrfoo1.

Modifié par sarx8172, 22 mars 2010 - 06:15 .

[bartoni33]

For what it's worth I've ran game on both XPx32 and Win7x64 and it slows to a crawl/crashes at the same place (Landsmeet) on both systems.

[Terrifyer]

I'm beginning to think this is a DirectX 10 issue, or it's at least somehow involved. With that said, here are a couple of minor things I did that seemed to be helping, as I just played a long session without any crashes, doing several battles and boss fights.

Note: You should only do these if you're running Windows Vista or Windows 7, either 32 or 64 bit.

I installed the 4GB memory patch from ExplorerSuite (info here: http://social.biowar...35264/1#1845819) and still had the same CTD issue, however I also decided to try 3 other things with my daorigins executable and as a result played for the last 5 hours crash free:

1) Run it as administrator
2) Set the compatibility mode to Windows XP service pack 3
3) Force the game to run in dx9 mode

For those that don't know how to do this, just right click on the game's shortcut on your desktop (make one if you don't have one). The target field should read something like "C:\\Program Files\\dragon age\\bin_ship\\daorigins.exe" or the like. at the end of the line add "-dx9", without the quotes. You can change the game to run in XP sp3 compatibility mode under the compatibility tab, just select it from the drop down box.

Again I'm just saying this worked for me, as I just played for the last 5 hours or so, doing several battles and boss
fights without a single CTD. Good luck.

Modifié par Terrifyer, 22 mars 2010 - 10:00 .

[ROBO249]

64 bit vista- most crashes at battle scenes, 3.2 gig amd cpu-gigabyte ds5 board,2x asus 3850 video cards,crossfire,4 gig memory

[Megbear]

I have window 7 64 bit, quad core, 4g ram and have been running the game in dx9 mode but I still experience random crashes within 1-2 hours playing. Also noticed that during combat scene the screen start to lag if it is a big battle or I have been using a lot of spells simultaneously. So far from the threads I've read the problem seem to be patch 1.03, I just hope Bioware will fix this problem soon because it really decrease my enjoyment of playing Dragon Age!!

[TheEightman]

 Unfortunately I don't have a solution, but maybe my situation is unique enough that the information will be helpful.

I have been playing the game since release on 32-bit Windows XP with zero audio/video problems and zero crashes.  This includes about 5-7 hours on version 1.03, also with no problems whatsoever.

Yesterday I upgraded my PC to 64-bit Windows 7.  I haven't made any changes to hardware or anything else.  In other words, the only thing that changed was my OS.  I reinstalled all of my programs, updated all of my drivers, reinstalled the game from disc, and re-patched to version 1.03.  I am still using my old saves carried over from when I was playing on WinXP.  Within 30 minutes of starting the game it crashed to desktop mid-battle.  I restarted the game and once again it crashed at pretty much exactly the same point.  

The strange part is, the battle the game crashed on isn't even the first one that occurs after my save point, it's the second.  As far as I can tell I was using the same spells/abilities in both battles, so I don't know why the game was fine with them in one context and not the other.  Not sure if it matters, but the battle I was able to play through fine is the first one that occurs *-trying to avoid spoilers!-* right after Sloth in the Mages Tower segment of the core game.  The battle that crashed me both times is the one that occurs directly after that.

So, to sum up:  On 32-bit Windows XP everything is hunky-dory, but on 64-bit Windows 7 something is rotten in the State of Ferelden.  

I hope this information is helpful to someone that is more tech-savvy than I am.  I'm going to go try some of the suggestions posted here and in other threads and see if they help.  If not, I may just reinstall the game and try to run it un-patched until BioWare comes up with a solution to whatever the problem is.

[Ickis99_MA]

W7 64bit, Quad-Core, 4GB Ram.Two crashes so far after 40 hours of playing. Both in combination with excessive use of spells.

[shnauser]

64-bit Vista.

Manged to play for a full 30 min yesterday before the crash galore started again.

[AllThatJazz]

64 bit Win 7. Had one Origins playthrough with 64 bit Vista, didn't crash at all. This playthrough, Denerim seems like bug city. Crashes on area transitions, battles, just walking around. Only really in Denerim, though (the occasional crash elsewhere is starting to creep in, but only since patch 1.03). Also getting weird graphical glitches. Thought it was my gfx card, but again it only happens in Denerim.

[Melisenta]

Win 7 64 bit here. Completed 3 playthroughs prior to installing 1.03 - no lag/ctd issues at all. Now it's a crash fest.

[Jockel04]

Dragon Age (without Awakening), Patch 1.03



Win 7 Pro 64Bit, AMD Phenom II X3 720, Radeon 4770, 4GB Ram.

Game crashes anywhere between 5 to 90 minutes but always during battle scenes. Never happenend before this last patch.

[warchanter]

DAO gave me very few problems (some crashes here and there, but after some hours of gameplay). Awakening crashes a lot. And I mean A LOT. 32 bit system (Windows XP).

Modifié par warchanter, 22 mars 2010 - 04:59 .

[Katreyn]

64-bit Win 7. I don't think I ever crashed very often if ever in Origins. At least not a crash to desktop. The crashes I had before were due to slowing down frame rate that ended in my video card freaking out.

In Awakening Now I crash went AoE spells are used. This is really the only time I can say I crash to desktop. Pandemonium to be sure, is one of the spells that almost always crashes me at the start of a battle.

[Xiol32]

W7, i5 750, ATI 5770, 4GB RAM.



I'm running a 64-bit OS because I have 4GB of RAM and prefer to have access to all 4GB, thank you. Not supporting a 64-bit OS is unforgivable - especially considering it worked fine pre-1.03.



I have not been able to carry on my game since the patch, and will not be purchasing Awakening until this issue is fixed.



You want my money, EA? Fix your damn game.

[MMO_Addict]

64-bit Vista. Have never experienced a single crash...but I still have all the slow loading and now FPS issues with that last patch.



Have not bought Awakenings yet...so no clue if I would start to crash (might have to go get it now just to see...*must....resist....)