BSOD from scans

My computer:
Windows XP Home Edition, SP3
Intel Dual E2180 @ 2.00GHz, 3.50 GB RAM(4 1 gig DDR2)
GeForce 8800GTS 512
520W PS
250 gig HD as my main(windows and programs)
1 Tb internal storage(all video files)
500gig external HD storage(audio/video)

Problem: While Scanning my C: drive(usually registry files when I was present) it hits a BSOD with this error:
STOP: 0x0000008E (0x0000005,0x8062F357,0xB5854714,0x00000000)

I originally read the Run and Readme cleanup procedure for malware for XP and was unable to finish any of the scans it suggested and so could not produce logs. There were never any threats found up until the crash.
While trying to use CCleaner on the registry I am able to scan everything except Type Libraries. That scan causes the BSOD. I did windows debugging for minidump and it produced the following log in quotes.

The problem first arose at some point after I installed my second internal hard drive. That is the only change I can think of that was preceeding the ongoing problem.

I have followed the advice of various sources. I have ran chkdisk and it usually fixes errors caused by the crashes, but then the problem will persist. I have done memtest86+ with no problems. I had my windows cd check for errors. To the best of my knowledge I only get crashes while scanning registry, but I could be wrong. I am not always present during the incident. For example, I crashed about 35 minutes into using SUPERAntiSpyware. I believe a time or two it has crashed while installing something or other, but I can't quite remember.

I am willing to try anything. I would prefer not to reformat and reinstall as that always takes weeks to reinstall/download all the programs I use, but that may become a last resort. I only use COMODO firewall/AV and somehow it is able to scan at night. Originally it would crash, but after disabling it for a few weeks and re-enabling it, it works.

Thanks for reading this,
Eric

 

Interesting you say that. That may have been where I read about the memory a few weeks ago. Anyway, I ran memtest86+ today before posting that and it did not show any errors. If it is faulty ram would that have shown up by the test? Or perhaps I have to let it run the test for several hours or something?
-Eric