Jump to content

Scanning results in a ATAPI (11) \Device\Ide\IdePort4 error in the event vi

Recommended Posts

I have had this same issue and the update to RST did indeed help for a while.

However, the ATAPI errors are back!

Scan (with rootkit scan enabled) performed today, resulting in a system that is not responsive during the rootkit scan part, with multiple instances against the IDE port that corresponds to the hard disk with the system drive (C:). The machine runs W7SP1 and the highest version of Intel RST officially supported and available for this platform (Asus P8P67D mobo), which is

Version: MBAM free version with latest signatures (Aug 26, roughly 9:30am PST).

Additional notes: only happens during MBAM scan, no other issues, errors, etc.

Link to post
Share on other sites

Reporting back. Version 3.2 works fine regarding the disk/ataport functionality. Seems to be fixed.

Can you share what was changed on the driver/fs level as I did notice the userspace-reported disk activity goes down to zero during the scan, so I presume you are using your own access to the disk structure.

On a side note, the installation was not smooth - it failed to restart its service, required second installation to fix it. But this is a separate topic.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • 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.