Page 1 of 1

ISBoxer crashing on account login

PostPosted: Fri Jun 29, 2018 4:19 pm
by sleepdeprived01
When I first started using ISBoxer I had zero issues, but now for some reason every time I start my character set and try to login to my WoW account it crashes one of the characters.

This is the top part of the crash message:

Software: Inner Space Kernel 1.16 Build 6282 (Thu Jun 28 16:14:55 2018)
Current time: Fri Jun 29 21:10:45 2018
Crash: 0x00007FF6E9A901D0: Exception 0xc0000005 reading from address 0x0000000000000008
Additional information: 210C7E 100 D 1C0001


I have tried completely reinstalling, enabling developmental patches, and turning off any weird overlays. I can not find a solution to this issue anywhere.

Re: ISBoxer crashing on account login

PostPosted: Fri Jun 29, 2018 4:28 pm
by bob
For starters, the top lines of a crash report only tells us there is a crash and a memory address. The rest of the crash report has the rest of the detail, such as what is being loaded, and the stack, which is all rather useful.

That said, get a compatibility diagnostic. It will show a lot of the info we tend to look for.
http://isboxer.com/wiki/Diagnostics

Re: ISBoxer crashing on account login

PostPosted: Fri Jun 29, 2018 10:23 pm
by sleepdeprived01
Diagnostic:
https://pastebin.com/4TSKgUS1


Here is the full crash report too if it helps:
https://pastebin.com/P6fa8cdN

Re: ISBoxer crashing on account login

PostPosted: Sat Jun 30, 2018 1:17 am
by bob
A few choices stand out.

In order of likelihood.

1. Trend Micro may be causing a problem and be uninstalled.
2. MSI Nahimic may need to have its OSD disabled, be shutdown (if it can) or uninstalled.
3. Update your NVidia graphics driver, and unless you have a VR headset or 3D screen, don't install those driver items (i.e. do a custom setup and only install the bits you actually need).

Re: ISBoxer crashing on account login

PostPosted: Sat Jun 30, 2018 4:07 pm
by sleepdeprived01
Uninstalled Nahimic, updated my video drivers, got rid of Trend Micro, but nothing worked. I had the same drivers and programs on my pc when I first started using ISBoxer, but it just stopped working like a month after I used it.

Re: ISBoxer crashing on account login

PostPosted: Sat Jun 30, 2018 5:02 pm
by bob
Going to suggest another compatibility diagnostic.

Re: ISBoxer crashing on account login

PostPosted: Wed Jul 04, 2018 6:26 am
by sleepdeprived01

Re: ISBoxer crashing on account login

PostPosted: Wed Jul 04, 2018 7:53 am
by bob
ok, so the development build(test) patches, is known to have an issue currently which may be causing the crashes, so you wan tot turn that off, and go back to build 6260.

You also want/need to leave things uninstalled/turned off, while you go through the process of seeing if the crash can be tracked down.

This includes Trend Micro, which is a known anti software which one of the updates to it a while back just doesn't want to work alongside Inner Space, and is still showing modules hooking into the game.

Essentially, what we are doing with the diagnostic, is looking over it for Application Compatibility settings on InnerSpace or the game that shouldn't be there (down the bottom); None that I can see currently

What is hooking the game that might be the cause (the middle bit which is showing the game process selected), and for you still shows these Trend Micro items
Code:
6. C:\WINDOWS\system32\tmumh\20019\AddOn\7.30.0.1099\TmUmEvt64.dll
22. C:\WINDOWS\system32\tmumh\20019\TmMon\2.6.0.2027\tmmon64.dll


And what else is running (the top part) of the processes on your system, which might also be a cause but don't show up anywhere else, and give you a few hints.
These are normally things like known pieces of software that through either their recent auto updates, or just behaviours (like the MSI Gaming OSD, because any overlays can cause crashes) may be a potential cause. This covers the following
Code:
177. TmsaInstance64.exe - Process ID: 12932 (C:\Program Files\Trend Micro\AMSP\module\10011\8.0.1061\8.0.1061\TmsaInstance64.exe) [Admin:NO] [x64] [8.0.0.1061] [Trend Micro Inc.] [Trend Micro Browser Exploit Detection Engine]
179. uiSeAgnt.exe - Process ID: 7372 (C:\Program Files\Trend Micro\UniClient\UiFrmWrk\uiSeAgnt.exe) [Admin:NO] [x64] [5.5.0.1256] [Trend Micro Inc.] [Client Session Agent]
180. uiWatchDog.exe - Process ID: 14004 (C:\Program Files\Trend Micro\UniClient\UiFrmWrk\uiWatchDog.exe) [Admin:NO] [x64] [5.5.0.1256] [Trend Micro Inc.] [Trend Micro Client Session Agent Monitor]
51. MsiGamingOSD_x64.exe - Process ID: 4348 (C:\Program Files (x86)\MSI\Gaming APP\OSD\x64\MsiGamingOSD_x64.exe) [Admin:YES] [x64] [1.0.0.07] [Micro-Star INT'L CO., LTD.] [MsiGamingOSD_x64]
52. MsiGamingOSD_x86.exe - Process ID: 4380 (C:\Program Files (x86)\MSI\Gaming APP\OSD\x86\MsiGamingOSD_x86.exe) [Admin:YES] [x86] [1.0.0.07] [Micro-Star INT'L CO., LTD.] [MsiGamingOSD_x86]
33. GameScannerService.exe - Process ID: 5028 (C:\Program Files (x86)\Razer\Razer Services\GSS\GameScannerService.exe) [Admin:NO] [x86] [1.0.6.2843] [GameScannerService]
29. EyeRest.exe - Process ID: 9540 (C:\Program Files (x86)\MSI\MSI OC Kit\ActiveX_Service\EyeRest.exe) [Admin:NO] [x86] [1.0.1.23] [Micro-Star INT'L CO., LTD.] [EyeRest]

There are a bunch of other MSI apps in there that might also be problems, which I would tend to focus on the VideoCard OC modules.

Simply, the process is to go through, shut these down (whether one at a time or all together is up to you), and where they can't be shutdown effectively (like Trend Micro), uninstalled, and test if the behaviour (crashing) stops. When it does, you can enable/reinstall things as you like. Depending on whether you did them one at a time, or all together, normally determines whether you enable/reinstall one at a time or all together, leaving out the cause of the crash.

All in all, I would start with removing the pieces of the Trend Micro, which are still hanging about and hooking in, as this is a piece of software which is known to currently be incompatible with Inner Space.

Finally, wanted to address your initial comment that you had all these things when it first worked. You may have. But software autoupdates so the versions of what you have last week may not be the same this week, and that can be the cause, as new updates bring new features, that may require compatibility patches. I can see several auto updaters running in your process list.

Re: ISBoxer crashing on account login

PostPosted: Wed Jul 04, 2018 1:12 pm
by sleepdeprived01
Finally got it working after uninstalling all that crap. Thanks a ton for all the help!