65 réponses à ce sujet

[Bfler]

I don't WIn 7 is the main reason for the crashes. I have installed the game on 2 different PC. The first is a dual boot with Vista 32bit and Win 7 64bit. The second runs with Win 7 64. Both have 4 GB Ram. On the second PC there are no crashes but on the first PC there are some crashes with Win 7 and a lot of crashes with the old Vista.

The difference seems to be the amount of installed modules. I have installed a lot of mods on the first but only the basic Bioware modules on the second PC. What I recognized is that with Vista the amount a crashes seems to increase with every additional module.

In my opinion the crashes are caused by some serious problems with memory allocation.

[Sigismundo]

Deadmac wrote...

Sigismundo wrote...
This is NOT a hardware problem, it runs fine on XP on my system, this is NOT a PSU problem, And it ran fine on
original and 1.02 patch so this HAS to be a game setting problem...4GB (2 x 2GB) 240-Pin DDR2 SDRAM...

Windows 7 is also not your problem. 4GB of RAM may be your problem. Since Windows XP requires 512MB of RAM to work, you would have more memory available to run "Dragon Age: Origins" and the graphics card.

Deadmac wrote...While I was in taking a shower, I thought about something else. It is also related to RAM. Since "Dragon Age: Origins" needs to be open inorder to download content, you also have to consider the RAM being used by firewalls and Anti-Virus programs. Upgrading you system to 6GB should do the trick.

Okay I have put two theories to bed, sorry Deadmac, and Gorath but memory, and also page file are NOT the issue. I don't think it's just me either given the number of posts that all seem to reproduce same problem.
I now have upgraded my machine to 12gb of memory of ddr2 800 (thank you newegg)....which I do not regret i mean it still makes me cackle to say it, I remember when I upgraded my Atari 400 to 48k....ahh now that was a reliable little machine. How far we have come.....

In any case, I tested my memory out made sure settings were good on pc and in bios etc......loaded up DAO Ultimate loaded up save from mages tower Templar level, had alister charge in and hit smite and BOOM! Crash to dektop......at least i have become a master in reproducing the issue perfectly........
Now here is what we all KNOW.

