52 réponses à ce sujet

[Locane256]

Seriously, this is ridiculous.  DA:O has crashed 5 times today alone, seemingly at random.  The only commonality I can draw between all of them is that it was after playing for a good amount of time (an hour or so?).  I know I'm not the only one with this problem, and it's far too general of a crash to try to actually troubleshoot.

Fix it Bioware!

Modifié par Locane256, 02 décembre 2009 - 04:55 .

[oca_rold]

I also have this problem, random system crash. it is too random, sometimes i can play a 5 hours without any problems, and sometimes just 10 minutes into the game. i already updated my driver and DAO patch. nothing works.

[Velgaren]

Aye, this happens to me also. I've noticed it happens more often when I am running in the close-up camera perspective. When zoomed out all the way it doesn't seem to occur as much. Maybe this is a good way to get people to save their games more often ;0)

[jimmyhff]

This game crashes more than any other game I have ever played in my life. And to make matters worse, I have emailed "tech support" via the "official website" once per week the last three weeks and haven't gotten any response whatsoever.

EA, you suck at your job. Take that. Not only did I return the game, but I called the company and left a long message regarding their great ability to suck. Hopefully they got the gist before pressing the delete key and moving on to the next hundred customers that don't matter to them.

[Locane256]

jimmyhff wrote...

This game crashes more than any other game I have ever played in my life. And to make matters worse, I have emailed "tech support" via the "official website" once per week the last three weeks and haven't gotten any response whatsoever.
EA, you suck at your job. Take that. Not only did I return the game, but I called the company and left a long message regarding their great ability to suck. Hopefully they got the gist before pressing the delete key and moving on to the next hundred customers that don't matter to them.

That's hard core man, power to you.

EA should probably take a page from Blizzard's book and release it when it's not going to crash repeatedly.

They should rename the quicksave key to "crash insurance".

[snow0815]

100+ hours in the game and not a single crash here, so my bet is on your hardware, not the game.

[Matthew Young CT]

Why do people always assume crashes are a problem with the game? Sigh.

[Tosheroon]

+1 for hardware and conflicting software.

[futs22]

Although I will admit that I have had a few crashes already (around 4-5) and one BSOD from playing this game, I find it quite tolerable since the frequency of these crashes are very low. I've probably poured in more than 100+ hours into this game already and 4-5 crashes and 1 BSOD, isn't too bad(I have been playing since launch date).



The memory leak problem also isn't too annoying for me since it usually starts to rear its ugly head only after I have been playing for about 6 hours at the very least. Also, the solution to returning the load times to less than a minute from about 2 minutes (I've never experienced the 10-minute loading screen some people claim to have had) is to exit the game and launch it again which doesn't even take a minute to do.



I did notice something consistent with the 4 or 5 crashes I have had. After restarting the game after theses crashes, I've noticed that my EA/Bioware account is logged out despite me enabling the auto log-in option. In addition to that, I sometimes am unable to log-in to my account for about a minute and when I do get to log-in my DLCs are sometimes showing as either not yet downloaded, downloading or unauthorized. Clicking the refresh button repeatedly always put everything back in order meaning all the 3 DLCs (Shale, Armor, Warden's Peek) are enabled.



I'm going to make a guess and say that my game crashed as a result of being disconnected from the EA server. However, I did experience getting disconnected from the EA server but still being able to play. Oh well.....

[kinsha22]

Much to as I hate to back up EA on this one, but I've really had few random crashes. I can only remember one and a quick restart of DA and it loaded right over the problem spot without a hiccup. The only repeatable problem I've had is loading save games in the Denerim- market place and all the sub-sections/buildings in that area. I've learned to save in camp instead of in denerim - market place to save the frustration of losing progress.

[Matthew Young CT]

There should be a rule that you can't complain about crashes until you have:



1) Installed the game on a fresh OS. It isn't Bioware's fault if you install problematic junk on your system and it crashes or does weird stuff to their game. See AVG minimizing games (which crashes many games) for example.

2) Run Memtest86+, linpak, and furmark and passed them all.

[Locane256]

Matthew Young CT wrote...

There should be a rule that you can't complain about crashes until you have:

1) Installed the game on a fresh OS. It isn't Bioware's fault if you install problematic junk on your system and it crashes or does weird stuff to their game. See AVG minimizing games (which crashes many games) for example.
2) Run Memtest86+, linpak, and furmark and passed them all.

Hey, I'm glad you mentioned these things.

Ironically, I just purchased a 64 gig SSD drive (with 128 megs of cache) and put windows xp 64 on it, so my system is fresh.  (Note that means I have the latest drivers as well)  I was chasing this crash issue and ran prime95 (the 64 bit version) for a few minutes just to test my hardware, and it's clean.  I've had prime95 identify bad ram before, that's why I don't buy patriot memory.

It may very well be that my hardware combination is causing a crash in Dragon Age, but it happens to be only Dragon Age that is crashing.  I have a billion steam games (8 installed right now, god only knows how many not installed, probably somewhere on the order of 40), and none of them have the same behavior.  If I had to bet, I'd say we'll see a patch for DA:O with something cryptic in the changelog alluding to a general crash fix in the next couple of weeks.

