Aller au contenu

Photo

Configuration Utility fails, what now?


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

#1
OhoniX

OhoniX
  • Members
  • 508 messages
I just bought the game for my PC, installed it, and tried to start it up. The configuration utility loads up, a progress bar begins to move, and about 1/3 of the way across, it crashes. I cannot play the game. What do I do? It's not like I have a bad computer, it can easilly run games like Oblivion, Fallout, and Champions Online.

#2
Slatanness

Slatanness
  • Members
  • 1 messages
Same here.And windows wants to send a report as well.What gives?????

#3
bugsraid666

bugsraid666
  • Members
  • 2 messages
same here , c'ant play the game T_T

#4
monkeyfoot34343

monkeyfoot34343
  • Members
  • 13 messages
same!!!!! don't even try to fix it... i've looked every where for answers! uhh

#5
monkeyfoot34343

monkeyfoot34343
  • Members
  • 13 messages
i hope some one finds a fix!!!

#6
FallenHero007

FallenHero007
  • Members
  • 1 messages
I am having the same issue, any answers yet?

#7
cheeseslayersmu

cheeseslayersmu
  • Members
  • 197 messages
I believe the problem is that you play fallout.<br />
<br />
[comment deleted]

Modifié par BioWareMod01, 28 août 2013 - 05:49 .


#8
omgitsbounce

omgitsbounce
  • Members
  • 6 messages
I am also getting this error. I tried patching, and still nothing.



"Dragon Age: Origins Configuration Utility has encountered a problem and needs to close. We are sorry for the inconvenience."

#9
Kaaji

Kaaji
  • Members
  • 2 messages
same problem here too.

#10
lord xxxxx

lord xxxxx
  • Members
  • 11 messages
same here, dont know what to do


#11
Lariadia

Lariadia
  • Members
  • 4 messages
It did not crash in the beginning, but gameoverlayrenderer.dll now crashes the configuration utility while it scans the system.

#12
ModerateOsprey

ModerateOsprey
  • Members
  • 773 messages
I had the same problem on W7, I simply ran the installer as Administrator and it loaded just fine.

Edit: Actually, I ran both the installer and the launcher as Administrator. I also disabled anti-virus. I pretty much always do that when installing games

Modifié par ModerateOsprey, 07 avril 2010 - 11:58 .


#13
angelmar

angelmar
  • Members
  • 1 messages
I see lots of posts about this in Mass effect 2 and DA:O but no solutions. Running as an admin has not fixed anything.

#14
hexaligned

hexaligned
  • Members
  • 3 166 messages
What OS? I'm no computer guru but I'll take a stab in the dark and recommend trying to run the setup exe in a different compatibility mode.

#15
cheerfulchaotic

cheerfulchaotic
  • Members
  • 1 messages
same problem. Are you serious that there's no solution?

#16
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
First, this is not the place to ask.  This is General Discussions.  Tech questions go either to EA for official support, or to the appropriate platform Tech Discussions forum, where users discuss tech stuff with each other, offer advice, & suggestions ("Self Help").  However, none of the readers there can determine from any of the several comments here in this thread what platform any of you are on, what your symptom details are, and what contribution to those symptoms your hardware makes (if you are running the game on a PC). 

According to an official Bioware source, the greatest majority of cases with this symptom involve seriously low quality hardware, way below minimum. 

There are no clairvoyants in either place.  Therefore, when reporting a problem, here is the guide: 

Including adequate information in a (PC System) problem report, DA O:

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

Modifié par Gorath Alpha, 09 juin 2011 - 07:14 .


#17
GravyNavy

GravyNavy
  • Members
  • 1 messages
I had the same issue and then disabled the Steam in-game overlay (the shift+tab) screen and it started right up. For non-steam versions of the game I don't know.

#18
DocTerry

DocTerry
  • Members
  • 4 messages
