DonZ63 if you are getting memory detections about malwarebytes then you must be running a custom scan with memory scan included, as this scan tends to delve deeper into memory than the normal scans which is why your picking up MBAM signitures, there is no way round it but to either untick the memory scan section or to stick to the normal scans, or simply just ignore the detections of MBAM as there harmless anyway.
We are having a debate over in the Comodo firewall forum on this issue.
Individuals with identical security setups; Comodo ver 5.x firewall and Defense+ with Avast 6.x with web shield active are getting different results when Avast memory scanner is run. Most get the FakeVimes signature found result. However, others do not. This has more than a few people concerned. Note than none of these individuals every had Comodo's AV installed including yours truly.
Comodo has admitted that Defense+ does do process hook injection to minimize Defense+ alerts. This however does not explain why Avast memory scanner is finding unencrypted signatures.
Then there is the MBAM Pro issue in the same area. As far as I know MBAM Pro does not do any process hook injection.