I can't say with any real certainty how many hours in I am, but I'm at the quests for the landsmeet in Denerim right now, so I would imagine 100 or so.  Guessing at the number of crashes I've had so far overall, it would probably be near 50, and that doesn't include the 3 times my save file ended up being corrupted somehow and I had to jump back a step.  That's why I double save now.

Modifié par Locane256, 02 décembre 2009 - 10:34 .

[Locane256]

So, this is new.



I just got a crash that I tried to screenshot but couldn't. An error window popped up instead of the normal "Send this error to microsoft" dialogue and said something like:



"Microsoft Visual C++ runtime error: no true function call"



Anyone else seen this?

[Matthew Young CT]

Ironically, I just purchased a 64 gig SSD drive (with 128 megs of cache) and put windows xp 64 on it

Maybe put a supported OS on it? 

, so my system is fresh.  (Note that means I have the latest drivers as well)

Don't forget PhysX and stuff like sound card drivers! Since XP 64 isn't going to have many by default...

I was chasing this crash issue and ran prime95 (the 64 bit version) for a few minutes just to test my hardware, and it's clean.  I've had prime95 identify bad ram before, that's why I don't buy patriot memory.

Er, you need to run it for a lot more than a few minutes.

It may very well be that my hardware combination is causing a crash in Dragon Age, but it happens to be only Dragon Age that is crashing.

I understand that that makes it seem obvious that the fault is with DA, but it isn't necessarily. Many games do something uniquely stressful to a system and crash it. I've seen the Street Fighter benchmark crash systems that passed furmark and prime95 for example (when stability checking OCs).

I have a billion steam games (8 installed right now, god only knows how many not installed, probably somewhere on the order of 40), and none of them have the same behavior.  If I had to bet, I'd say we'll see a patch for DA:O with something cryptic in the changelog alluding to a general crash fix in the next couple of weeks.

Wouldn't be at all surprised. I'm not saying it has no crashing issues, just that it doesn't have lots of them or anything (evidence being plenty of people getting none-hardly any). So, so many crashes are hardware or other software issues.

I can't say with any real certainty how many hours in I am, but I'm at the quests for the landsmeet in Denerim right now, so I would imagine 100 or so.  Guessing at the number of crashes I've had so far overall, it would probably be near 50, and that doesn't include the 3 times my save file ended up being corrupted somehow and I had to jump back a step.  That's why I double save now.

Had 1 repeatable hard crash and about 2 CTDs personally. Maybe 150 hours total? Maybe it's the game's fault you had so many. Maybe it's running it on an unsupported OS. I don't know. It's unfair to blame the game unless you're sure your system is stable and you're running it on supported hardware & software however!

[gambledaniel]

The point is, Bioware doesn't care about their customers. Okay some people might have a flawless experience, but for those hundreds that have problems; they say to send an email, and a response will arrive in about 1 to 2 days.  But after posting numerous emails to bioware and not a single word from them? Yeah, Bioware doesn't care about their customers.  Oh well, at least the games is fun when it doesn't crash.

-and to top it off.  Its been almost a month and no information about a new patch?  >_>

Modifié par gambledaniel, 02 décembre 2009 - 12:19 .

[Matthew Young CT]

Bioware doesn't handle tech support.



There's been plenty of information about the patch in the last month.

[Locane256]

Matthew Young CT wrote...
Maybe put a supported OS on it? 

Yeah, sorry. I'm not about to install a 32 bit version of windows as a troubleshooting method to get a game to work that is obviously having similar crashing issues for other people who are not running my OS.  I think you know that though, hence the winky face there.

Don't forget PhysX and stuff like sound card drivers! Since XP 64 isn't going to have many by default...

I'm pretty sure Nvidia's drivers distribute with physx?  I could be wrong.  The sound drivers are downloaded directly from realtek's website, so I know those are up to date.

Er, you need to run it for a lot more than a few minutes.

Yeah, but honestly we're going back to the whole "how much effort should I really have to put into debugging a buggy game?" thing.  Running prime95 for 3 - 10 minutes has always produced errors on faulty hardware before, so running the same test again is a pretty good basic benchmark.

I understand that that makes it seem obvious that the fault is with DA, but it isn't necessarily. Many games do something uniquely stressful to a system and crash it. I've seen the Street Fighter benchmark crash systems that passed furmark and prime95 for example (when stability checking OCs).

I wasn't even aware there was a "Street Fighter" benchmark.  I get your point here, but honestly neither of us knows enough about how DA:O uses resources to draw any real conclusions, all I see is the end result.

Had 1 repeatable hard crash and about 2 CTDs personally. Maybe 150 hours total? Maybe it's the game's fault you had so many. Maybe it's running it on an unsupported OS. I don't know. It's unfair to blame the game unless you're sure your system is stable and you're running it on supported hardware & software however!

