1370 réponses à ce sujet

[HeartCore2009]

Orchomene wrote...

Small question : does everybody having this constant crash issue (around a crash every 15 minutes) use a retail version with a DVD ?
Because the problem may come from the DVD copy protection, can't it ?

No, steam version in my case.

[RhemaThomas]

I am playing both Origins and Awakening on the PC. Both are digital downloads from D2D. I have been having crashes since installing patch 1.03 and Awakening. Same problem everyone else is reporting. After a short while, loads start taking longer and I end up crashing to desktop in a fight. My only work around has been to quit the game every 30 minutes or so and restart. Event then, I will occasionally crash during a battle.

[WonderGamer]

Perhaps something that should be looked at for the people that are crashing is what extra codecs have been installed.  I know that incompatible codecs can crash your games (this was my case in Oblivion anyways).  Likewise, I know the K-Lite codec pack is known to cause problems with programs other than games, so people who are crashing might want to list any codecs/codec packs that they have installed in case this is where the problem lies.

[didymos1120]

nvm.  wrong thread.

Modifié par didymos1120, 12 mai 2010 - 01:50 .

[didymos1120]

wolfwarp wrote...
Man, I should have bought the PS3 version instead. Lesson learned.

No,  it's still far inferior in basically every other respect.  Granted, if you're crashing every 5 minutes, that's not much consolation.  Still, take it from a PS3 immigrant: no, you shouldn't have bought it, and neither should I have.

[jsmile39]

I doubt it's codec related, 1.03 was crashing like crazy on a clean install (XPSP3-x86) with just the bare minimum drivers installed, and no video stuff. It continued to crash a lot after installing basic video stuff:



ffdshow_beta7_rev3154_20091209

MPC-HC/Hali/etc



Bought an SSD which prompted the new installation of DA:O, otherwise I'd probably still be playing trouble free on my old 1.01 install.



v1.02a is playing just fine now, that 1.03 seems to crash the most during combat, and specifically during heavy spellcasting, points to scripting or graphics issues imo. For what it's worth, I am running 2xAA and (forced) 8xAF for all of this. Didn't think to test turning any of it off while I still had 1.03 installed.

[Cloud Windfoot Omega]

memory overflow i think. tries to access more memory then it can. would make sense for it to do this in battle since that's where all the sells and skills are sued that would take up all the memory, that would explain why the 3g memory fix helps in certain crashes.



it could also be that the game is not purging certain things off the memory causing it to build causing it to crash. but i know nothing and i may be 100% wrong

[jsmile39]

Most of my crashing was happening in the Fade, shapeshifting to/from Mouse, or when entering combat. It was actually not too unstable up until then, I played maybe 10 hours up until that point, and crashed maybe 5-10 times, which was relatively stable in comparison.



Once I hit the Fade there were several instances where I would crash out of combat during shapeshifting, reboot, crash again, and repeat for 10-15 minutes. There was also several encounters where I would just crash repeatedly as soon as the fight began. In other words, it went from quite annoying to borderline unplayable.



The heavy spellcasting/AoE crashes that seem common might certainly be memory related, but I think there's multiple issues involved here, that make it very hard to diagnose... my gut feeling at least!

[jsmile39]

On the other hand, it's scenarios like this that give you new respect for the stability of some other games. For example, I've been playing Everquest on and off for more than 10 years now, and I think my client has crashed less than 10 times *total*... excluding user error (wrong UI loaded after a patch or something) or disconnects -- and this is 10-year-old spaghetti code developed by people who stopped working on the game 7-8 years ago.



Heck, half the time you ask they don't even know what that old code does, or how it works, it's just mind boggling how they can keep it so stable when the original code was written for win98/dx7, and after thousands of patches, etc

[dragonsouce]

dragonsouce wrote...

Just checked system policies for the
patch and Dragon age origins folder, They say full control but there
could still be registry keys and system folders and gods know what else
that might not be getting the control they need to write.

