Malwarebytes caused Windows "STOP" error (can't boot Windows XP, help!)

[Apple IIGS]

I'm not sure if I'm directing this to the right forum, but I'm just wondering if anyone else has encountered this problem with Malwarebyte's Anti-Malware software...

Long story short, I decided to do a routine full system scan using Malwarebyte, like I do every so often. It detected 1 infection--a Rootkit trojan or virus hiding in a /temp directory. I asked it to remove it, and then got a message saying it needed to reboot Windows XP in order to complete.

At this point I let the system reboot, the Windows splash screen appears and then I get a blue screen error and an instant reboot:

STOP: 0x00000024 (0x001902fe, 0xf78c6380, 0f78c607c, 0x8aaa180f)

Bottomline is I cannot get into my Windows XP, even in Safe Mode. I did a search and found other people who've experienced the exact same scenario with Malwarebyte's software doing this after requesting a Windows restart.

I'm currently only able to get into the Windows recovery console, and right now running a "chkdsk /f" but don't feel optimistic that will get me back up and running. Anyone else encounter this, and know a simple resolve? I'm rather at my wits end and would love to hear any suggestions, I don't want to have to reinstall Windows. :/

[Sartori]

Well, first off, its not MBAM that's causing this, its the removal of the malware thats causing it. If Malware gets its hook's into your system or a critical system file and you remove it, this is the type of behavior that happens...

Just be patient and there will be some knowledgable people that will respond to your problem...

[AdvancedSetup]

Please review the following Microsoft KB to see if it provides any help. Though written for 2000 the same methods should apply.

Error message in Windows 2000: "Stop 0x24" or "NTFS_FILE_SYSTEM"

[Apple IIGS]

Well, first off, its not MBAM that's causing this, its the removal of the malware thats causing it. If Malware gets its hook's into your system or a critical system file and you remove it, this is the type of behavior that happens...

Just be patient and there will be some knowledgable people that will respond to your problem...

Yes, realize that. More specifically it indirectly caused the problem (I would think the software take precautions about ripping out pieces of a virus that is linked to system files).

Well, the chkdsk /f completed, and guess what? IT WORKED! Yay, I can sleep easy tonight. (hopefully it'll work after another reboot, but at least I'm in!)

Sometimes you have to take an error message literally. That STOP error relates to NTFS corruption or driver issues. I don't think it was coincidence, but likely a side effect of the virus or Malwarebytes (one of them step on something).

[AdvancedSetup]

Normally what I've seen happen quite a few times is that MBAM removes the infection and then the Anti-Virus or other Security software can now see other files that are or were Malware that they partially saw but could not remove. Now they don't have enough information left about the infection to make an intelligent removal and they remove items that should not have been removed. It happens and it difficult to completely prevent as this is an ever changing environment when dealing with Malware.

Glad you got it sorted out and are back up and running again.

[Apple IIGS]

Normally what I've seen happen quite a few times is that MBAM removes the infection and then the Anti-Virus or other Security software can now see other files that are or were Malware that they partially saw but could not remove. Now they don't have enough information left about the infection to make an intelligent removal and they remove items that should not have been removed. It happens and it difficult to completely prevent as this is an ever changing environment when dealing with Malware.

Glad you got it sorted out and are back up and running again.

I ended up having more issues following that, I was infected with the TDSS rootkit and it had attached itself to my atapi.sys driver! The solution was running a specific removal tool: http://support.kaspersky.com/viruses/solutions?qid=208280684

Following that, I did a clean up to remove any other traces of the infection, had to use an online scanner as neither Malwarebytes or any of my other installed anti-virual applications could detect it.

I'm finally back up and running, with the virus gone. Just going to run one last tool to be sure there wasn't any permanent damage to my system drivers.