Dale,

Hard to say what's happening to you.

One possibility is that MBAM is buggy and behaving erratically, in and of itself (i.e., without specifically interacting/conflicting with other security programs).   Another possibility --- since I believe you like to keep "lots" of security programs running on your system [as do I] --- is that MBAM is somehow conflicting with another security program... but if so, it can be quite painstaking to determine exactly where the conflict might be.   Might it be an interaction with your updated HitMan Pro?? --- I have no way of knowing.

As I mentioned last time you posted here, I am NOT a fan of "routine" on-demand scanning by programs that are already continually running in real-time.   Doing so is more likely to generate a false-positive detection than a real problem.

However, I would run an on-demand scan if I had reason to believe something was actually wrong with my system.

Since you and others are clearly having "intermittent" problems (including BSODs) with MBAM scans, I would strongly advocate that you don't continue to tempt fate by running them.   [Like the old joke:   A patient says to his doctor, "It hurts when I raise my hand here"... to which the Dr. replies, "Then don't raise your hand there anymore" :emotion-4: ]

While I clearly have an abundance of security on my system(s), I am not noticing any problems (nor slowdowns).   At Joe's recommendation, I tried HitMan Pro.ALERT [which is not the same as HitMan Pro].   It resulted in slow-downs (and/or some other issues) FOR ME... after which I decided to remove it.  My understanding is that BugBatter did the same.   But as long as it's working-well for Joe, I expect him to keep it.   You need to figure out what works for you... and what does not.   Again, I'm not suggesting you abandon MBAM's real-time protection... only that you might stop the routine scanning.

I do an Avira AV scan every Sunday, and then quick scans with the others while I am at it, since WD, SAS and Hitman Pro just take a few minutes. For now, will avoid doing any scans with MBAM unless some problem shows. It's a weird program...this time when I cranked up the computer after running to the store, it put up two matching icons in the tray!

Dale,

Try downloading and installing Resplendence Software - WhoCrashed then click on analyze. Then look and see if it tells you the reason for the BSOD. It could be a coincidence of maybe a driver got updated that is not working properly.

You can uninstall the above software, when finished.

Rick

Dale,

Microsoft has a solution for the ntfs.sys for Windows XP and it might work for other operating systems but looks more like a software driver bug, like it mentioned.

 http://support.microsoft.com/kb/822800

Rick

Thanks Rick, here is the result of the scans. I'll post this on the MBAM forum for their perusal.

Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 10/30/2014 12:59:01 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini103014-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0xEF268) Bugcheck code: 0x50 (0xFFFFFFFFC5DB4084, 0x1, 0xFFFFFFFF8E0F2268, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 10/30/2014 12:59:01 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x1A4B0) Bugcheck code: 0x50 (0xFFFFFFFFC5DB4084, 0x1, 0xFFFFFFFF8E0F2268, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

I agree with just about all ky says, Dale.

The more I add security programs, the more I suspect conflicts. I have no idea why MBAM Premium slows down my XP, or why HitmanPro.Alert works well for me but not for others. There are just too many variables.

 I sincerely doubt, however, that the HitmanPro AV is contributing to problems with MBAM. HMP does not run in real-time. Unless you were running both on-demand scanners simultaneously, I can't imagine how they could conflict.

Rick,

the Microsoft support article you linked to refers specifically to a problem under XP that occurs on the first reboot  "after you convert your hard disk [from FAT] to the NTFS file system" (which results in a failure to start).   It seems to me that this is not the problem Dale is facing.

ky331,

I was looking at the Resolution to replace the nfts.sys file if it became corrupt

Rick