innerspace problems

[hykun]

SO here is something strange
i installed everything on a second computer clean install everything, load everything up make my team upload to innerspace it recieves it .

i wanna start up my team on wow nothing , then i thought to myself oh im using the 32 bit i have to change to 32 in configuration so i rightclick innerspace configuration > innerspace uplink starts then nothing it freezes (doesnt react) trying to close the window give report that innerspace.exe doesnt react anymore and closes fully down ditto patcher


Did i miss anything on changes? been boxing for over a year now never had any problems with it untill now

[bob]

Seen this with some computers that have certain other products, like some antivirus, or ASUS Sonic Sound Suite....

[hykun]

Seen this with some computers that have certain other products, like some antivirus, or ASUS Sonic Sound Suite....

I was thinking the samen thing thought it was avast that was on that system but even with avast turned of it Still doesnt work

[bob]

Can you get a diagnostic for crashes. Feel free to get it on the InnerSpace.exe process.

[hykun]

Can you get a diagnostic for crashes. Feel free to get it on the InnerSpace.exe process.

everytime i use diagnostic it just shows up what im running

http://pastie.org/10751445
http://pastie.org/10751455

[bob]

That is what it does. It's nice you truncated half the info, except for the fact that we look for two things. 1. Running processes that might be interfering (no we don't have a consolidated list because it can be different for everyone), and 2. whether anything is hooking InnerSpace (or your game). I can't see 1 in your paste, so you are on your own on that one.

From what you have provided, I can only suggest you rollback your graphics driver to version 359 and see if that helps. If you are also running shadowplay, disable it, or uninstall it. It might make a difference.

[hykun]

That is what it does. It's nice you truncated half the info, except for the fact that we look for two things. 1. Running processes that might be interfering (no we don't have a consolidated list because it can be different for everyone), and 2. whether anything is hooking InnerSpace (or your game). I can't see 1 in your paste, so you are on your own on that one.

From what you have provided, I can only suggest you rollback your graphics driver to version 359 and see if that helps. If you are also running shadowplay, disable it, or uninstall it. It might make a difference.

this is full one sorry http://pastie.org/10751474

[MiRai]

I would suggest shutting down the following:

Code:

18. GameScannerService.exe - Process ID: 2340 (C:\Program Files (x86)\Razer\Razer Services\GSS\GameScannerService.exe) [Admin:NO] [x86] [1.0.6.2673] [GameScannerService]
35. RazerIngameEngine.exe - Process ID: 6040 (C:\Program Files (x86)\Razer\InGameEngine\32bit\RazerIngameEngine.exe) [Admin:NO] [x86] [1.0.12.8578] [Razer, Inc.] [RazerIngameEngine]
37. rzcefrenderprocess.exe - Process ID: 5212 (C:\Users\Robby\AppData\Local\razer\InGameEngine\cache\RzStats.Manager\RzCefRenderProcess.exe) [Admin:NO] [x86] [1.0.12.8578] [Razer, Inc.] [Razer Chromium Render Process]
38. rzcefrenderprocess.exe - Process ID: 6672 (C:\Users\Robby\AppData\Local\razer\InGameEngine\cache\RzStats.Manager\RzCefRenderProcess.exe) [Admin:NO] [x86] [1.0.12.8578] [Razer, Inc.] [Razer Chromium Render Process]
39. RzStats.Manager.exe - Process ID: 5800 (C:\ProgramData\Razer\Synapse\RzStats\RzStats.Manager.exe) [Admin:NO] [x86] [1.0.1.1] [RzStats.Manager]
72. xwidget.exe - Process ID: 1408 (C:\Program Files (x86)\XWidget\xwidget.exe) [Admin:NO] [x86] [1.9.3.1022] [xwidget.com] [Widget Engine by xwidget.com]

It also looks like you have some WoW processes that are hanging and will need to be stopped before trying to re-launch anything for testing. There has also been a report with Razer Synapse causing issues on Windows 10, so you may want to temporarily shut down that, as well.

Code:

40. RzSynapse.exe - Process ID: 4852 (C:\Program Files (x86)\Razer\Synapse\RzSynapse.exe) [Admin:NO] [x86] [1.18.21.28549] [Razer Inc.] [Razer Synapse]

[hykun]

I would suggest shutting down the following:

Code:

18. GameScannerService.exe - Process ID: 2340 (C:\Program Files (x86)\Razer\Razer Services\GSS\GameScannerService.exe) [Admin:NO] [x86] [1.0.6.2673] [GameScannerService]
35. RazerIngameEngine.exe - Process ID: 6040 (C:\Program Files (x86)\Razer\InGameEngine\32bit\RazerIngameEngine.exe) [Admin:NO] [x86] [1.0.12.8578] [Razer, Inc.] [RazerIngameEngine]
37. rzcefrenderprocess.exe - Process ID: 5212 (C:\Users\Robby\AppData\Local\razer\InGameEngine\cache\RzStats.Manager\RzCefRenderProcess.exe) [Admin:NO] [x86] [1.0.12.8578] [Razer, Inc.] [Razer Chromium Render Process]
38. rzcefrenderprocess.exe - Process ID: 6672 (C:\Users\Robby\AppData\Local\razer\InGameEngine\cache\RzStats.Manager\RzCefRenderProcess.exe) [Admin:NO] [x86] [1.0.12.8578] [Razer, Inc.] [Razer Chromium Render Process]
39. RzStats.Manager.exe - Process ID: 5800 (C:\ProgramData\Razer\Synapse\RzStats\RzStats.Manager.exe) [Admin:NO] [x86] [1.0.1.1] [RzStats.Manager]
72. xwidget.exe - Process ID: 1408 (C:\Program Files (x86)\XWidget\xwidget.exe) [Admin:NO] [x86] [1.9.3.1022] [xwidget.com] [Widget Engine by xwidget.com]

It also looks like you have some WoW processes that are hanging and will need to be stopped before trying to re-launch anything for testing. There has also been a report with Razer Synapse causing issues on Windows 10, so you may want to temporarily shut down that, as well.

Code:

40. RzSynapse.exe - Process ID: 4852 (C:\Program Files (x86)\Razer\Synapse\RzSynapse.exe) [Admin:NO] [x86] [1.18.21.28549] [Razer Inc.] [Razer Synapse]

same thing just nothing happens wont load up clients or even let me enter innerspace configuration /patcher or console its weird never had that problem before

[MiRai]

same thing just nothing happens wont load up clients or even let me enter innerspace configuration /patcher or console its weird never had that problem before

At this point we usually ask for another diagnostic to ensure things still aren't loading, but I'll also point out that you haven't tried rolling your driver back to 359 as bob suggested prior to anything I posted (if you did, it's not reflected in your diagnostic).