I know this threat is a bit old, but I also was having trouble on my Alienware Netbook and the Steam version of Dragon Age Origins. Whether I clicked PLAY or CONFIGURE the game would crash. However, I experimented a little and maybe my workaround will work for you.

I had already installed, and played DAO (Steam) on my Asus notebook. So I copied the whole Bioware folder and copied it over the same folder on my Netbook. I guess that the configuration items had been set on the notebook, so the netbook bypassed that. Then I was able to change the Video settings to suit the netbook.

The folder (on both of my machines) was created by DAO in C:\\Users\\YourName\\Documents\\Bioware\\Dragon Age. Just copy the Dragon Age folder, and all its contents, over to your problem machine and hopeflly your problem is also solved.

I realize that this may not work for people without a working copy on at least one computer, but I couldn't find any sort of solution elsewhere, so hopefully it will help some people.

#19
thekarlm

thekarlm
  • Members
  • 1 messages
If you're running the steam version, disable the in-game overlay - that worked for me (crash 1/3 way through also until I disabled the in-game overlay ... how crap is that?)

#20
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
Windows XP Minimum Specifications
OS: Windows XP with SP3
CPU: Intel Core 2 Single (or equivalent) running at 1.6Ghz or greater
AMD 64 (or equivalent) running at 2.0Ghz or greater
RAM: 1 GB or more
DVD ROM (Physical copy)
20 GB HD space
Video: ATI Radeon X850 256MB or greater (this is clearly wrong)
NVIDIA GeForce "6600 GT" 128MB or greater (and this one is more wrong)

(Note: IMO, the practical choices for the two video cards above should be the Radeon X800 Pro, and the Geforce 6800 GS, at least, for small textures - it will take a Radeon X1650 XT (or X1800 GTO, same thing, almost) for medium or better textures)

INTEL'S GARBAGE (Graphics Chip) IS NOT SUPPORTED, and there is an interesting possibility that male party characters are easier to choose than female when using substandard video solutions, such as Intel's. 
 
This thread is in the wrong forum, since it's of a Tech type nature.

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

Modifié par Gorath Alpha, 09 juin 2011 - 07:19 .


#21
tuto1

tuto1
  • Members
  • 34 messages
you can try several things : 1. Run as administrator 2. Rewrite the game (recomended to c driwer ) 3. Update your os 4. Update drivers ( video card) 5. Try turn off antiwirus then install and lounch the game 6. Patch the game. 7. Turn off all runing programs and then try to run it 8. Try install new sound driwers (helped for me to fix total war games, but i dont recomend this)

#22
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
Someone in the correct (for a PC version of the game) Tech forum has been digging up old graves. Was that desecration a result of this off-topic continuation?

Here is it is: http://social.biowar...58/index/161545

#23
BeyondAbraxas

BeyondAbraxas
  • Members
  • 1 messages
Yeah, I've researched the crap out of this game - it didn't work for me several years ago, and doesn't work for me today. I thought with the steam sale going on, it might be fixed, but it still doesnt work.

my specs? 2x e5-xeon 2670 @ 3.1Ghz, 2x 580 GTXs - so specs aren't the problem.
Neither does the whole "run as admin" solution work. Nor does compatibility mode.
I've been trying to play this game since release, and its a dud for me.

Using steam on Win7 64 bit.
Bottom line, configuration wizard crashes. Run as admin and compatibility mode don't work.
Game: Unplayable.

<- Pissed.

Modifié par BeyondAbraxas, 24 décembre 2012 - 03:00 .


#24
Just-Me

Just-Me
  • Members
  • 576 messages
You are in the wrong place. Official Tech has ALWAYS been handled by the EA Help site, and the Social Site has recently been demoted. All of the former Self-help gamer to gamer tech discussions here that previously were handled in forums of their own were evicted. Those now belong at Answers.HQ.Com, not on this site.

#25
L33T BEANS

L33T BEANS
  • Members
  • 5 messages
Good game, I also have this problem. None of the above fixed it either.