Microsoft KB Archive/290361

= How to troubleshoot Office Kernel32.dll errors in Windows 98 =

Article ID: 290361

Article Last Modified on 1/31/2007

-

APPLIES TO


 * Microsoft Excel 2002 Standard Edition
 * Microsoft Outlook 2002 Standard Edition
 * Microsoft PowerPoint 2002 Standard Edition
 * Microsoft Word 2002 Standard Edition
 * Microsoft Windows 98 Standard Edition

-



This article was previously published under Q290361



For a Microsoft Office 2000 version of this article, see 218853.

WARNING:This information is preliminary and has not been confirmed or tested by Microsoft. Use only with discretion.



SUMMARY
This article contains information about how to troubleshoot and remove invalid page faults that occur in module Kernel32.dll when you work with a Microsoft Office XP program on a computer that is running Microsoft Windows 98. A Kernel32.dll message is similar to the following

caused an invalid page fault in module Kernel32.dll

where  is the name of the Office XP program that you are using.

For more information about troubleshooting OfficeKernel32.dll issues in earlier versions of Office, click the following article numbers to view the articles in the Microsoft Knowledge Base:

218873 Troubleshooting Office 2000 Kernel32.dll errors under Windows 95

190517 OFF: Troubleshooting Office Kernel32.dll Errors Under Windows 98



MORE INFORMATION
When an invalid page fault occurs, an unexpected event occurs in Windows. An invalid page fault indicates that a program improperly tried 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 damage other program code in that area of memory.

An invalid page fault can occur when parameters are passed between programs and Windows. An invalid parameter can cause a program to run invalid instructions, which results in an invalid page fault. This behavior typically 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 can increase the time that it takes to identify the problem.

Determine Whether the Problem Is Documented
Many 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:

&quot;invalid page fault&quot; kernel32.dll

NOTE: To narrow your search, you can add the program name in which the problem occurs at the end of the query.

Check for a Valid Temporary Folder, and Delete Temporary Files
There 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:  Restart your computer. Press and hold down the CTRL key until the Windows 98 Startup menu appears. On the Windows Startup menu, select Command Prompt Only, and then press ENTER. Type set and then press ENTER. Note the location of the TEMP variable. Change to the folder that you noted in step 3. For example, if TEMP is set to C:\Windows\Temp, type the following line, and then press ENTER:

cd\windows\temp

If the folder that you noted in step 2 does not exist, create the folder. To create the folder, type the following command, and then press ENTER:

md c:\windows\temp

 Delete any temporary files in this folder. Temporary files have a .tmp file name extension. To delete these files, type the following line, and then press ENTER:

del *.tmp



NOTE: Do not delete these files when you are running Windows, because Windows, or a Windows-based program, may be using one of these files.

Start Windows in Safe Mode
Windows 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 can help you identify the problem. To start Windows in Safe mode and make the additional troubleshooting features available, follow these steps:
 * 1) Click Shut Down on the Start menu. Click Restart and then click OK.
 * 2) Press and hold down the CTRL key until the Windows 98 Startup menu appears.
 * 3) On the Windows Startup menu, select Safe Mode, and then press ENTER. Windows starts in Safe mode.
 * 4) Perform the same operation that caused the error.

When you use Safe mode or when you disable 32-bit protected-mode drivers, Windows does not process protected-mode drivers (the Autoexec.bat and Config.sys files). Therefore, the CD-ROM drive is not available. To use Safe mode with CD-ROM drive support, determine whether Windows uses protected-mode drivers for the CD-ROM drive. If Windows is using protected-mode drivers, install the real-mode (MS-DOS) drivers for the CD-ROM drive. The real-mode drivers are typically located on a disk that is included with the CD-ROM drive or with the computer. The drivers are installed in the Autoexec.bat and Config.sys files.

For additional information about determining whether Windows is using protected-mode drivers, click the article number below to view the article in the Microsoft Knowledge Base:

151634 Protected-Mode CD-ROM Drive Support in Windows

Check the Hard Disk for Disk Errors and Fragmentation
Use the ScanDisk program to check the hard disk for lost clusters and other file allocation table (FAT) errors and to test the integrity of the hard disk. You can also use the ScanDisk program to repair any of these problems. To run ScanDisk, follow these steps:
 * 1) On the Start menu, point to Programs.
 * 2) Point to Accessories, point to System Tools, and then click ScanDisk.
 * 3) Click the drive that you want to check for errors, and then click Start.

