|What make and model of computer do you have?|
Is it a desktop/tower computer, or a laptop computer?
Do you have a Windows CD?
( I have found that if you have a fairly recent Dell, HP, or Compaq brand name system, one of the CDs that came with the computer is often actually a slightly modified XP Home or Pro CD that can be used the same way as a regular Windows CD. If so, it has an /i386 folder on it, as well as other folders)
Searching using: rundll32 bad image (no quotes)
reveals there is no one cause of you getting that message, and the problem is probably not with rundll32 itself..
When you get the rundll32 bad image error you almost always get one or more references to files that are a bad image - the problem usually is not with rundll32 itself - it's with something rundll32 is trying to run.
rundll32 bad image
THE APPLICATION OR DLL C:\WINDOWS\SYSTEM32\SHIMENG.DLL IS NOT A VALID WINDOWS IMAGE.
Quote that or those messages you are getting along with rundll32 bad image
When and/or under what circumstances do you get this/these error(s)?
Are you still able to use Windows once or after you get this or these error(s), or is it unusable once or after you get it/them?
Are you able to boot into Safe mode?
(Remove any bootable CDs or DVDs you have in drives.
Press F8 repeatedly while booting the computer - don't hold down the key - when the boot choices appear on the black screen, chose Safe mode, or Safe mode with networking.)
If so, do you get the same error(s) in Safe mode?
These days, if you do have malware, it usually isn't a virus - it's something else.
No one anti-malware program can find and remove all possible malware these days.
You may have malware, or you may not.
Sometimes this error is caused by a corrupted file on your hard drive, or buggy software that you have installed, or that has been installed by something that does that automatically, which you may or may not get a message about when that is done.
Did you first get this/these error(s) after some software was installed??
That includes after an update to a program was installed, such as after an anti-malware update was installed, which may have been installed automatically.
If you know about WHEN you first started getting this/these error(s), you could try loading a System Restore restore point with a time and date BEFORE you first got it/them.