> ... what this means is that ...<br> To me, that does not make any sense. Any insights? It is quite possible that the code whose execution precedes the misbehavior you observe induces the (ill)famed "undefined behavior" well known to mortal C/C++ programmers with much experience. Whether that inducement is in your code or in the image you loaded that came from a semi-mysterious source is not clear. I have found that making sense of undefined behavior can be quite challenging at times, requiring careful use of a debugger and inordinate time expenditure. It is best to just avoid it, or find where it is induced and fix that. It would take much more evidence to convince me that it is worthwhile to attempt to diagnose your ex-problem without source for the mystery DLL you found.