As I mentioned in a comment the last time you posted this, if you can crash IE remotely, you should contact Microsoft. This vulnerability can lead at least to a denial of service attack, and potentially a remote code execution or remote root (a bug that lets a web page crash a browser on demand has a high likelyhood of being exploitable to allow the attacker to run untrusted code on your machine). While people here may be able to help you work around your problem, Microsoft really ought to be informed so they can fix the underlying bug.
edit: Both for trying to work around your own problem, and for the sake of reporting the bug, you should try and reduce the problem to a minimal test case. Strip all of the content down to a minimal set of elements that is sufficient for reproducing the bug. Then do the same with the code. You should endeavor to get a test case that is just one or two images, and just the crossfades that trigger the problem, with nothing else present.
Then, yes, to report the bug, send them a link to your minimal test case (or include it inline in the bug report if you can). Mention that it is a remote denial of service vulnerability, and that you don't know if it could lead to remote code execution.
And as I mentioned, cutting this down to a minimal example should be able to help you workaround your bug. At the very least, you're more likely to get help here on a minimal code example than an entire site with lots of stuff going on that no one really feels like digging through.