Jump to content

Ran Malwarebytes. Now my computer won't start up


Recommended Posts

I've been using Malwarebytes for several months, and it has been great. Today, I ran a weekly scan. Nothing had been detected in a while, however, today there were three malicious files found. One was a trojan. I don't recall what the other two were, but they were registry files, while the trojan was located somewhere else. I selected "Remove Files," and it didn't alert me of a problem with deleting them. When I tried to re-boot to complete the deletion, I got a blue screen on the boot. I tried booting with Last Good Configuration, Safe Mode, and Safe Mode with CMD. No avail on any of these. Same blue screen issue. The error is:

STOP: [memory location]

atapi.sys - Address BA7217c0 base at BA70B000, DateStamp 4802539d

I tried booting with my Windows XP Pro install disc. Doesn't work. Same issue. I'm guessing two essential registry items were replaced with malicious files, MWB deleted them because they were malicious, and that's why I'm getting the blue screen. Any help would be appreciated.

Thanks

Link to post
Share on other sites

Hi rconnermwb welcome to MalwareBytes.

Can you give me the exact error that comes up after this part:

STOP: [memory location] <-- that would be the error code I need to see.

atapi.sys - Address BA7217c0 base at BA70B000, DateStamp 4802539d

It may be something such as Stop 0x0000007e or something similar to that.

Link to post
Share on other sites

STOP: 0x0000007E (0xc0000005, 0xBA7217c0, 0xBACCB528, 0xBACCB224)

Thanks a lot for the quick reply.

An update for what I've tried to do after following other instructions in the forums:

I tried to create the Universal Boot Disc on my desktop. I got 7 errors while building the disc. It's a Dell Windows XP cd. I don't know that has anything to do with it.

I've tried booting from the Windows cd from my internal drive and a usb drive. With each, the disc begins to spin during the BIOS screen, then stops. That's where I am so far.

Thank you.

Link to post
Share on other sites

Let's try another cd please.

Download RC.ISO and burn it to a cd as an ISO image. You may need a burning toy like ISO Recorder to do this...be sure to get the version for your operating system.

Once you have burned this as an ISO image, insert the CD into the drive, and then restart the computer.

Since this is a dell pc then the boot from disk would be to press F12 during the bios splash screen to boot from another device.

Watch for the prompt to "Press any key to boot from cd" and press the spacebar when you see it.

When the "Welcome to Setup" screen appears, press R to start the Recovery Console.

If you have a dual-boot or multiple-boot computer, select the installation that you want to access from the Recovery Console...by number (usually 1)

When you are prompted to do so, type the Administrator password. If you have not set an administrator password, leave it blank and just press "Enter".

At the Recovery Console command prompt, type expand D:\I386\atapi.SY_ C:\Windows\system32\drivers\ /y then press Enter.

At the next prompt, type the following bolded text, and press Enter:

exit

============

Take the disk out of the drive and see if it get's into Windows then.

Link to post
Share on other sites

Thanks for the help. Last night, I got a USB to SATA cable, and put atapi.sys back on the drive from another computer. It booted up and everything was back to normal. I backed up the data, with plans to wipe the OS. But it appears my optical drive doesn't work now, which explains why I couldn't boot from it yesterday. It hasn't read audio CDs in a while, and it looks like it stopped reading data yesterday too. Fun stuff.

Thanks again for the help.

Link to post
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.