18 réponses à ce sujet

[shawnglory]

Yeap exactly as it says in the topic.
Comp specs are as follows:

CPU: Core 2 Quad 9550 @3.41 ghz
MOBO: ASUS P5KPL/1600
GPU: ASUS HD 4850
OS: VISTA ULTIMATE SP1 x32
RAM: 4 GHZ 667 (2 x 2GB)
PSU: COOLER MASTER eXtreme Power Plus 650W

After getting the same error over and over again I decided to install the game on another rig that is running the same OS as this rig. 

I'm quite sure that both my rigs are capable of running this game at all max considering that the second rig mentioned is running on an i7 975 and a 5870. Perhaps it is the OS or is this a common problem in the game it self? I've played MW 2 and the likes of it at all max and have not had this happen except on DAO.

Thanks for your time, appreciate it much ^^

[EricHVela]

I haven't seen this before, so I'll just grasp at straws.

Are you running with the BCDEdit switch to break the 3GB limit in 32-bit Vista? There are several things out there that hate that.

[shawnglory]

Nopes i'm still at the 3.5gb defaults on vista 32.



Decided to run tweaking progs after seeing the error appearing over and over again and to no avail >.<

[JironGhrad]

Did it run on the 2nd rig at all? What brand of memory are you using? Is it the same in both systems?

[shawnglory]

my second rig specs are



CPU: i7 975 @3.33

MOBO: ASUS Rampage 2 Extreme

GPU: ASUS HD 5870

OS: VISTA ULTIMATE SP1 x32

RAM: 6 GB 1600 (2 x 3GB) Kingston where as the first one was a corsair and kingston mix

PSU: Cosmic 1000W



both are running on different platforms with completely different setups



ddr 2 667 - ddr 3 1600

socket 775 - 1366

graphic card is a generation ahead



and yet the same problem exists on both rigs. I'm surprised at how well both rigs handle games with extremely detailed graphics and high cpu demand yet is having problem at running this game.



just wondering though how can a game that is such a hit amongst the critics and reviewers can have 200+ pages of technical support posts >..<

[Gorath Alpha]

Picture a neighborhood park back a few years ago, on a warm weekend, with a few score people minding their own business (fun, mostly, of course).  A couple of radical leftists arrive on the scene with handsfull of leaflets to pass out, and a sturdy apple crate. 

The taller, balding one of them places the crate on a rise in the ground to stand on, climbs up, and raises his voice to address anyone nearby with his earnest  cry:

"A lot of ignorant people are out there these days. The entire western education system is a shambles, and has been for years. The majority just don't READ any more, and ignore opportunities to end their ignorance. When as many copies of a game sell as DA: O has sold, the odds are that multiple thousands of the buyers are from among the most ignorant of all, and if one in ten of those manage to find their way here and get an account started, there are going to be hundreds of them asking the same twenty or thirty questions over and over and over.

"They won't read. We can answer their questions, but if it's written in small enough words that they will at least look at the answer, they are as like as not to get upset at being "talked down to", so answering them at all is a no-win situation.   We can post a half page of useful stickies, and they will ignore them all. 

"For instance, about 30 - 35 % of the questions in here have remained off topic ever since the game release, being about the DLC, which is problems with the web site rather than with the game, and the web site has its own forum. And those DLC questions are the self-same six or seven questions, endlessly."

The tirade ends abruptly.  No one was listening at all.  They leave the apple crate behind.

Gorath
-

Modifié par Gorath Alpha, 13 décembre 2009 - 03:31 .

[Gorath Alpha]

Not one single "Amen, brother!" Not even from Deacons' Row?

[JironGhrad]

Amen Brother! As to the OP's question, does it just say "could not read memory" or is there a fault location code of some kind?

[shawnglory]

Ah I was away for the weekend and I have to admit Gorath I am amazed at the truth in what you have said. Cheers.



Erm I'll get it to appear again and post it here in a while ^^ thank you jiron

[shawnglory]

Dragon Age: Origins: daorigins.exe - Application Error

The instruction at 0xe40c2200 referenced memory at 0xe04c2200. The memory could not be read.

Click on OK to terminate the program.

Also what I've realised is that whenever I plug both rigs on a CRT monitor the error occurs more often compared to HD capable monitors/lcd which either doesnt happen at all (Tested after the last post before my weekend getaway. It didn't crash for at least 4 hours where as on CRT it lasts anywhere between 1 minute - 20 minutes)



Don't ask me how i ended up with the idea of plugging it to a CRT monitor >.

Attempt 1, 2, 3,

The instruction at 0xe40c2200 referenced memory at 0xe04c2200. The memory could not be read.

Click on OK to terminate the program.

Attempt 4,

The instruction at 0x007c8b2e referenced memory at 0x0000000a. The memory could not be read.

Click on OK to terminate the program.

(Attempt 3&4 happened 2 minutes after the other at the mountain top after killing the dragon that carries oh so many equipments it couldnt probably wear)

Modifié par shawnglory, 14 décembre 2009 - 04:05 .

[shawnglory]

Attempt #5 - the pure fail attempt



decide to set priority and affinity through task manager



daorigins.exe - cpu 0,1 + real time priority

daorigins-updater - cpu 2,3 + high