I totally agree.  Fortunetly, I'm pretty sure my system is stable.  I haven't scientifically torture tested every component individually and in every combination, but I'm confident enough that I'm willing to blame the game at this point.

Something is very wrong with DA:O, and all we can do is hope that it will get fixed.  Honestly, $75 is a lot to spend on a game that I have only seen the "exit" button on 3 times since I started playing it, because every other time I take a break is because it has crashed.

Modifié par Locane256, 02 décembre 2009 - 01:45 .

[Aezay]

What kind of hardware do you have?

[Dobralov]

Problem:

Crashes to Desktop upon save game restore and/or
crashes to desktop upon leaving Chantry in Lothering. Disabling sound
in the configure menu remedies the problem, but I'm not going to endure
a soundless game.

System:
Intel Core 2 Duo 2.4 GHz
Nvidia Geforce GTX 260 with 11/28 drivers (latest) with Direct X 9.0c
Realtek HD Audio Output
4 Gigs RAM
Windows XP SP 3

Again, if I disable the sound, the game seems to work, although I have not endured extended playtesting sans sound.

[Matthew Young CT]

Locane256 wrote...
Yeah, sorry. I'm not about to install a 32 bit version of windows as a troubleshooting method to get a game to work that is obviously having similar crashing issues for other people who are not running my OS.  I think you know that though, hence the winky face there.

Ah, no, I wasn't joking. The minimum supported OS is Windows XP SP3. Windows Server 2003 (rebranded) is not supported. EA are well within their rights to offer you no support on that OS. It says right on the box it ain't supported.

AFAIK XP 64 is well known to be a little dodgy when it comes to games, anyway. It was never intended as a gaming OS.

I'm pretty sure Nvidia's drivers distribute with physx?  I could be wrong.  The sound drivers are downloaded directly from realtek's website, so I know those are up to date.

Not sure, don't have an Nvidia card these days. Figured it couldn't hurt to mention.

Yeah, but honestly we're going back to the whole "how much effort should I really have to put into debugging a buggy game?" thing.

I'd start by not assuming it's buggy

Running prime95 for 3 - 10 minutes has always produced errors on faulty hardware before, so running the same test again is a pretty good basic benchmark.

Guessing you haven't done much OCing? A very slightly wonky CPU can easily pass 3-10 minutes of prime95, and fail on a proper torture test. Or linpack. Or a random game benchmark. Such is hardware

I wasn't even aware there was a "Street Fighter" benchmark.  I get your point here, but honestly neither of us knows enough about how DA:O uses resources to draw any real conclusions, all I see is the end result.

Right, a crash. Which could have many causes, as you are surely aware. Best to rule out other possibilities, since you want a stable system regardless.

I totally agree.  Fortunetly, I'm pretty sure my system is stable.  I haven't scientifically torture tested every component individually and in every combination, but I'm confident enough that I'm willing to blame the game at this point.

Fair enough. After you try it on a supported OS.

Something is very wrong with DA:O, and all we can do is hope that it will get fixed.  Honestly, $75 is a lot to spend on a game that I have only seen the "exit" button on 3 times since I started playing it, because every other time I take a break is because it has crashed.

If there were something very wrong, many people would be having the problem. Most of us aren't. There could well still be something wrong, but not very.

Modifié par Matthew Young CT, 02 décembre 2009 - 03:03 .

[Dobralov]

Updated Motherboard drivers: No effect

Disabled V. Sync: No effect.

Windowed mode: No effect

Disabled V. Sync and Windowed mode: No effect.



I'm retiring this game until they patch it, as I've now wasted two hours of my life, not including the time I spent playing the game so far. I love the game, hate the instability on my system.

[qetqrqerfasd]

The game runs fine on my xp64, the only problem I had were the physx crashes but those got adressed with the latest nvidia driver.

[Matthew Young CT]

Sure, but unsupported OSes can be fairly hit and miss. Nice you got lucky, but you can't complain if it doesn't work.

[OneUntamed1]

I experience the load time increases frequently but the crashes not so much. I had an issue where I killed the lady that takes you to prison, then couldn't leave the arl's place without it crashing 100%. I just had to reload and surrender to bypass that crashfest.



Core specs:

AMD 5200+ dual core

4gb DDR2 800

Sapphire 4850 hd

Windows Vista Pro 64bit

[Aezay]

Back when I used xp32, I often crashed, mostly due to my GPU, which is an ATI 3870. But now that I have win7, things run a lot more stable. Maybe xp is just getting a little old with all the new hardware configurations?

Now, I am not saying win7 is the best thing ever made, because I actually miss xp, don't really find win7 that amazing, but from a gaming perspective, I need it for DX10+, and hardware wise, I need it because xp is going to get phased out eventually.



@Dobralov

You say the crash could be avoided by disabling the sound, did you try to update the sound driver?

Also, wasn't there an error in xp with the HDA bus, which needed one of these patches, but none of them comes for sp3, which would be the problem.

- http://support.microsoft.com/kb/888111

- http://support.microsoft.com/kb/835221