Hard disks that are very fragmented can affect the performance and reliability of Office programs and other tasks in Windows. To resolve this problem, run Disk Defragmenter to defragment the hard disk drive. To run Disk Defragmenter, follow these steps:
 * 1) On the Start menu, point to Programs.
 * 2) Point to Accessories, point to System Tools, and then click Disk Defragmenter.
 * 3) Click the drive that you want to defragment in the Which drive do you want to defragment list, and then click OK.

Turn Off the CD-ROM Drive Cache
If 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 it does reduce performance. To turn off the CD-ROM drive cache, follow these steps:
 * 1) Click Start, point to Settings, and then click Control Panel.
 * 2) In Control Panel, double-click System.
 * 3) Click the Performance tab, and then click File System.
 * 4) Click the CD-ROM tab. In the Optimize access pattern for list, click to select No Read-Ahead
 * 5) Drag the Supplemental Cache Size slider to the left position (the Small setting), and then click OK.

If you are using real-mode CD-ROM drivers, the drive may be cached by the Smartdrv.exe program. If this is the case, the Smartdrv.exe program must be made unavailable in the Autoexec.bat file. To do this, follow these steps:
 * 1) Click Start, point to Programs, point to Accessories, point to System Tools, and then click System Information.
 * 2) On the Tools menu, click System Configuration Utility.
 * 3) Click the Autoexec.bat tab.
 * 4) Click to clear the Smartdrv check box, and then click OK.
 * 5) To restart the computer for the change to take effect, click Yes.

Verify That the CD-ROM Is Clean and Unscratched
If the error message appears while you are installing from a CD-ROM, verify that the CD-ROM is clean. You can wipe the CD-ROM with a soft, lint-free cloth. Also ensure that there are no large scratches on the CD-ROM. If the CD-ROM is damaged and unreadable, error messages may appear during installation.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

266700 OFFXP: Troubleshoot Installation from Compact Disc Media

Check for a Damaged Swap File
The Kernel32.dll error also can appear if your Windows swap file is damaged. 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:  On the Start menu, click Shut Down.</li> In the Shut Down Windows dialog box, click Restart in MS-DOS Mode, and then click OK.</li> At the MS-DOS prompt, change to the Windows folder by typing the following command

cd :\Windows

where  is the drive letter that contains the Windows folder. Typically, this is drive C.

NOTE: The swap file exists in the Windows folder if Windows manages virtual memory settings on your computer. If you chose to manage virtual memory settings on the computer, the swap file exists at the root level of the hard disk. To determine whether Windows manages virtual memory settings, right-click My Computer, click Properties, click Performance, and then click Virtual Memory.</li> To delete the swap file, type the following:

del Win386.swp

</li> After you delete the swap file, restart the computer.</li></ol>

Damaged Custom Profile
Damaged custom profiles also sometimes cause Kernel32.dll errors. Deleting and recreating the profile can sometimes resolve this problem.

If you are using the Office system policy templates that are included in the Microsoft Office XP Resource Kit, you must use the version of the System Policy Editor that is included in the Microsoft Office XP Resource Kit.

NOTE: The System Policy Editor that is included with Windows 98 does not work with Office XP. Be sure to install the latest version of the System Policy Editor from the Microsoft Office XP Resource Kit or from Windows NT Server 4.0 with Service Pack 6. You can download OrkTools.exe, a self-extracting file that contains Poledit.exe and the Office system policy templates, from the following Microsoft Office XP Resource Kit Web site:

http://www.microsoft.com/office/ork/xp/appndx/appa18.htm

Remove and Reinstall the Program
If the problem occurs after you run the Setup program, some of the dynamic link library (.dll) files may be damaged. To troubleshoot this problem, first completely remove the program. After you completely remove the program, reinstall the program. Follow these steps to reinstall:
 * 1) Click the Start button, point to Settings, and click Control Panel.
 * 2) Double-click Add/Remove Programs. Click Microsoft Office XP, and then click Add/Remove.
 * 3) In the Microsoft Office XP Maintenance Mode dialog box, click Repair Office, and then click Next.
 * 4) In the Reinstall/Repair Microsoft Office XP dialog box, click Reinstall Office, and then click Install.

