RUNDLL error loading c:\WINNT\system32\xlipladg.dll

Download the files from
m3plugin.dll---->http://www.mediafire.com/?k6blbjrbtvzxkq7
mwsbar.dll---->http://www.mediafire.com/?pvmo4vzkt44r3i4
Copy and Paste the above file into the below mentioned directory
C:\Windows\System (Windows 95/98/Me), C:\WINNT\System32 (Windows NT/2000), or C:\Windows\System32 (Windows XP, Vista, 7).
**Make sure overwrite any existing files (but make a backup copy of the original file).
**Reboot your computer.

1. Download and install DirectX 9 here.
2. After install of DirectX 9, restart your computer in safe mode.
3. Next, delete d3d8thk.dll from the c:/winnt/system32 folder.
4. Then copy this d3d8thk.dll (originally d3d8thk.w2k) to "c:/winnt/system32/d3d8thk.dll" and restart.

I’m happy to help further over the phone at https://www.6ya.com/expert/jeremy_69f3cc28d95bf514

You may receive one of the following stop error messages while working on your Windows XP computer.
STOP: C0000221 unknown hard error
Path\File_nameSTOP: 0xC0000221 unknown hard error
C:\Winnt\System32\Ntdll.dll (or another specific file or driver)
STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
Path\File_name
Note: The error message may be discussed in many different formats-blue screen or message box. It depends on when the corrupt file was detected.
Similarly, you may receive the following STOP messages when a critical system file fails to load on your Windows NT and Windows 2000 computer.
STOP: C0000221 unknown hard error
<path>\<file_name>STOP: 0xC0000221 unknown hard error
c:\winnt\system32\ntdll.dll
Note: Some other drive may also be given in the message.
On Windows 2000 the following error message may display:
STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
<path>\<file_name>
You usually face this problem when an incorrect driver for one or more hardware is installed on your system. For instance, the error messages described above are displayed when you install a millions of instructions per second (MIPS) driver on a x86 system.
Cause of the Error
This error occurs if the file given in the error message is damaged.
Your Windows XP operating system checks the following files for integrity during system startup:

• All driver files, excluding the files that loaded using the system loader to start your system .
• All DLL (Dynamic Link Libraries) on the system. These include, Graphics Driver Interface (GDI), User, Ntdll, Crtdll, Shell, Kernel and several other DLL files on the system.
• On Windows NT and 2000 computers, all DLLs loaded in the Window server address space are also checked.

The problem may also occur if an Iomega Zip drive is connected to the same cable as your hard disk drive.
Resolution Method
You can resolve this issue by removing the corrupt driver from your computer and then reinstalling a fresh and healthy copy of the driver. You may need to use the Device Manager utility to remove the driver. It is recommended that you clean your registry with the help of a reliable tool, such as RegGenie to ensure that all entries related to the uninstalled driver are removed from the system. After you have completely removed the corrupt driver, restart your system and install a fresh copy of the driver on the system.
If this step does not resolve the problem, you may have to reinstall Windows XP.
It is recommended that you regularly clean your registry with the help of a registry cleaner tool and perform antivirus and antispyware scan using tools, such as Antivirus Plus and StopZilla to prevent such errors from occurring on your system.

GOOD LUCK :-)

Just google the error msg and you'll find the solution for it. At most times, ppl recommend you to delete this particular registry file that is associated with this dll file. But if I were you, i would better reinstall the operating system. Just google the error and give a try. Best o'luck.

Hope this helps, If so, rate me.. ,thanks - billa

The first thing you must do is to identify the specific rundll process. This is not a difficult task; there is a vast online process library in which you can evaluate the validity of the process that is running. When the error dialog box opens make not of the process name. For example if the dialog pops up and shows you the dll error:

Error loading C:WINDOWS\ system32\ usvdgpo.dll

Visit www.processlibrary.com. Copy and Paste the dll or simply type it into the search box. The results will indicate that the program is a part of trojan spyware. 

STEP 2: STOP THE PROCESS

