WoW crashes when loading a team

That implies that there is something else going on which is chewing up your available RAM, or you do not have enough to support the number of clients you are running.

If you look at the Task Manager (right click your Taskbar, select Start Task Manager, Processes tab, sort by Memory (Private Working Set)), what is taking the most other than WOW. Also how much are the WOW instances taking?. You may need to select the "Show processes from all users" button.

May also be worth taking a look at the Performance tab and checking the values at the bottom, like Physical Memory -> Available, Kernel Memory -> Paged, System -> Commit (or a screen shot).

Also, that diagnostic?

Have you tried rebooting?

edit: and it may be worth unloading all WOW addons (other than ISBoxer of course) if it seems like WOW is the culprit.

According to task manager, I have 13GB of free Ram, only used 3GB. I open always 5 instances, a full team. BUT the funny thing is that it crashes on the first one (when it has more memory available), no matter which character, no matter which team.

My workaround now is to create a new team of 6 characters. On the first position I have a dummy character that I never load, and on the rest of positions my real team. Then via contextual menu (right clicking inner space icon) -> ISBOXER character set slots, I load mu real team one by one from 2 to 6. That way I don't have any issue. If was a wow problem, addon problem or memory problem, they would not load that way neither.

It is a really really weird problem, I have never faced anything like this with Isboxer. Especially since without install or change anything of my computer, the thing stopped working, I guess was around build 6030 of innerspace (not sure if that helps)

The good news is that with the workaround I can play, but I want to fix it, mostly QoL purposes.

[bob]

Yes, but if it is increasing the paging file size, or reporting that it is, then something is preventing the allocation being requested and the Windows VMM is resorting to paging to disk in order to try and free something up.

This may be some background process that is not releasing fast enough, or something that is deliberately hiding itself (some nefarious programs can), or Windows is just telling you lies.

While I sympathise with your QoL, you are the only person reporting this issue out of many WOW players, so it appear unique to your computer at this point, and not an issue in the general WOW multiboxing population, and thus not necessarily something that can be corrected by an update to ISBoxer/Innerspace.

Perhaps that diagnostic would prove useful...................

Yes, but if it is increasing the paging file size, or reporting that it is, then something is preventing the allocation being requested and the Windows VMM is resorting to paging to disk in order to try and free something up.

This may be some background process that is not releasing fast enough, or something that is deliberately hiding itself (some nefarious programs can), or Windows is just telling you lies.

While I sympathise with your QoL, you are the only person reporting this issue out of many WOW players, so it appear unique to your computer at this point, and not an issue in the general WOW multiboxing population, and thus not necessarily something that can be corrected by an update to ISBoxer/Innerspace.

Perhaps that diagnostic would prove useful...................

I totally agree, I have 2 more pc's not as powerful and they just work fine.

Diagnostics may help:

Code:

ISBoxer Diagnostics Report generated 10-Jan-15 7:20 PM by ISBoxer 41.11.1227.1

