Aller au contenu

Photo

Dragon Age Unofficial Troubleshooting FAQ


334 réponses à ce sujet

#51
Frightened

Frightened
  • Members
  • 8 messages
That would take some time... Playing through the origin story then the fist battle...

I tried deleting some toolset related stuff and I'll try one more time.

#52
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
Alrighty, Frightened... fortunately for the future they understand why the game is being corrupted by the toolset and the fix is in the pipe. Unfortunately, it's not here yet and it might not fix your save (if it's corrupted; I sure hope I'm wrong about how stuff is saved in the game)

#53
Dateranoth

Dateranoth
  • Members
  • 434 messages
Phenom fix for problems ranging from long load times to poor performance. Try only if you've tried everything else first.

All information courtesy of Nujabes via this post: http://social.biowar...58/index/156838

Following this link from the post listed above you can find the full information of what this does:

http://www.hardwarec...our-phenom.html

To sum up the problem with the Phenoms. Vista SP1 enabled a bandaide patch to fix RARE crashing on certain early phenoms. The fix disables that bandaide patch. When the bandaide is enabled the phenoms see a performance decrease of up to 30% . So this program simply disables that bandaide fix.

All I've done is combined the two needed programs into one and summed up the instructions here:

Step 1:

I've combined the needed files from the phenom fix here:

Files lost in crash.

It's a compressed executable rar file. Just extract them to a folder on your computer somewhere. Everything needed is in there. Once extracted simply open the folder and run this file: TLB_Disable.exe with administrative privaledges. If it works it should say

Status: Phenom TLB patch disabled. Phenom at full speed.

Now try to play the game and if it helps continue to step two:

Step Two:

This is not necessary if you are willing to manually run the TLB_Disable.exe everytime you reboot.

If the fix did work you are going to want to set it up to do it automatically when the computer starts as it's only permanent if you change it in your bios. As I don't know if each particular bios has it or not its easier to just change it on startup.

Go back to this page:

http://www.hardwarec...our-phenom.html

Scroll to the bottom of the first post and follow the instructions about Setup Program AutoRun at Startup. I would recommend moving the folder with the needed files to a permanent location first.

You should actually see a performance increase across the board. ( in other words better performance in DAO as well as most other games and CPU intensive apps )

Modifié par Dateranoth, 29 août 2010 - 09:48 .


#54
Frightened

Frightened
  • Members
  • 8 messages
I Sure hope so too, luckily for me I started saving on different slots as soon as I noticed the corruption so I won't have to start from nothing.

EDIT: JironGhrad this should confirm the fear that the bad things are saved. I loaded an older savegame and the party camp worked perfectly. Now I can start playing again... and redo hours of work. Stupid damn toolset!

Modifié par Frightened, 16 novembre 2009 - 02:34 .


#55
Hrtlsmoe

Hrtlsmoe
  • Members
  • 71 messages
thx JironGhrad you've been doing alot on the forums helping us.. hope they pay you man :)

#56
JironGhrad

JironGhrad
  • Members
  • 1 657 messages

Hrtlsmoe wrote...

thx JironGhrad you've been doing alot on the forums helping us.. hope they pay you man :)


Hah, but then I'd have to give up being the "Most Organiziferous One" of the "DA: O Unpaid Tech Support" team... it'd probably make my wife happy though if I "did" get paid

#57
JironGhrad

JironGhrad
  • Members
  • 1 657 messages

Frightened wrote...

I Sure hope so too, luckily for me I started saving on different slots as soon as I noticed the corruption so I won't have to start from nothing.

EDIT: JironGhrad this should confirm the fear that the bad things are saved. I loaded an older savegame and the party camp worked perfectly. Now I can start playing again... and redo hours of work. Stupid damn toolset!


Good to know. I'll make a note for the next time I edit the main post (such a pain having to remove extra \\\\\\ every time)

#58
Selvec_Darkon

Selvec_Darkon
  • Members
  • 722 messages
