*Cries* Crash As Balor Dies

I have search and not found an answer to this. I really hope that I am not the only one that has run into this and someone has an answer.

Anyway, I am using Livonya's Mod (1.5) and I have the Balor dead, or rather a single hitpoint of damage and he will die. Yay me! Except as soon as the damage registers the game crashes to desktop.

I have tried making the final blow with every weapon I have available as well as several spells so it doesn't seem to be caused by any particular item bug.

For reference I am getting the following error:

The intructions at "0x2112ddba" referenced memory at "0x9b68e40". The memory could not be "read".​

Anyone have any ideas?

I am looking right now for video card driver updates but I have the feeling that isn't the problem since it seems to be event driven rather than graphics driven.

More info: the Balor summoned another Balor and I killed that (took some serious damage when it died) but the game didn't crash then which, again, leads me to believe that it has to be the event causing the problem.

 

This is a known issue, though for some reason it has never happened to me. I get plenty of crashes during the fight, but none when the Balor dies. Then again, my Balors don't seem to explode either. So far there is no known solution.

All right, this is a call to all modders. What causes the Balor to explode? I have yet to figure it out. IIRC, someone once mentioned that the explosion was added by Liv. If we can remove it we can stop the CTD.

 

Is the explosion different from the one that I experienced when the first Balor died (the one that did the damage to my party, the one the Balor summoned)? Because that one didn't cause the CTD.

You probably expected this but the Video card driver update didn't help.


This is really frustrating. I really would like to finish this game. I want to run another party build after this but it is a little hard to get excited to do so if I am not going to be able to complete that one as well.

 

ShiningTed reported that as long as there are two Balor in combat, when the first one dies it won't cause CTD. People are just having to repeat the combat until it finally doesn't CTD.

 

Repeat the entire combat? I have a save just before he dies. DO I have to start the combat over or am I just going to be repeating that last hit until it doesn't CTD?

I guess that without a root cause it will be hard to say.

 

I think that I'll add my $0.02

As the balor was one of my test subjects for The Sword of Cahoem I killed him many times and I still haven't encountered this CTD you all speak of. I also don't have not much if any lag in the fire node either (crappy old PC)

 

OK, I'll give as much info as I can, maybe it will help figure out what is happening.

Things I have tried:

- Running the battle from beginning to end - CTD when Balor dies
- Saving incrementally up to Balor has a single hitpoint before dying - CTD when balor dies
- Taking the final hit with every weapon and spell that will actually do damage - CTD when balor dies
- uninstalling and reinstalling ToEE and all patches and mods - CTD when Balor dies
- Uninstalling, deleting all files but the save, reintstalling all patches and mods - CTD when Balor dies

I like this game anough that I am willing to play through again with a different party build and just take the battle with the Balor as the final scene but it would be a lot more satisfying to actually finish it for once (the first time through the game was ruined because I just installed all 3 Atari patches).

 

my 2 ¢

I have experienced the Balor crash. The save during combat is a bad idea. Delete that saved game; everything will be the same at the moment when it is ready to die, including what is causing the crash. Also, my suggestion for when it happens is to close the game so that ToEE is not running. Then, reboot your computer. Try it again after the reboot and do the entire fight.

 

It is my experience that ToEE and Norton's do not play well together.

 

This was a last resort. I had tried the fight so many times that I thought maybe I could isolate when the problem occurred.

That is actually interesting. I do have Norton and I am sure that I have run with it disabled but I am not certain that I have during this fight.

 

It didn't matter if I had it enabled or disabled. The only thing that worked was running msconfig and stopping Norton's from load at start up. But then I had no antivirus at all. I got rid of so many problems when I switched to AVG. Of course, Norton's doesn't go quietly when you try to uninstall it as well.