Article ID: 218853 - View products that this article applies to.
This article was previously published under Q218853
For a Microsoft Office XP version of this article, see 290361
For a Microsoft Office 97 version of this article, see 245050
For a Microsoft Office 95 version of this article, see 190517
WARNING:This information is preliminary and has not been confirmed or tested by Microsoft. Use only with discretion.
This article contains information about troubleshooting and eliminating Invalid Page Faults that occur in module Kernel32.dll when you work with a Microsoft Office program under Microsoft Windows 98. A Kernel32.dll message is similar to the following
where Program name is the name of the Office program you are using.
Program name caused an invalid page fault in module Kernel32.dll
For additional information about troubleshooting Office Kernel32.dll issues under Microsoft Windows 95, please see the following article in the Microsoft Knowledge Base:
218873For additional information about troubleshooting Office Kernel32.dll issues in earlier versions of Office, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/218873/EN-US/ )Troubleshooting Office 2000 Kernel32.dll errors under Windows 95
(http://support.microsoft.com/kb/190517/EN-US/ )OFF: Troubleshooting Office Kernel32.dll Errors Under Windows 98
When an Invalid Page Fault occurs, an unexpected event occurs in Windows. An Invalid Page Fault indicates that a program improperly attempted to use random access memory, for example, when a program or a Windows component reads or writes to a memory location that is not allocated to it. When this occurs, the program can potentially overwrite and corrupt other program code in that area of memory.
An Invalid Page Fault may occur when parameters are passed between programs and Windows. An invalid parameter may cause a program to run invalid instructions, which results in an Invalid Page Fault. This behavior usually occurs because a program incorrectly passes data that Windows or a Windows-based program cannot interpret.
NOTE: Follow the steps in each of the sections in this article in the order in which they are presented. Because Invalid Page Faults are typically caused when two or more programs interact, skipping steps may increase the time it takes to identify the problem.
Determine If the Problem Is DocumentedMany Kernel32.dll errors are already documented in the Microsoft Knowledge Base and have solutions. For more information, query on the following words in the Microsoft Knowledge Base:
"invalid page fault" kernel32.dllNOTE: It may be helpful to add the program name in which the problem occurs at the end of the query to narrow your search.
Check for a Valid Temporary Folder and Delete Temporary FilesThere should be at least 20 megabytes (MB) of free space on the hard disk that contains the temporary folder. To check for a temporary folder and delete excess files from that folder, follow these steps:
Start Windows in Safe ModeWindows has a built-in troubleshooting mode called Safe mode. It bypasses startup files and uses only basic system drivers, including basic networking. When you start Windows in Safe mode, Windows uses only the mouse, keyboard, and standard video graphics adapter (VGA) device drivers. This makes Safe mode useful for isolating and resolving error conditions that are caused by both real-mode and Windows-based drivers. Windows also has troubleshooting features that may help you identify the problem. To start Windows in Safe mode and make the additional troubleshooting features available, follow these steps:
For additional information on determining if Windows is using protected-mode drivers, please see the following article in the Microsoft Knowledge Base:
151634For additional information about installing real-mode drivers for the CD-ROM, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/151634/EN-US/ )Protected-Mode CD-ROM Drive Support in Windows
(http://support.microsoft.com/kb/167069/EN-US/ )Installing Real Mode CD-ROM Drivers for Office Installation
Check the Hard Disk for Disk Errors and FragmentationUse the ScanDisk program to check the hard disk for lost clusters and other file allocation table (FAT) errors and test the hard disk integrity. You can also use the ScanDisk program to repair any of these problems. To run ScanDisk, follow these steps:
Turn Off the CD-ROM Drive CacheIf the error message appears while you are reading from a CD-ROM drive, try turning off the CD-ROM drive cache. This may make the drive more reliable but reduce performance. To turn off the CD-ROM drive cache, follow these steps:
Verify That the Compact Disc Is Clean and UnscratchedIf the error message appears while you are installing from a compact disc, verify that the compact disc you are using is clean. You can wipe the compact disc with a soft, lint-free cloth. Also ensure that there are no large scratches on the compact disc. If the compact disc is damaged and unreadable, error messages may appear during installation.
For additional information, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/174713/EN-US/ )Troubleshooting Installation from Compact Disc Media
Check for a Corrupted Swap FileThe Kernel32.dll error may also appear if your Windows swap file is corrupted. To create a new swap file, restart the computer in MS-DOS mode, delete the Win386.swp file in the Windows folder, and then restart the computer. To create a new swap file, follow these steps:
Corrupted Custom ProfileCorrupted custom profiles have also been known to cause Kernel32.dll errors. Deleting and recreating the profile can possibly resolve this problem.
If you are using the Office system policy templates that are included in the Microsoft Office 2000 Resource Kit, you must use the version of the System Policy Editor that is included in the Microsoft Office 2000 Resource Kit.
NOTE: The System Policy Editor that comes with Windows 98 does not work with Office 2000. Be sure to install the latest version of the System Policy Editor from the Microsoft Office 2000 Resource Kit or from Windows NT Server 4.0 with Service Pack 4. You can download Policy.exe, a self-extracting file containing Poledit.exe, from online services. Download this file from the following Web site:
Remove and Reinstall the ProgramIf the problem occurs after you run the Setup program, some of the dynamic link library (.dll) files may be damaged or corrupted. To troubleshoot this problem, first completely remove the program. After you completely remove the program, reinstall the program.
Check for Software UpdatesOutdated and incompatible software may also cause error messages to appear. Check with the manufacturer of the computer for various software updates, such as BIOS updates, OEM Windows updates, and hardware driver updates such as CD-ROM drivers. If you are using third-party partitioning software, for example, EZDrive, or Ontrack Disk Manager, verify that you have the most recent versions of these products.
Scan the Computer for VirusesIf a virus is present on your computer and has damaged some files, Kernel32.dll error messages may appear when you use a program. Scan the hard disk and floppy disks with a virus detector. If the virus detector finds a virus on your computer, remove the virus before you run the Office program again.
NOTE: Do not run a virus detector terminate-and-stay-resident (TSR) program while you run any of the Office programs, including the Setup program. Run a virus detector before you run the Setup program, and then disable it.
Check for Registry CorruptionWhen you start Windows in Safe mode, Windows does not read the entire registry. Therefore, damage to the registry may not be evident when you run Windows in this mode. It may be necessary to replace the existing registry (System.dat) with a backup to determine whether the problem is caused by a damaged registry. Use one of the following methods to troubleshoot a damaged registry:
Method 1: Use Registry CheckerWindows includes a tool called Registry Checker that can scan your registry for corruption, and if necessary, restore a backup of the registry. Follow these steps to use Registry Checker to scan your registry:
For additional information about Registry Checker, please see the following articles in the Microsoft Knowledge Base: 183887
(http://support.microsoft.com/kb/183887/EN-US/ )Description of the Windows Registry Checker Tool (Scanreg.exe)
(http://support.microsoft.com/kb/183603/EN-US/ )How to Customize Registry Checker Tool Settings
(http://support.microsoft.com/kb/184075/EN-US/ )Description of Microsoft System Information (Msinfo32.exe) Tool
Method 2: Restore the System.1st FileTo restore your System.1st file, follow these steps:
NOTE: The System.1st file is a backup of the registry that is created during the final stage of a Windows installation. When you restart your computer, Windows Setup starts at the "Setting up hardware and finalizing settings" phase of setup.
If replacing the System.dat file with the System.1st file resolves the issue, the problem may be related to registry damage. Note that you may have to reinstall programs and device drivers that you installed after you installed Windows to update the new registry.
If the issue is not resolved, restore the original registry. To do this, follow these steps:
Reinstall Windows in a New FolderUse this method only after you try all of the troubleshooting steps in this article. If you reinstall Windows in a new folder you must reinstall all Windows-based programs under the new Windows installation.
For additional information, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/200378/EN-US/ )OFF2000: How to Install Windows 98 to a New Folder to Troubleshoot Problems in Office 2000
Turn Off Enhanced BIOS FeaturesMost computers have several enhanced settings that allow the computer to fully use the computer hardware. These high-speed settings can cause the system to become unstable; turning off these features may make the computer more stable. Contact your computer manufacturer for information about entering the basic input/output system (BIOS) and changing the BIOS settings. You can enter the BIOS on most systems immediately after turning on the power. Usually a keystroke, such as DEL, is required to enter the BIOS. Below are the common features that can interfere with Office programs:
WARNING: Incorrectly altering hardware BIOS settings can cause serious problems that may cause your computer to fail to start or function properly. Microsoft cannot guarantee that problems that result from the incorrect setting of hardware BIOS options can be solved. Alter the hardware BIOS settings at your own risk.
Check HardwareIf you exhaust all other troubleshooting steps and you are still receiving error messages, it is possible that one or more pieces of your hardware are incompatible with Windows or are damaged. To identify a problem with your computer hardware, contact your computer vendor.
Badly seated memory or bad memory has been reported to cause Kernel32.dll error messages. Switching memory around in the motherboard memory banks has been known to correct some of these issues.
It has also been reported that running the Atron 380 Bus Mastering Ethernet Card can cause Kernel32.dll errors. Removing this card from the computer may resolve these error messages.
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
For information about how to contact the companies mentioned in this article, visit the following Microsoft Web site:
Article ID: 218853 - Last Review: July 16, 2012 - Revision: 1.0