30 common dll errors
A lot of DLL errors are very specific to what you are doing when the error occurs. This is because a DLL can contain such a large number of different functions, of which you probably only require one or a small number at a time. When attempting to deal with a DLL error you should record as much information as possible. You should attempt to regenerate the error in order to help determine the exact reason.
In a bid to help you research any problems you might be suffering with DLL files we have included a list of some of the most common errors below. There are approximately 30 errors, and while this may only touch on the surface of the potential problems, they are a varied range of errors so give good insight into how you may be able to tackle similar errors on your own computer.
User Interface Failure:
The Logon User Interface DLL msgina.dll failed to load.
Contact your system administrator to replace the DLL, or restore the original DLL.
This error occurs on machines using the Windows 2000 operating system. Specifically, it occurs if you use Windows 2000 with Service Pack 3 installed. More recent service packs and older service packs do not encounter this problem.
This error occurs when you first log on to your computer, because several DLLs and executable files that are dependent on one another attempt to start at the same time. If the files start in the wrong sequence then you will receive this error.
In order to resolve this error users should download the latest Windows 2000 service pack, because this error is not present in any apart from version 3.
Iexplore caused an invalid page fault in module Tps108.dll
When attempting to open Internet Explorer version 5.5 on your system you may receive the error message above, or a GPF (General Protection Fault) that mean the application must be closed. A similar error may also be encountered when you attempt to open My Computer or Windows Explorer.
Tps108.dll is a third party DLL and this error only occurs if said DLL is resident on your computer. This DLL can prevent IE and Windows Explorer from working properly.
Any of the following solutions should prove effective for resolving this error:
Disable third party extensions within your Internet Explorer application – Click Tools, Internet Options, and then Advanced. Within the Settings section of the page, locate the Browsing header and remove the tick from Enable third-party browser extensions (requires restart). Click OK and restart IE.
Disable tps108.dll – Disabling the extension will enable Internet Explorer and Windows Explorer to work properly on your system. Locate the dll using the Windows search function, and note the path to the file. Click Start, then Run, type cmd, and press Enter. Type regsvr32 /u <<enter path here>>\tps108.dll. Click OK and then restart your computer.
Explorer caused an exception 6d007fh in module Webcheck.dll at…
Some users have reported receiving the error message above when their computer is idle as well as error messages when they click the Synchronize button in Internet Explorer. This problem occurs for people running Internet Explorer version 5 only.
The error occurs simply because you are using the incorrect version of webcheck.dll. You should use the version that was included with Internet Explorer 5.
Resolution of this problem is quick and simple – reinstall Internet Explorer 5 on your system and restart your computer. You should not receive these errors any longer.
Microsoft Internet Explorer has encountered a problem and needs to close. We are sorry for the inconvenience.
If you were in the middle of something, the information you were working on might be lost.
Restart Internet Explorer
Please tell Microsoft about this problem
We have created an error report that you can send to help us improve Outlook Express. We will treat this report as confidential and anonymous.
If you receive the error message above when attempting to browse the Internet using Internet Explorer version 6 then a third party IE add-on has added shell64.dll on your computer.
Resolution of this problem is relatively simple – users can choose to either disable or delete the shell64.dll file from their system. The file itself is usually located within the system32 folder of your computer, although this may be different so do check thoroughly before taking any action.
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:
Iexplore caused an invalid page fault in module Mshtml.dll…
This error can occur when browsing the Internet using Internet Explorer version 5 or earlier. It is often caused by the use of High or True color resolution within the settings of Internet Explorer, and can typically be resolved quickly and easily.
Reduce the settings of the color palette to 256 color. This error usually occurs on computers that have a setting of High color or True color, which are 16 bit and 24 bit respectively.
Request a driver update from the manufacturer of your video card. Ensure that the driver version coincides with the version of Windows that you use.
Actxprxy.dll and shdocvw.dll
Internet Explorer Script Error
An error has occurred in the script on this page.
Error: No such interface supported
Do you want to continue running scripts on this page?
This error usually occurs when you attempt to open a link in a new window. The new window will not display the page you are attempting to open and you will, instead, receive this error message. Typically, this error is displayed, because information within the Windows registry that pertains to Internet Explorer, and specifically one of the DLLs listed, has become damaged.
In order to resolve this issue, you will need to register the DLLs again, in order that the information they contain can be updated and fixed. Click Start and then Run to open the Run dialog box.
Type regsvr32 actxprxy.dll in the box and click OK, and then OK again on the resulting message window.
Open the Run dialog box again, type regsvr32 shdocvw.dll, click OK, and then OK again on the message that appears.
Iexplore caused an Invalid Page Fault in module 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.
IEXPLORE caused an invalid page fault in module MSJAVA.DLL at 137:7c025b57
In order to resolve this issue, download the latest Java machine from the Microsoft website, restart Internet Explorer and attempt to navigate to the page that was causing the error.
This program has performed an illegal operation and will be shut down
This error occurs when attempting to open Windows, but only with versions of Windows that were added with a Microsoft Works suite. When you click to view the details of the error you will receive a further error message stating that an exception occurred in module msvcrt.dll.
This error most commonly occurs because files and DLLs associated with the Word add in for Works have become corrupt or damaged. This can happen for a number of reasons, as discussed earlier in this guide.
In order to resolve this issue and continue to use Word, remove the Works Suite Add-in for Microsoft Word entry from the Add/Remove programs function of Control Panel. Using Windows Search, find a file called normal.dot and rename this. Restart your computer so that you receive a message stating that Windows can not find all components of Works. Insert the Works disk, locate setup.exe from the WordAdd folder and double click it to reinstall the add-in and use Word normally.
Microsoft Word has encountered a problem and needs to close. We are sorry for the inconvenience
This error is associated with Hewlett Packard 1200 and 3200 printer drivers, especially when you then install other HP printer drivers. This is because all HP printers require the hpafd32.dll file, and many require the later versions of this DLL. While in the majority of cases, the dll will update on installation, this isn’t always true. If you install another printer after using the 1200 or 3200 printers from HP, the dll does not update as required.
If you need to install a new printer driver then remove all of the components of the old HP printer and install the new printer as normal. This should install the updated version of the necessary dll. Failing this, contact HP support with the exact details of your problem and they will provide a solution.
Cannot load Library DLBAPRP.dll
This error message may display when you attempt to print a Word document and you have one of several Lexmark or Dell printers installed on your computer. In a small number of cases, the error can also occur when attempting to save a document. In either case the document will not print or save as you requested.
There is one workaround that should work in the majority of cases, otherwise you will need to contact the printer manufacturer to request a resolution to this problem.
Copy all the printer driver files from the drive:\Windows\System32\Spool\Drivers\W32x86 folder into the main Windows/System32 folder.
Clipart cannot complete the operation.
Interface not registered. Error code 0x80040155
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:
Type regsvr32 ole32.dll in the dialog box and click Open
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.
The command cannot be performed because a dialog box is opened, click OK then close dialog-boxes to continue
This error typically occurs when the officeav.dll library, the Office plug-in from Norton AntiVirus, has become corrupted or damaged. The error message above will be displayed when you attempt to open a Word document.
Dll files required by applications are often installed as and when needed. As such, removing the officeav.dll, or in this case renaming it, will enable you to add the Office plug-in through Norton and register a clean and undamaged version of the dll. To do this, follow these instructions:
Locate officeav.dll by using the Windows Search function
Rename it as officeavold.dll or officeav.old
Restart your computer
The MSIEXEC file is linked to missing export MSI.DLL:222
This error message is displayed during installation of Office applications, if the installation disks have become damaged or corrupted in any way. This can occur for numerous reasons. For instance, if you have downloaded the installation files and the download was interrupted before it could complete then this may cause damage to the installation files. Damage to an installation disk can also cause this error.
It is necessary to update the installer that is resident on your hard drive. This is done by visiting the Microsoft website, and downloading installer version 2.0. Once you have done this, try again to run setup. Everything should now work.
Wmpdxm.dll and dxmasf.dll
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.
Type regsvr32 msdxm.ocx
Type regsvr32 dxmasf.dll
The file wmp.dll has a version number of 184.108.40.20675 where 220.127.116.1180 was expected. Windows Media Player is not installed properly and must be reinstalled.
This error message can be misleading in some respects. It is typically displayed whenever you attempt to open Windows Media Player but, despite the content of the error, uninstalling and reinstalling the Windows Media Player will have no effect in resolving this issue.
The issue does relate to a conflict in dll versions, however, as the message suggests and can be resolved using the following technique:
Type c:\windows\inf\unregmp2.exe /UpdateWMP
explorer has caused an error in wmp.dll and needs to close
wmp.dll is the main library used by the Windows Media Player and there are a number of problems that can surface because of this file. In this case, it is highly likely that the dll has not been registered properly or at all, or it has become corrupt for one reason or another. Re-registering the dll will usually resolve this issue and enable you to continue using Media Player on your computer.
Type regsvr32 wmp.dll
You should receive a message stating that the registration was successful – click the OK button
Attempt to open and use Windows Media Player
Msvcp60.dll and msvcrt.dll
Msvcp60.dll is linked to the missing export Msvcrt.dll
This error usually occurs when you attempt to open Clip Gallery 5.0 although it may occur in other circumstances as well. The most likely cause is that you have the incorrect version of msvcrt.dll installed on your computer. In order to resolve this issue you should either repair your version of the Microsoft operating system or replace the msvcrt.dll file installed on your system. How to repair Windows will depend on the version that you have installed and also the settings on your computer. In order to replace the dll follow these instructions:
Search for msvcrt.dll using the Windows search function
Rename it to something like msvcrt.old
Restart your computer in MSDOS mode
Type cd system
Type ren msvcrt.dll msvcrt.old
Open Add/Remove Programs
Outlook.exe caused an ‘access violation’ fault in module Riched20.dll at 014f:4802bc95
You may receive this error message when attempting to start Microsoft Outlook. When you click OK on the error message the application will close down and you will be unable to access Outlook. Alternatively you might receive a similar error message when you attempt to create a new email. You will be unable to write the email but you should still have access to the Outlook program.
The solution to this problem is to first rename the riched20.dll file and then to repair your version of Outlook. Rename the file so that it will not be called by any other application and so that you do not mistakenly copy over another dll that may be required for other applications. One method to ensure this does not happen is to rename the file riched20.old.
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.
Omint.dll and outlib.dll
Cannot start Outlook. A required component is missing OMINT.DLL. Please run setup again
This error only occurs when trying to start the older Outlook 98 version. It means that you have an incorrect version of outlib.dll installed on your computer that needs updating or backdating. Another possible cause, although less likely, is that the registry entries were not updated when you first ran Outlook on your system.
In order to resolve this issue you should first ensure that you are logged on to Windows NT as an administrative level user and you should then reinstall Outlook 98 on your computer. This will ensure that all registry entries are updated and that you have the proper version of all the necessary dll libraries installed. If necessary you will need to contact a network or computer administrator to either grant the appropriate access or to perform this for you.
missing WAB.dll file
This error occurs when attempting to open or use the Windows Address Book. In turn you will be unable to access the features that it offers until you have resolved the problem. There are two likely causes of this problem and both require similar steps to resolve. The Windows Address Book dll, or wab.dll is either missing or has become damaged or corrupt. It may also be possible that you have an incorrect version of the wab.dll library installed on your computer, but again these steps will resolve the issue if this is the cause.
Locate the wab.dll file on your system, and rename it something like wab.old. This will prevent Windows from attempting to access the file it is corrupt and enable you to add a clean and undamaged version. If the file does not exist then proceed with the following steps anyway. Ensure that you are logged on to your computer as an administrator or with administrator privileges and then remove and reinstall Outlook Express. Outlook Express contains the Windows Address Book files, including wab.dll, so this reinstallation will ensure that everything now works correctly.
When printing a PowerPoint presentation you may receive the above error message. The document will stop printing, meaning that you will not have a hard copy of the entire presentation. This error occurs on computers using PowerPoint 2000 Standard Edition, although may occur on other versions with a slightly different error message, but under the same circumstances.
This error is usually caused because Background Printing has been enabled on your computer. This means that a temporary version of the file is stored on your system before printing commences. It is during this process that the error occurs. To resolve the problem, disable background printing by following these instructions:
Select the Print tab
Remove the check from the Background Printing checkbox
Microsoft PowerPoint “hlink.dll” can’t be loaded
Again, this problem can occur for one or more of several reasons. If the hlink.dll library, that is required by PowerPoint, has become damaged or corrupt then you will receive this error when attempting to view a PowerPoint Presentation. The library may also be missing or it may the incorrect version compared to the version that PowerPoint requires.
Resolution of this problem means the removal and addition of the hlink.dll file again. The hlink.dll library can be found on your Windows installation disk and is installed as part of the Internet Explorer installation. As such, you should first locate and delete or rename the existing hlink.dll file. Then, ensure that you have administrative privileges on your computer and remove and reinstall Internet Explorer from your installation disk. Restart your computer to refresh the required files.
There was a problem starting the Office Assistant. Would you like to try reinstalling it?
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.
The file ‘OLEAUT32.DLL’ is out of date. This program requires a newer version.
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.
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.
As you can see from this list, many of the problems are very specific to the program you are attempting to use. In some cases the error message does not necessarily indicate that the problem is associated with a dll file, while in other cases it may indicate a dll problem when the problem is associated with another file. This is why it is often best to research the exact problem that you are experiencing to ensure that you are getting the most relevant and useful information available to successfully and cleanly repair any errors.
DLL File Conclusion
Dll files are essential to the proper running of your computer. A Dynamic Link Library is essential an executable file that contains a long list of different functions. Applications and even your operating system can call a dll library and make a declaration for one specific function within this list. By doing so, the amount of code needed to perform this particular function can be greatly reduced, often replacing tens or even hundreds of lines of code with just five or six lines. This, in turn, means that the running application requires less system memory (RAM) in order to run.
Dlls are used by virtually all Windows based computers and applications, as well as a number of other operating systems. There popularity and the vast number of them that are usually included on your system makes them a prime location for system and application errors. When a dll becomes corrupt or damaged it may fail to work properly. Having the incorrect version of a dll will also cause errors, while a missing dll will almost certainly cause problems with any application that requires its use.
The registry of your computer contains a number of entries that are concerned primarily with the use of Dynamic Link Libraries. When these registry entries are incorrect you are also prone to receive errors with the use of software, hardware, or system functions that rely on making a call and declaration to these libraries. This may require the editing of the Windows registry using the registry editor. This is not advised if you do not have the knowledge of confidence to do so, because incorrectly altering the registry can cause more serious errors than you are already experiencing.
This guide is meant as an all round look at potential dll errors. We have listed some of the more common errors in order that you can learn how these errors are combated. With many thousands of different DLLs and the possibility of a number of errors for each it would be impossible to list each one in a guide of this size. Research the specific problem you are experiencing, and attempt to generate the same error again so that you may learn whether it is a specific function of an application, or the running of that application that is causing the error. Search online for help with the problem, and where necessary download and install any missing dlls onto your computer. Hopefully you should be able to resolve the error and regain a computer in fully working order.
Find More Clipart Articles