BUG: ACMSETUP Invalid Page Fault in Kernel32

ID: Q195231

The information in this article applies to:

SYMPTOMS

When you are installing one of the products listed at the beginning of this article, you might receive the following error message during the middle to later part of the installation:

This program has performed an illegal instruction an will be shut down.
When you click Details, the following message appears:
ACMSetup caused an Invalid Page Fault in module kernel32.dll


CAUSE

This problem can occur for a variety of reasons, but it often occurs during self-registration of DLLs that have missing or incompatible dependant DLLs.


RESOLUTION

In some situations, you can resolve this problem by simply restarting Windows after the error message appears to allow some of the copied files to replace older files that were in use and could only be replaced during Windows restart. After restarting, start setup again.

On rare occasions, this problem can also occur on some laptops with DMA access enabled. This is described in the following article in the Microsoft Knowledge Base:

Q190630 OFF97: Kernel32.dll Error Installing Products with DMA Enabled

In this case, it can be difficult to identify what is failing and fix the problem. Please see the More Information section.


STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.


MORE INFORMATION

There can be a variety of causes for this failure, and there is no simple solution. However, the first step is to identify what is failing. Start by generating a setup log file as described in the following article in the Microsoft Knowledge Base:

Q192392 HOWTO: Troubleshoot Visual Studio 6.0 Setup

Even if you end up having to talk to Microsoft Technical Support to resolve this problem, the Microsoft Support Professional is likely to need this log file to resolve the problem.

The setup log might indicate a failure in registering an object, but it might only identify the object by number. You can look up more specific information on the object in the STF file in the \setup directory of CD1. Look for a line that begins with the number of the object.

The cause of the failure might be clear from the setup log. Perhaps it is a DLL that is failing to self-register. This typically indicates that the DLLs it depends on are incompatible versions or that some files were corrupted when they were copied. If it is clear what files might need to be replaced, try to replace them manually from a known source such as the product CD. Before replacing DLLs, check to make sure you are not accidentally replacing a newer DLL with an older one. Do this by right- clicking on the DLL in Windows Explorer, selecting the properties, and then looking at the version numbers. Check the version of the DLL currently on your system and the DLL you intend to replace it with. If you do decide to replace a newer DLL with an older DLL, save a copy of the newer DLL so that you can restore it later if this turns out to be a cause of other problems.

Even with the setup log, it might not be obvious what is failing or how to fix it. You might need to contact Microsoft Technical Support. To do this, go to the following Web page:
http://support.microsoft.com/support/contact/default.asp

Additional query words: ACME kbdss 


Keywords          : kbsetup kbSSafe600bug kbVBp600bug kbVC600bug kbVFp600bug kbVisID600bug kbVJ600bug kbVS600bug 
Version           : WINDOWS:6.0; winnt:6.0
Platform          : WINDOWS winnt 
Issue type        : kbbug

Last Reviewed: June 30, 1999