65 réponses à ce sujet

[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.

Windows XP = 512MB RAM
Windows 7 = 2GB RAM

Your system has = 4GB RAM

Ya know I want to beleive this is my major problem very badly....it's certianly the first new idea i have run across that makes sense, to me. thank you, I'll deffinately be upgrading my memory and see if that helps.

Any advise on why Player Profile on this site hates win 7 64 also? Pretty sure it's tied to administrator issue.

[Deadmac]

Sigismundo wrote...

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.

Windows XP = 512MB RAM
Windows 7 = 2GB RAM

Your system has = 4GB RAM

Ya know I want to beleive this is my major problem very badly....it's certianly the first new idea i have run across that makes sense, to me. thank you, I'll deffinately be upgrading my memory and see if that helps.

Any advise on why Player Profile on this site hates win 7 64 also? Pretty sure it's tied to administrator issue.

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.

When it comes to the 'player profile' issue and Windows 7, did you check to see if the firewall is allowing "Dragon Age: Origins" to access BioWare's servers? Check to see if there is an exception for "DAO" set within your firewall program. I am currently running Windows 7, MS Firewall, NAV, Zone Alarm, and DAO without a problem.

Modifié par Deadmac, 22 janvier 2011 - 09:20 .

[Deadmac]

"Dragon Age: Origin's" problems is a backwards and forwards compatibility issue. Half the game is running on extreme backwards requirements, and the other half is running on extreme forwards requirements. Its crazy.

Modifié par Deadmac, 22 janvier 2011 - 09:26 .

[Sigismundo]

Yes firewall is letting program do it's thing, checked ports on faq.....just will not update. I deleted chars as I rea dthat was a fix and tried to reload stuff no as you can see by my lack of an avatar, that dd not work so well.

[maepage87]

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.

[RaenImrahl]

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.

It can obviously be a very graphics-intensive fight.  Consider loweing your screen res for it.  If you post your specs, we can troubleshoot more.

[Scimal]

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.

I'm in the exact same boat.

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.

Whatever 1.04 did, it screwed it up. My guess is that it's a graphical setting somewhere that we can't access which will fix it, since I'm convinced it's the visual eye-candy portion of the spells which causes the crash. Makes me wish I knew more about rendering so I could try a few things.

[Sigismundo]

It's not a great solution but I can say I got through that very fight by turning graphics down, ticked me off that I had to do it for a game that quite frankly isn't that high on eyecandy considering the other stuff I can run. I'm stillw aiting on memory to get here to test deadmac's theory of it being memory based. Scimal how uch memory do you have and what OS are you using?

[Scimal]

Win7-x64 HP, which supports up to 8GB (so the 512mb of my 8800GT doesn't detract at all from RAM).



I currently have 4GB installed, DDR2-800mhz.



It's not the RAM, though. My RAM doesn't hit max usage through DA:O, though. I have meters to record CPU/RAM usage, and the only thing I use that maxes out RAM are encoder programs.



Like I said before, I'm convinced it's something to do with executing the rendering of certain spells, and not a resources issue. If it was a resources issue, the crashes would occur very consistently as things are loaded into memory and it hit a wall. Lowering the graphic quality would also be the confirmed fix. If it's a rendering issue, it would only happen when the thing was rendered - which is the closest thing to my experience. AoE spells appear to be the culprit for me, Mana Clash, Cleansing Aura, Paralysis Explosion - all have consistently triggered crashes for me.



Maybe if I remember to, I can cap some YouTube videos of reproducing the crash, since I was able to do it with a fair bit of consistency prior to the start of this semester.

[RaenImrahl]

Scimal wrote...

Like I said before, I'm convinced it's something to do with executing the rendering of certain spells, and not a resources issue.

I was in the process of writing out a long explaination, but I am going to retry it in shorter form

If you want to both successfully solve your issues, I encourage you to think of "resources" as being much more than just hardware specs.  Specs are important-- they are a general guide to what you should expect your computer to do.  But, now that I've spent a few weeks helping others troubleshoot on this site, I have come to realize one important thing...

... the critical issue in most cases is how the OS and DA:O work together to use your hardware to carry off the desired effect.

In short:  look to Windows.  Running the Windows repair installation function, or better yet, reinstalling the OS completely and starting with a "clean" system may do wonders for you.  I don't suggest this lightly, I know it is a lot of work.  But DA:O is what it is... a program with chunky programming that, like it or not, does not tolerate aberations in the OS.  This intolerance is most likely to become a problem when you're engaged in graphically-intensive things, like the spells you've mentioned.

RI

p.s.  More RAM may indeed help Sigismundo's issue, if her OS (and I'm talking about her own copy of Win 7 running right now on her machine) is loading a lot of "extra" stuff into memory, or for whatever reason, no longer uses her system's memory effectively.  And that's not Sigismundo's fault, by the way.  Windows tends to get cluncky over time, especially when your doing a lot of installing and uninstalling of various things.  A recent discussion that may help can be found here:  http://social.biowar...8/index/5816873

Good luck, both of you.

[Scimal]

RaenImrahl wrote...


I was in the process of writing out a long explaination, but I am going to retry it in shorter form

If you want to both successfully solve your issues, I encourage you to think of "resources" as being much more than just hardware specs.  Specs are important-- they are a general guide to what you should expect your computer to do.  But, now that I've spent a few weeks helping others troubleshoot on this site, I have come to realize one important thing...

... the critical issue in most cases is how the OS and DA:O work together to use your hardware to carry off the desired effect.

In short:  look to Windows.  Running the Windows repair installation function, or better yet, reinstalling the OS completely and starting with a "clean" system may do wonders for you.  I don't suggest this lightly, I know it is a lot of work.  But DA:O is what it is... a program with chunky programming that, like it or not, does not tolerate aberations in the OS.  This intolerance is most likely to become a problem when you're engaged in graphically-intensive things, like the spells you've mentioned.

RI

*sigh*

No, it won't do any good.

Even on the loooooooong shot you're right, and it's Windows, I'm not reinstalling just to play a game. That's a weekend's worth of work to bring Windows back in-line to play a game that BioWare has essentially left in the dust.

I'm simply not giving BioWare my money for DA:O 2. That's my response. Chunky programming is not an excuse for anything, especially when I can reproduce it with fairly decent consistency. This stuff should've been patched a month after it was introduced, and the fact that it's not is ignorance or inability on BioWare's part.

Nothing less, nothing more.

[RaenImrahl]

Scimal wrote...

I'm simply not giving BioWare my money for DA:O 2. That's my response. Chunky programming is not an excuse for anything, especially when I can reproduce it with fairly decent consistency. This stuff should've been patched a month after it was introduced, and the fact that it's not is ignorance or inability on BioWare's part.

Nothing less, nothing more.

For what it's worth, I can completely respect that.  For me it was, of all things, "Star Fleet Command III".  I loved SFC2.  Still play it once and a while.  Interplay rushed the third installment out as its license to the trek franchise was evaporating and it was going belly-up.  Total crap.

[Sigismundo]

Ahem, For the record I am a he and not a her....and my avatar such as it is, a great looking red X is rather genderless now as well thanks to player profile also being broke.

Also I have never had a "chunky" OS, I am extremely protective at what goes on, and try and keep it lean......maybe one xp copy I had a year or two got "chunky" but over all my os is no more chunky than when i installed it. I been min maxing my systems for gaming since teh days of tinkering with emm386 and highmem.sys junk, when everytime you got a game you knew the first 3 hours would be getting your memory configured to run it in DOS.



That said I really do not think memory is the final answer, but hey I didn't know windows 7 64 took such a large chunk so I'm happy to expand my memory anyway. We'll see.

[RaenImrahl]

Sigismundo wrote...

Ahem, For the record I am a he and not a her....and my avatar such as it is, a great looking red X is rather genderless now as well thanks to player profile also being broke.

Actually, all I see now is a blank square.  I thought you were shy.

[Sigismundo]

I could not get my main character to update so it loaded a alt I made female elf, so I used that for avatar, but then in a moment of inspiration I deleted all pictures characters and files thinking perhaps that would cause it to update......no dice..... So I had just a blank face....now i have chosen a a generic on teh off chance that woudl hang it......I've tried everything, I'm convinced Bioware hates me.

[ShinsFortress]

I run Vista-32 with 4GB of RAM and rarely have stability issues. For me, it's the gameplay bugs still present that annoy me. I could easy alter my system and install 64-bit, but I am primarily a gamer and so many games have problems with Vista/7 64.

[Orusaka]

Just wanted to update and say that while I had this very problem, as I suggested earlier in the thread, I tried some of the fixes one of the posters here gave, and manually setting the fan speed of gpu to 70% has given me only 1 crash in 8 hours now.



Just thought I'd share this, as it might be the problem for others, too. I find it really odd as the card was never all that warm in the first place, and this sort of thing doesn't happen for any other game. Mass Effect 2, for instance, hasn't crashed on me once in 100+ hours I've played it.

[Sigismundo]

I'm checking out my Pagefile info and services, just to be sure I am cleaning up the old pc and rerunning all my malware stuff just to make sure it's running as trim as possible.

[n8mahr81]

RaenImrahl wrote...
In short:  look to Windows.  Running the Windows repair installation function, or better yet, reinstalling the OS completely and starting with a "clean" system may do wonders for you.  I don't suggest this lightly, I know it is a lot of work.  But DA:O is what it is... a program with chunky programming that, like it or not, does not tolerate aberations in the OS.  This intolerance is most likely to become a problem when you're engaged in graphically-intensive things, like the spells you've mentioned.

Ah  common, Raen, you are not seriously suggesting a new win7 installation like, in "the old days"? This is Win7 and not WinME, after all. Win7 is one perfectly stable OS, never seen a better windows.

As Sigismundo has pointed out, his system is perfectly stable UNTIL he plays DA:O.
Same for my System, I may only call an old crutch of a computer my own, but it runs games like BattleField:BC2 on lowest settings just fine. And that is some hardware-hungry beast, performance-monitor shows almost 100% load on both ram (2 gb) and cpu (Athlon x2 4600+).
When talking of graphically intensive - I have seen games a lot more "intensive"... DA:O uses xbox style graphics with some of the t ugliest textures I had to look at for years.

DA is the first game in a looong long time that gives me the headaches. Not only the stupid "updater" service did not start the first time after installation and had to be set manually to start every time with windows, no, the game crashes quite regularly every now and then when I try to open the inventory or the skills-page.

It may be related to the sound that the game is playing while opening the "book", or maybe a failure to address/display some of the goods in the inventory... maybe the "updater" checks if I am still allowed to own DLC? I really do not know. All I know is that DA:O and not win7 is buggy and needs fixing.

But, I have to give you that : you are the most polite forum poster I have read in a very long time !

Modifié par n8mahr81, 27 janvier 2011 - 10:27 .

[RaenImrahl]

n8mahr81 wrote...

Ah  common, Raen, you are not seriously suggesting a new win7 installation like, in "the old days"? This is Win7 and not WinME, after all. Win7 is one perfectly stable OS, never seen a better windows.

I agree that Windows 7 is a great OS... I love it, and feel sorry for friends who sneer at it and cling to XP.  Doing a clean install is the "nuclear option"... I would only consider it a last resort (which is why I also suggested using the Repair option, which works in Win 7, from my experience).  In Sigismundo's case, reading through his histrionics across several threads, describing several diffent types of failure... I maintain it's a valid, if deperate option. 

n8mahr81 wrote...

When talking of graphically intensive - I have seen games a lot more "intensive"... DA:O uses xbox style graphics with some of the t ugliest textures I had to look at for years.

No argument there.  Compounding this, of course, is the bloated code which translate the textures to the screen.  That's what I mean by intensive.  Other games will perform fine on a system, where DA:O will choke.  What I am trying to help with is not assigning blame.  Rather, it's making something inherently, but not fatally, flawed workable. 

n8mahr81 wrote..

But, I have to give you that : you are the most polite forum poster I have read in a very long time !

Well, there's only one response to that... thank you!

[PsiMeson]

Deadmac wrote...

Majority of the computers in which came out with a the 'dual core processor' schemetic were 32bit systems. 
Single processor with a dual core = Last of the 32bit computers.

<snip>

'Windows 7' needs 2 GB of RAM to run and "Dragon Age : Origins" needs another 2GB of RAM (to run on 'Windows 7); therefore, you would need over 4GB to run them together successfully. Don't forget that graphics cards also use a significant amount of RAM. In order to run everything together smoothly, you would need at least 6GB of RAM.

Deadmac, I appreciate your trying to shed some light on this issue, but telling people with 4GB of RAM to go buy more RAM is not helpful.  I think you are a little unclear on how modern operating systems manage memory, particularly as it concerns the swapfile.   Bottom line anyway, is that no one needs to upgrade from 4GB to 6GB just to play this game.

Regarding 32bit and 64bit computing, that is another kettle of fish, but afaik, all multiple core machines have the instruction sets required for 64bit computing.   On the Intel side, they've had x86-64 in place since the days of the Pentium 4.     This is besides the point however; gaming on a 64bit platform is not assured, especially when the developer makes no compatibility claims.

Back to the issue at hand, I am also experiencing constant crashing in the mage tower.   The game was initially crashing everywhere, but another post suggested turning off the frame buffer.  That helped a lot in the rest of the game, but not here.

I'm running Win7 32bit, so I think we can rule out Win7-64 as the sole cause of this.  I am running the AMD X3 processor though - may experiment with the affinity suggestion a little.

I also have an X-Fi based sound card, but this is an Auzentech X-Fi Forte board.  (Incidentally, do not buy an Auzentech Forte card - terrible drivers - wish I could get my money back.)   I see the OP has Realtek though, so it's probably not a soundchip specific issue.

For the time being I plan to just save every few minutes and reload as necessary, but it really is a pain in the butt.

[RaenImrahl]

PsiMeson wrote...

For the time being I plan to just save every few minutes and reload as necessary, but it really is a pain in the butt.

What kind of video card do you have? 

[fkirenicus]

Right, now I can announce my membership in this club as well. :-(

In the first major battle in the game - Redcliffe - the game constantly crashes somewhat "halfway". I can play the battle near the mill without problems, but when the next wave of attackers hits the village street the game first becomes slow to respond (I can click "Heal" on a militiaman, and then 4-5 seconds later the spill actually fires) and then fails altogether.

Had to turn down graphics to a minimum to avoid this, which resulted in a following cutscene that looked completely and utterly awful. Ah well. :-)

[PsiMeson]

Things seem to be mostly under control now. I tweaked a couple more settings and crashes have been reduced dramatically. My only complaint is that Bioware should really be more proactive in helping the user base, rather than force us to sift through the forums. Anyway, fixes that worked for me below.



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.



Offtopic, but does anyone know if there's a switch to turn off the intro cutscenes? I'm getting tired of hitting escape twice every time I launch the game.

[RaenImrahl]

PsiMeson wrote...

Offtopic, but does anyone know if there's a switch to turn off the intro cutscenes? I'm getting tired of hitting escape twice every time I launch the game.

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.