This problem is primarily an issue for people with Window 7 and Vista 64 bit....(i.e. people with the new OS we'll be using from now on as memory limitations on 32 bit OS is sooo 2008.....ignoring this segment is ignoring what every hardcore gamer is building....64 OS is both NOW and the future.)

We also know that this worked fine on the 64 OS up until that last patch, and I can reproduce it specifically in mages tower using original cast fo chars and equipment like clock work....using the same spell graphical effects etc as the game came with.....so the idea that it's a hardware issue, or OS issue when it worked fine before doesn't make any logical sense to me at all. I'm not alone...

Scimal wrote...Before 1.04 I had the wide-spread memory leak problem that everybody had, but 0 crashes. Not a single one.

Now every time I try to cast Mana Clash or Paralysis Explosion it's a 50/50 shot at whether or not I crash. It's completely a software issue since I've had the same hardware since the game came out, and I've played it without crashes on Win7 x64 with my system before 1.04.

As for memory and Page file? I have now have 12gb of memory resulting in like a 21,0000 plus page file......memory and pagefile are NOT the issue.

THIS IS A PROBLEM AS A RESULT OF THE 1.04 PATCH.

time for some people to take responsibility for that.

So then, when will the staff at bioware man up and admit that their last patch has messed up a loved game by many of the fan base, and convince someone it may be worth investing some money for manhours to fix the issue?....this effects specifically the hardcore gamers who treat their machines like loved specialty cars, and tend to write most of the REVIEWS. You write off the 64 OS community and your going to feel it across the forums, magazines, and anywhere people read reviews.  I don't know ANYONE in that community building a machine who is not going to a 64 OS so they can unleash their machine from the 4gb barrier.

So when will they look into this before or after the release the next game? Because I have to tell you based on what I am seeing i have little reason to feel this will be worked out by the Dragon Age 2 release? Or did they simply say well that game has made it's money and that community no longer interests us, and cut all support for Dragon Age Ultimate which is what not even a year out of the gate? To me Bioware has stood for Excellence in gaming i have loved everything to come out from this company and been a faithful consumer of their games. I have bought just about every Bioware game. I don't know if their learning bad EA behavior as to poor customer service....but this issue really does need some attention.
The patch CAUSED this issue, we either need a patch to fix it, or a truly investigated response as to what is causing it so we know how to fix it on our machines.

This not my hardware I can run the baddest games out there on full and eat them alive.........this is not my OS, because it ran original game fine, this is not my memory, this is not my pagefile....this is an issue in this patch that while maybe it doesn't effect every 64 bit user it seems to effect a large portion of them as not only I have had the problem but most of those in my gaming groups that play this game have had same issue.

Modifié par Sigismundo, 29 janvier 2011 - 06:09 .

[PsiMeson]

RaenImrahl wrote...

I think it's on the launcher's configure menu... maybe under video?  You have to check something like "Disable Intro Movies"... I never noticed it until a few weeks ago.

Thanks RaenImrahl.   I like bypassing the launcher now, so I'll put up with the cutscenes for mow.


Update on stability: game runs perfectly now.   Played for 12+ hours yesterday without a single crash.

Sigismundo, don't know if you've tried the three things I mentioned above, but they're definitely worth a shot.

Modifié par PsiMeson, 29 janvier 2011 - 06:10 .

[Sigismundo]

Hmm Interesting because I have tried those things before, but maybe not at same time....however now that I reload with cpu set to just 0, and frame buffer off I am unable to make it crash......however i only played a few minutes, have to paint room today I will try playing it that way for a longer period....

As for third thing, how can you set affinity after you have run as administrator? It does not allow me to change affinity after I run that way. Also I am running game on built- in Administrator account...I created and renamed...does running administrator while in that account really matter?

I'll test this later and see if it combination of frame buffer at cpu affinity does work long term.....it certainly makes a difference....

All that said I still am miffed that to fix this I have to cripple a graphic setting, and my other two cores....when all worked fine before patch.

Modifié par Sigismundo, 29 janvier 2011 - 06:49 .

[RaenImrahl]

PsiMeson wrote...


Thanks RaenImrahl.   I like bypassing the launcher now, so I'll put up with the cutscenes for mow.

You only need to run the launcher once to configure the change.  Then you can use the bypass the launcher and still avoid the movies.

[PsiMeson]

Ah, you're right! The game configuration utility has an option to disable the intro movies - very cool.



@ Sigismundo: my setup is similar to yours, I use the administrator account as my primary account, and have User Account Control completely turned off. I have no idea what the "Run as administrator" option does for me in the compatibility tab, probably nothing, but it doesn't hurt to check it. I haven't noticed any issues with the Set Affinity option disappearing from Task Manager - you might need to google that one a little further.



As for being miffed, I'm just relieved the game is finally stable. I haven't noticed any graphics or performance degradation, so I'm fine with the altered settings as long as I can get on with killing Darkspawn.

[Sigismundo]

PsiMeson wrote...
1) disable frame buffer: this resolved 80% of the crashes outside the mage tower. Launch DAOriginsConfig.exe, select Video, and uncheck "Frame-Buffer effects"

2) processor affinity: tried this last night and mage tower crashes basically went away. In fact, I don't think the game crashed at all for the rest of the night, but the odd crash here or there is no big deal. Anyway, I am not aware of any way to set affinity on a permanent basis under native Win7. You have to do this for each gaming session: launch the game; alt-tab out to desktop; launch TaskManager and select the processes tab; rightclick daorigins.exe and select "Set Affinity"; uncheck all cores apart from CPU 0; play game.

I made one additional change that has questionable value, but might as well list it while I'm here.

3) compatibility mode: right-click daorigins.exe and choose properties; on the compatibility tab, select Run this program in compatibility mode for WinXP SP3, and check run as administrator; create shortcut to daorigins.exe in the startmenu to use instead of the default launcher

Just wanted to give props, i did a complete run through of the mage tower spells a flying and not a single crash.

