Error #132 (New to ISboxer 7 day trial)

Redacted

Redacted

[bob]

Seen it; there are still several things running in your paste that you could shut down that may or may not help.

Code:

4. CCC.exe - Process ID: 4916 (C:\Program Files (x86)\AMD\ATI.ACE\Core-Static\CCC.exe) [Admin:YES] [x64] [4.5.0.0] [ATI Technologies Inc.] [Catalyst Control Center: Host application]
10. FastBootService.exe - Process ID: 1860 (C:\Program Files (x86)\MSI\Fast Boot\FastBootService.exe) [Admin:YES] [x86] [1.0.0.3] [MSI] [FastBootService]
11. GameScannerService.exe - Process ID: 2256 (C:\Program Files (x86)\Razer\Razer Services\GSS\GameScannerService.exe) [Admin:YES] [x86] [1.0.6.2588] [GameScannerService]
18. KillerService.exe - Process ID: 2136 (C:\Program Files\Qualcomm Atheros\Network Manager\KillerService.exe) [Admin:YES] [x64] [1.1.49.44] [Qualcomm Atheros] [Qualcomm Atheros Killer Network Service]
27. RaRegistry.exe - Process ID: 2172 (C:\Program Files (x86)\NETGEAR\WNDA4100\Service\RaRegistry.exe) [Admin:YES] [x86] [1, 0, 0, 26] [Ralink Technology, Corp.] [RalinkRegistryWriter]
28. RaRegistry64.exe - Process ID: 2232 (C:\Program Files (x86)\NETGEAR\WNDA4100\Service\RaRegistry64.exe) [Admin:YES] [x64] [1, 0, 0, 26] [Ralink Technology, Corp.] [RalinkRegistryWriter]
29. remoting_host.exe - Process ID: 1816 (C:\Program Files (x86)\Google\Chrome Remote Desktop\40.0.2214.44\remoting_host.exe) [Admin:YES] [x86] [40.0.2214.44] [Google Inc.] [Host Process]
30. remoting_host.exe - Process ID: 2000 (C:\Program Files (x86)\Google\Chrome Remote Desktop\40.0.2214.44\remoting_host.exe) [Admin:YES] [x86] [40.0.2214.44] [Google Inc.] [Host Process]
38. SpotifyWebHelper.exe - Process ID: 2612 (C:\Users\Matt\AppData\Roaming\Spotify\SpotifyWebHelper.exe) [Admin:YES] [x86] [1.0.2.6] [Spotify Ltd] [SpotifyWebHelper]
39. StikyNot.exe - Process ID: 2724 (C:\Windows\System32\StikyNot.exe) [Admin:YES] [x64]
61. WLIDSVC.EXE - Process ID: 2984 (c:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) [Admin:YES] [x64] [6.500.3165.0] [Microsoft Corporation] [Microsoft® Windows Live ID Service]
62. WLIDSVCM.EXE - Process ID: 3348 (c:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSvcM.exe) [Admin:YES] [x64] [6.500.3165.0] [Microsoft Corporation] [Microsoft® Windows Live ID Service Monitor]
67. WNDA4100.EXE - Process ID: 4244 (C:\Program Files (x86)\NETGEAR\WNDA4100\WNDA4100.EXE) [Admin:YES] [x86] [1.2.0.10] [NETGEAR] [WNDA4100 Genie MFC Application]
71. XtuService.exe - Process ID: 3004 (C:\Program Files (x86)\Intel\Extreme Tuning Utility\XtuService.exe) [Admin:YES] [x86] [4.4.0.103] [Intel(R) Corporation] [XtuService]


It seems when I run Isboxer with the retail version of wow, I dont get any crashes.

If you are running the retail version and it works correctly, then perhaps the issue is because you are using an older, potentially modified, version of the WOW executable that does not behave in the same way as the current supported version of WOW? Have you tried the support options for your game?


I should bring your attention to this http://www.isboxer.com/wiki/FAQ#Will_th ... _server.3F, as it would appear to be relevant.

Redacted

[bob]

It is something on your computer unfortunately, whether a driver, a missing update, corruption or other. Your paste still shows things you could shut down, or even uninstall if shutting down is not possible.

I've downloaded and tried out the same install you are using. When using the supplied launcher, it throws an error under Inner Space, but not the error you are seeing, but the executable still loads, just not within Inner Space control so multiboxing with it is out of the question. If I point directly at the WOW.exe that was part of the install it loads up correctly and can be controlled via Inner Space, although I don't get the choice of server, so that may be something that needs to be set elsewhere, but it works.

