20 réponses à ce sujet

[Harime]

Hello,

I just purchased the game in its PC version yesterday, i installed it correctly and updated it to version 1.01

I suffer random crashes while playing, i've been playing for 5 or 6 hours and the game crashed like 4 times. I get no error message from the game, game freezes and in a few seconds i get a Windows message " Dragon Age Origins stopped working ".

I have no problems with other games, so i may not think about hardware problems.

My hardware is :

Intel Core i7 Xeon W3520
DFI Lanparty UT X58 T3eh8
ASUS Nvidia GTX295
6GB G.Skill Trident DDR3
Creative X-fi Platinum
WD Caviar Black 640GB x2 (RAID 0)

I'm running the game in Windows 7 Professional x64 with an original license. My graphic drivers are up to date and so is my DirectX.

Thanks in advance, looking forward to hearing from you soon.

Harime.

Modifié par Harime, 11 novembre 2009 - 01:04 .

[Boeresmurf]

where in the gameplay did it crash ?

i had 3 of the exact same crashes all in lothering after i defeated the 3 bandit groups and before i beat the darkspawn guarding the 2 dwarfs.... for rest i had no problems, did ya tried to Q save alot for half an hour and see if u still had problems in 1 other zone ?

[Harime]

Random places, last time in the town where you rescue Sten and the female rogue.



Another time i remember was while i was in the Wilds talking to Morrigan...

[gizzt]

Yea i had similar random crashes. I had to put the game on high settings, medium textures and 0xaa even tho my hardware played at max at an ok framerate. :/

Setting any of the options just 1 pip higher on any of those settings would cause it to crash.

Modifié par gizzt, 11 novembre 2009 - 01:32 .

[Harime]

I have an Intel Core i7 cpu and a GTX295 card to play the game at max. The 95% of the time i have 60 fps with maximun graphic settings, i don't think lowering the settings is the solution.

[gizzt]

Try lowering them anyway see if you get a crash. I can also run at 40fps with all options on with lots of things on screen on max, but it does crash after a while.

If it does nt crash, then you can put options back on to see what is causing it to crash.

Modifié par gizzt, 11 novembre 2009 - 01:43 .

[Shadianna]

try this...

http://social.biowar...58/index/139102

[gizzt]

Cool, i might give that a shot see if i can put graphics on higher again... thanks

[Harime]

Thanks a lot, i'll try this tonight when i go back home.



I'll update this with the details.

[Harime]

Hello everyone,



I updated the game to its version 1.01b, still crashing at random places in random moments...



I'm disappointed with this, i was hoping this crashes would have been fixed in this patch.



Is there any other solution to this?



Thanks.

[lolcat790]

I had similar issue--upping my chipset voltage seemed to fix it.

[lasy001]

Hi all !



Also has this strange crashes randomly and also black screen on some of the video sequences and when I go back to the latest save I can see the video when entering the same place.

i have updated to the latest patch without any result (does not state that it will fix but I gave it a try)

[Harime]

My hardware is absolutely stable. I have tested it through many tests for many months and i didn't have any problem. High demanding games like Crysis, Stalker Clear Sky and similar ones work perfectly from beginning to end.



The problem is in this game, not in my comp.

[Hrtlsmoe]

You are right.. they need to fix this... but we have'nt even gotten an update atleast saying they will adress any issues.. but anways i hear that this is what the company does.. even fom mass effect

[DDT55]

I started to have this problem after updating my video driver to 195.55 beta.
After reverting back to 191.07 WHQL + SLI profile update 3 (for SLI support in DA:O) crashes are gone.
You can get driver and profile from these links:
http://www.nvidia.co...aspx?lang=en-uk
http://www.nvidia.co...date_v3_uk.html

Modifié par DDT55, 23 novembre 2009 - 09:36 .

[Doofus42]

Has anyone looked in the Windows Application Event Log for an error message?



For a CTD (Crash to Desktop) you should see an entry something like this:

#####

Faulting application name: DAOrigins.exe, version: 1.1.9363.0, time stamp: 0x4ae9d52d

Faulting module name: FRAPS32.DLL, version: 3.0.0.10475, time stamp: 0x4af2418c

Exception code: 0xc0000005

Fault offset: 0x0001c6b4

Faulting process id: 0x13c4

Faulting application start time: 0x01ca6b94567b6e30

