>>Thanks, that's what I did prior to asking here hoping that someone using MM.NET encountered the problem before and may save me digging through all the possible solutions
>>
>It may be not MM.NET specific as you see it's quite a common problem with unknown cause.

Yes, but most of the comments I've found on-line point to the MM.NET code, or at least to understanding it.