13 réponses à ce sujet

[Surango]

First off, this thread is NOT a place to complain. If that is your intention, please go elsewhere. Whether these solutions work for you or not, let us know. If your bug is not related to this, here's the link to the bug list for 1.03: social.bioware.com/forum/1/topic/58/index/1633999

What is needed:

1. Try the suggestions BEFORE posting.
2. Is it a retail version or digital version of the game?
3. What, exactly, is going on when the game crashed?
4. What OS do you run, is it 32 or 64 bit?

DirectX 9c End user Runtimes:

This game was originally deigned on DirectX 9. Yet Win7 and Vista run on
DX10/11 have you tried installing the end user runtimes? www.microsoft.com/downloads/details.aspx

Instructions:

Make a folder and call it DX on your desktop.
Download the file, when you run it, it asks for a destination path to extract the files. Use the folder you just made.
Go into the DX folder and find the setup utility and follow its instructions from there.

It doesn't say you have to restart afterward, but it's probably a good idea to do so either way. When you're done, you may delete the DX folder.

if you need to find out what version of DirextX is on your computer, go to Help and Support from your star menu and type in directx and you'll see a link that says. "What version of DirectX is on your computer?" Let this run a diagnostic and you'll know for sure. If you let it connect to the internet, it says it will also check your drivers.

From the looks of things, this mostly helps people that have a retail version of the game. It may work if you have a digital version, but most folks that say they have one also say it didn't help.

Drivers:

This one's pretty obvious, but I'll say it anyway. Check your drivers. Don't know how to find them? An easy way is to go from the DA launch program and click Configure. You can find the driver version under summary. Then check it against the current version from your provider. Installation is pretty straightforward in most cases.

Digital Version:

My gut is telling me something in the 1.03 patch for digital users got corrupted. I have no way of testing this as I do not have a digital copy of the game. I'm not sure why the problems are more prevalent on Steam, but this seems to be what everyone is saying. If the DX solution works for you, I'd be VERY interested to know.

XP Users:

I've only seen one XP user report a problem with crashes, but they fall under the digital version category as well. We need more feedback from you.

Modifié par Surango, 23 mars 2010 - 05:44 .

[Karnage28]

I'm using XP, I can give it a try

[wolfwarp]

Hi Surango, thanks for the info!



I have a question. If I am to apply this directX directly and if I am suppose to be on directX 11, would I still be able to play my directX 11 games like Dirt 2?



And may I know what is the rationale of reapplying the directX runtime to our machines that have been working flawlessly on patch 1.02 but not 1.03? I am keen to fix the issue, but I prefer to do so with my eyes open. Hope you understand.



Cheers!

[Surango]

wolfwarp wrote...

Hi Surango, thanks for the info!

I have a question. If I am to apply this directX directly and if I am suppose to be on directX 11, would I still be able to play my directX 11 games like Dirt 2?

Yes, the DirectX runtimes only call the files installs if a program needs them. This basically means if a game was designed on an older format (DX9) and played with a newer one (DX10/11) the grapghical formats would be what they need to be. I'm no technical guru- if someone else can elaborate more on that, go for it.

And may I know what is the rationale of reapplying the directX runtime to our machines that have been working flawlessly on patch 1.02 but not 1.03? I am keen to fix the issue, but I prefer to do so with my eyes open. Hope you understand.

Cheers!

If you already have the runtimes installed you don't need to redo them. From your post on the bug page though you don't have them or at the least need to update them. I'm not really sure why it's needing the runtimes now, but most people are reporting graphical crashes when doing holy smite, mana clash, the fight with the sloth demon, and the shade in the kocari wilds. Gazarath, I think. These all have one thing in common- a certain vfx that kind of looks like a blue fireball.

Some have also reported that turning off all options in the "online" tab and turning off autosave seems to help. No idea why that would be unless it has something to do with the unable to connect to server message you can sometimes get.

[carlosjuero]

Well, just to chime in a smidge:



I have the DX 9 updated run time files installed on my W 7 64 box - its a requirement for many of the older games I run.



Using D2D's Digital version



OS noted above, but again its Windows 7x64