I don't use 3rd step at all compatability mode makes no difference on my system.
Interestingly Processor affinity does not work by itself, though it may lower amount of crashes, and frame buffer does not stop crashes but it lowers them, but with frame buffer disabled and just using Affinity 0 I have zero crashes now!!! thanks! I had tried both of these independently before but when it crashed figured they were no help. It seems both are seperate issues that can make PC crash.....

Thank you Thank you Thank you!!!!!!!

Now if Only I could figure out why my main character's profile will not update on here. That will be for another post.

[Elencia]

I am a PC noob, so can anyone explain what to do (in small words ) because I crash constantly in the Archdemon Fight.

[godsize-baron]

maepage87 wrote...

I have the exact same issue. I'm actually currently TRYING to accomplish the last boss fight for the Fade and it crashes every time around the 3rd form switch. VERY annoying. I also have Win 7 - 64 bit and Steam. I would have to agree that the issue does seem to have a lot to do with the last update since I was having 0 issues before... Bah.

This describes my problem EXACTLY. I too have Win7 - 64 bit and the Steam UE Version. The game ran super-perfect (almost 30 hours) UNTIL the last boss fight in the Fade. I have tried this 5 times now and every time when the Sloth Demon switches to the second, third or fourth form, the games crashes to the desktop with the infamous Windows 7 message that a solution for the problem is being searched.

My specs:
Toshiba Satellite Notebook L650
Intel® Core™ i5 CPU       M 480  @ 2.67GHz
ATI Mobility Radeon HD 5650 1 GB
4 GB RAM

Update: 

DUDES. The recommendation to disable the Frame-Buffer effects TOTALLY WORKED! Not only got i rid of the annoying "blurry" effect of the Fade, but I could finish the Sloth Demon final boss fight in peace.

Modifié par godsize-baron, 29 avril 2011 - 04:23 .

[AdelaisAer]

I have Windows 7 64-Bit, 4GB RAM, 256 VRAM, Duo Core. Game plays a little bit slow but manageable until it randomly crashes every so often.

Going to try PsiMeson's steps to see if it resolves it.

[M4cB3th]

okay, seems i've ended up with the worst case:

gaming pc:
windows 7 64bit (on intel 80gb ssd)
8gb ram
radeon 6950 2gb
playing with an eyfinity display setup (3 displays)

"edit: da:origins with all dlc and patched up to 1.05" (installed on normal hdd drive)

everything worked fine until i installed dragon age : origins about three weeks ago.
(meaning that every other game, including dragonage 2 works)

...but after i started playing da:origins i had several complete system system crashes after which i was forced to pull the plug out of my pc to start it again.
about 7-8 of those freeze-crashes my graphics card broke, resulting in those exact same freeze-crashes even when doing nothing at all (checking settings in the mainboards bios, so drivers are / os were DEFINITLY NOT the issue anymore).
now my radeon got sent back to the shop i bought it from (warranty still intact) and replaced by a 6970.
am going to sell whatever they get me as a replacement for the old card.

i never had any kind of problems with da:origins prior to patch 1.04/1.05, but ending up with a piece of broken hardware is going to keep me from playing this game for a long time ( until they completely fix the issue at least)

Modifié par M4cB3th, 08 août 2011 - 07:54 .

[M4cB3th]

