Event 1060, Application Popup

\SystemRoot\SysWow64\Drivers\Aspi32.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

After starting with a completely clean Windows 7 64-bit installation I monitored Avid's MediaComposer 5 installer adding this driver to the computer and to the registry. Which then results in the above error message getting reporting in the Windows Event Viewer.

And it seems this goes all the way back to MediaComposer 3. Maybe Avid should remove it?

I was trying to find out which piece of software installed this driver. I didn't know it was Avid. I started to look at the Event Viewer to see if there were any issues and found this one.

One way to prevent it from loading is to go the registry and do the following:

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\ASPI32 and set the parameter 'START' to 4.

This should prevent it from loading.

The other way I think is to use 'Autoruns'. You don't have to install this program. Just go down the 'Everything' tab and find the ASPI32.SYS drive and uncheck the box next to it. You can then close the app. I didn't do it this way but it may work. You can find the program here: http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx.

It's the Adaptec SCSI driver. I hope there isn't going to be too much of a problem with this as I plan to try and use my old Adaptec SCSI card in a new computer so I can utilise a RAID array that is still perfectly serviceable. Otherwise, I guess I'll have to use Atto.

ASPI32.sys WIN7/64/MC5 Is anyone else having this problem? Seems every month or so my machine takes forever to boot...I have to wait for it to rebuild the File Indexing & Super-Fetch before it's usable. The machine is slow...slow...until it's happy, so slow it will not even load MC5. This may take up to an hour to complete. Is there a solution? Thanks

in windows 7-64 bit I had the same problem and did the following to solve it:

delete the driver: \SystemRoot\SysWow64\Drivers\Aspi32.SYS

Just to be save I have stored the a.m. driver in a tool box, I keep to manage my system. In addition I added a textfile to remember what I did, in case I have to reinstall the driver.

Thanks anthas - that was the 1st thing tried with no success. Seems MC5 then wants the "Avid Media Composer.msi" file - when I point it to that file on the install DVD it is still not happy and will not open...fatal error. I have to put "aspi32.sys" back where it was to open MC5. This file is wreaking havok on the 64bit system error reports and really an ongoing problem. Is anyone else seeing this happen?

... strange, helped for me though. Are you using a SCSI Raid, so do I but I have installed the proper 64 bit driver for the Adaptec RAID Adapter of course.

I have the same issue with my system. Until now I went through the registry and deleted all entries with references to aspi32.sys. Now I will try the way described by mtahir. I will report about success.

Joachim

Same here but also didn't know what installed it. Figured it didn't hurt anything so left it alone. Guess it's messing up for some people. Please post any success with its removal.

Shouldn't there be a way to update the driver to a version that is compatible with Windows 7 64-bit?  I visited the drivers page on the Adaptec website, but there appear to be many versions, depending on the hardware.  I noticed the error and disabled it from loading, per mtahir.  It hasn't been a problem on my system, but I'm surprised that Avid let this one slip through.

--
Michael

I'm seeing this as well ever since installing Avid on a fresh system a couple weeks ago.

So what's the official word on what to do?  Is it recommended to just ignore it, or is it better to try one of the methods to prevent it from loading?  Is there a fix in the works that will happen with a patch, or ???

I imagine that a lot more people are getting this, but that they just don't know it because they either don't check the event viewer, or they don't realize it's due to Avid.

Thanks,

Larry

Don't remove it just use the mtahir registry method to set the startup to disabled. That way nothing will moan about mising files they just aren't allowed to run (and no point as they fail to run anyway)

Always worth keeping an eye on the event logs and fixing easy to fix warnings and errors. Then you can cathc problems before they become a big issue.

Pat Horridge:

Don't remove it just use the mtahir registry method to set the startup to disabled. That way nothing will moan about mising files they just aren't allowed to run (and no point as they fail to run anyway)

Always worth keeping an eye on the event logs and fixing easy to fix warnings and errors. Then you can cathc problems before they become a big issue.

So it sounds like it's better to use the mtahir method instead of removing it, but what I'm still not entirely clear about is if it's better to just do nothing and let the error occur in the event viewer.

I'm wondering if editing the registry line may actually be worse than doing nothing at all.  For example, if Avid does eventually fix this, the fix may work by looking for a certain line in the registry in order to apply the fix.  If this line has been edited, it could theoretically interfere with the fix.  I realize that this is entirely conjecture, but again, if the ONLY issue is the presence of the registry error, might it be better to just let the error happen?

Thanks,

Larry

PS.  On a semi-related note, I find that the event viewer in Win7 tends to log a lot of both warning and error events that don't actually matter.  It seems like it's easier than ever to be fooled into thinking you have a problem when you really don't.

So it's 7 months down the line and we've had 5.5.3 released, but this error is still an issue.

I installed 5.5.3 and have had several crashes with no idea why until I started looking through the Windows Event viewer and google search for

"Aspi32.SYS has been blocked avid"

This thread came number 1.

It doesn't help to have these sort of bugs in the install, when do you think this is going to be resolved ?