Windows XP Bad Image Errors at Startup

Here are a list of the errors that i receive at start up:

Rundll32.exe- Bad Image
 -application or DLL c:\WINDOWS\ilaqucad.dll is not a valid windows image. Check against installation diskette.

Rundll32.exe - Bad Image
-application or DLL C:\WINDOWS\abdsdmsg.dll is not a valid windows image. Check against installation diskette.

-error loading ofqsi.dll  specified module could not be found

-error loading C:\WINDOWS\ilaqucad.dll
 %1 is not a valid WIn32app

-error loading c:\WINDOWS\abdsdmsg.dll
%1 is not a valid Win32app

Some of these do not pop up until i click OK on previous errors.  I do not have the installation diskette anymore.

What do i do?

Question Info

Last updated November 26, 2019 Views 4,055 Applies to:
Part of the problem is if you set the computer to boot in a clean boot state, and then things work okay (unlikely), there are no instructions that tell you what to do next except return your computer to a normal state and that fixes nothing.

Is that stuff working out pretty good for you there JoshB_2011?  Of course it's not and it will not - ever.

Is there supposed to be some kind of magic that happens when you boot into a clean boot state that makes all the problems go away, then you return to a normal state and all is well? 

There needs to be something in between those two things...  and that would be the "troubleshooting" part... there  is no troubleshooting included.

I would read this all the way through (it may not make sense at first), then apply it.

It is sometimes easy to get rid of the error message by doing something like disabling the startup item in msconfig (if you can even find it), but I suggest you fix the problem and not just fix the symptom of the problem by merely eliminating the startup message.

I would also not recommend that you start poking around in the registry to try and find the startup item and remove it unless you have a backup of your system or at least a backup of your registry since there is no "undo" or "quit without saving" option in regedit.  If you make a mistake, that's it.

Those ideas offer "quick" and sometimes risky relief of the symptom if they even work at all, but they may not actually fix the problem.  I would also be wary of ideas that begin with the words "try".  You do not need to try things, you need to fix things.  You don't need to try ideas that might work, you need to do something that is always going to work all the time.

Here are comprehensive instructions that will keep you safe and resolve your issue the "right" way.

There are very few .DLL files that should be loaded from the C:\WINDOWS folder and that is not one of them.

A "Cannot find...", "Cannot start..., "Cannot load...". "Could not run..." Cannot run" "Error loading..." or "specific module could not be found" message at startup is usually related to malware that was set to run at startup but the referenced file(s) has been deleted after a malware scan leaving behind a registry entry or startup item pointing to a file that does not exist.  

It could be from a malicious software removal or an uninstalled application.  The entry may have a curious looking name since it was probably generated at random when the malware was installed. If you search your system for the referenced file, you may not even find it.

Windows is trying to load this file but cannot locate it since the file was mostly likely removed during a scan for malicious software. However, an associated orphaned startup parameter or registry entry remains and is telling Windows to load the file when you boot up or login.

You need to remove the referenced entry so Windows stops trying to load or run the file. It may or may not be in the registry but you can find it.  Autoruns (see below) will find the item no matter where it is.  

If you just locate and uncheck the item in msconfig, that disables the item but does not remove the reference to the bogus startup item from your computer.   The msconfig program is not a startup manager, it is a troubleshooting tool.  Disabling things in msconfig to put a stop to the messages and thinking your problem is resolved is short sighted and leaves behind a sloppy XP configuration.  Merely disabling the display of a startup error message should not count as a "solution" to the problem.

If you are comfortable editing the registry you can search for and remove the reference directly from there or remove it using a popular third party tool called Autoruns.  The problem may not always be found in the registry though.

Before making any changes to your registry by hand or with third party tools, be sure to make a backup of the registry first. There is no undo or quit without saving option in regedit.

Here is a link to a popular registry backup tool:

You can also use Autoruns to find the leftover startup item no matter where it is hiding.  Autoruns does not install anything on your computer.  It will display all of the startup locations where the reference might be so you can disable it or delete it completely.  Here is the download link for Autoruns:

Launch Autoruns.exe and wait for it to finish populating the list of entries.

When Autoruns is finished scanning your system, it will say "Ready" at the bottom left corner.  Autoruns can be a little intimidating at first if you have never see it before since it displays a lot of information.  You are really only interested in a couple sections.

The problem item is usually in the system startup or user startup entries so click the Logon tab and see if the startup item is there.

Scroll through the list and look for a startup entry related to the file(s) in the error message.

If you don't find it in the Logon tab, look for it in the Everything tab.

You can also click File, Find to search the Logon or Everything tab for all or part of the name of the item.

Right-click on the offending entry and choose to delete it.  If you are not sure what it is, you can just disable it, reboot and if the issue is resolved, and then delete the offending entry.  If you don't see it in Autoruns you may have to edit the registry and remove the item from the Startup folder there.  Autoruns should display the same information though.

Since you had or have an infection, follow up with this:

Perform some scans for malicious software, then fix any remaining issues:

Download, install, update and do a full scan with these free malware detection programs:

Malwarebytes (MBAM):
SUPERAntiSpyware: (SAS):

They can be uninstalled later if desired.

Reboot your computer and troubleshoot remaining issues.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.