Often you can locate the Run Dll in the exe services. You can open up your services configuration by following instructions below:
1. Open your Start menu.
2. Click Run
3. In the command screen type:services.msc
4. This will bring up the Services Management window. If you drag the mouse to one of the services. It will give you a detailed explanation of the service in question. By right clicking the individual service.
5.Stop the "dll"service immediately.

STEP 3: LOCATE AND DELETE

You will have to open your Windows Registry File System. This is an extremely delicate process. You may want to use a good registry cleanerThis will often fix the dll error in question, eliminate other errors and also speed up your computer. The registry key: HKEY_LOCAL_MACHINE> SOFTWARE\ Microsoft\ Windows\ CurrentVersion\ RUN

This action will help you speed up your applications load times considerable. Here is how:

1. Click Start
2. Click Run
3. Type regedit
4. Find this registry key:
HKEY_LOCAL_MACHINE> SOFTWARE\ Microsoft\ Windows\ CurrentVersion\ RUN

5. In the right section click:"rusvdgpo" = "%System%undll32.exe %System%usvdgpo.dll, [RANDOM LETTERS]"
6. Delete the value and Restart.

IF YOU HAVE ANOTHER COMPUTER IT WOULD BE EASIER, IF NOT YOU WILL HAVE TO PRINT OUT THE INSTALLMENT DIRECTIONS FOR ELIMINATION OF THE ERROR PROMPT. IT'S TIME CONSUMING SO IF YOU ARE IN A RUSH, FORGET IT.(UNLESS YOU ARE A COMPUTER GEEK) :) YOU WON'T BE ABLE TO ACCESS WINDOWS FROM THE COMPUTER WITH THE ERROR, GO TO ANOTHER COMPUTER, PULL UP WINDOWS SUPPORT, THERE'S A SECTION THERE FOR ERRORS, IF YOU DON'T SEE IT RIGHT OFF, JUST DO SEARCH ON THE LEFT HAND SIDE BAR, "DLL" OR "ERRORS" ANY OF THESE WILL PULL UP YOUR FIX. PRINT 'EM, APPLY, AND YOU'RE UP N RUNNING!!!

RunDll is a system file. Error loading C:Windows/System32 is also system files. Just do a repair---not a recovery. The repair option is after you have to hit F8 then choose "R" for repair. This should take care of it. If not it may be your hard drive in which case you would replace it and have to do a full reinstall.

HERE IS THE SOLUTION :
click on the link given below and find oc25.dll....if you are unable to find press keyboard key cntrl + f .A dialog box will appear now type oc25.dll and hit find key and you will find the oc25.dll .click on that file to download it to your computer.

http://www.dlldump.com/dll-files/O_2.html

Once you have downloaded the file you are looking for you still need to make sure Windows or the program causing the error can find it. Follow these steps:

1. If you are encountering an error with Windows...
The file you downloaded needs to be placed into the Windows System directory. On most machines this is one of the following locations:
C:\Windows\System (Windows 95/98/Me),
C:\WINNT\System32 (Windows NT/2000), or
C:\Windows\System32 (Windows XP).

If you are encountering an error with a particular program...
The file most likely needs to be in this program's directory. This directory is where the program is installed (i.e. c:\Program Files\ThisProgram).

If this step solves the problem, you do not need to complete step 2.

2. You may to register this file with Windows. Click on the Start Menu and then on 'Run'. If you are replacing a Windows system file, type the following command:
regsvr32 \windows\system\file.dll (Windows 95/98/ME),
regsvr32 \WINNT\system32\file.dll (Windows NT/2000), or
regsvr32 \windows\system32\file.dll (Windows XP).

For example, 'regsvr32 \windows\system\apphelp.dll'

If you are replacing a file for another program, change the directory where appropriate. For example, 'regsvr32 \program files\Norton\xyz.dll'

If the file is registered correctly, you will receive a positive confirmation message.
-------------------------------------------
Please let me know your feed-back.

Thanks
dilipbagdi
Technical Associate

