Error #132 (New to ISboxer 7 day trial)

Redacted

[bob]

Google indicates that error 132 is fairly normal even when not multiboxing, so you may need to try some of the standard steps to resolve it. The majority tend to focus on corruption of something, and most commonly the wtf. As these are copied for each character, then perhaps you have free space restrictions, or just a corrupted base wtf file?.

https://eu.battle.net/support/en/article/error-132
http://eu.battle.net/wow/en/forum/topic/7526882614
http://www.wowwiki.com/World_of_Warcraft_(WoW)_Error_132

or search for "wow error 132" on google for more potential answers.

Another possible reason is the other things hooking the game, like the Razer software, Logitech, or potentially others. A diagnostic may be helpful. http://isboxer.com/wiki/Diagnostics

Redacted

[bob]

The error is Access Violation. The exception is thrown because something is trying to access a section of memory it is not authorised to.

According to your crash dump the thread throwing the error is this one.

Code:

250.--- Thread ID: 37444 [Current Thread] ---
251.779C8DC9 0C4BF168 0001:00028DC9 C:\Windows\SysWOW64\ntdll.dll
252.779C8CD8 0C4BF190 0001:00028CD8 C:\Windows\SysWOW64\ntdll.dll
253.737547E0 0C4BF1AC 0001:000037E0 C:\Windows\system32\RASAPI32.dll
254.737557C7 0C4BF3D4 0001:000047C7 C:\Windows\system32\RASAPI32.dll
255.73754EB8 0C4BF690 0001:00003EB8 C:\Windows\system32\RASAPI32.dll
256.73754E48 0C4BF6B4 0001:00003E48 C:\Windows\system32\RASAPI32.dll
257.73755135 0C4BF6D4 0001:00004135 C:\Windows\system32\RASAPI32.dll
258.737550F3 0C4BF6F4 0001:000040F3 C:\Windows\system32\RASAPI32.dll
259.73755004 0C4BF744 0001:00004004 C:\Windows\system32\RASAPI32.dll
260.73754996 0C4BFBA8 0001:00003996 C:\Windows\system32\RASAPI32.dll
261.73755E11 0C4BFBDC 0001:00004E11 C:\Windows\system32\RASAPI32.dll
262.752C530A 0C4BFC08 0001:0002430A C:\Windows\syswow64\WININET.dll
263.752C5469 0C4BFC20 0001:00024469 C:\Windows\syswow64\WININET.dll
264.752C53B5 0C4BFC4C 0001:000243B5 C:\Windows\syswow64\WININET.dll
265.752C5361 0C4BFC68 0001:00024361 C:\Windows\syswow64\WININET.dll
266.752B376F 0C4BFC8C 0001:0001276F C:\Windows\syswow64\WININET.dll
267.752B3707 0C4BFCCC 0001:00012707 C:\Windows\syswow64\WININET.dll
268.752B4BE6 0C4BFCF4 0001:00013BE6 C:\Windows\syswow64\WININET.dll
269.752B819B 0C4BFD18 0001:0001719B C:\Windows\syswow64\WININET.dll
270.752B41B2 0C4BFD58 0001:000131B2 C:\Windows\syswow64\WININET.dll
271.752D6C9B 0C4BFDA4 0001:00035C9B C:\Windows\syswow64\WININET.dll
272.76CBB2B1 0C4BFDB4 0001:0001A2B1 C:\Windows\syswow64\SHLWAPI.dll
273.779F94D2 0C4BFE28 0001:000594D2 C:\Windows\SysWOW64\ntdll.dll
274.779E43E9 0C4BFF88 0001:000443E9 C:\Windows\SysWOW64\ntdll.dll
275.7680338A 0C4BFF94 0001:0000338A C:\Windows\syswow64\kernel32.dll
276.779C9EF2 0C4BFFD4 0001:00029EF2 C:\Windows\SysWOW64\ntdll.dll
277.779C9EC5 0C4BFFEC 0001:00029EC5 C:\Windows\SysWOW64\ntdll.dll


573.--- Thread ID: 37444 [Current Thread] ---
574.779C8DC9 ntdll.dll    RtlIntegerToUnicodeString+764 (0x00000000,0x00000000,0x03782178,0x00000000)


As this thread is calling a number of network related libraries, the issue may be somewhere in the network stack, although not guaranteed.
This has been seen several times recently and could be caused by any number of programs, for which a diagnostic could be helpful to determine, but the most common frequent occurrence of network issues is due to firewalls, Antivirus filter drivers, proxies, vpns. You could start looking here.

Another possibility is a "mod" in the executable that is generating a pointer to the part of the application that is performing the networking communications, and when running under Inner Space it is not isolating/calculating a pointer/value for the multiple instances correctly, resulting in an incorrect address which is attempting to access a memory location that is outside of the allocated Virtual Memory Address Space for that process.

This error was asked about recently in IRC, and Lax asked the person in question if they had the same issue with Retail WOW. Do you?

Redacted

[MiRai]

I cant figure out how to launch retail, when I go to export it keeps saying something about Ctrl + Alt + F12. But I disabled my anti-virus and turned off my firewall and I was able to get twice as many applications to open as I was before.

The easiest way you're going to fix that is by clearing your profile (File > Clear) and then recreating a Character Set. I'd suggest not changing a thing during the final step of the Wizard.

In addition to that, we need that diagnostic that bob asked for hours ago.

Redacted

[MiRai]

How do I run a diagnostic? It seems when I run Isboxer with the retail version of wow, I dont get any crashes.

The instructions don't tell you to make your game crash, they just tell you to run it outside of Inner Space and pick it from a list of running processes.

Redacted

[lax]

First thing to do is try shutting down other running programs that are affecting the game. You should find that by shutting down one of them that the problem goes away.

I would start with Razer In Game Engine, try shutting that down first and see if it makes a difference. If not, follow with other software that you can try without -- CCC, CCleaner64, Avast! (note that for a proper test to see if Avast! is the issue, you may need to uninstall it and reboot. It can of course be installed again after you rule it out as the cause of the problem)