Bad things are saved even in game, without the toolset. For example, I have an issue with the game causing my characters armor apperance to permently get stuck on him during cutscenes, I believe this started before a certain event prior to my last save. Now the issue is constantly stuck.



Funny thing, I'm noticing more bugs as I progress into the game. This suggests the infamous "EA Rush" was at work.

#59
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
what's especially odd (in reference to your point Selvec) is that the game was "other than the DLC and toolset" ready for release back in March or April. And (aside from the usual slew of "my drivers are broken" and such hardware issues) the only real issues that have arisen from the game are toolset or DLC related or resulted from one or both of those affecting some other part of the game (such as saving and then corrupting the saved game in question).

Modifié par JironGhrad, 16 novembre 2009 - 05:23 .


#60
Selvec_Darkon

Selvec_Darkon
  • Members
  • 722 messages
Possiably EA forced Bioware to work on the Xbox360 and PS3 versions, while keeping the PC stuff in storage. I'm unsure what EA's policies are on such things. I imagine when a company says a games complete, EA takes it and keeps it in storage, possibly going through some more play tests, but likely not letting the company fix anything else for fear of more delays.

#61
Lord_Dark82

Lord_Dark82
  • Members
  • 1 messages
/bump and Bump

#62
Allan Schumacher

Allan Schumacher
  • BioWare Employees
  • 7 640 messages
Thanks to everyone for taking the time to compile this. It's appreciated.

#63
memyselfeandi

memyselfeandi
  • Members
  • 3 messages
Is there a clock for time if day in this game? If so, where is it?

#64
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
There does not appear to be a game clock, but the single player game advances (the enemy horde for example) based on event triggers to give the feel of the passage of time.

#65
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
There's a new patch out (1.01b) and the FAQ has been updated to note that people with Windows 7 NEED to install the PhysX file from NVidia as the on-disc version doesn't have the Win 7 files included.

#66
Quaxo

Quaxo
  • Members
  • 164 messages
"This applies especially to AMD processors but also affects some Intel Core 2 Duo and Core 2 quads!
For dual core set to CPU 1 only, for quad core set to CPU 2 and 3, for i7s set to 4, 5, 6, and 7."

It applies to just about every processor. There have also been reports of that issue from people with PentiumD and Pentium4 processors.

#67
JironGhrad

JironGhrad
  • Members
  • 1 657 messages

Quaxo wrote...

"This applies especially to AMD processors but also affects some Intel Core 2 Duo and Core 2 quads!
For dual core set to CPU 1 only, for quad core set to CPU 2 and 3, for i7s set to 4, 5, 6, and 7."

It applies to just about every processor. There have also been reports of that issue from people with PentiumD and Pentium4 processors.


Pentium D's are an abomination that should never have occurred.  The processor-side thread management is so bad that they actually perform worse than the single core unit they were built from.  Both Pentium D and P4 processors fail to meet the minimum requirements laid out by the game's manufacturer's, and while they may work fine for some (including me) it's not the indication of overall processor readiness to run the game. It may well affect all varieties of processors but I've been compiling a list of CPU's that are verifiably corrected by CPU affinity and I'm reluctant to make the claim that it will fix any CPU (as there may be one or more other reasons it's having the described problem as well)

#68
jimmyhff

jimmyhff
  • Members
  • 18 messages
Hello All!



Awesome game, but...

I am crashing to desktop every 10-15 minutes of play. Tried the patches, updated all of my PC drivers, adjusted settings from super low-end to super high-end and everything in-between.

Crashes happen 95% of the time when a cut-scene or dialogue is about to start. Coincidence?



I have a P4 2.8 with 1GB of RAM, an Nvidia GeForce 7800GS, SB Audigy 2 platinum, windowsXP.



Any ideas out there?!



You guys rock.

#69
JironGhrad

JironGhrad
  • Members
  • 1 657 messages

jimmyhff wrote...

Hello All!

Awesome game, but...
I am crashing to desktop every 10-15 minutes of play. Tried the patches, updated all of my PC drivers, adjusted settings from super low-end to super high-end and everything in-between.
Crashes happen 95% of the time when a cut-scene or dialogue is about to start. Coincidence?

