Article ID: 245050 - Last Review: February 8, 2007 - Revision: 4.5 Troubleshooting Office Kernel32.dll errors under Windows 98This article was previously published under Q245050
For a Microsoft Office XP version of this article, see 290361
(http://support.microsoft.com/kb/290361/
)
.
For a Microsoft Office 2000 version of this article, see 218853
(http://support.microsoft.com/kb/218853/
)
.
For a Microsoft Office 95 version of this article, see 190517
(http://support.microsoft.com/kb/190517/
)
.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/
)
Description of the Microsoft Windows registry WARNING: The information in this article has not been confirmed or tested by Microsoft. Some or all of the information in this article has been taken from unconfirmed customer reports. ANY USE BY YOU OF THE INFORMATION PROVIDED IN THIS ARTICLE IS AT YOUR OWN RISK. Microsoft provides this information "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. On This PageSUMMARY
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
will be similar to the following:
Program name caused an invalid page fault in module Kernel32.dll
For additional information about troubleshooting Microsoft Office Kernel32.dll issues under Microsoft Windows 95, please see the following article in the Microsoft Knowledge Base: 164519
(http://support.microsoft.com/kb/164519/EN-US/
)
Troubleshooting Office Kernel32.dll Errors Under Windows 95
MORE INFORMATION
When an invalid page fault occurs, an unexpected event occurs in the
Microsoft Windows operating system. 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 the Windows 98 operating system. 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. IMPORTANT: 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 take 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.dll NOTE: It may be helpful to add the program name in which the problem occurs at the end of the query to narrow your search.
For additional information on related Kernel32.dll error messages, please
see the following articles in the Microsoft Knowledge Base:
162398
(http://support.microsoft.com/kb/162398/EN-US/
)
First Aid 97 causes invalid page fault
166125 (http://support.microsoft.com/kb/166125/EN-US/ ) Problems with Millennium and Mystique video cards when you use Office 97 programs 162153 (http://support.microsoft.com/kb/162153/EN-US/ ) Problems after returning computer from suspended state Do Not Install ClipArt, Binder, and Find FastOn some systems, cancellation of the installation of ClipArt, Binder, and Find Fast will resolve this problem during Setup.These components are installed with a Typical or Custom installation. You must perform a Custom installation and choose not to install these components. To do this, follow these steps:
Check for a Valid Temporary Folder and Excess Temporary FilesThere should be at least 10 megabytes (MB) of free space on the hard disk drive that contains the temporary folder. To check for a temporary folder and to delete excess files from that folder, follow these steps:
Start Windows in Safe ModeWindows 98 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 98 also has troubleshooting features that may help you identify the problem. To start Windows 98 in Safe mode and make the additional troubleshooting features available, follow these steps:
151634
(http://support.microsoft.com/kb/151634/EN-US/
)
Protected-mode CD-ROM drive support in Windows
For additional information about installing real-mode drivers for the
CD-ROM drive, please see the following article in the Microsoft Knowledge Base:
167069
(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 drive for lost clusters and other file allocation table (FAT) errors and test the hard disk drive integrity. You can also use the ScanDisk program to repair any of these problems. To run ScanDisk, follow these steps:
Disable the CD-ROM Drive CacheIf the error message appears while you are reading from a CD-ROM drive, try disabling the CD-ROM drive cache. This may make the drive more reliable but reduces performance. To disable 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: 174713
(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 re-creating the profile can possibly resolve this problem.If you are using the Microsoft Office 97 system policy templates that are included in the Microsoft Office 97 Resource Kit, you must use the version of the System Policy Editor that is included in the Microsoft Office 97 Resource Kit or the Microsoft Windows NT 4.0 Resource Kit. Use the Office 97 Templates for Windows 95 for Microsoft Windows 98. NOTE: You can download Policy.exe, a self-extracting executable file containing Poledit.exe, from online services. Download this file from the following Microsoft World Wide Web site:
http://www.microsoft.com/office/ork/appa/appa.htm#dex4
(http://www.microsoft.com/office/ork/appa/appa.htm#dex4)
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, completely remove the program. For additional information, please see the following articles in the Microsoft Knowledge Base:158658
(http://support.microsoft.com/kb/158658/EN-US/
)
How to completely remove Microsoft Office 97
133274
(http://support.microsoft.com/kb/133274/EN-US/
)
Setup "Remove All" doesn't remove all files
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 drive 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.The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products. For more information about hardware and software vendor contact information, visit the following Microsoft Web site: http://support.microsoft.com/gp/vendors
(http://support.microsoft.com/gp/vendors)
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 drive 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. If a virus is found on your Setup disk, you must obtain a new set of disks.NOTE: Do not run a virus detector terminate-and-stay-resident (TSR) program while you run any of the Microsoft Office programs, including the Setup program. Run a virus detector before you run the Setup program, and then disable it. If you determine that you have a Setup disk that was damaged by a virus, you can order a new set of disks. IMPORTANT: Microsoft Office 97 Service Release CD-ROMs and replacement CD-ROMs are no longer available from Microsoft. For more information about obtaining the Microsoft Office 97 Service Release 1 (SR-1) and Microsoft Office 97 Service Release 2 (SR-2), click the following article number to view the article in the Microsoft Knowledge Base: 192874
(http://support.microsoft.com/kb/192874/
)
An overview of Microsoft Office 97 Service Release 2 (SR-2)
Check for Registry CorruptionWhen you start Windows 98 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 98 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) 183603 (http://support.microsoft.com/kb/183603/EN-US/ ) How to customize Registry Checker Tool settings 184075 (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:
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 98 to update the new registry. If the issue is not resolved, restore the original registry. To do this, follow these steps:
Disable DMA for the CD-ROM During InstallationThere are unconfirmed reports that disabling Direct Memory Access in Device Manager for some CD-ROM drives may prevent Kernel32.dll errors.For additional information, please see the following article in the Microsoft Knowledge Base: 190630
(http://support.microsoft.com/kb/190630/EN-US/
)
Kernel32.dll and other error messages when you install Office 2000 products with Direct Memory Access (DMA) enabled on Windows 95 or Windows 98
Reinstall Windows in a New FolderUse this method only after you have tried 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 98 installation.For additional information, please see the following article in the Microsoft Knowledge Base: 190040
(http://support.microsoft.com/kb/190040/EN-US/
)
Installing Win 98 to new folder to t-shoot Office problems
Disable 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; disabling 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 Microsoft Office programs:
Memory Shadow RAM
Newer chipsets may have more advanced features (such as memory wait states)
that may cause errors. Most BIOS installation programs have an option to
load the BIOS default settings. This option usually disables all advanced
features.
Video Shadow RAM Internal Cache External Cache Built-in Virus Protection 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 98 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. APPLIES TO
| Article Translations
|
Back to the top