Faulting application path: D:\\Program Files (x86)\\Dragon Age\\bin_ship\\DAOrigins.exe

Faulting module path: D:\\Program Files (x86)\\Fraps\\FRAPS32.DLL

Report Id: 97485b80-d787-11de-be5a-00044b18f385

#####



This error report indicates that DAO and FRAPS were not getting along.



I have others that indicate the problem was in the Visual C++ RTL.



More information could be very helpful.....

[Harime]

I will test the SLI Update from Nvidia right away.

[badkenbad]

I started having this same problem around the time the last patch came out. I thought it was because I had got to Denerim and something was corrupted with my save, but I have since started a couple of new characters and am still having the problem in random locations. Sometimes in camp, sometimes in a town, sometimes in combat, sometimes out of combat. It doesn't seem to have anything to do with how long I've been playing, either.

I've tried several solutions listed here, including running with low graphics settings, but nothing seems to work.

My computer is a Core 2 Duo 6750 (2.67 GHz), 3 GB RAM, 8800 GT 512 MB on Vista Home Premium 32 bit. Nothing is overclocked, and all system software and drivers are up to date.

All of the crashes show version "1.1.9363.0" for DAOrigins.exe. Some say "faulting module unknown," which is odd, but most show DAOrigins.exe as the faulting module. The earliest such error was at 2009-11-13 16:00:37 and the game had not crashed on me at all prior to that point. I have not installed anything new on my machine since I bought DA Origins Digital Deluxe edition from Steam on release day.

Some Event Viewer crash logs (there are a lot more in my Event Viewer application log):

2009-11-22 22:16:59
Faulting application DAOrigins.exe, version 1.1.9363.0, time stamp 0x4ae9d4e2, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x000044f5, process id 0x484, application start time 0x01ca6bf612119730.

2009-11-22 15:23:27
Faulting application DAOrigins.exe, version 1.1.9363.0, time stamp 0x4ae9d4e2, faulting module DAOrigins.exe, version 1.1.9363.0, time stamp 0x4ae9d4e2, exception code 0xc0000005, fault offset 0x0006ee8e, process id 0x16d8, application start time 0x01ca6bbf0a731440.

2009-11-20 20:34:56
Faulting application DAOrigins.exe, version 1.1.9363.0, time stamp 0x4ae9d4e2, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x00000000, process id 0x132c, application start time 0x01ca6a5aad5489c0.

2009-11-20 20:26:55
Faulting application DAOrigins.exe, version 1.1.9363.0, time stamp 0x4ae9d4e2, faulting module DAOrigins.exe, version 1.1.9363.0, time stamp 0x4ae9d4e2, exception code 0xc0000005, fault offset 0x0006ef70, process id 0x17ec, application start time 0x01ca6a4c7d7ca560.

2009-11-20 18:45:24
Faulting application DAOrigins.exe, version 1.1.9363.0, time stamp 0x4ae9d4e2, faulting module DAOrigins.exe, version 1.1.9363.0, time stamp 0x4ae9d4e2, exception code 0xc0000005, fault offset 0x003f8d43, process id 0x131c, application start time 0x01ca6a47e21268c0.

Modifié par badkenbad, 23 novembre 2009 - 10:03 .

[Doofus42]

I looked up the 0xc0000005 exception code on the Microsoft support site and this is caused by an instruction trying to access memory outside of the DAO process memory space. Unfortunately without more debugging tools than the public has are needed to analyze this.



The Visual C++ libraries have caused me some problems in the past, so I would suggest making sure that only the latest version is installed. My Vista machine at one time had about 4 different versions installed. Things got better when I removed them all and just installed the July 2009 version.



You had several that said "faulting module unknown" which is a bit strange. Have you run a memory diagnostic lately? Normal PCs do not have any memory parity or ECC built in. So a bad memory cell could cause random problems.

[Harime]

Crashes don't stop with the SLI Update.

[badkenbad]

Okay, so after several days of playing the game, manually setting Processor Affinity to a single CPU in Windows Task Manager each time I play, I haven't had a single crash. Quite the difference from crashing several times per day. From what I've been able to gather googling around about this sort of problem, it's something that needs to be fixed in the application. I hope Bioware can track it down and patch it!

Modifié par badkenbad, 26 novembre 2009 - 07:46 .