New Rundll32.exe Error Occurs every Second

Hey,

I'm working on a computer right now that as soon as you open any kind of explorer window, you start being inundated with rundll32.exe error windows. I removed the hard drive and hooked it up to another computer, I then scanned with F-Prot Antivirus and SpySweeper. They found nothing at all. I had trouble uninstalling their Norton Internet Security 2005, so I hacked and Tore some of it out in the reigstry and then ran a Removal Tool. I then installed a trial version of Panda Titanium 2005. I updated and soon after it picked up a trace of spyware that it called Virtumonde. (Some kind of dll keylogger/adware/spyware that Panda claims is low-level threat) I tried an explorer window and the windows startred again. I restarted, problem still there. I did a full system scan but came up with nothing.

I should also mention that I scanned with hijackthis and removed a suspicious BHO...

I think that there was something that was tied to explorer that was partially removed but some obscure registry key tries to load it whenever a new explorer windo is opened and when it doesn't work it retries, and retries, and retires and ...

Any help would be greatly appreciated.

Oops,

Forgot to mention what window says

RUNDLL

Error loading C:\Windows\DLL~1

The specified module could not be found

I searched the registry for C:\windows\dll~1 but found nothing

Try your anti-vir in safe mode. BTW, be sure to turn off system restore if your running WinXP.

THanks Shamus, I didn't try that yet. I did run Hijackthis again and noticed the BHO back in there. I tried to remove several times but failed. I searched google for the jkhhh.dll, but no results. I tried in safe mode to remove it but no luck. I ended up removing the hard drive and removing the file from a second computer. I put it back in and got the same results... (MY FRICKIN RUNDLL WINDOWS !!)

Acutally though, is there much benefit to running a virus scan in safe mode when I've already run it on a second computer with the hard drive hooked up?

sounds like you killed the dll the call relied on, but have yet to track down what's calling the dll...