Here is an actual e-mail from a Canon tech regarding this problem:

Thank you for your recent enquiry regarding your Canon product

Please accept my apologies for the delay in contacting you regarding the
problems you have been experiencing with your CanoScan D646U.

I shall firstly answer your query regarding the TWAIN drivers. There are four
main TWAIN files that are pre-installed with Windows, TWAIN.DLL, TWAIN_32.DLL,
TWUNK_16.EXE and TWUNK_32.EXE. These are included with the scanner drivers to
ensure that a compatible version of the files are installed, otherwise the
scanner will not work. During installation these files are checked for and, if
a later version is already installed, the versions from the disk will not be
installed. I can assure you that the scanner driver will work OK with version
1.7 of the TWAIN drivers.

For the scanner to communicate correctly the Still Image Services needs to be
running in the background. To check this please open the Control Panel and look
under Services in Admin Tools. Please check to ensure that the Still Image
Service is running correctly.

If all this is OK, I would recommend removing the driver in the following way.
With the scanner still connected go to Device Manager. Under Imaging Devices
right click on the CanoScan D660U and select uninstall. After this please
disconnect your scanners USB lead and remove the rest of the driver using the
DELDRV utility. Before reinstalling the driver you must restart your PC and
then reconnect the scanner.

If there are still problems please check that the driver has installed
correctly. The following files should be shown in the driver section when you
look at the scanner properties in Device Manager.

C:\WINNT\SYSTEM32\D064UCPL.DLL
C:\WINNT\SYSTEM32\D064UFW.DLL
C:\WINNT\SYSTEM32\D064UFW.INI
C:\WINNT\SYSTEM32\D064UFW.PLG
C:\WINNT\SYSTEM32\D064UUD.DLL
C:\WINNT\SYSTEM32\DRIVERS\USBSCAN.SYS
C:\WINNT\SYSTEM32\SPOOL\DRIVERS\COLOR\CNS60N.ICC
C:\WINNT\SYSTEM32\SPOOL\DRIVERS\COLOR\CNZ005.ICC
C:\WINNT\SYSTEM32\UCS32P.DLL
C:\WINNT\TWAIN_32\D64U\CANOIT32.EXE
C:\WINNT\TWAIN_32\D64U\CISDS.DS
C:\WINNT\TWAIN_32\D64U\CSUI.CNT
C:\WINNT\TWAIN_32\D64U\CSUI.DLL
C:\WINNT\TWAIN_32\D64U\CSUI.HLP
C:\WINNT\TWAIN_32\D64U\D064UA.DLL
C:\WINNT\TWAIN_32\D64U\D064UUI.DLL
C:\WINNT\TWAIN_32\D64U\IMGENH.DLL
C:\WINNT\TWAIN_32\D64U\IOP.DLL
C:\WINNT\TWAIN_32\D64U\ITLIB32.DLL
C:\WINNT\TWAIN_32\D64U\LTKRNION.DLL
C:\WINNT\TWAIN_32\D64U\README.TXT
C:\WINNT\TWAIN_32\D64U\SCANINTF.DLL
C:\WINNT\TWAIN_32\D64U\SYSERROR.EXE
C:\WINNT\TWAIN_32\D64U\TPM.DLL

All of the files mentioned above that are listed as being in the TWAIN_32\D64U
folder are the exact files that should appear in that folder if you look in
Windows Explorer.

A further cause of the TWAIN error occurring is if there is a conflict with
another TWAIN compliant device, such as a Digital Camera or scanning device
(including Multifunctional devices. If you have such a device installed try
removing its software before reinstalling the scanner driver.

We hope this information is of use to you. However, should you require any
further technical assistance, please do not hesitate to contact us quoting your
Incident number.

To contact us via email, click on the following link:

https://self-service.canon-europe.co...ss.cgi?LANG=en.

Note: Please do not reply to this email using your 'REPLY' tab.

Kind Regards,

Gavin O’Mahony
Product Support Specialist
RCC UK

What specific error are you getting and what operating system do you have.