I have a P4 2.8 with 1GB of RAM, an Nvidia GeForce 7800GS, SB Audigy 2 platinum, windowsXP.

Any ideas out there?!

You guys rock.


I see 3 things... all related to minimum specs.  Your processor, doesn't meet them.  1Gb of RAM while it clearly will "run" the game is really not adequate .  The 7800 series is at least a gaming series card but the GeForce 7 series is really not much of a card today.  We might benefit from seeing your dxdiag file. Are you running AVG 9.0?

#70
KorrickAsh

KorrickAsh
  • Members
  • 10 messages
If I may, I was having horrible crashing issues (CTD with DA.exe errors) and a few BSOD with this game and none of the previously mentioned fixes did me 1 bit of good.



I'm not sure if it's the memory leak that caused the problems, but I went into my BIOS and upped the 3 main memory timings by 1. My TL, tRCD, and tRP. Played the game 2 straight nights, for 3-4 hours with 0 problems. Also seems to have fixed a few stuttering/sound issues as well. Still have to restart the game every couple hours because the mem leak can lead to an overall performance drop. But it might be something to try for those having CTD issues.



System

Win7 64

i7@4Ghz

6Gigs Mushkin@1600 7-8-7 (new timings, was 6-7-6)

GTX280 SLI

OCZ Vertex SSDs

#71
JironGhrad

JironGhrad
  • Members
  • 1 657 messages

KorrickAsh wrote...

If I may, I was having horrible crashing issues (CTD with DA.exe errors) and a few BSOD with this game and none of the previously mentioned fixes did me 1 bit of good.

I'm not sure if it's the memory leak that caused the problems, but I went into my BIOS and upped the 3 main memory timings by 1. My TL, tRCD, and tRP. Played the game 2 straight nights, for 3-4 hours with 0 problems. Also seems to have fixed a few stuttering/sound issues as well. Still have to restart the game every couple hours because the mem leak can lead to an overall performance drop. But it might be something to try for those having CTD issues.

System
Win7 64
i7@4Ghz
6Gigs Mushkin@1600 7-8-7 (new timings, was 6-7-6)
GTX280 SLI
OCZ Vertex SSDs


A memory leak is a situation where memory is allocated (either by an application like a game or the OS) to the program and then left unused.  Because the memory is going unused the program (or OS) keeps adding additional RAM in an effort compensate until the RAM is used up, the page file may overflow and the system crashes. A memory leak is not something that can be fixed by tweaking hardware on any machine, nor can it be avoided by any user.  If a program has a true memory leak it will affect all users who operate the program and I can say with utmost confidence (after a stress test the other night, my game had been running continuously for over 60 hours and I didn't see a load time over 45 seconds) that the game may have issues with how it handles processor interaction but the slow downs aren't actually a true memory leak. For those who are still reading and are interested.  I'm running a Pentium 4 3.2Ghz Hyper-threaded Single Core Processor, Over-clocked to 4.9Ghz (and technically this processor doesn't meet the minimum requirements to run the game), with 2Gb of RAM, a 512mb Radeon X1650 Series AGP graphics card (also reputed to be near the bottom of the pile) on Windows XP Pro SP3 (32-bit).  If anyone should be loading slow and lagging while playing, it's me; but I'm not.

The point I'm trying to make (and people should be aware of it) is that it may not just be something they patch and it will go away.  They "fixed" the problem in Neverwinter Nights... by adding a CPU affinity toggle to .ini file.  Incidentally, people screamed that Neverwinter Nights had a memory leak too, but 7 years later there are computers that explode when playing it (a friend of mine had that problem but he gave up after 30 minutes of troubleshooting so I never got a chance to solve that one, and this was on a brand new system just 18 months or so ago).

#72
kalgorath

kalgorath
  • Members
  • 10 messages
Hello, just thought I'd add another fix I've stumbled upon accidentally. Apparently this game does not like Soundblaster X-Fi cards. I've removed the card and am using onboard sound at the moment, and I haven't had a crash after 7 hours play. My drivers were up to date. My Soundblaster card was the Soundblaster X-Fi Titanium. Hope this helps some people.

