@ Thunder Bird
Avast doesn't scan its chest, as it is a protected area, the files are encrypted and the file names are changed.
Whilst MBAM is running a scan, guess what avast as a resident on-access scanner will be monitoring the MBAM activity. So when it tries to open a file for scanning avast will scan it first, so it is entirely possible for this to happen.
What is strange is the detection on the files again, presumably in the same original location and file names ?
Though that too isn't impossible as there is likely to be an underlying hidden (rootkit) or undetected malware instance restoring/recreating the files. So that is why it is going to take more tools to hunt down these hidden elements.