Now that's quite easy to say...
That's the only correct thing to say, because it's technically impossible for an uninstalled scenery to cause a crash into the effects module. And, the KORD installer doesn't modify any of the default effects in any way. It only reference to some default texture files, but it doesn't touch them and of course the KORD effects files themselves are removed when installing the scenery.
It is VERY remarkable the problem appeared after I installed FSDT ORD
As I've said, it was purely coincidental. And this is misleading you thinking the problem has anything to do with it.
.I did not install anything else apart for ORD
That doesn't mean of course that's nothing in your FSX installation can't be corrupted, without this having anything to do with the KORD installation or even without you having to install another addon. In fact, since as I've already said, the only other file the (REMOVED) Effect file that comes with KORD are calling are default texture files (but even when KORD is installed, these are NOT MODIFIED in any way by it), it's possible it's one of the default texture files for effect might have been corrupted, simply because of a problem with your file system, for example.
and you know yourself these dll's don't change themselves...
It's not the .dll has "changed", when you have a crash into a .dll, it doesn't necessarily mean the .dll is "bad" or has been "changed", .dll usually crash when they access OTHER files and THOSE might been corrupted.
When you get a FE.DLL crash, it's not the FE.DLL that "changed", it's one of your AI models that has a problem, when you have a TERAIN.DLL crash, it's one of the default *texture* files that has a problem, when you have a G3D.dll crash, it's one of the thousands of .MDL files included in a .BGL that has a problem, etc, etc, etc.
So no, fact that the crash happens in visualfx.dll, only indicates there's some kind of problem with one of the effect files that this .DLL access, not that .dll has "changed".
