Just to let everyone know, I think we have addressed this problem. Turns out that it was a fuck-up in IE7. Microsoft released an update, and caused IE7 to have this error when there was some really specific conditions met. It was all over the internet, so wasn't just a newschoolers thing.
We figured out what was causing it, and have fixed the problem!
Let us know if you see it again...