Receiving a RunDLL error upon startup

January 30, 2011 at 14:10:23
Specs: Windows Vista, AMD / 2.00 GB RAM
Hi everyone - I have been receiving an error message upon startup that reads "Error loading C:\Users\Rach\AppData\Local\Temp\dosk_isv.dll The specified module could not be found."

I currently have Norton 360 installed and running on the computer and I have also run Malwarebytes in an attempt to correct the problem. Neither seems to do the trick.

Any help with resolving this problem would by much appreciated - Thanks!


See More: Receiving a RunDLL error upon startup

Report •


#1
January 30, 2011 at 14:24:28
I'm not much of an advocate of registry cleaners in general but using one might be your best way forward. Download CCleaner Lite - their cleaner is one of the safest. Run the Reg Cleaner and look for an entry referring to dosk_isv.dll then mark that one and get it to delete it. I suspect it is the registry remnants of some software that has been removed.

Whether you let the Reg Cleaner remove anything else is up to you.

The alternative is to search for dosk_isv.dll in the registry but you have to be careful what you delete there.

There is one other way, see if dosk_isv.dll appears in msconfig Startup tab. Probably unlikely but if so, untick it there - very safe.

We all live on a ball.


Report •

#2
January 30, 2011 at 18:58:17
go to the run command off the start menu. type msconfig, then "start up" tab. Look down the list and see if anything there references that file you describe if so uncheck it and reboot the computer.

Report •

#3
January 30, 2011 at 19:17:28
HopperRox
Thx for amplification of my last line #1, poster might not have known where to find msconfig Startup tab.

MountieHeel
I guess, msconfig would be the best first option - it's easiest.

We all live on the same ball.


Report •

Related Solutions

#4
January 31, 2011 at 08:13:15
Thanks for the quick response and suggestions everyone!

The file DID show up in msconfig. Is the problem completely fixed when I uncheck it, or is that a sign of a bigger problem elsewhere in the system that I should be concerned about?

Thanks again, you all are wonderful!


Report •

#5
January 31, 2011 at 09:27:08
I don't think there is a big problem, it was just some registry entries that got left behind after an install or uninstall. The file itself has obviously gone. By unticking it in msconfig it will still leave some "don't run" registry entries lurking but as there is no file they are invalid, so they will not be acted upon even if it was a virus. They can be removed by the methods I gave in #1 but unless you are particularly keen I doubt it is worth the trouble.

We all live on the same ball.


Report •

#6
February 1, 2011 at 09:20:12
Good to know. Thanks again for your help!

Report •


Ask Question