Aller au contenu

Photo

Crashing during character creation


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

#1
suffron

suffron
  • Members
  • 4 messages
I cant get past character creation because the game will crash.

Very frustrating

anything to do to fix it ?

#2
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
Preliminary diagnostic information

PCs are not *anything* at all like game console systems.  There is almost nothing that is truly "standard" between various branded PCs, making the game developers' jobs very difficult, and resulting in warning labels attached to game boxes for those games that have serious requirements. 

In case you have misunderstood how to evaluate your PC compared to that game box label, we have to start from here.  Fill it all in.  

Basic Hardware Specification Chart (Empty so far)

Processor Manufacturer: AMD / Intel
Processor Name / Type: Athlon 64 / Pentium / C2D / dual core / quad, etc.
Processor Speed:  ?.? Ghz (or AMD Performance Number)
Operating System / Service Pack: WindowsXP with SP #?, Vista ? (Oh, no!)
System RAM: ? ? GBs (MBs, if less than 1024)
Video (GPU) Manufacturer: ATI / Nvidia (only those two are supported, PERIOD)
Video Card Model: (examples) Radeon HD 3650 Pro / Geforce 8600 GT
Video Card Driver Version: Catalyst ?.? / Nforce ??.?? (use numbers, not the word "latest")
Video Card onboard RAM: ? ? ? MBs
Sound Card Manufacturer:
Sound Card Model:

Gorath
-

#3
suffron

suffron
  • Members
  • 4 messages
Processor: AMD athlon 64 X2 Dual core processor 5600+ 2.8 GHz

Operating system: Vista...... SP2

System RAM: 3 GB

Video Card: Nvidia Geforce 8600 GTS driver: 191.07 onboard RAM: 256 MBs

Sound Card:Realtek High Definition Audio, 6.0.1.5350




#4
trickydonut

trickydonut
  • Members
  • 6 messages
Played through once, no problem, then tried to play again with new character. Game crashes every time after I select class and race and click next. Very frustrating - dont know what to do.

#5
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
All right, I see you played at pin the tail on the donkey with three tails.  The OP on this one had a Geforce 8600 GTS.  Many owners of nVIDIA 8n00 graphics cards have conflicts between audio and video drivers and this game.  Do you have an 8600 GTS? 

From the other answer to your second of three of the same question in three old threads:

This one (had been) meaningless, since if the OP's system was a
junker, he / she was lucky to get past the first menu. and the OP chose
not to respond about his / her hardware. 

You say you played before, but not how well it went.  Some players have
written that choosing a distaff sex meant they were unable to continue
with their new character.  Did you attempt to change sexes?  You really
need to offer a lot more data, probably including the standard system
configuration summary. 

I have had a lot of trouble with Geforce drivers and playing games (though not particularly with Dragon Age, actually) using my own Geforce 8600 GTS, if you finally return to your comments in either of the threads.

I have a feeling that you were either overstressing your hardware before, and it's failing now, or it was performing way above what it should have been able to do, and now cannt do so any longer. 

Modifié par Gorath Alpha, 16 juin 2010 - 02:15 .


#6
trickydonut

trickydonut
  • Members
  • 6 messages
Thanks for the quick reply. A bit more detail. My system is running Windows 7 (64bit), core i5-520M (2.4Ghz), ATI Mobility Radeon HD5470, 6MB RAM, . DA:O with Shale DLC only, no other mods. Went throught the game once without incident (well, ok, CTD a couple of times, okay on restart). Can still access the completed game, but cannot start a new character. Whenever I click next after selecting sex, race, class, the game quits. Have tried most permutations of attributes, logged in/logged out, cleaned the CD, and restart. Have not reinstalled.



Sorry for the posts on other threads.

#7
trickydonut

trickydonut
  • Members
  • 6 messages
Problem solved. I had the sound disabled in the configuration menu. When turned back on, worked fine. Was able to recreate this bug.