btw, i think it really funny that an old (and mostly converted from the xbox console) game like jade empire seems to work without any problems INCLUDING near flawless eyefinity support, but a newer game like dragon age: origins causes so many problems and mass effect 1+2 not working with eyefinity (in that case due to the crappy unreal shooter engine theyve used, maybe try some solid german engine like the one from crysis next time

Modifié par M4cB3th, 08 août 2011 - 08:48 .

[Gorath Alpha]

AdelaisAer wrote...

I have Windows 7 64-Bit, 4GB RAM, 256 VRAM, Duo Core. Game plays a little bit slow but manageable until it randomly crashes every so often.

Going to try PsiMeson's steps to see if it resolves it.

If you need further assistance, you'll need your own personal message thread, and a completed problem report, as per Raen Imrahl's "Read first" guide. 

M4cB3th wrote...

radeon 6950 2gb

my graphics card
broke, resulting in those exact same freeze-crashes even when doing
nothing at all (checking settings in the mainboards bios, so drivers are
/ os were DEFINITLY NOT the issue anymore).  now my radeon got sent
back to the shop i bought it from (warranty still intact) and replaced
by a 6970. am going to sell whatever they get me as a replacement for
the old card.

i never had any kind of problems with da:origins
prior to patch 1.04/1.05, but ending up with a piece of broken hardware
is going to keep me from playing this game for a long time ( until they
completely fix the issue at least)

If you are trying to claim that DAO "broke it", you are way off base. 

Modifié par Gorath Alpha, 08 août 2011 - 09:33 .

[M4cB3th]

Gorath Alpha wrote...

AdelaisAer wrote...

I have Windows 7 64-Bit, 4GB RAM, 256 VRAM, Duo Core. Game plays a little bit slow but manageable until it randomly crashes every so often.

Going to try PsiMeson's steps to see if it resolves it.

If you need further assistance, you'll need your own personal message thread, and a completed problem report, as per Raen Imrahl's "Read first" guide. 

M4cB3th wrote...

radeon 6950 2gb

my graphics card
broke, resulting in those exact same freeze-crashes even when doing
nothing at all (checking settings in the mainboards bios, so drivers are
/ os were DEFINITLY NOT the issue anymore).  now my radeon got sent
back to the shop i bought it from (warranty still intact) and replaced
by a 6970. am going to sell whatever they get me as a replacement for
the old card.

i never had any kind of problems with da:origins
prior to patch 1.04/1.05, but ending up with a piece of broken hardware
is going to keep me from playing this game for a long time ( until they
completely fix the issue at least)

If you are trying to claim that DAO "broke it", you are way off base. 

way off base ? definitely NOT !
but for some additional information, now that THIS problem seems to be fixed by upgrading my system some more...

I'll grant you one thing: the grapics card was not broken after this.
i sent it in (see my mentioning of the intact warranty above) and testing by the hardware shop i bought it from showed it was still in good working condition.

BUT i found out something else was broken after all, the psu!

it looks like my system was already quite close to the max output of it and dragon age origins is probably one of the few games around which get the whole system up to its full power consumption.

so in short, after a while the psu didn't take it anymore, something that could've been triggered by more or less any other game needing that much power, just happening to play only dragon age origins that time.

my assumption of the graphics card beeing the broken part in my pc simply came frome the fact that the system did function like normal after i took it out and temporarily switched to onboard graphics. 
of course this action greatly reduced the systems need for energy thus making it stable again.

_______________________________________________________________________________________________
this should also be a small hint to some of the guys who end up with a crashing system, might be your psu giving in...
_______________________________________________________________________________________________

new system now:
amd phenom 955 (3.2ghz)
8gb ram
>>Radeon HD6970 2gb<<
psu upgraded from 500watt to 600watt

...now if i just find out some way to stop objects ingame from vanishing in my 3-monitor resolution (6060x1080) ^^

Modifié par M4cB3th, 21 août 2011 - 10:25 .

[mcsupersport]

Personally I would have gone with even a higher PSU than 600 for that system. PSU degrade and lose power, around 10% per year according to some listed data, especially when stressed at all, and the 6970 will eat some power along with everything else. You really need to have 20-45% more PSU than you actually need to get any staying power.
The HD 6970 card alone will draw 25-30% of your 600W PSU output...something to consider.

[M4cB3th]

As my system was built having a small case in mind
( Lian Li PC-V351b http://www.lian-li.c...ss_index=64&g=f )
the parts inside it don't need that much power (with the exception of that graphics card of course and that one is not taking up that much more than my old one did)

And if i really need another psu... i'm working for an it reseller/repair service, so to get anotherone i'll just have to get one out of our storage. ^^

It's only gaming hardware that i usually get somewhere else as we don't have that in our storage.
(we only have small and medium companies as customers and none of them need anything more than onboard graphics)

Modifié par M4cB3th, 23 août 2011 - 09:29 .