PMDG says that it is something to do with your software and security settings I think and to use at my own risk
They are wrong, and it's clear they used this explanation without knowing anything about how our software works.
In fact, since almost all objects are called by a module that is *external* to FSX (the Couatl.exe), it would be even less likely it would cause such problems to FSX, like memory consumption for example, since the memory is taken from a different set than the maximum of 4GB FSX can allocate (while, for example, their own gauges and *their* security module, being in-process .DLL, will take away from the same memory available to FSX). The Addon Manager, which runs in-process, does almost nothing right now, it's basically left just as an interface to activate the scenery.
And besides, how they explain it doesn't happen with the MD11 ? If it was our "security module", causing a conflict with their own, for example, it should happen with the MD11 too, on an FSDT scenery.
The fact that it occurs on a completely new machine is interesting
What I found more interesting, instead, apart for the fact it doesn't happen with the MD11, is that nobody else posted in this thread.