Redacted

[bob]

The only options you have left as far as I can tell are:

Uninstall those things that you can't shut down, unless they are absolutely essential to the running of your PC (at which point you be screwed), e.g.

Code:

17. FastBootService.exe - Process ID: 1480 (C:\Program Files (x86)\MSI\Fast Boot\FastBootService.exe) [Admin:YES] [x86] [1.0.0.3] [MSI] [FastBootService]
18. GameScannerService.exe - Process ID: 2380 (C:\Program Files (x86)\Razer\Razer Services\GSS\GameScannerService.exe) [Admin:YES] [x86] [1.0.6.2588] [GameScannerService]
24. KillerService.exe - Process ID: 1148 (C:\Program Files\Qualcomm Atheros\Network Manager\KillerService.exe) [Admin:YES] [x64] [1.1.42.1045] [Qualcomm Atheros] [Qualcomm Atheros Killer Network Service]
28. PnkBstrA.exe - Process ID: 1520 (C:\Windows\system32\PnkBstrA.exe) [Admin:YES] [x86]
29. RaRegistry.exe - Process ID: 2068 (C:\Program Files (x86)\NETGEAR\WNDA4100\Service\RaRegistry.exe) [Admin:YES] [x86] [1, 0, 0, 26] [Ralink Technology, Corp.] [RalinkRegistryWriter]
30. RaRegistry64.exe - Process ID: 2352 (C:\Program Files (x86)\NETGEAR\WNDA4100\Service\RaRegistry64.exe) [Admin:YES] [x64] [1, 0, 0, 26] [Ralink Technology, Corp.] [RalinkRegistryWriter]
31. remoting_host.exe - Process ID: 1276 (C:\Program Files (x86)\Google\Chrome Remote Desktop\40.0.2214.44\remoting_host.exe) [Admin:YES] [x86] [40.0.2214.44] [Google Inc.] [Host Process]
32. remoting_host.exe - Process ID: 1476 (C:\Program Files (x86)\Google\Chrome Remote Desktop\40.0.2214.44\remoting_host.exe) [Admin:YES] [x86] [40.0.2214.44] [Google Inc.] [Host Process]
61. WLIDSVC.EXE - Process ID: 2804 (c:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVC.EXE) [Admin:YES] [x64] [6.500.3165.0] [Microsoft Corporation] [Microsoft® Windows Live ID Service]
62. WLIDSVCM.EXE - Process ID: 2928 (c:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSvcM.exe) [Admin:YES] [x64] [6.500.3165.0] [Microsoft Corporation] [Microsoft® Windows Live ID Service Monitor]
69. XtuService.exe - Process ID: 4724 (C:\Program Files (x86)\Intel\Extreme Tuning Utility\XtuService.exe) [Admin:YES] [x86] [4.4.0.103] [Intel(R) Corporation] [XtuService]


Or format, and clean install Windows, the drivers for your motherboard and graphics (only the drivers not all the extra rubbish they flog with it), do all the Windows updates (yep all 200 odd, and the 5 or 6 cycles it takes). Try again. If that doesn't work, I could only guess that it is something to do with your router/switch/nic (I say this because there have been a couple of instances where someones switch caused them all sorts of grief).


As for support, the options are these forums, the wiki, or the IRC channel. AFAIK, there is no more than that offered. At the moment, I'm not sure what further could be offered anyway without driving over to your house to give your computer a good kicking and then commiserate over some buds and nuts.

[bob]

This post http://www.wowhead.com/forums&topic=209 ... -exception also has some suggestions that haven't come up previously (well none that you've indicated you have tried)

It also indicates that the Error 132 comes up during game play and not when you try and launch. No idea "when" it happens for you, but I just assumed originally it was during the loading.

That said, you could try forcing DX9 (using parameter -d3d9, or setting it in the wtf file) as it seems the most common fix, or you could continue the search through the other options, or google, or a clean install, etc.

Redacted

[bob]

Can you patch up Windows to SP1 and all outstanding updates (the security and important ones, except the language packs). This may take several iterations.
Can you use a wired connection rather than wireless?
Can you use the retail version of WOW (6.1.2) and on blizzard servers?

Can you get the crash report too?. The diagnostics are useful to see what is running on your PC and hooking the game. Also, the crash report may indicate that a memory dump has occurred and the location. You should find that if you can.