I
still betting it's the install program that screwy.The problems are to
broad and experienced by to many people to be just a bad Exe. It's the
install that screwy. People are reporting less or no problems that use
the DVD to install.

To Manny glitches repeating but not on all
machines of same type . It's got be install App that mangling that patch
on windows 7.

Going to try an Experiment install the game on a
XP VM Machine then copy it over to real machine or maybe install it with
a network drive form a XP client.

Tested my bad installer theory.


Well I tried installing to a Virtual Machine XP then patching 1.03 and copying over the install to my normal windows 7. renamed the original. It crashed anyway. No difference. It could still be somethink in the window system folders or game folders but no clue what.


#$#%@# Even tried the damed crack.

What the hell is this this Glitch it makes no sence!!!

Modifié par dragonsouce, 12 mai 2010 - 03:21 .

[wchen68]

This patch has caused my Return to Ostagar DLC to malfunction. It's listed in my DLC menu and I have the offer files with them, but for some reason, I'm not allowed to travel to Ostagar while in game. Help anyone?

[Eurypterid]

wchen68 wrote...

This patch has caused my Return to Ostagar DLC to malfunction. It's listed in my DLC menu and I have the offer files with them, but for some reason, I'm not allowed to travel to Ostagar while in game. Help anyone?

Did you go to Bann Loren's land first?

[Gulaman]

There's too many pages to read through, so can someone please tell me if there is a fix to this "memory leak" that causes the CPU to max out to 100% when the game is running? I'm running on 32-bit Windows 7, version 1.03.

Previously I was running on Windows XP using an older patch (1.01b) and I don' recall this happening. I certainly wasn't getting any performance problems but now the game barely runs properly.



Thanks

[Gnaeus.Silvanus]

Gulaman wrote...

There's too many pages to read through, so can someone please tell me if there is a fix to this "memory leak" that causes the CPU to max out to 100% when the game is running? I'm running on 32-bit Windows 7, version 1.03.
Previously I was running on Windows XP using an older patch (1.01b) and I don' recall this happening. I certainly wasn't getting any performance problems but now the game barely runs properly.

Thanks

Ask the person above you, he knows a lot about what is happening to this game fail.

[dragonsouce]

Gulaman wrote...

There's too many pages to read through, so can someone please tell me if there is a fix to this "memory leak" that causes the CPU to max out to 100% when the game is running? I'm running on 32-bit Windows 7, version 1.03.
Previously I was running on Windows XP using an older patch (1.01b) and I don' recall this happening. I certainly wasn't getting any performance problems but now the game barely runs properly.

Thanks

For windows 7 32

there been some luck with a couple of salutions but what confuses us all is they do not work for every one and different salutions work but only some times , with 64 bit there less more problems.

First try setting to xp sp3 compatable, with Adminstation rites on daorigins.exe, If that fails try using the tag Dragon Age Origins\\\\\\\\bin_ship\\\\\\\\daorigins.exe" -dx9 in the target line ,if that fails try a crack,if that fails ,.... curse the Name of the EA God and join the rest of us here in  Dragon Age Hell.

By the way these fix sometime work some time do not and no one can figure out why.

Oh that right I remeber now. It's becouse patch 1.03 is the REAL number of the Beast
And is pure EVIL!

Modifié par dragonsouce, 13 mai 2010 - 03:11 .

[Rhys Cordelle]

Glad to know the overloaded memory thing is an issue with the patch. I thought my computer was falling apart.

[didymos1120]

Rhys Cordelle wrote...

Glad to know the overloaded memory thing is an issue with the patch. I thought my computer was falling apart.

More like an issue with the game.  Patch 1.03 didn't introduce the problem, and depending on who you ask, it either improved the memory leak situation or made it worse.

In fact, 1.03 was in part a fix for this (or supposed to have been, anyway).  Just read the patch notes: "Some players were experiencing increasingly long load times. A major
cause of this problem has been fixed."

