I really do not know what to think about it. MBAM last version ( 2.0.2 ) was running fine in my sys. Then this with 2.0.3. It really bug down my sys. Before the last crash, it showed a bunch of iastor error for my C. drive in event viewer, but the last crash corrupted my event registry and I have to rebuild it.
Yes the mini dump is not even from the BSOD related to the topic in MBAM. I realized it is from a couple of month ago. I attached it by mistake because it was the only dump I had so I asked myself so where is the dump for my new MBAM BSOD ?
I don’t know where AvancedSetup comes with that idea that my sys is probably infected or that my WMP caused the BSOD. I would go there and see what’s up.
I still have MBAM Pro 2.0.2 (holding back on 2.0.3 thought is is still beta) and for some reason both my XP and win7 installations have stopped the malicious sites checking. So both have the asterisk on red circle over the MBAM tray icon. Changing the settings and or selecting Fix, doesn’t resolve it.
MBAM 2.x seems to have gone down the toilet compared to mbam 1.x, it is a real resource hog and not this niggle.
Doing an update check doesn’t pull down 2.0.3, why I was thinking it is still in beta.
I’m pretty sure it’s released as I read they were rotating the upgrade etc. to deal with Server load.
I also don’t run v.2 realtime on xp as it is a resource hog AND I don’t like v.2.03 on my Production Machine (W8.1) as it is also heavy on resources
This really pi… me off. They have a bunch of people reporting error 6 during heuristic analysis and they say it is infection related. I did not have this error, but there is definitely something wrong with the heuristic analysis.
I’ve got a bunch of Error: (10/15/2014 10:22:50 AM) (Source: 0) (EventID: 9) (User: )
Description: \Device\Ide\iaStor0 while running the scan and this corupted my registry and the event viewer.
I know I have an old sistem and a bunch of old programs. I also have a wierd drive set up with RAID ON but not activated because my second drive is set up only as back up. I also have a third hidden partition with a DeLL MBR to invoke a Ghost image, but everything run find from here.
I did notice with MBAM 2.0.2 that everytime I boot my sys, it gives some 3000 seg delay thing in System event and it produces a clack in my HDD. Anyhow 2.0.2 was running fine, yes a bit on the resource hog side but no problems.
Now this 2.0.3 really screwed my system and registry, but I will play the game they want and see if they can find out what is really wrong.
@ essexboy
I have a new minidump and a full MEMORY.DMP. You want to take a look at it ? Where can I send it to you ?
Have you tried a clean install of MBAM with their clean tool Hernan, there has been problems on some systems with MBAM files not upgrading correctly which are fixed with a clean install.
Thank you Craig, but yes, I did a clean install, twice, and rebooted several times also. I think it has something to do with the way my HDD is set up, because I can not imagine that a program, does not matter how old it is, can cause a Kernel stack inpage error. I know my HDD and memory modules are OK. I checked them. So according to this report: http://support.microsoft.com/kb/228753
It can be a virus in my MBR. I know my MBR is specially built by DeLL to invoke the hidden third partition which hold the original image of my system when it was delivered. I belived MBAM is trying to read that sector it it can’t and BSOD
Otherwise the report says it can be a bad block in my HDD but all tests come out clean. the same for my RAM.
I think I am doing this troubleshoting just for the heck of it. To tell you the truth I was thinking in going back to 1.75 myself anyways since this is a XP.