result - distorted sound at times + a bsod about 15 minutes in.



hey look at the bright side it wasnt a memory could not be read error >.<

[JironGhrad]

I wonder if that's GPU memory failing...

[stubbieAussie]

It is not the GPU memory failing.......well at least I dont think it is.
It may not have anything at all to do with memory.

Give me a minute to try and help explain.
I get this exact error 50% of the time I exit Sacred 2. I have also had it happen twice in 80hours of playing DA:O.
I do not have it happen with any of my other games.
Searching on the net will show you that this "memory could not be read" error can be anything from a bad piece of RAM, to a program conflicting with another, to simply bad coding on the games part.
In essense it is a bugger to find the solution.

So my first suggestion is to run www.memtest.org/ overnight to elimate any RAM problem and turn off ALL other programs running in the background when you play DA:O.

I admit I did this myself and still Sacred 2 comes up with this error sometimes when I exit but I'm exiting the game so it doesnt bother me.

If after doing this you still get the errors then I can try to further help with some more suggestions.

[shawnglory]

i had to pull the line off earlier due to monsoon rain to avoid dragon-like-smoke coming out of my rig but after the bsod in attempt #5 there was no errors for a good 3-4 hours of straight gaming even with alt+tabbing out and running heavy load programs.



I doubt that it is related to the GPU as i have two systems on what could most accurately be described as a generation apart. c2q q9550 + ati hd 4850 | ci7 975 + ati hid 5870 and both had the exact same problems with almost similar timing between each occurring event.



For the q9550 rig i did plug out my ram did a little dusting off and pin cleaning and the problem did stop for a bit or more accurately extended the time i could stay in game.



What leaves most of us stumped would probably be how it sometimes lasts for hours and once through out the night as i left the game on with macros spamming every skill i have to force a heavy load until i woke up and the game was still running fine the next day.



Possibly suggestible that I may have a bad copy of the game ? considering that i used the same medium for installation for both rigs. Might torrent another copy but don't know how much difference that may pose as it could be a leaked or modified copy which wont really give me a mode of testing and I am sure that I am not planning to buy a second box just for diagnostics.



I've also tried program elimination prior to starting up DA:O and at time even with all programs except for major system monitoring which is definitely needed to keep a close eye on temperatures and yet the problem persist (note that the i7 rig doesn't have the monitoring pros. OC'ed everythign I could in the 9550 rig so yeah a smoking pile of technology isn't really what I am looking forward to)



Yeah I did get the failed to ready memory upon closing some other programs but it's been a while since that hapened.

[shawnglory]

Update: one simple solution that usually works just crossed my mind. gonna try to turn ati catalyst ai off and see how that works out.

man i sure hope we find a solution soon just incase anyone else is experiencing this. this is a **** of a problem to solve

Conclusion - FAIL!

Updated: apparently the game will run fine after a memory dump via BSOD probably due to garbage collector overflowing from massive memory leaks from this game which is correctable via memory dump which will (according to my friend who is a freelance programmer) clear up all memory traces and collected "garbage" from the leaks.

What numbs my mind is that the second BSOD suggested a RAM error ~PAGE FAULT IN NON PAGE ERROR~ but when I run intensive games like GTA IV (CPU and Memory dependent more than GPU)  it ran absolutely fine on both systems not to mention the likes of crysis and a fully infested sims 3 town with all at max including neighbourhood rendering (hey what better way to test your pc than downloading a bunch of random "simlings" and dump em all in a town and let the pc load em all up at the same time) as well as causing pure carnage in GTA IV which will trigger more events which in turn requires more processes from your pc.

Anyways, both tests listed up did not trigger any error. Infact it was running perfectly smooth. I decided to start up DA:O and no errors are to be found since 4-5 hours ago (after BSOD) left the game on, went out had a few drinks, the usual macro spamming to cause more load and as soon as i came back everything was running properly with a few hints of minor degradation from the said memory leaks all around the forums.

Modifié par shawnglory, 14 décembre 2009 - 05:49 .

[stubbieAussie]

shawnglory wrote...
What numbs my mind is that the second BSOD suggested a RAM error

Well if you do ever try and run memtest overnight like I suggested then that will confirm if it is a RAM error.

[shawnglory]

i did run a memtest yesterday =D

no errors found though disabled everything except for critical components and ran it twice.



oh well ^^ it either hates my rig settings or it just refuses to give me some smooth gametime ^^ doesn't really matter anymore though just raped the archdemon a day ago and i guess i'll wait for new ati drivers to be out and test it on my other rig to see compatibility upgrade for the 5870 from the 9.12 patch

[stubbieAussie]

Don't know if this is of any use to you but I am still using Catalyst 8.12 drivers.



They run all my games fine so I haven't had need to update them.

I firmly believe that the latest is not always the best.



Best of luck with fixing your problem.

[shawnglory]

true that older versions are stable but the later versions enhances the crossfire experience and my i7 rig needs the newer ones since it's using the new 5870.



only other thing i could think off right now is my overclock settings on my q9550 rig and have set everything back to default. guess what error not appearing anymore. hwoever whats weird is that my i7 at stock settings is still gettin the error.



oh well

thanks everyone ^^