A more "low-level" approach would be to run filemon, filter out the standard Windows activity such as svchost, winlogon etc and see if you can find out what application is producing these files that way. It may turn out that it is all perfectly innocent, but better safe than sorry
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.