Aller au contenu

Photo

DAO keeps crashing and gives no error


  • Veuillez vous connecter pour répondre
22 réponses à ce sujet

#1
Darkshadow29

Darkshadow29
  • Members
  • 132 messages
Like the title says, i be playing along, and all of a sudden it crash to desktop, no error message. I load it up and it plays fine for so long then happens again. Has happened 3 times now.

#2
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
No one can answer you without some useful information.  We don't even know yet that you picked the correct forum to ask that question in.  When that becomes clear, then we need version, vendor, OS, Service Pack, Driver Data, Hardware Component Inventory, etc etc. etc.

social.bioware.com/forum/1/topic/58/index/2154638

Here is just the hardware, without the needed problem description outline: 

Basic Hardware Specification Chart (Empty so far)

Processor Manufacturer: AMD / Intel
Processor Name / Type: Athlon X2 / Pentium D / C2D / dual core / quad, etc.
Processor Speed:  ?.? Ghz
Operating System / Service Pack: WindowsXP with SP #?, Win7, Vista ? 
System RAM: ? ? GBs (MBs, if less than 1024 ? )
Video (GPU) Manufacturer: ATI / Nvidia (only those two are supported, PERIOD, so please answer which of them you have)
Video Card Model: (examples) Radeon HD 5670 / Geforce GT 240
Video Card Driver Version: Catalyst ?.? / Nforce ??.??
 . . (please use the numbers, and dates, *not* the word "latest")

Video Card onboard RAM: ? ? ? MBs
Audio Driver version number and date
Sound Card Manufacturer:
Sound Card Model:

(And this is only for the raw hardware & driver variations.  Potential software conflicts are far more likely to be game play problems, and developers cannot test for all possible program loads.)

P. S.  Please use every day business style paragraph breaks, punctuation, and spelling.    

Modifié par Gorath Alpha, 26 février 2011 - 08:52 .


#3
Darkshadow29

Darkshadow29
  • Members
  • 132 messages
Ok, thats what I need to know is what to tell you...



OS: Win7 64 SP1

CPU: i7 920 4.33ghz

Ram 6gig 1600 DRR3

DVD DOA:Ultimate edition

SSD HD with 62.3 freespace

sli Evga gtx 570hd with 266.58 driver

1920*1200 res

max grahic settings.

#4
Darkshadow29

Darkshadow29
  • Members
  • 132 messages
is there something else you need to know to help me stop this?

#5
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages

Gorath Alpha wrote...

. . . then we need version, vendor, OS, Service Pack, Driver Data, Hardware Component Inventory, etc etc. etc.

social.bioware.com/forum/1/topic/58/index/2154638


Video Card Driver Version: Catalyst ?.? / Nforce ??.??
 . . (please use the numbers, and dates, *not* the word "latest")


Audio Driver version number and date
Sound Card Manufacturer:
Sound Card Model:


From what I've seen so far, nothing jumped out to say to me "I'm the guilty one", no.  You have omitted the above items, and we can also go for more detail about the symptoms, as follows:

3.  Problem Details

  a.  When it comes to problem details, think
about the five basic questions: Who? What? When? Where?  Why? Okay, so
“Who?” doesn’t really apply here, but the others do.

  b.  What?  What is the nature of the problem that you’re seeing?

  c.  When?  When does the problem occur? Every time you engage in a particular action or only after so many hours of play?

  d.  Where? Where does the problem occur? Is the problem localized to a particular planet or does it occur everywhere?

  e.  Why? As much as possible, can you isolate the problem to a specific set of steps?


That's from Chris Priestly's "How to Report a Problem" sticky on top of the ME-1 Tech Forum (where it's got me as author, although I wasn't, actually).

Modifié par Gorath Alpha, 27 février 2011 - 11:06 .


#6
RaenImrahl

RaenImrahl
  • Members
  • 5 386 messages

Darkshadow29 wrote...

Like the title says, i be playing along, and all of a sudden it crash to desktop, no error message. I load it up and it plays fine for so long then happens again. Has happened 3 times now.


Some questions:

