Recurring Crashes During Full AV Scans

(Windows Version: Windows XP SP3, 1.58 GHz & 1.98 GB RAM)

Whenever I try to perform a full scan(not a quick scan) on my computer, it will crash. I don't know if this has to do with a software issue, or if it's just something on the computer itself that is corrupt, but I'd like to see if anyone has advice on this.

 

Malwarebytes, Avast, and Super Anti-Spyware.. they will scan, but will eventually crash later on into the scan. It's been happening ever since I installed the programs. Even in Safe Mode it happens.

 

Quick question, are ye overclocking? If so, set to default and try again.

 

Not to my knowledge. This is only a laptop with semi-par specs.. I don't think it would be worth the hassle to put this thing through the process :-D

 

Malwarebytes does not recommend doing a full scan unless the quick scan turns up malware.
Did malwarebytes quick scan find anything? If not, do not beat your head against the wall trying to run a full scan with that program.

I do not use the other two programs so I'm not sure what the recommended procedure with them is.

 

It did find quite a few infected objects. It's what worries me though; I'll never know if my system's completely clean or not. It's the reason why I have also downloaded other programs, just to see if everything is ok. Was just wondering if these crashes had anything to do with corrupt memory or anything of the sort.

 

You need to head to the malware removal section http://forums.majorgeeks.com/forumdisplay.php?f=35
Start by reading this and downloading and running MGTools
http://forums.majorgeeks.com/showthread.php?t=35407

The malware fighters are excellent here and they will get your computer clean.

 

Yeah everything is fine, I just wanted to see if there was some sort of quick fix so that I could scan fully again. At first I thought it was malware, but it seems like it's just some sort of corrupt hardware\software problem.. but thanks guys :cool

 

It says that there is an unexpected error. I've downloaded the most recent .NET and Powershell 1.0, but I'll search their forums for an answer.

 

Turns out that I have to rename the autorun.inf file since AV's decide to disable any sort of access to it, but when I go to modify the value's name it won't let me.