August 22 2008

Missing or Corrupt hal.dll

Tagged Under : , ,

There are few different ways that the “missing or corrupt hal.dll” error may present itself, with the first listing being the most common:

“Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll.
Please re-install a copy of the above file.”

Winnt_root>\System32\Hal.dll missing or corrupt:
Please re-install a copy of the above file.”

“Cannot find \Windows\System32\hal.dll”
“Cannot find hal.dll”

The “missing or corrupt hal.dll” error displays shortly after the computer is first started. Windows XP has not yet fully loaded when this error message appears.

Cause

Causes of the “missing or corrupt hal.dll” error include, naturally, a damaged hal.dll file or a hal.dll file that has been deleted or moved from its intended location. Additional causes may include a damaged or missing boot.ini file or possibly a physically damaged hard drive.

Resolution

  1. Restart the PC. The hal.dll error could be a fluke.
  2. Run a Free Registry Scan
  3. Check for proper boot order in BIOS. You might see the hal.dll error if the boot order in BIOS is first looking at a hard drive other than your main hard drive.If you’ve recently changed your boot order or recently flashed your BIOS, this may be what’s causing your problem.
  4. Run Windows XP System Restore from a command prompt. If this doesn’t work or you’re receiving the hal.dll error message before you’re able to complete this process, move on to Step 3.
  5. Repair or replace the boot.ini file. This will work if the cause of the problem is actually Windows XP’s boot.ini file and not the hal.dll file, which is often times the case.
  6. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn’t properly configured, you may receive the hal.dll error.
  7. Restore the hal.dll file from the Windows XP CD. If the hal.dll file is truly the cause of the problem, restoring it from the original Windows XP CD may do the trick.
  8. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.
  9. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch. While this will almost certainly resolve any hal.dll errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.If you can’t gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.
  10. Finally, if all else has failed, including the clean installation from the last step, you’re most likely facing a hardware issue with your hard drive. Replace the hard drive and then perform a new installation of Windows XP.

August 19 2008

Oleaut32.dll

Tagged Under : , ,

If you receive one or more of these error messages when you attempt to open Microsoft Office applications then you have the incorrect version of oleaut32.dll installed on your system.

There was a problem starting the Office Assistant. Would you like to try reinstalling it?

The file ‘OLEAUT32.DLL’ is out of date. This program requires a newer version.

Microsoft Excel requires file OLEAUT32.DLL to run. The version of OLEAUT32.DLL that is on your computer is older than the one required by this version of Microsoft Excel.

Please run Setup again, and select the Reinstall option to install the correct version of the file.

The required file OUTLRPC.dll cannot be found in your path, please reinstall Microsoft Outlook.

The AGENTSVR.EXE file is linked to missing export OLEAUT32.DLL:277.

Microsoft FrontPage is not installed properly on this system and cannot function. Please reinstall Microsoft FrontPage.

Click OK to exit.

To resolve this issue, you may attempt to use the Detect and Repair function, install the correct version of the oleaut32.dll file or, perhaps the easiest method, download the latest security pack from the Windows website. Security packs often contain fixes and updated versions of files such as oleaut32.dll, providing you with a means to remedy many of the problems that might surface on your computer. This is especially true of older problems or problems with older versions of applications.

August 15 2008

Gwmspi.dll

Tagged Under : ,

Unable to open your default mail folders. MAPI was unable to load the information service GWMSPI.DLL

This is another error that typically occurs when you try to open Microsoft Outlook. This error is usually only prevalent in Microsoft Outlook 2000 Standard edition and when you click OK on the error message you will be unable to access the Outlook program or any of your emails. This error is caused by a software and feature conflict between Outlook and Novell, and you have added a messaging profile for both applications to the same Windows messaging profile.

To resolve this error ensure that you set up two Windows messaging profiles, one each for Novell and Outlook. Uninstalling and reinstalling either application, and attempting to install them in a different order will not help you to work around this problem.

August 13 2008

Wmpdxm.dll and dxmasf.dll

Tagged Under : ,

Cannot Complete Windows Media Player 9/10 Series Setup

This error message may be displayed when you attempt to install Windows Media Player version 9 or version 10. The installation will fail and you may also begin to experience problems when attempting to use Internet Explorer.

This error usually occurs because the wmpdxm.dll file has become damaged or corrupt, or has not been registered properly. In order to counteract this problem you should first exit all applications, especially the Media Player setup screens and then follow these instruction to register the library.

  • Click Start
  • Click Run
  • Type regsvr32 msdxm.ocx
  • Click OK
  • Click Start
  • Click Run
  • Type regsvr32 dxmasf.dll
  • Click OK

August 08 2008

Kernel32.dll

Tagged Under : ,

“Explorer caused an invalid page fault in module Kernel32.DLL”

“Iexplore caused an invalid page fault in module Kernel32.DLL”

“Commgr32 caused an invalid page fault in module Kernel32.dll”

“Error in Kernel32.dll”

[PROGRAM NAME] has caused an error in Kernel32.dll”

This error message typically occurs when closing an open Internet Explorer window and you may receive similar error messages when closing Outlook or Outlook Express windows. It is most common for this error to occur when you have multiple Internet Explorer and Outlook or Outlook Express windows open.

This error can occur when using all of the email scan, Internet scan, and Internet filter functions in McAfee security software. The quickest way to prevent the error from occurring is to disable these features. However, you should contact McAfee to inquire about a fix for this issue in order that you can continue to enjoy the protection that these features of the software provide.

August 04 2008

Ole32.dll

Tagged Under : ,

Clipart cannot complete the operation.
Interface not registered. Error code 0×80040155

This error is usually displayed when you attempt to add Clipart to a Word document. It occurs because the ole32.dll library has not been registered correctly and, as such, Windows cannot use the information it contains. This, in turn, may be caused by damage to your Windows installation.

In order to resolve this problem you should first attempt to register the ole32.dll library. This is done through the Run command Window as follows:

  • Click Start
  • Click Run
  • Type regsvr32 ole32.dll in the dialog box and click Open
  • Click OK
  • Click OK on the message window that is displayed

If this does not work then you will, instead, need to reinstall your Windows operating system. This will replace and, therefore, repair any of the installation files such as Dynamic Link Libraries that have become damaged.

August 01 2008

Urlmon.dll

Tagged Under : ,

Iexplore caused an invalid page fault in module Urlmon.dll

The error message above may be displayed when you attempt to run or open Internet Explorer. This occurs when there are several entries for Quick View Plus that appear within the Windows registry. Most applications require and indeed demand only one registry entry each, although more are possible in some cases.

Resolving this issue requires the editing of the Windows registry and the use of the registry editor. If done incorrectly, this can cause serious errors with software and with your system as a whole. If you are unsure how to use registry editor properly then seek advise from somebody else.

Remove all but one of the references to Quick View Plus that appear in the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\InternetSettings\Accepted Documents