ToEE encountered an error (?)

Not just you

Helcat, I just wanted to chime in and let you know that you are not the only one with this problem. Everything worked fine until I dropped in the Co8 patch and Liv's beta. Now I crash every few minutes.

However, my work machine runs the game and patches fine (although if I equip a chain and flail at same time the game chugs out to 1FPS), so the problem is clearly one with a conflict between your and my PC hardware and the fan patches.

I have tried multiple driver sets so the aforementioned memory angle may be the correct one. I am attempting to check this myself and will post if I get anywhere.

 

Thank you. I am currently working on it too, but do not have a printer right here, so I have to figure a way to get the instructions copied to disc or emailed to a friend.

 

I'll be damned.

I uninstalled the game and reinstalled it but did not run the patches. No problems (so far). At least as far as the game crashing goes. I got almost two hours of play in without any problems.

So... Now to narrow it down to which patch (I'm not entirely certain its the fan patch). But surley it's one of them...

 

Keep me informed on this one - I won't be able to help if it is software, but I'd be mighty interested in how it is triggering a memory error if that is what is causing the problem. You haven't changed anything since you initially ran into the problem, other than a fresh install?

BTW Glad you are able to play

edit: might be interesting to compare your and Swampcow's systems.

 

Sorry Zebedee, I spoke to soon. Although I had a couple hours of play earlier (I has started a new game after the reinstall) when I went back to play some more, low and behold after approximately 10 minutes the exe error occurred.

Hmmm... Why would it happen from a saved game but not from a new one?

Or was it just luck earlier?

I still haven't run a memory test. I don't know how to get my comp to boot from a CD. However, my friend who built it for me does. If he has the time, I'm sure he'll walk me through it. He has already told me that he doesn't really have any experiance running memory tests.

Of course I'll also give downloading the instructions from the site where I got the memory test from, but last time it created a wierd file my comp didn't know how to open (I just didn't know what program to use).

 

Another Victim

I too am having the same problem. The interesting thing is that it started after I installed XP SP2. Before that the game still CTDed ocassionally, but not with the "memory cannot be read" error. Before and after installing SP2 I was running with patches 1 and 2, and the Co8 fanfix. Half-Life 2 and Thief: Deadly Shadows, both much more memory intensive games, run just fine on my system. I am off to do a memory check now.

Edit: Memory check came back clean.

 

A Solution!!?

I tried so many things. I removed Norton Antivirus (the subscription was almost up and I wasn't going to renue anyway, plus AVG Free found 5 trojans that Norton's had missed for almost a year), updated my BIOS, updated my drivers, and shut down all other applications except for my firewall. I still had the same problem. Then I un-overclocked my FSB, and was able to play for hours with no error. I don't know why the 5% overclocking I was using was causing a problem with ToEE and not other much more memory intensive games like HL2 or Thief: Deadly Shadows, but now it seems to be working. Now I'm off to see if 2.5% will work.

 

me too

i am also having this problem, i believe it is a directx problem, this is similar to a problem people were having a couple years back. every game plays for about 10 minutes then crashs with the same error. only after i upgraded to directx 9c for city of heros did this start to happen. i have updated both video and audio drivers. it has been suggested in some tech forums that if you turn down your hardware accl. on your sound card that it may solve the problem.

 

Can I just clarify something - this error has a huge number of causes. So the same error message could be triggered by something totally different in each and every case. Check the Half-life link I posted above as it gives some of the most basic things to check. But this is a true PITA error simply because you can't just say "turn this off and it will fix it" - for some people it will, for others it won't.

Just a thought on overclocking teh hardware, don't If you need the speed so much, buy a new processor or gfx card. You'll end up having to do it anyway if you overclock too much or for too long.

 

Overclocking makes any memory problems worse. It's like having a tiny hole in a sweatshirt and then pulling it hard and fast. It gets bigger. Strange you haven't had it on HL2 though - there's a game where even my own PC has said "please no more" at times hehe

 

I don't overclock because I need the speed. I overclock because I can. Same reason why I build computers rather than by them. Call it a hobby. You're going to need to by a new cpu and gfx card eventually anyway. It's Moore's Law.

 

I don't think it is a memory problem. I'm running fine now at 2.5% overclocked. As I said before, it started when I installed SP2, and possibly upgraded directx as well. I was running 5% overclocked before that and had no problem.

As for HL2, I keep a close eye on temps and have great cooling. I'm not saying HL2 hasn't crashed on me occasionally, just not with that error. And I HAD to turn off all background programs for that one just to keep a decent frame rate.

 

The error is a memory error but the triggers can vary a lot. If you've found the fix for your machine, groovy, but it won't work for everyone sadly.

 

The error is a call to a memory location that cannot be read. It is possible that the error is in the call, not the memory location. It could be that some application is trying to read memory reserved for another application. I still believe that this is a software issue between DirectX 9c and ToEE or one of it's patches.