Error #132 issue, unable to run wow through ISBoxer

I have been trying to run ISBoxer without much success. I keep getting the #132 fatal exception. And I've done a lot of troubleshooting to try and fix it.

I sometimes can get one of them to launch, with seemingly no rhyme or reason, but launching additional ones cause the error. Only once have I managed to get all 3 running at once, the only thing I changed that particular time was checking the "Use 64-bit Inner Space"... but only that once, never worked again.

Here is a copy of the error: http://imgur.com/a/WHGn2

Here is the ISBoxer diagnostics. http://pastebin.com/qzJPbznz

Wow error log file for last one (this particular one was after it was able to launch one but not the other two). http://pastebin.com/xwgQ344k

I regularly run 3 copies of wow at a time without issue. I can run wow outside of ISBoxer just fine. I did run a memtest to be sure, it came back fine.

I have tried doing it through ISBoxer launching just the game, by launching character set and by launching characters individually, to no avail. I've tried shutting down all unneeded apps/processes. I've tried launching without the battle.net launcher running and with. I've even tried running wow outside of ISBoxer and then launching without luck. I saw the NVDIA conflict with one of their processes, but my computer doesn't have that particular process installed/running. I reran the wizard to re-add characters and exported it, and that didn't fix it. I am running out of ideas and hope it is something obvious I missed

[jabberie]

I don't read the diagnostics but I'm sure someone will be along soon. These would be my 2 top picks to do anyways.
1- make sure you are using the proper wow install that works normally
2- windows 10, disable Game DVR

I am using Windows 8.1. Yes, the install directory appears to be correct, since I can sometimes (rarely) launch it.

[bob]

So, as there is nothing particularly obvious, the first port of call (as a TEST) will be to uninstall Spybot and Nortons and see if you have the same issue. Error #132 is fairly generic, but the reports indicate that an incorrect memory address is being read (at least a protected one), and it might be caused by these programs redirecting the I/O.

It (tentatively) seems that Spybot was the guilty party. I have successfully launched on the first try after Spybot removal and restart. Fingers crossed!

Well, after the one time successful launch, I am back to getting the error #132 when attempting to launch. Any other suggestions?

[MiRai]

Well, after the one time successful launch, I am back to getting the error #132 when attempting to launch. Any other suggestions?

If after you remove something from the mix, it's usually helpful to see an updated diagnostic.

New diagnostics:
http://pastebin.com/YxPs6D59
Wow Error report:
http://pastebin.com/aecXxk2C

I also disabled Norton to debug without any luck (it is back fully installed in this error report though, I don't like going too long without antivirus).

[MiRai]

You can also try shutting this down, as well:

Code:

53. RzOvlMon.exe - Process ID: 572 (C:\Program Files (x86)\Razer\Core\64bit\rzovlmon.exe) [Admin:NO] [x64] [1.0.1.66] [Razer, Inc.] [Monitor Razer Overlay Driver Service]