No lax reason I think it might be innerspace to clarify not isboxer. I use one folder on my second pc to launch 4 instances of the game. When i use keyclone to launch those game instances it works fine. I have never gotten a #132 memory access violation. I am using 8 gigs of ocz reaper in a fairly new machine under a year old which I put together in April of '09. When I run my team with innerspace it will load the one copy of wow on my main machine then load the other 4 copies on my slave computer but once they are all loaded every instance closes even on my main computer but I only get the #132 memory access violations on my slave computer that tried to run the 4 instances of wow not on my main computer. The reason I think its innerspace is because it is shutting down the one instance of wow on my main computer also. As far as corrupted files go I don't think its that because keyclone will launch 4 instances on the computer fine and I never have a problem. If the game does crash from a fatal error during game play, which is not very often, only one instance of the game will close on the computer running my 4 slave copies not all of them. I'd really like to get innerspace working right using two computers because I want to use the mouse broadcasting feature which keyclone doesnt have. Its driving me crazy that it won't work!
It would help to see your configuration, then. (This post http://isboxer.com/forum/viewtopic.php?f=18&t=13 explains how to do this, and note that your account names are censored)

If you made a Mapped Key that recurses in every window, I could see this happening. I can't really imagine what else you could have configured through ISBoxer to make all of your WoW windows close/crash at once. 2 people talked to me yesterday in the ISBoxer chat room who both managed to create a recursive Mapped Key that would crash the game when they hit it. I may need to make ISBoxer detect recursive Mapped Keys.

In plain English, in order to produce a crash like this, they had to create a Mapped Key that had a Do Mapped Key Action which ended up doing the same Mapped Key (this is the definition of recursion). It might be a Do Mapped Key Action set to do itself, or set to do a different Mapped Key that, in turn, does the original Mapped Key with a Do Mapped Key Action. This creates an infinite loop, crashing the game. (Note that no delays are possible, so it is not possible to use this "loop" functionality for anything but crashing the game)

There is no way, with the default configuration and no changes, for this crash to happen.