Running processes:
1. ActivateDesktop - Process ID: 6036
2. AdminService - Process ID: 1756
3. Ath_CoexAgent - Process ID: 2348 (C:\Program Files (x86)\Bluetooth Suite\Ath_CoexAgent.exe)
4. audiodg - Process ID: 4804
5. BDAppHost - Process ID: 4720 (C:\Program Files (x86)\Microsoft\BingDesktop\BDAppHost.exe)
6. BDExtHost - Process ID: 7464 (C:\Program Files (x86)\Microsoft\BingDesktop\BDExtHost.exe)
7. BDRuntimeHost - Process ID: 924 (C:\Program Files (x86)\Microsoft\BingDesktop\BDRuntimeHost.exe)
8. BDSurrogateHost - Process ID: 2652 (C:\Program Files (x86)\Microsoft\BingDesktop\BDSurrogateHost.exe)
9. BingApp - Process ID: 1816 (C:\Program Files (x86)\Microsoft\BingBar\7.3.117.0\BingApp.exe)
10. BingBar - Process ID: 1864 (C:\Program Files (x86)\Microsoft\BingBar\7.3.117.0\BingBar.exe)
11. BingDesktop - Process ID: 7980 (C:\Program Files (x86)\Microsoft\BingDesktop\BingDesktop.exe)
12. BingDesktopUpdater - Process ID: 1800 (C:\Program Files (x86)\Microsoft\BingDesktop\BingDesktopUpdater.exe)
13. bingsurrogate - Process ID: 2284 (C:\Program Files (x86)\Microsoft\BingBar\7.3.117.0\BingSurrogate.exe)
14. bingsurrogate - Process ID: 5032 (C:\Program Files (x86)\Microsoft\BingBar\7.3.117.0\BingSurrogate.exe)
15. bingsurrogate - Process ID: 7064 (C:\Program Files (x86)\Microsoft\BingBar\7.3.117.0\BingSurrogate.exe)
16. BitTorrent - Process ID: 6900 (C:\Users\Jaume\AppData\Roaming\BitTorrent\BitTorrent.exe)
17. brs - Process ID: 6852 (C:\Program Files (x86)\CyberLink\Shared files\brs.exe)
18. BtvStack - Process ID: 6004
19. ChargeService - Process ID: 2008 (C:\Program Files (x86)\MSI\Super-Charger\ChargeService.exe)
20. cm106eye - Process ID: 4396 (C:\WINDOWS\system\Cm106eye.exe)
21. conhost - Process ID: 3224
22. conhost - Process ID: 3548
23. conhost - Process ID: 7208
24. conhost - Process ID: 8784
25. conhost - Process ID: 9156
26. csisyncclient - Process ID: 1268 (C:\Program Files\Microsoft Office 15\Root\VFS\ProgramFilesCommonX86\Microsoft Shared\OFFICE15\CSISYNCCLIENT.EXE)
27. csrss - Process ID: 536
28. csrss - Process ID: 672
29. dasHost - Process ID: 1844
30. Dropbox - Process ID: 6836 (C:\Users\Jaume\AppData\Roaming\Dropbox\bin\Dropbox.exe)
31. dwm - Process ID: 384
32. explorer - Process ID: 3648
33. FlashUtil_ActiveX - Process ID: 6960
34. GfExperienceService - Process ID: 1136
35. Google+ Auto Backup - Process ID: 6724 (C:\Users\Jaume\AppData\Local\Programs\Google\Google+ Auto Backup\Google+ Auto Backup.exe)
36. HD-LogRotatorService - Process ID: 1824 (c:\Program Files (x86)\BlueStacks\HD-LogRotatorService.exe)
37. HeciServer - Process ID: 1680
38. hkcmd - Process ID: 3756
39. IAStorDataMgrSvc - Process ID: 6244 (C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe)
40. IAStorIcon - Process ID: 3180 (C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorIcon.exe)
41. ICCProxy - Process ID: 3444 (C:\Program Files (x86)\Intel\Intel(R) Integrated Clock Controller Service\ICCProxy.exe)
42. iexplore - Process ID: 3172 (C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE)
43. iexplore - Process ID: 4924
44. igfxpers - Process ID: 5424
45. igfxsrvc - Process ID: 4532
46. igfxtray - Process ID: 6132
47. InnerSpace - Process ID: 5452 (D:\Program Files (x86)\InnerSpace\InnerSpace.exe)
48. IntelMeFWService - Process ID: 3340 (C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\FWService\IntelMeFWService.exe)
49. ISBoxer Toolkit - Process ID: 7936 (D:\Program Files (x86)\InnerSpace\ISBoxer Toolkit.exe)
50. jusched - Process ID: 7444 (C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe)
51. KillerService - Process ID: 2140
52. KLM - Process ID: 7428 (C:\Program Files (x86)\MSI\KLM\KLM.exe)
53. livecomm - Process ID: 4048
54. LMS - Process ID: 2856 (C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\LMS\LMS.exe)
55. lsass - Process ID: 812
56. MSIService - Process ID: 1888 (C:\WINDOWS\SysWOW64\MSIService.exe)
57. MsMpEng - Process ID: 2324
58. NetworkManager - Process ID: 3580
59. NisSrv - Process ID: 3332
60. NvBackend - Process ID: 4652 (C:\Program Files (x86)\NVIDIA Corporation\Update Core\NvBackend.exe)
61. NvNetworkService - Process ID: 1940 (C:\Program Files (x86)\NVIDIA Corporation\NetService\NvNetworkService.exe)
62. nvspcaps64 - Process ID: 6696
63. nvstreamsvc - Process ID: 2084
64. nvstreamsvc - Process ID: 3216
65. nvstreamsvc - Process ID: 3536
66. nvtray - Process ID: 1276
67. nvvsvc - Process ID: 1020
68. nvvsvc - Process ID: 416
69. nvxdsync - Process ID: 372
70. OBS - Process ID: 1376 (C:\Program Files (x86)\OBS\OBS.exe)
71. officeclicktorun - Process ID: 2016
72. ONENOTEM - Process ID: 8144 (C:\Program Files\Microsoft Office 15\root\office15\ONENOTEM.EXE)
73. PDVD10Serv - Process ID: 6216 (C:\Program Files (x86)\CyberLink\PowerDVD10\PDVD10Serv.exe)
74. Plex Media Server - Process ID: 3680 (C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe)
75. PlexDlnaServer - Process ID: 8068 (C:\Program Files (x86)\Plex\Plex Media Server\PlexDlnaServer.exe)
76. PlexScriptHost - Process ID: 7188 (C:\Program Files (x86)\Plex\Plex Media Server\PlexScriptHost.exe)
77. PlexScriptHost - Process ID: 8760 (C:\Program Files (x86)\Plex\Plex Media Server\PlexScriptHost.exe)
78. PlexScriptHost - Process ID: 9148 (C:\Program Files (x86)\Plex\Plex Media Server\PlexScriptHost.exe)
79. PluginService - Process ID: 1388 (C:\ProgramData\IePluginServices\PluginService.exe)
80. PnkBstrA - Process ID: 2124 (C:\WINDOWS\system32\PnkBstrA.exe)
81. RAVCpl64 - Process ID: 5880
82. ReflectService - Process ID: 2156
83. rundll32 - Process ID: 5348 (C:\Windows\SysWOW64\rundll32.exe)
84. rundll32 - Process ID: 5420
85. RuntimeBroker - Process ID: 5096
86. RzKLService - Process ID: 2176 (C:\Program Files (x86)\Razer\Razer Game Booster\RzKLService.exe)
87. RzSynapse - Process ID: 6672 (C:\Program Files (x86)\Razer\Synapse\RzSynapse.exe)
88. SBCinema - Process ID: 7684 (C:\Program Files (x86)\Creative\Sound Blaster Cinema\Sound Blaster Cinema\SBCinema.exe)
89. SeaPort - Process ID: 9864 (C:\Program Files (x86)\Microsoft\BingBar\7.3.117.0\SeaPort.exe)
90. SearchIndexer - Process ID: 4444
91. services - Process ID: 804
92. SettingSyncHost - Process ID: 4832
93. SkyDrive - Process ID: 4644
94. SkypeC2CAutoUpdateSvc - Process ID: 1916 (C:\Program Files (x86)\Skype\Toolbars\AutoUpdate\SkypeC2CAutoUpdateSvc.exe)
95. SkypeC2CPNRSvc - Process ID: 1964 (C:\Program Files (x86)\Skype\Toolbars\PNRSvc\SkypeC2CPNRSvc.exe)
96. smss - Process ID: 360
97. SP - Process ID: 7024 (C:\Users\Jaume\AppData\Roaming\Search Protection\SP.exe)
98. spoolsv - Process ID: 1576
99. Steam - Process ID: 6392 (D:\Program Files (x86)\Steam\Steam.exe)
100. SteamService - Process ID: 7700 (C:\Program Files (x86)\Common Files\Steam\SteamService.exe)
101. steamwebhelper - Process ID: 7240 (D:\Program Files (x86)\Steam\bin\steamwebhelper.exe)
102. Super-Charger - Process ID: 7896 (C:\Program Files (x86)\MSI\Super-Charger\Super-Charger.exe)
103. svchost - Process ID: 1060
104. svchost - Process ID: 1112
105. svchost - Process ID: 1316
106. svchost - Process ID: 1644
107. svchost - Process ID: 2220
108. svchost - Process ID: 2236
109. svchost - Process ID: 3048
110. svchost - Process ID: 424
111. svchost - Process ID: 4292
112. svchost - Process ID: 4988
113. svchost - Process ID: 716
114. svchost - Process ID: 892
115. svchost - Process ID: 932
116. System - Process ID: 4
117. taskhost - Process ID: 8776
118. taskhostex - Process ID: 3588
119. TeamViewer - Process ID: 3596 (C:\Program Files (x86)\TeamViewer\Version9\TeamViewer.exe)
120. TeamViewer_Service - Process ID: 2288 (C:\Program Files (x86)\TeamViewer\Version9\TeamViewer_Service.exe)
121. tv_w32 - Process ID: 3028 (C:\Program Files (x86)\TeamViewer\Version9\tv_w32.exe)
122. tv_x64 - Process ID: 3380
123. Viber - Process ID: 4580 (C:\Users\Jaume\AppData\Local\Viber\Viber.exe)
124. wininit - Process ID: 652
125. winlogon - Process ID: 776
126. WmiPrvSE - Process ID: 2644
127. WmiPrvSE - Process ID: 7496
128. wmpnetwk - Process ID: 3868
129. Wow-64 - Process ID: 1684
130. XtuService - Process ID: 3584 (C:\Program Files (x86)\Intel\Extreme Tuning Utility\XtuService.exe)


