One Theory I have
The local shell explorer interface used in FlashFXP also loads all 3rd party shell extensions into the FlashFXP namespace, it's possible that one of these 3rd party shell extentions generate an error or conflict with FlashFXP under some unusual circumstances.
Although it could be something totally different