It tends to want to crash on me (and does off and on) at random intervals - sometimes on achievement unlock, sometimes on combat start/cut scene end/start. It is related to how long I play the game in a single sitting and how 'fast' I go (in other words, if I don't wait a second or two after loading into a new area and just jump to the next area).



I was able to lower the issue frequency by turning off AA and lowering texture levels as well as turning off the extra processing effects (none of which has an effect on my FPS oddly enough). I am pretty sure it might have to do with the texture processing - the excessive load times the patch 1.03 was supposed to fix might have been caused by texture loading/unloading - 'speeding' it up could have created a 'hole' for a leak within the texture memory (obviously there is no way to know this for sure).



I appreciate that there are folks out there trying to help, and I hope the steps they are coming up with are indeed helping some people.

[Dawglicous]

Just to chime in regarding the XP users, I am on XP playing this through Steam and I too have had it crash to desktop, something it never did before. Fortunately for me, I already beat this and was thinking of playing again when all of this happened with the horrible new patch, so for now I will just be playing something else. Hopefully this is resolved by Bioware at some point. Good luck on your work Surango!

Also was wondering, if I am on Steam and the latest patch is already installed, am I outta luck or can I install and still somehow get the last patch BEFORE 1.03?

Modifié par Dawglicous, 25 mars 2010 - 07:19 .

[Surango]

Dawglicous wrote...

Also was wondering, if I am on Steam and the latest patch is already installed, am I outta luck or can I install and still somehow get the last patch BEFORE 1.03?

As far as I know, digital users get autopatched so the only way to install and not get 1.03 is to stay offline. Even that may not work. You probably couldn't use DLC either.

[Surango]

@ carl

Have you tried unchecking the online options and turning off autosave? Does it help?

[Eurypterid]

Dawglicous wrote...

Also was wondering, if I am on Steam and the latest patch is already installed, am I outta luck or can I install and still somehow get the last patch BEFORE 1.03?

No, I don't think so. The only way to 'roll back' would be to uninstall then reinstall the game. But Steam would force you to the latest patch.

There is a setting you can adjust so it doesn't automatically update your games, if memory serves. But that does you no good at this juncture.

[carlosjuero]

Surango wrote...

@ carl
Have you tried unchecking the online options and turning off autosave? Does it help?

I tried that once and it led to a crash (or, rather, I still crashed after changing the options).

Right now if I keep my play sessions semi-short I can survive, though it gets pretty bad the longer I play - to the point where its just about impossible to get a hang on whats going on w/ moving/loading/etc.

[lennypdx]

Installed the directX9c end user runtimes as per the description above.

Updated my Nvidia driver to 197.13, released yesterday.

Game still crashes if I play too long, with "too long" being about 1 hour. This is since installing patch 1.03, by now also awakening is installed.
What happens? Usually during a dialog, but it also happened during a fight or simply looking at talents, the screen goes black. The last sound bit continues to the end in case of dialog; if the crash occurs during fighting the last sound effect goes into a loop. Nothing helps, except a hard reboot, i.e. pressing the reset button.

Graphics card is Nvidia GeForce 9800 GT.
Window Vista home premium 32-bit SP2.

EDIT: This is with the retail version (europe, NL) of both origins and awakening.

Modifié par lennypdx, 26 mars 2010 - 02:57 .

[Karnage28]

I pretty much gave up looking for solutions on my end, no matter what I do, game crashes, so I will have to wait and see what happens within the next few weeks and maybe receive either a formal fix from Bioware, another patch that fix everything or throw the game out the window and forget about it.

[GenghisQuan]

Well my graphics card is a Nvidia GeForce 9600GT

Windows 7 64 bit professional.



I originally had the the crashing problem and I uninstalled Dragon Age Origin. I never installed Awakening.



I reinstalled Origins up to the newest 1.02 patch and it ran flawlessly.



I followed someones advice and cleared my temp folder, then I decided to install awakening and not the stand-alone 1.03 patch. I have 1440x900 res with Medium Graphics & Texture detail. AA at 2x and I do not automatically upload information online. I hope this helps at least one person.



Awakening now runs flawless for me but I am not even 10% through the game. I have suffered 0 crashes though.

[Surango]

That's good to know Genghis. I use a free and open source window washer for that. It's from eusing.  It asks you to register it every time you use it, but you don't have to. It's kind of like the donate to firefox buttons you see. Here's the link for the window washer: eusing.com/Window_Washer/Window_Washer.htm

Guys and gals, you've probably heard all the hype about registry cleaners and how great they are right? There's on one the site I'm linking to, but I'm going to recommend you NOT use it, or any other one for that matter. Unless you know what you're doing you can royally screw up your computer with them. Thou hast been warned!