1) Do you at least get a "The Program has stopped working" error?
2) Have you modded the game in any way?
3) I just want to be clear...  When you say the program is crashing, are you being tossed back to the desktop, or is there a Blue Screen of Death, or is the computer restarting on its own?  Have you experienced a BSOD or auto-restart doing other things?
4) Looking at your specs... are you indeed using two Nvidia graphics cards in SLI configuration, or using one card and an onboard chip for Hybrid SLI?  Or is the card on its own?

Modifié par RaenImrahl, 27 février 2011 - 01:31 .


#7
Darkshadow29

Darkshadow29
  • Members
  • 132 messages
1 yes
2 no
3 back to desktop
4 2 570's

Modifié par Darkshadow29, 27 février 2011 - 01:46 .


#8
RaenImrahl

RaenImrahl
  • Members
  • 5 386 messages

Darkshadow29 wrote...

1 yes
2 no
3 back to desktop
4 2 570's


Okay... I notice you have an i7 920.  4.3GHz?  Are you overclocking, by any chance?

If so, here's the deal... DAO hates overclocked CPUs.  I know, I know, other games run fine on it.  DAO does not.  Even with the Intel Turbo thing, people will have problems.  I just helped someone in another thread with this same issue.  So if you are overclocking, then try going back to normal clock speed (adjusting graphics if needed) and see if you get some more stability.  If you are... I'll bet my next paycheck that's it.

If I am reading the situation wrongly... then consider doing a complete uninstall/reinstall of the Nvidia drivers... there's a link in my sig.

#9
Scimal

Scimal
  • Members
  • 601 messages

Darkshadow29 wrote...


OS: Win7 64 SP1


Thars yar problem.

DA:O 1.4 hates Win7 x64.

