This will happen if an exception is thrown, but then caught. There are a few bits of structure that do this at a depressing frequency ... but usually you can ignore it. If this happens very often, and you think that it can affect performance, you can always try to figure out what causes it and see if there is anything you can do to stop it - but in my experience this usually happens in perfectly normal situations :(
To find out where this happens, go to the debugger options and make it break as soon as an exception occurs - this way you should get a stack trace that at least shows if any of your codes will be directly contact the framework code.
, DLL , , ... , :)