Okay, so I have read the 10,000 posts regarding the use of File Monitor by sysinternals.com in order to diagnose a memory leak. Works really nice and I have a great log file.The problem is, and I'm sure I'm not the only one, what should I be trying to interpret from here? I have several files that have flagged "error" on them as being "not found," and if my hunch is correct, those are going to be my problems.Can someone please confirm this and maybe give a short tutorial on what it is exactly that users should be looking for when using this program?

I'd like help with this as well. thanks

Me to please:-) :-)

Guys, Do not trust filemon with FS. FS by design looks for a lot of non-existant files and even in a lot of non-existant locations. This is by design and does not cause any error within FS. If you are having OOM errors I would not rely on Filemon to diagnose them, I would look at the usual culprtis, add-ons, LC files, drivers, bad memory etc...FS is not made for Filemon LOL...-Paul

Well, yes, I understand that, but when it's looking for files that are supposed to exist and don't, it sure makes life a lot easier than ripping everything off and spending the next 24124 hours trying to figure out which file of the 3232523 installed is causing the issue. ;)At the very least, it's a great place to start.