#73
Quaxo

Quaxo
  • Members
  • 164 messages

kalgorath wrote...

Hello, just thought I'd add another fix I've stumbled upon accidentally. Apparently this game does not like Soundblaster X-Fi cards. I've removed the card and am using onboard sound at the moment, and I haven't had a crash after 7 hours play. My drivers were up to date. My Soundblaster card was the Soundblaster X-Fi Titanium. Hope this helps some people.


I've had no problems with my X-Fi Extreme. Saying the game doesn't like X-Fi cards is just a poor assumption. There probably is some underlying problem you haven't found yet, but I wouldn't say it's X-Fi cards in general. I'm currently using version 5.10.0.209 and everything works great.

#74
ArminW68

ArminW68
  • Members
  • 46 messages
Now, this is one tip that everyone with some knowledge about PCs will say does not make sense, but I just have to add it. It completely solved my troubles, and those of 2 other people I know.

We all had the much reported freezes, hiccups and dialogue delays in various parts of the game. My own game would freeze for minutes at some points, then resume, would crash after minutes of being idle or continuously hiccup with smaller interruption during some areas (not everywhere, just in certain spots). None of the tips here worked.

The one thing we all had in common is, that our PCs all were built "by the book" (2 of them in the same store in fact, just about a year apart): Windows (2xVista, 1x7) on it's own, smaller partition, the rest of the HD in one or 2 larger partitions for games and applications. We all had DAO installed on another partition of the same physical drive as the OS.

Uninstalling it from my D: drive and reinstalling it on C: removed my problem completely. Have been playing for over 50 hours since then, no more freezes, no more hiccups, not a single crash.
Same for the 2 other guys. Removing the game from the partition and installing under the default path (C:\\\\programfilesX86 or whatever) solved the issues.

I have had similar issues with some other games before, that simply refuse to work properly on a drive partition that is on the same physical drive as the OS. Especially ones with Securom it seems, btw.

So, I really don't know if it makes sense, but it worked for me and at least 2 other people, and it can't hurt to try...

P.S.: I'm only a silly biologist with limited computer knowledge, but 2 things I noticed: the problem seemed to become worse after installing any DLC and it also was worst for the one with the largest amount of RAM (we all had 4 gig and more).
Secondly, my crash logs, if any, had lots of "IDEport: idle" messages among the usual tech gibberish. So, yould the problem be that some games, DOA among them, have a problem with the way they try to load data into memory? Some data (save games and settings mainly) in Vista always HAS to be on C: under the silly /user/my documents folder, and IIRC the DLC files are also located there? So might the trouble be a port conflict when the game tries to access 2 logical drive simultaneosly, that are actually the same physical drive?

Really, just a blind guesswork, the thing that counts is that I can play, managed to finish this incredibly brilliant game and have now started my second playthrough (again, already 12 freeze-and-crash-free hours of pure joy :o

Modifié par ArminW68, 17 novembre 2009 - 12:56 .


#75
kalgorath

kalgorath
  • Members
  • 10 messages

Quaxo wrote...

kalgorath wrote...

Hello, just thought I'd add another fix I've stumbled upon accidentally. Apparently this game does not like Soundblaster X-Fi cards. I've removed the card and am using onboard sound at the moment, and I haven't had a crash after 7 hours play. My drivers were up to date. My Soundblaster card was the Soundblaster X-Fi Titanium. Hope this helps some people.


I've had no problems with my X-Fi Extreme. Saying the game doesn't like X-Fi cards is just a poor assumption. There probably is some underlying problem you haven't found yet, but I wouldn't say it's X-Fi cards in general. I'm currently using version 5.10.0.209 and everything works great.


Well good for you. What is true for me, is that once I removed the X-Fi Titanium card, the game has not crashed in about 12 hours play. Doubt if there is any other problem as I have not encountered any kind of problem with other games or applications. Just putting it out there for people to try out.