The Shell NotifyIcon error may be a red herring. It just may be the point that the failure is being reported. Unfrotunately the error code is a fairly generic error code (a bit like using vbObjectError if you've used Visual Basic before), and doesn't lead to what might be causing whatever issue you are having.
So, to that end, a
Compatibility Diagnostic may be a good place to start. Grab it on any process, although the running Inner Space might be useful, if it shows up in the list.
It may also useful to get a Trace Diagnostic too when that error appears, although it might be less so. I had a process somewhere to get a dump at the point of failure to avoid it rolling up the stack.
heh, found it.
Download ProcDump from
https://technet.microsoft.com/en-us/sys ... 96900.aspx. Unzip it and put it in a folder, like C:\DumpDir.
Open a command prompt as Admin,
Run the below command (replacing any parts as necessary for your installation of ProcDump and InnerSpace).
- Code:
C:\DumpDir\procdump -accepteula -e -t -l -f "" -x C:\DumpDir "C:\Program Files (x86)\InnerSpace\InnerSpace.exe" > C:\DumpDir\procdump.log
Then reply back and attach the log file and the dmp file you have generated in the C:\DumpDir folder.
If you can't attach the dmp file here (it may not like it, 1. because it is a binary, and 2. it's big), then email it to
lax@lavishsoft.com, referencing this thread. He may be able to spot something in it.
If you're really keen you can upload the dmp file here:
https://www.osronline.com/page.cfm?name=analyze, it may point you to what the issue is.