1.5.2RC1 caused BSOD & restart

[Who Knew]

(Windows XP Home, SB S&D 1.5.2RC1)

Hi,

I've been using Spybot for years, at least since version 1.3 :bigthumb:.

Just tonight, when I installed 1.5.2RC1, and scanned my computer, when it appeared almost finished scanning, I got the blue screen of death, and my computer restarted.

After restart, I tried to scan again, and the same thing happened.

What do I do to help figure out why scanning causes my computer to crash? Does the scanner have a logging feature I can turn on so I can see where/when the crash happens?

My event log shows the two "Save dump" events. Should I post the dumps, would that help? Should I do a bug report?

How about a nice big HJT listing? ;)

Anyway, just let me know what I should do next to try to figure this out.

Thanks,

Who

[spybotsandra]

Hello,

Was anything already found although the scan did not finish?

Please run also a scan in safe mode:
http://www.computerhope.com/issues/chsafe.htm

Best regards
Sandra
Team Spybot

[Who Knew]

Hello,

Was anything already found although the scan did not finish?

Please run also a scan in safe mode:
http://www.computerhope.com/issues/chsafe.htm

Best regards
Sandra
Team Spybot

Hi Sandra,

Yes, it found a few things, like Windows virus protection override (because I use a virus protection, F-Secure, that windows doesn't automatically recognize, so I have to turn windows virus protection warnings off manually, and this is detected by Spybot when I upgrade Spybot, until I exclude this detection from further searches.), and usage tracks (also an indication that the search was nearly finished, since it was beginning to list the usage tracks..It usually does this at the end of the search). Nothing critical was detected, that is, I saw nothing indicated in red text before the BSOD happened. Also, note that I did have F Secure disabled disabled during the scan, because Spybot scans faster when the virus protection is disabled.

I'll try running a scan in safe mode and see what happens.

Who

[Who Knew]

I was able to do a complete scan while windows was in safe mode. Nothing critical was detected, just the before mentioned Windows virus protection override, and a bunch of usage tracks.

Should I try another scan in normal mode?

If I don't have a problem scanning in safe mode, and it keeps giving me the BSOD for normal mode, how do I figure out what's causing it?

Thanks,

Who

[spybotsandra]

Hello,

I would try a scan in normal mode.
Probably the blue screen does not appear again.

Best regards
Sandra
Team Spybot

[Who Knew]

OK, I'll report back how it goes.

Who

[Who Knew]

One successful scan with no BSOD. Why did you ask me to run a scan in safe mode? I thought it was a diagnostic step, but it appears it may have fixed the problem. Can you explain this, or just a fluke?

Thanks,

Who