Just had a Teamviewer session with Hnla. His problem was different, since he had random crashes from any modules, like fsuipc, etc.
I checked his DLL.XML and EXE.XML file and, especially the DLL.XML, was probably the most crowded and full of stuff I ever seen. Dozen of 3rd party modules, all loaded together, so it was a miracle that FSX even started, and of course, each of them takes some memory, there was a separate DLL for *each* OrbX scenery, talk about efficient memory usage...
However, I tried disabling *every* 3rd party module there, except bglmanx.dll, Couatl and SODE, which are all required by KMEM. In addition to that, I excluded the whole FSX folder from the antivirus.
And sure enough, on the next restart, I was able to start KMEM and use it for some time with no errors. I loaded the Aerosoft A320, and started GSX servicing.
Hnla went away in the meantime but, while he was away, I kept FSX running, and I did it from 1:13 ( my time ) to 2:00. It ran continuously with no crashes, made a complete GSX service and Pushback and using SODE jetways too, then I quit the sim normally, which ran over KMEM for 47 minutes with no errors, and then I just quit the session, because it's 2:07 AM here (talk about "not investigating"...)
So, even in case of Hnla, it's confirmed the problem it's NOT KMEM, it's just happening there, likely because, with such an ungodly amount of 3rd party modules loaded, FSX might just have ran out of memory, which might happen at any other detailed scenery.
It's also possible the problem is just a single module but, following Hnla report that crashes happens at random everywhere, I'd be more inclined to believe it's just a low memory issue. And, with so many modules installed, I couldn't possibly try all combinations, just restarting the sim every time a new module would be re-enabled would take hours, so I'll have to leave this to him.
But it's clear that, even in this case, it has been proven again there's nothing wrong with KMEM.
