This looks like a completely legitimate (as in, unrelated to Inner Space or ISBoxer) WoW crash. The stack in the current thread is 100% wow.exe, with no Inner Space stuff in it. That's usually (but not 100%) a good indicator that the problem code in question is entirely within WoW, and providing this crash log to the right WoW developer should result in a bug fix. Or at least a narrow area for them to look at.

I'll take a closer look shortly and see if I can come up with something that might help, but that's my initial impression.