Check for Software Updates
Outdated and incompatible software also can 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 Viruses
If a virus is present on your computer and has damaged some files, Kernel32.dll error messages can 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 Damage
When 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. You may have 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 Checker
Windows includes a tool called Registry Checker that can scan your registry for damage, and, if necessary, restore a backup of the registry. Follow these steps to use Registry Checker to scan your registry:  Click Start, point to Programs, point to Accessories, point to System Tools, and then click System Information.</li> On the Tools menu, click Registry Checker. You may receive the following error message:

Windows encountered an error accessing the system registry. Windows will restart the computer and repair the system registry for you.

If you receive this error message, proceed to step 3. If you do not receive the error message, your registry is okay.</li> To restart your computer, click OK.</li> Press ENTER when the Windows 98 Startup menu appears.</li> At the command prompt, type Scanreg and then press ENTER.</li> In the Check Your Registry dialog box, press ENTER. You should receive the following prompt:

Windows found an error in your system files and restored a recent backup of the files to fix the problem.

</li> Press ENTER to restart your computer.</li></ol>

Windows stores five backups of your registry. If the registry has been damaged for a long period of time, you may need to use &quot;Method 2: Restore the System.1st File&quot; to determine whether your registry is damaged.

For additional information about Registry Checker, click the article numbers below to view the articles in the Microsoft Knowledge Base:

183887 Description of the Windows Registry Checker Tool (Scanreg.exe)

183603 How to Customize Registry Checker Tool Settings

184075 Description of Microsoft System Information (Msinfo32.exe) Tool

Method 2: Restore the System.1st File
To restore your System.1st file, follow these steps:  Restart your computer. Press and hold down the CTRL key until the Windows 98 Startup menu appears.</li> <li>On the Windows Startup menu, select Command Prompt Only, and then press ENTER.</li> <li>To remove the file attributes from the backup of the registry, type the following command, and then press ENTER:

c:\windows\command\attrib -h -s -r c:\system.1st

</li> <li>To remove the file attributes from the current registry, type the following command, and then press ENTER:

c:\windows\command\attrib -h -s -r c:\windows\system.dat

</li> <li>To rename the registry, type the following command, and then press ENTER:

ren c:\windows\system.dat *.dax

</li> <li>To copy the backup file to the current registry, type the following command, and then press ENTER:

copy c:\system.1st c:\windows\system.dat

</li></ol>

Restart the computer. If the Windows 98 Startup menu appears, choose Safe Mode, or choose Safe Mode With Network Support if you need network connectivity.

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 &quot;Setting up hardware and finalizing settings&quot; 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. 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: <ol> <li>Restart your computer. Press and hold down the CTRL key until the Windows 98 Startup menu appears.</li> <li>On the Windows Startup menu, select Command Prompt Only, and then press ENTER.</li> <li>Type the following commands:

c:\windows\command\attrib -s -h -r c:\windows\system.dat

copy c:\windows\system.dax c:\windows\system.dat

Press Y and then press ENTER when you are asked to overwrite the existing System.dat file.</li> <li>Restart the computer.</li></ol>

Reinstall Windows in a New Folder
Use 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, click the following article number to view the article in the Microsoft Knowledge Base:

290121 How To Install Windows 98 to a New Folder to Troubleshoot Problems in Office XP

Turn Off Enhanced BIOS Features
Most 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 can 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 you turn on the power. Typically a keystroke, such as DEL, is required to enter the BIOS. The following are the common features that can interfere with Office programs:
 * Memory shadow RAM
 * Video shadow RAM
 * Internal cache
 * External cache
 * Built-in virus protection

Newer chipsets may have more advanced features, such as memory wait states, that can cause errors. Most BIOS installation programs have an option to load the BIOS default settings. This option typically disables all advanced features.

WARNING: Incorrectly altering hardware BIOS settings can cause serious problems that can cause your computer to fail to start or function correctly. 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 Hardware
If 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, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:

65416 Hardware and Software Third-Party Vendor Contact List, A-K

60781 Hardware and Software Third-Party Vendor Contact List, L-P

60782 Hardware and Software Third-Party Vendor Contact List, Q-Z

Additional query words: krnl32 inf Msiexec caused an Invalid Page Fault in Module Kernel32.dll

Keywords: kbtshoot KB290361

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.