Debug technique for debugging an unusual memory leak

I have a windows application (legacy) that leaks a lot of memory. It does not leak private bytes, I only see with process explorer that it keeps loading from time to time many instances of the same (topically) windows dll-s.

Is there a tool I can use to "trap" the moments when dll-s are being mapped to the process space so that I can track that (with the application symb开发者_如何学Cols) to the source code ?

In Process Monitor, you get the stack trace of every recorded action, so you can see who opened some file. Define a filter which includes, say: Path contains iologgingmsg.dll. If you get too much noise, you can try to add a filter like Operation is CreateFile.