Obviously, it can't be the sole cause, unless it also possesses the ability to time-travel and f*ck up your game in the past, in addition to its super crashing powers. 

Also, it seems to be that the .NET framework is partly to blame.  I and others have found that updating to .NET 4 helps quite a bit.  It still fails to deallocate all the unused memory, but it takes much, much longer to have any significant effect.

Modifié par didymos1120, 13 mai 2010 - 11:45 .

[wolfwarp]

didymos1120 wrote...

Rhys Cordelle wrote...

Glad to know the overloaded memory thing is an issue with the patch. I thought my computer was falling apart.

More like an issue with the game.  Patch 1.03 didn't introduce the problem, and depending on who you ask, it either improved the memory leak situation or made it worse.

In fact, 1.03 was in part a fix for this (or supposed to have been, anyway).  Just read the patch notes: "Some players were experiencing increasingly long load times. A major
cause of this problem has been fixed."

Obviously, it can't be the sole cause, unless it also possesses the ability to time-travel and f*ck up your game in the past, in addition to its super crashing powers. 

Also, it seems to be that the .NET framework is partly to blame.  I and others have found that updating to .NET 4 helps quite a bit.  It still fails to deallocate all the unused memory, but it takes much, much longer to have any significant effect.

To be honest, I'd rather put up with the slower loading time than the random crashes.  How I wish BioWare could roll back that fix.

So, still no luck eh?

[Necrosis103]

I had the stone prisoner DLC installed before getting the patch, then I got the patch and started to download the other dlc, namely Warden's keep and return to ostagar. Warden's Keep successfully downloaded.....but it won't work, saying it requires the '1.0' version of the game. Return to Ostagar is still being downloaded so it may encounter a similar problem. The Stone Prisoner works perfectly fine however

Any help for this? Someone? Anyone?

[Necrosis103]

Ooh, update, Warden's Keep kicked in and is now operational. Return to Ostagar had a similar problem, though it was asking for a 'later' version (1.02)

I'll leave it for a bit, come back to it later, if the problem persists, I shall return

[Necrosis103]

okay, the DLC installed fine, but now Shale is bugged, whenever I talk to her she acts like she did as a statue, plus when I leave conversation, I end up in a little bugged zone. Anyone have this problem or a fix? fix would be preferred

[Gulaman]

Hmm, I need to retract my earlier statement about 1.03 being the cause for the CPU overload - it's not. I just reinstalled the game, version 1.0, and I'm still getting CPU at 100, RAM also shoots up massively.

So it appears the game doesn't behave well with Windows 7 (Pro, 32-bit). I had no problems when I was on XP a month ago, although I never checked CPU/RAM usage at the time, since I had no problems with the game when running on XP.



The solution I use to get around this is to use just one CPU core while the game is running. (task manager > Processes > Right click DA:O.exe > Set Affinity )

Obviously this isn't the best solution since one core is being completely consumed by the game but the game does run a lot better this way.

[WonderGamer]

Necrosis103 wrote...

plus when I leave conversation, I end up in a little bugged zone. Anyone have this problem or a fix? fix would be preferred

I don't have a fix to this, but I ran into the same kind of placement bug in The Provings (Dwarf Noble) after getting moved to the lower balcony (if I even got moved at all; that was part of the placement bug).  If I did get moved, then I'd be booted back up to the higher balcony after talking to somebody.  If I didn't get moved, then I'd be stuck on the upper balcony with nothing left to do but load an old save.  The wierd thing is I didn't notice it until after installing 1.03, but I continued to have the same problem even after reverting back to 1.02a.

[Eurypterid]

There's a fix for that Shale issue, but it may involve using the console. I had to go through that myself. Check out section 1 of This Thread. At the bottom of that section is a link with instructions on how to enable the console.

[Marathax]

this patch is pretty buggy. My computer crashes randomly only when i play DA, but it never happened before this patch. Also my blood armour vanished when i got to 38 str for my warrior and now longer appears! hope that Bioware fixes these problems fast!