"that KMEM uses quite a bit of texture memory ( VRAM )"
Light out! bye.
I'm not sure what you are trying to say, but I simply posted something, which included a suggestion to use GPU-Z to check if you ARE low in VRAM in that particular situation, because I cannot obviously imagine any other cause.
Note that, KMEM uses LESS RAM than, for example, KLAX, but it might use more VRAM instead. There's really no "free lunch", you either optimize in a way or in another. The correct way forward, especially under a 32 bit sim, when we don't have so much RAM available, is to push in the direction of using more VRAM, for the obvious reason that video cards with more and more VRAM are easier to get than having to wait for a 64 bit version of the sim and of course, even if we *had* a 64 bit version of the sim, pushing on VRAM usage instead of RAM, would always be faster, since newer video cards increase in speed WAY more than the main CPU would ever be able to.
Of course, users with a very unusual configuration ( 3 monitors AND a TV is, sorry, far from being normal, and you cannot expect we would anticipate or test under this conditions ), might be more exposed to VRAM usage, since they DO use more VRAM *BY DEFAULT*. Again, there's no "free lunch". You want to drive 4 screens ? There's a resource costs associated with it.
But this is just a THEORY, which is why I suggested to verify, using GPU-Z, if you *really* are low on VRAM when KMEM is loaded *and* your TV is connected. If you are low on VRAM, there are things that can be tried to reduce its consumption, such as reducing the texture resolution, for example.
But maybe you are *not* low on VRAM ( again, GPU-Z should tell you ), and the reason is just more mundane, and you simply found a BUG in the video driver, that will cause FSX crashing when so many displays are connected, that happens only at KMEM because you need to consume AT LEAST a certain amount of VRAM, without necessarily exhausting it all.
