Page 2 of 4

Re: Wow Will NOT launch

PostPosted: Wed Jan 10, 2018 10:50 pm
by casibal

Re: Wow Will NOT launch

PostPosted: Thu Jan 11, 2018 1:43 pm
by MiRai
Okay, fantastic.

There is still quite a bit to shut down, including the MSI stuff that bob suggested on the first page of this thread, so I'd start with that. In addition, GameScannerService is a Razer product that can potentially interfere, as well.

Code:
9. ChargeService.exe - Process ID: 1792 (C:\Program Files (x86)\MSI\Super Charger\ChargeService.exe) [Admin:NO] [x86] [1.3.0.19] [MSI] [Super Charger Service]

15. downloader2.exe - Process ID: 7064 (C:\Program Files (x86)\Real\RealDownloader\downloader2.exe) [Admin:NO] [x86] [18.1.9.106] [RealDownloader]

18. EyeRest.exe - Process ID: 7340 (C:\Program Files (x86)\MSI\MSI OC Kit\ActiveX_Service\EyeRest.exe) [Admin:NO] [x86] [1.0.1.08] [Micro-Star INT'L CO., LTD.] [EyeRest]
19. GameScannerService.exe - Process ID: 2276 (C:\Program Files (x86)\Razer\Razer Services\GSS\GameScannerService.exe) [Admin:NO] [x86] [1.0.6.2843] [GameScannerService]
20. GamingApp_Service.exe - Process ID: 1748 (C:\Program Files (x86)\MSI\Gaming APP\GamingApp_Service.exe) [Admin:NO] [x64] [6.2.0.24] [Micro-Star Int'l Co., Ltd.] [GamingApp_Service]
21. GamingHotkey.exe - Process ID: 452 (C:\Program Files (x86)\MSI\Gaming APP\GamingHotkey.exe) [Admin:YES] [x86] [1.0.0.19] [Micro-Star INT'L CO., LTD.] [Gaming Hotkey]
22. GamingHotkey_Service.exe - Process ID: 1840 (C:\Program Files (x86)\MSI\Gaming APP\GamingHotkey_Service.exe) [Admin:NO] [x86] [1.0.0.7] [Micro-Star INT'L CO., LTD.] [Gaming Hotkey Service]

33. KillerService.exe - Process ID: 2232 (C:\Program Files\Qualcomm Atheros\Network Manager\KillerService.exe) [Admin:NO] [x64] [1.1.42.1045] [Qualcomm Atheros] [Qualcomm Atheros Killer Network Service]

37. MSI_ActiveX_Service.exe - Process ID: 1940 (C:\Program Files (x86)\MSI\MSI OC Kit\ActiveX_Service\MSI_ActiveX_Service.exe) [Admin:NO] [x86] [1.0.1.21] [Micro-Star INT'L CO., LTD.] [MSI_ActiveX_Service]
38. MSI_LiveUpdate_Service.exe - Process ID: 1592 (C:\Program Files (x86)\MSI\Live Update\MSI_LiveUpdate_Service.exe) [Admin:NO] [x86] [1.0.0.49] [Micro-Star INT'L CO., LTD.] [MSI Live Update Service]
39. MSI_Trigger_Service.exe - Process ID: 1872 (C:\Program Files (x86)\MSI\MSITrigger\MSI_Trigger_Service.exe) [Admin:NO] [x86] [1.0.009.0] [MICRO-STAR INTERNATIONAL CO., LTD.] [MSI_Trigger_Service]

41. MsiGamingOSD_x64.exe - Process ID: 4972 (C:\Program Files (x86)\MSI\Gaming APP\OSD\x64\MsiGamingOSD_x64.exe) [Admin:YES] [x64] [1.0.0.05] [Micro-Star INT'L CO., LTD.] [MsiGamingOSD_x64]
42. MsiGamingOSD_x86.exe - Process ID: 4724 (C:\Program Files (x86)\MSI\Gaming APP\OSD\x86\MsiGamingOSD_x86.exe) [Admin:YES] [x86] [1.0.0.05] [Micro-Star INT'L CO., LTD.] [MsiGamingOSD_x86]
43. MSIRegisterService.exe - Process ID: 1920 (C:\MSI\MSIRegister\MSIRegisterService.exe) [Admin:NO] [x86] [1.0.0.6] [Micro-Star INT'L CO., LTD.] [MSI Register Service]

55. realdownloader264.exe - Process ID: 7820 (C:\Program Files (x86)\Real\RealDownloader\RealDownloader264.exe) [Admin:NO] [x64] [18.1.9.106] [RealNetworks, Inc.] [Tools for RealDownloader]
56. RealPlayerUpdateSvc.exe - Process ID: 2492 (C:\Program Files (x86)\Real\UpdateService\RealPlayerUpdateSvc.exe) [Admin:NO] [x86] [18.1.9.106] [RealNetworks, Inc.] [RealPlayer]
57. realsched.exe - Process ID: 7628 (C:\Program Files (x86)\Real\RealPlayer\Update\realsched.exe) [Admin:NO] [x86] [18.1.9.106] [RealNetworks, Inc.] [RealNetworks Scheduler]
58. rpdsvc.exe - Process ID: 2548 (C:\Program Files (x86)\Real\RealPlayer\RPDS\Bin\rpdsvc.exe) [Admin:NO] [x86] [18.1.9.106] [RealNetworks, Inc.] [RealTimes Desktop Service]
59. rpsystray.exe - Process ID: 5044 (C:\Program Files (x86)\Real\RealPlayer\RPDS\Bin\rpsystray.exe) [Admin:NO] [x86] [18.1.9.106] [RealNetworks, Inc.] [RealPlayer with RealTimes]

67. Snagit32.exe - Process ID: 8000 (C:\Program Files (x86)\TechSmith\Snagit 13\Snagit32.exe) [Admin:NO] [x86] [13.1.4.8008] [TechSmith Corporation] [Snagit]
68. SnagitEditor.exe - Process ID: 8368 (C:\Program Files (x86)\TechSmith\Snagit 13\snagiteditor.exe) [Admin:NO] [x86] [13.1.4.8008] [TechSmith Corporation] [Snagit Editor]
69. SnagPriv.exe - Process ID: 1424 (C:\Program Files (x86)\TechSmith\Snagit 13\SnagPriv.exe) [Admin:NO] [x86] [13.1.4.8008] [TechSmith Corporation] [Snagit RPC Helper]

72. Super Charger.exe - Process ID: 6844 (C:\Program Files (x86)\MSI\Super Charger\Super Charger.exe) [Admin:NO] [x86] [1.3.0.19] [MSI] [Super Charger]
73. SuperRAIDSvc.exe - Process ID: 2656 (C:\MSI\Smart Utilities\SuperRAIDSvc.exe) [Admin:NO] [x86] [2.0.0.11] [Micro-Star INT'L CO., LTD.] [SuperRAIDSvc]

89. TriggerModeMonitor.exe - Process ID: 7348 (C:\Program Files (x86)\MSI\MSI OC Kit\ActiveX_Service\TriggerModeMonitor.exe) [Admin:NO] [x64] [1.0.1.09] [Micro-Star INT'L CO., LTD.] [TriggerModeMonitor]
90. UploaderService.exe - Process ID: 2732 (C:\Program Files (x86)\Common Files\TechSmith Shared\Uploader\UploaderService.exe) [Admin:NO] [x86] [5.0.6.303] [TechSmith Corporation] [TechSmith Uploader Service]
91. VideoCardMonitorII.exe - Process ID: 7332 (C:\Program Files (x86)\MSI\MSI OC Kit\ActiveX_Service\VideoCardMonitorII.exe) [Admin:NO] [x86] [1.0.1.06] [Micro-Star INT'L CO., LTD.] [VideoCardMonitor]

Re: Wow Will NOT launch

PostPosted: Fri Jan 12, 2018 11:42 pm
by casibal

Re: Wow Will NOT launch

PostPosted: Sat Jan 13, 2018 12:22 pm
by MiRai
There's still some stuff running...

Code:
41. KillerService.exe - Process ID: 420 (C:\Program Files\Qualcomm Atheros\Network Manager\KillerService.exe) [Admin:NO] [x64] [1.1.42.1045] [Qualcomm Atheros] [Qualcomm Atheros Killer Network Service]

60. RzStats.Manager.exe - Process ID: 8308 (C:\ProgramData\Razer\Synapse\RzStats\RzStats.Manager.exe) [Admin:NO] [x86] [1.2.16.0] [RzStats.Manager]

83. UploaderService.exe - Process ID: 3204 (C:\Program Files (x86)\Common Files\TechSmith Shared\Uploader\UploaderService.exe) [Admin:NO] [x86] [5.0.6.303] [TechSmith Corporation] [TechSmith Uploader Service]
84. VideoCardMonitorII.exe - Process ID: 5836 (C:\Program Files (x86)\MSI\MSI OC Kit\ActiveX_Service\VideoCardMonitorII.exe) [Admin:NO] [x86] [1.0.1.06] [Micro-Star INT'L CO., LTD.] [VideoCardMonitor]


...but if it still doesn't work after that, then:

1) If you have GeForce Experience installed, disable nVidia Share.
2) Try the development build of Inner Space (right click Inner Space and select Patcher, tick "Download development (test) patches" and then close and restart Inner Space to let it patch up)
3) You can try using DirectX 9 instead of DirectX 11 (how to adjust which profile is used)
4) You can try using the 32-bit client instead of the 64-bit client (how to adjust which profile is used | how to allow Inner Space to launch 32-bit games)
5) If the game is frozen and sitting in the Task Manager, then you can get a Trace Diagnostic on it (using the 32-bit client) and send it to Lax (lax [at] lavishsoft.com) so that he can look at it.

Re: Wow Will NOT launch

PostPosted: Sun Jan 14, 2018 1:01 pm
by casibal
With all processes and services stopped
https://pastebin.com/yMErYQnP

If you have GeForce Experience installed, disable nVidia Share.
I don't have it.

After dev patch
Tried and did not work.

Profile changed to
Launcher used - exported to Innerspace after each - Did not work
64bit directx9 - exported to Innerspace after each - DId not work
32bit directx9 - exported to Innerspace after each - DId not work

My game lauches just fine as I stated in my original post. what does not work is the launching of the clients via Multibox software.

I also tried lauching just the characters - nothing. I just sits there. As I said my game and each of the clients (i.e. my wow accounts) will star no problem manually (i.e. not using Innerspace/Isboxer)

Re: Wow Will NOT launch

PostPosted: Mon Jan 15, 2018 3:28 pm
by MiRai
Then Lax will need to look at a trace diagnostic:
MiRai wrote:5) If the game is frozen and sitting in the Task Manager, then you can get a Trace Diagnostic on it (using the 32-bit client) and send it to Lax (lax [at] lavishsoft.com) so that he can look at it.

Re: Wow Will NOT launch

PostPosted: Mon Jan 15, 2018 8:07 pm
by casibal
I don't know what you mean by game is frozen. The Wow Game runs, Isboxer does not launch it. I'll run the trace

Re: Wow Will NOT launch

PostPosted: Mon Jan 15, 2018 8:25 pm
by bob
He means, when you run the game from InnerSpace/ISBoxer, and it loads into the background, get a trace diagnostic on the background instance of the game after you have attempted to load from InnerSpace/ISBoxer and it has not appeared on the screen.

You are correct in the fact it has not actually hung. It is waiting on a lock to be released. If it had actually hung, Windows would pop a message about an application has stopped working. We are trying to find the thing causing the lock. We make you go through all the other stuff to make sure it is not another application causing the problem, because 95% of the time, it is.

Re: Wow Will NOT launch

PostPosted: Wed Jan 17, 2018 9:19 pm
by casibal
I don't have the 32bit client of wow.

I thought it was the .exe file in the World of Warcraft folder wow.exe as there is one that says wow-64 however both launch the 64bit client. per the ISBoxer diag processes.

Also this may shed some light on the issue.

I was going to uninstall and when I went to the downloader, I noticed the default location of the install is on C:\... but my Wow client is installed on the D drive. Is that an issue?

Let me know what you want done for the 64 bit issue.

Re: Wow Will NOT launch

PostPosted: Thu Jan 18, 2018 6:32 am
by bob
You do have a 32bit client (wow.exe), and if it detects you have a 64 bit CPU, then it will load up the 64 bit client (wow-64.exe) anyway, unless you supply parameters forcing 32bit. However my understanding is Blizzard are dropping support for the 32bit client, so it becomes a bit moot.

Unfortunately, the Trace diagnostics in the ISBoxer Toolkit wont take a 64bit dump (it will say failed), so you need to work around that by downloading procdump from Microsoft. https://docs.microsoft.com/en-us/sysint ... s/procdump

Extract that to a folder you can get to (like C:\procdump)
Open an admin command prompt.
Change directory to the folder you put ProcDump in.
Run "procdump wow-64.exe" (w/o quotes) when you have a hung wow-64.exe process. It will create a file in the folder. Email that dmp file to lax@lavishsoft.com, please let him know why he's getting it, e.g. reference this thread.