I see, but I'd like to be asked before someone makes such a change. And yes, I tried to remove the section (I run a large amount of buffer pools), but it still crashes.
Both PoolSize and a too large buffer pools settings are equally dangerous (one would risk GD2.DLL crashes, the other OOMs), and we cannot afford for KMEM to be mistakenly accused to cause crashes, if it's running with settings that have been proven dangerous by the community at large.
The safest setting is default: which means no setting. That doesn't obviously mean FSX doesn't use any bufferpools: it just use a reasonable number.
It's just a setting which can be easily restored: there are 3rd party installers out there ( I won't name them, but we know there are ), which silent patch your FSX .DLLs, or patch your FSX.EXE, or corrupt your XML files. We only restore it to its correct default value.
Most of the issues with FSX, is from "miracle" tweaks, which don't really do anything, other then increasing the risk of crashes, we were in the FSX Beta since 2007 when the Acceleration/SP2 was releases (heck, we even WORKED on the Acceleration Pack!!), and the default values were carefully chosen for some reason.
If you really want to change something and have a more reliable product, switch to P3D instead. No miracle tweak can really fix a 10-years old sim.
I understand the problem you are facing - I really do. Is there some kind of logging I can activate in the Addon Manager?
You are still missing the point. The Addon Manager is NOT crashing. If it did, you would see a crash in bglmanx.dll. It's your FSX which is crashing and it's NOT crashing (according to your latest report), with any other airplane than the iFly.
How you could expect we would ever be able to "log" a crash happening only when another program is running ? Again, the only ones that can help you are iFly guys, assuming you could be able to help them replicate the problem.