Modules loaded by Wow-64 - Process ID: 1684:


Application Compatibility flags under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers:
Application Compatibility flags under HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers:


[bob]

So stuff that looks like you should shut down/uninstall with reboot.
This is either a process I don't recognise or the application name of something that could potentially conflict with the launching process. In no specific order.

1. ActivateDesktop - Process ID: 6036
2. AdminService - Process ID: 1756
Bingdesktop
BingBar
BitTorrent
20. cm106eye - Process ID: 4396 (C:\WINDOWS\system\Cm106eye.exe)
conhost <-- whatever is triggering multiple conhosts. You normally only have one under a standard install
Google+ Auto Backup
53. livecomm - Process ID: 4048
74. Plex Media Server - Process ID: 3680 (C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe)
82. ReflectService - Process ID: 2156
86. RzKLService - Process ID: 2176 (C:\Program Files (x86)\Razer\Razer Game Booster\RzKLService.exe)
89. SeaPort - Process ID: 9864 (C:\Program Files (x86)\Microsoft\BingBar\7.3.117.0\SeaPort.exe)
97. SP - Process ID: 7024 (C:\Users\Jaume\AppData\Roaming\Search Protection\SP.exe)
99. Steam - Process ID: 6392 (D:\Program Files (x86)\Steam\Steam.exe)
100. SteamService - Process ID: 7700 (C:\Program Files (x86)\Common Files\Steam\SteamService.exe)
101. steamwebhelper - Process ID: 7240 (D:\Program Files (x86)\Steam\bin\steamwebhelper.exe)
102. Super-Charger - Process ID: 7896 (C:\Program Files (x86)\MSI\Super-Charger\Super-Charger.exe)
123. Viber - Process ID: 4580 (C:\Users\Jaume\AppData\Local\Viber\Viber.exe)
130. XtuService - Process ID: 3584 (C:\Program Files (x86)\Intel\Extreme Tuning Utility\XtuService.exe)



