41 réponses à ce sujet

[Uzil]

Thanks bioware for making a yet another awesome game that nobody can ****ing play because your too god damn cheap to fix some ****ing bugs

[t0ykiller]

I am also crashing every now and then when I open either the inventory or character screens, it's the steam version of DA:O ultimate edition and I'm on Win7 32-bit. Since there doesn't appear to be any fixes (and I doubt there will be now), all I can suggest is to do what I do, after every encounter or event that you finish, hit the F5 key to quick save, and every so often make a normal save. I've only been screwed once from the crash and had to do an event over, all because I was too lazy to quicksave that one time... won't happen again though lol.

[krokous]

Hi peoples , try this :

set daorigins.exe to use only one core of your CPU

 Taskmanager > process > daorigins.exe > affinity

cheers

Modifié par krokous, 21 janvier 2011 - 09:46 .

[DeadJediJamie]

krokous wrote...

Hi peoples , try this :

set daorigins.exe to use only one core of your CPU

 Taskmanager > process > daorigins.exe > affinity

cheers

While this does indeed work (for some people) it's an absolutely awful solution. Running with one core makes the game barely worth playing.

[Darwaron]

Hi there, i had this Inventory-crashes since a week too, but i solved it today. Since the first time i had this crashes, iI asked me how the hell i could play over two weeks without any problems .. now i know. I use Win7 (x64) and 4GB of RAM. I just deactivated the service 'superfetch' (to find out what this service does you will find a lot infos on the web).

To check if this solution works for you, try the following first (will not harm your pc, its just a temporary chance):

1:. press 'windows-key + R'
2:. type services.msc and ok
2:. in the following window, search for the entry 'superfetch'..
3:. do a click on this entry, and then, in the upper left, 'deactivate' the service.. don't worry, nothing will go wrong.
4:. wait a little moment, check the 'status' of the service - it should now be shown as 'deactivated'..
5:. leave this window open and start Dragon Age. Do your things.. and if it works:
6:. make a doubleclick on the service and under 'startup type' select 'disabled'.. and apply.

If it doesnt work, you can activate the service again like you deactivated it under step .:3:., or it will be automatically loaded after the next reboot.

Maybe this could help someone.. and sorry for my bad english.. )
Darwaron

EDIT: Superfetch uses a lot of (in 'best' case all) available physical memory by loading the core-apps/threads into it to speed up the system and decrease latency - but you will not really notice that. The good thing is the small speedup. On the other side, all applications/games that dont fit into the RAM will be forced to swap their content to the harddrive. Make your choice. )

BTW: if someone manually set the swapfile to a fix value (e.g. 2GB), check if its not to small to hold DA, maybe there's too low available Space - especially if there are a lot addons loaded like HighResTexture-Packs and so on.

Modifié par Darwaron, 02 février 2011 - 10:06 .

[sgoudreau]

I just spent some time working this issue out a lil bit, im Runnin a i7-920, 6gb ram, and dual radeonhd 5870's. i played DA:O avbout the middle of the year last year, and hadnt come back to it till now, and now i get a hard crash when i go to my inventory screen, only after a while at first, but after i started messin around with stuff it was just about every second time i opened the inventory. I started uninstalling my video drivers and rolling back, i chose catalyst 10.10 to begin with and the issue seemed to be gone as i opened the game and wailed 'I' for about 5 mins straight and no crash. i skipped 10.11 and went straight to the 10.12, the last release before the new catalyst control center. i opened DA:O and proceeded to wail 'I', and it crashed immediately. I then Downloaded 10.11 for good measure and tried it, and so far so good, gave it my 5 min wailing 'I' test and no crash, now i have not actually played at all, and if it does crash, i will come back and repost. for you Nvidia users, i cant really help ya except start gettin old driver packages and trying if u really wanna play. hope this helps someone, and hope maybe it helps get the issue resolved once and for all :/

[sgoudreau]

o and i run win 7 64bit

[sgoudreau]

also, i am running the steam version of DA:O @ 1920x1200, 4x AA, Very high graphic details, and high texture detail.

[sgoudreau]

played for several hours now and no crashes with catalyst 10.11 drivers

[Kahmal the templar]

t0ykiller wrote...

I am also crashing every now and then when I open either the inventory or character screens, it's the steam version of DA:O ultimate edition and I'm on Win7 32-bit. Since there doesn't appear to be any fixes (and I doubt there will be now), all I can suggest is to do what I do, after every encounter or event that you finish, hit the F5 key to quick save, and every so often make a normal save. I've only been screwed once from the crash and had to do an event over, all because I was too lazy to quicksave that one time... won't happen again though lol.

Thats a good tip, its what im doing since i have to re-do 3 or 4 time the battle with the demon in the veil

[n8mahr81]

I just want to tell you that for me the "inventrory crash" seems to be gone.
What did I do? I installed up to date ati video drivers, made a "factory reset" of all driver options and removed any programme, that manipulated the ram-timings, like ati-tool.
Until then, I manually switched the timings for my graphics card via ATITool, and while no real overclocking did happen, it ran with 4mhz (!) to fast because of my laziness to finetune the mhz-slider.

My PC ran totally fine for months, NO other game did crash, no benchmark would fail because of this... But DA did take offense, somehow.
It still crashes during battles in the mage´s tower:wizard:, though. But the inventory related crashes seem to be gone.

Modifié par n8mahr81, 17 février 2011 - 01:08 .

[Silkbio]

sgoudreau wrote...

played for several hours now and no crashes with catalyst 10.11 drivers

I have these drivers and I crash almost every single  time I load inventory. Game is basically unplayable.

Got a top of the range system (radeon 5970, i7 and so on), never crashes, no other games crash, etc.

ALso using win7 64bit.

[Silkbio]

Quick update; Turning off "Frame buffer effects" in my video options seems to have cured this.

Hopefully this helps others.

[Viking Penguin]

Silkbio wrote...

Quick update; Turning off "Frame buffer effects" in my video options seems to have cured this.

Hopefully this helps others.

Thanx man, this fixed the problem.  I can't believe nobody else figured this out.  I tried modifying code and everything.  Jesus!!  I have 980x Extreme with Radeon HD 5970.  When I saw your spec I figured I'd give it a shot.  FRAME BUFFER is the culprit on this one!!  Thanks again, I owe you, good Karma to you Silkbio:)

[Deftones81]

I just wanted to thank Silkbio. I have the exact same GFX Card and a high spec system and have tried so many things over the months. This one thing fixed it 100%. I didnt want to post too early so I played it multiple times for different amounts of time and it is rock solid now. Thanks again.

[Freedom4556]

Somebody should submit a bug report to AMD or Bioware on this. I just confirmed it on my machine running two 4870 1Gb cards in crossfire. It's a crossfire bug that disabling "Frame Buffer Effects" prevents. The alternative is to simply disable crossfire. (you 5970 owners are running crossfire too whether you realize it or not)

Other specs:
Q8400
Win7 64bit
4GB DDR2
vanilla Catalyst 11.5
latest DA:O executables (as of 5/29/11)
Max settings 1920x1080 AA off

Thanks guys

[SogazuSeJin]

sgoudreau wrote...

played for several hours now and no crashes with catalyst 10.11 drivers

Also here, issue disappeared by using 10.11 except that frame rate was cut in half of even before turning on crossfirex with up to date driver (11.6b).

either Bioware or AMD seriously screwed up at this issue but no one's gonna fix it probably. It's just shame.