Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Right click on the compressed RegSearch folder, and choose "Extract All". In the box that pops open, click "Next", then "Next" again, and then "Finish". You now have another RegSearch folder on your desktop.

Open the new folder, and double click on regsearch.exe

Click "Import" in the lower left corner and browse to the options.txt file that you just saved on your desktop. Do not choose the one in the RegSearch folder itself.

Click OK and Registry Search will scan your registry for the file(s), and a Notepad box will open with a report.

Please reply here with the entire contents of the Notepad file from RegSearch.

JSntgRvr

Posted 03 September 2008 - 04:21 PM

Open the program and click on the Rootkit tab.Make sure all the boxes on the right of the screen are checked, EXCEPT for ‘Show All’.Click on Scan.When the scan has run click Copy and paste the results (if any) into this thread.

Xad

Posted 06 September 2008 - 11:26 PM

Xad

Member

Topic Starter

Member

42 posts

Well, I switched to avast! and it could just be a coincidence, but I haven't received a DrWatson error upon startup recently.

What has been happening recently (this happened before I switched antiviruses, too) is that soon after the computer starts up, any time a new window is opened a DrWtsn32.exe process to run in the Task Manager, which will freeze explorer.exe for a few seconds, and then it will disappear, and explorer.exe restarts. However, which programs this effects seems to be random, and after it happens once to a program, it usually doesn't happen again until rebooting. It seems that sometimes this goes "wrong" and then I receive the regular error about DrWatson.exe being unable to respond. I might be wrong, but it seems that the longer the computer is on, the less likely this is to occur.

Advertisements

JSntgRvr

Posted 07 September 2008 - 10:24 PM

Xad

Posted 09 September 2008 - 03:27 PM

Xad

Member

Topic Starter

Member

42 posts

Well, after restarting my computer again, nothing seems to have changed. I still experience the same problems as I did in my previous post. It really seems like there's just something wrong with explorer.exe, because the errors most often pop up whenever explorer.exe has to open a new window, or update the status bar or something.

JSntgRvr

Posted 09 September 2008 - 06:46 PM

JSntgRvr

Global Moderator

Global Moderator

11,089 posts

Hi, Xad

I am as puzzled as you are.

Download Getservices.zip from Here and extract the zip file to your C: drive. Once it is extracted there will be a directory on your C: drive called getservice. Inside the C:\getservice directory will be a file called getservice.bat . Simply double-click on the getservice.bat file and when it is completed a notepad will open with a lot of information. Save this document to your desktop and attach it to a reply.

Download pv.zip from Here and extract the zip file to your C: drive. Once it is extracted there will be a directory on your C: drive called PV. Inside the C:\PV directory will be a file called runme.bat . Simply double-click on the runme.bat file. A dos window will open. Select option 1 for explorer dlls by typing 1 and then pressing enter. Notepad will open with a log in it. Copy,. paste or attach the log into this thread. . Please do option 2 for Internet Explorer dlls too.

Attached Files

JSntgRvr

Posted 10 September 2008 - 08:06 PM

JSntgRvr

Global Moderator

Global Moderator

11,089 posts

Xad, there is nothing in those logs out of the ordinary. I would suggest you open a topic in the software forum (Windows XP) and allow one of the techs take a look at your situation. Whatever is causing this issue is not showing. The XP forum is the right way to go.