Now, I'm thinking that this is starting to look like a laptop, but cannot be absolutely sure about that. If it is, then it is possible that the game is trying to launch under the Intel Graphics GPU, so disabling that in the BIOS (if you can) would be helpful. If it is a desktop then ensure that the monitor is plugged into the graphics card, and not the mainboard.

It would help if the diagnostic was from the 32bit WOW client (you can select this in the options of the WOW launcher), as then it would show whether anything was directly hooking the WOW instance, and that would be a big clue as to a culprit, but in the meantime it is about paring down the list of running processes as much as you can until it works normally.

Nothing really jumps out at me, except maybe the multiple search services (avoid these if possible) and overclocking utilities (MSI/Intel). Followed by the Razer Game Booster. These are all red flags as potential compatibility problems.

Thank you for the tips, I will try to remove some but all that software was already there before the problems.

Yes it is a laptop, I am checking that it runs on the NVidia 780m, some of the programs already came with the laptop.

Tried to uninstall some and reboot with any success.

I cannot remove all them cause it is software I need, but I am pretty sure that the problem are not them since that software was installed long before the problems appeared.

If I open a normal wow instance (not from isboxer) everything works fine, no memory issues.
If I open from any team the first slot instance it crashes, different teams have different characters also, so can not be the character.
If I open from any team the slots from the 2nd till the last works flawlessly.

So my conclusion is that when loading the first instance isboxer is doing something, I don't know what is it, in normal circumstances should work (on other computers I don't have the issue) but for whatever reason not on this pc.
From a memory point of view does not make any sense that the first instances crashes but then I can log 4 more as long I don't log the first one.

Guess I would have to pass on this one... and wait till I reinstall my computer from scratch again.