1. 1. In order for us to analyze a potential problem and offer tips, we must rely only on the question content to attempt a qualifying response. A question should state the exact system error(s) - spelled, spaced, and capitalized just as it is shown on the display. Helpful perhaps is the window title in the colored bar of the report and any information when provided by a "Details" section also.
2. Most error messages: 1) usually list and describe standard default error messages - written within the program code and generally recognized by most "Gurus", and 2) the troubleshooting techniques may be published and explained in the Microsoft Knowledge Base (MSKB) library for the Windows operating systems, and may be searched for with accurately reported information.
3. Correct and complete information is vital if informative help and answers are what you seek. You want that Guru who reads your plea to understand the question, to possibly know the answer, and to reply giving you their assistance.
4. When confronted with a DLL file problem, a copy of some Microsoft media may already be owned from which the file can be extracted, [Definition and Explanation of a .DLL file (Q87934)].
5. To determine whether the file is a Microsoft issue (there is a two-page listing for this file), access the DLL Help Database, enter the file name -- including extension in the space provided, and then press Enter (correct spelling and punctuation is recommended). If a list is rendered, simply determine from what media is shown and that currently owned and extract a copy, [How to Extract Original Compressed Windows Files (Q129605)].
6. If the file is unknown, it's usually advantageous to simple uninstall and reinstall the applicable program for which the file belongs. Otherwise, search the Google_Group Web site for resources.