It's not your drivers, it's not your Overclock (assuming you've stress-tested the OC). I have a stock Q6600 (2.66Ghz) and have the same problem.

After watching the forums for two months looking specifically in threads with this problem, it seems 90% of the people having the problem have Win7 64-bit.

The kicker is that there isn't really a fix. The standard trouble-shoot stuff has varying results: Core affinities set to 1 or 2, processing to Below Realtime or at Realtime, running the game in XP-compatibility mode... Nothing really "solves" it consistently, most just delay the crashes a bit.

Seems it's just luck of the draw.

Sucks, yeah, but I sure wish BW would let us know if they're investigating, since it's only been a problem since 1.04.

Otherwise, Quicksave is your best friend, try toning down graphics settings, and hope for the best.

Modifié par Scimal, 27 février 2011 - 05:29 .


#10
RaenImrahl

RaenImrahl
  • Members
  • 5 386 messages

Scimal wrote...

Thars yar problem.

DA:O 1.4 hates Win7 x64.


Nonsense.  Get over it.  Many people, myself included, have played DAO with Win 7 from day one had experience few if any crashes.  Why does my computer run patch 1.04 fine and yours does not?  Does Bioware like me more than you?  Utter nonsense.

Problems and solutions with software are never that simple.  I suppose it's easier to just blame the big, faceless entity.  I can understand that-- I have issues with how Bioware/EA has handled DAO, and DA2 for that matter.  But to make such gross generalizations, as "DA:O hates Win7 x64" is... idiotic. 

And as far as CPU overclocking is concerned, I can recall off the top of my head at least two cases in the last ten days where OC was the root cause of the instability.  

#11
TigerWolfAus

TigerWolfAus
  • Members
  • 5 messages

Scimal wrote...

Darkshadow29 wrote...


OS: Win7 64 SP1


Thars yar problem.


The fix I have for win 7 x64 is to make the game only run on 1 CPU, all my crashing problems dissapeared after this. See the other thread.

#12
Scimal

Scimal
  • Members
  • 601 messages

RaenImrahl wrote...


Nonsense.  Get over it.  Many people, myself included, have played DAO with Win 7 from day one had experience few if any crashes.  Why does my computer run patch 1.04 fine and yours does not?  Does Bioware like me more than you?  Utter nonsense.


Do you run Win7 HP x64? I know you run Win7, but I've not read which version.

Problems and solutions with software are never that simple.


I'm not suggesting it's simple - there isn't a solid fix. I'm suggesting that the cause might not be hardware or Driver related.

I suppose it's easier to just blame the big, faceless entity.  I can understand that-- I have issues with how Bioware/EA has handled DAO, and DA2 for that matter.


1.03 = I finished several playthroughs without a crash.
1.04 = Crashes despite any attempted "fix."

I've had the same OS for 2 years, the same hardware for 4 years. I update my drivers frequently and keep a very clean system. I do not have a bloated AV/Malware package, and have no other troubles with any other game.

Ergo, I deduced that 1.04 did something which causes to interact poorly with Win7 x64.

"The simplest explanation is usually the correct one." - Occam's Razor

But to make such gross generalizations, as "DA:O hates Win7 x64" is... idiotic. 


You're telling me my idea is idiotic when you have admitted in the past that Win7 has caused problems for people in other threads, and your blame lies with "DA:O hates Overclocks"...?

I will acknowledge that his OC could be the issue. Even a stable OC can sometimes cause problems. However, seeing as the OP has the same problem as a hundred other people - who mostly don't have OCs - I can't say for sure.

I know you frequent this boards and are generally very helpful, but I found this entirely insulting. You can disagree with me - that's fine. I don't know the specific cause, you're right. My suspicions lie with Win7 and whatever patch 1.04 did - maybe it was the new audio drivers in 1.04, maybe it's some obscure background service running on all the affected machines...

However, until there's a known cause and a known fix - saying someone else's idea is "idiotic" is the definition of being a pompous ass. You don't know what's causing it, so any viable cause is valid until proven otherwise.

And as far as CPU overclocking is concerned, I can recall off the top of my head at least two cases in the last ten days where OC was the root cause of the instability.  


I don't doubt this. Most people do not OC properly, and acknowledged that if his OC wasn't done well, it could be the problem.

Modifié par Scimal, 27 février 2011 - 03:34 .


#13
Scimal

Scimal
  • Members
  • 601 messages

TigerWolfAus wrote...

Scimal wrote...

Darkshadow29 wrote...


OS: Win7 64 SP1


Thars yar problem.


The fix I have for win 7 x64 is to make the game only run on 1 CPU, all my crashing problems dissapeared after this. See the other thread.


Not a bad suggestion.

Modifié par Scimal, 27 février 2011 - 04:13 .


#14
RaenImrahl

RaenImrahl
  • Members
  • 5 386 messages
Scimal-- yes, I've been running DAO from the beginning on Win 7 x64. In that thread you allude to... the one with all the x64 problems... I told you that reinstalling Windows would probably improve your performance.  Here's your answer:

Scimal wrote...
*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.


... to which I responded that I respect that answer. I really did.  Now, here I am trying to help the original poster by troubleshooting with some solutions that HAVE WORKED for others... and you're butting in with this patch 1.04 doomsaying.  So now that repect is starting to evaporate.

I've never claimed it was a universal answer... and yes, I've been running Win 7 x64 since I got DAO in July.

EDIT:  Adding... those other threads:  http://social.biowar...index/5801847/1

http://social.biowar...48347/2#5828531

Modifié par RaenImrahl, 27 février 2011 - 03:47 .


#15
RaenImrahl

RaenImrahl
  • Members
  • 5 386 messages
Darkshadow29-- sorry we're a little off track here. Please let me know if I can help further.

RI

#16
Scimal

Scimal
  • Members
  • 601 messages

RaenImrahl wrote...

Scimal-- yes, I've been running DAO from the beginning on Win 7 x64. In that thread you allude to... the one with all the x64 problems... I told you


No, you didn't tell me. You posted it, and I must've skipped it while browsing the thread.

Fine, if yours is stable, that's a good thing. Makes me less suspicious of Win7 in and of itself being the problem.

... to which I responded that I respect that answer. I really did.  Now,
here I am trying to help the original poster by troubleshooting with
some solutions that HAVE WORKED for others... and you're butting in with
this patch 1.04 doomsaying.  So now that repect is starting to
evaporate.


I don't need your respect. I'd prefer a fix to the problem, or a word from BioWare about the issue.

I acknowledged the instability OC'ing can cause, so I didn't disagree with your solution - I just find it unlikely if his OC is stable.

At the time I made that post, I didn't think it was the OS. It so rarely is simply an OS problem - usually these crashes are bad interactions with background programs, cooling related, or especially driver-related. However, after reading the wide proliferation of the problem - with the accompanying variety of systems - I don't think it's driver or hardware related.

The most common software I saw side-by-side with the problem was Win7 x64.

I've never claimed it was a universal answer... and yes, I've been running Win 7 x64 since I got DAO in July.

EDIT:  Adding... those other threads:  http://social.biowar...index/5801847/1

http://social.biowar...48347/2#5828531


That's great. I'm happy for you.

That's still no reason to call someone else's cause "idiotic."

Like I said, disagree with me all you want. However, until the root cause is found, no answer is any more valid than another.

Modifié par Scimal, 27 février 2011 - 04:05 .


#17
RaenImrahl

RaenImrahl
  • Members
  • 5 386 messages
Sorry... I had posted while still composing my response... so you saw only a partial message. It's completed now. I do, however, stand by the notion that "DA:O hates Win 7 x64" is an idiotic statement. In that, at least, I can live with both my pomposity and my anality.

#18
Scimal

Scimal
  • Members
  • 601 messages
Works for me. I'm not here to argue with your or try to out-do each other's technical ePeens.

FWIW, OP:

If you're absolutely positive your OC is stable: Your Vcore is set to a stable rate, your RAM timings are in-sync with your CPU timings, you've ran Prime95 long enough (6+ hours) without an error, and all of your temps: North Bridge, CPU, GPU, etc. are all fine - then try anything listed.

Raen has some good starting points in his Round-up thread. The 1-Core trick is also an option, along with setting the processing to various parts in your manager (i.e. "Realtime", "Below Normal" etc.).

It might also be worth double-checking other drivers that could be involved: Network drivers, Audio drivers, and Motherboard drivers. They did change the way DA:O uses its audio drivers in 1.04, and it looks like you have onboard sound - which generally isn't as stable as having a discrete soundcard.

Beyond that, Win7 isn't officially supported for DA:O, so the chances of getting any official love are slim.

#19
Kastagir

Kastagir
  • Members
  • 359 messages
I've been running Windows 7 64-bit since day one and have never had these crashing problems that have been discussed. The game occasionally crashes when I open the inventory, but that's been rare and has been consistent through all the game updates. I run a dual core and I never overclock. Quad core systems may cause problems but it is far more likely that overclocking your processor is going to make the game crash more often. The "but other games run fine!" argument simply doesn't mean anything in reference to DA:O. Why overclockers come here to look for support without trying the game at stock rates is beyond me. It's like loading your game up with mods and then expecting the developer to fix the problems you're having.

Oh, and I don't think it is Windows 7 that isn't supported, just the 64-bit operating systems. This is because DA:O is not a 64-bit application.

#20
Kawazaku

Kawazaku
  • Members
  • 80 messages
Blame whoever you want. Bioware is to blame here. This game has had severe technical issues from day 1, in fact, all of their games have. Why are they not on here addressing problems and patching these issues? If I have a certain card, Dragon Age shouldn't crash because of it, it should be fixed. This is such bull**** how they overlook everything, and now they are rushing to get DA2 out, without even fixing the problems with this one!

#21
10kLakes

10kLakes
  • Members
  • 1 messages
I am getting a somewhat related problem.

In my case, the program dies when I am trying to load a game. It cranks away for a while and then dies, returning to the desktop. Thinking that the save file was corrupt, I brought up the game using earlier saves, but they too also die either during gameplay or when I do a new save.

I am now thinking that the game code is broken somewhere. This error first showed up one day when the game threw a message at me saying that the website link was lost. After that, I started getting this game abort problem.

If I reinstall the game, do I have to lose everything? Where are the save files kept so maybe I can save and restore those? I would hate to start completely over since I am so close to being finished.

#22
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
You need to determine which of the saves is really very bad.  Its mere existence in the saves folder screws up all of the other saves until you pinpoint which is bad, and get rid of it. 

#23
killkaan

killkaan
  • Members
  • 6 messages
I'm having a similar problem except I haven't actually started the game yet and it crashes to desk top with no errors.

The strange thing is, I bought the game when it came out and didn't have a single problem with it. I decided to give it another go and it's just broken, which tells me that they must have brought out a patch that messed it up as my hardware is all the same and my drivers are up to date. Obviously I could be wrong but somethings changed and it's not my pc!

I'm playing on steam
Vista32
2gig 800mhz RAM
Quad 2.66
GTS250