hi team, I'm looking for assistance!

[129260]

Well, here is what started happening lately that i have noticed.....

The following processes from spybot are hogging my cpu to 100%:

sbsdscan.exe and sdisttestsvr.exe

I know what these processes are, but it is unclear why there is such a high cpu usage for several minutes. Like 15 minutes. Eventually it does die down, but sometimes to calm it down, i would stop the testing service and restart it, and then it would be fine.

Testing service is up to date and can be found here:

http://forums.spybot.info/showthread.php?t=29452

So team, have any ideas?

I have tried the following methods:

Complete uninstall of spybot and the test client. Then install again, and still usage is high. Can this stuff be looked at or tested? Thanks.

Thanks for any help you can provide. System specs in sig.

[129260]

does anyone have any ideas?

[PepiMK]

At the end of the linked thread, the same problem has been mentioned as well. Yodama told me he had fixed that detectien pattern where a hang could occur due to an invisible messagebox asking to reboot. I'll have to ask him to look at it again!

[129260]

even now, right at this moment. It seems like it is the program itself however, not the detections. Because even when the program is running, (the service is running) but its not processing any data or testing anything, the cpu usage is still really high. Does that make sense? Like, the service is running, but it is not testing anything or downloading anything at all, so it makes no sense why it would take that much cpu. The only way to stop the high CPU usage is to stop the process/service. Its really odd....Thanks for the response PepiMK!

[Yodama]

this sounds really odd, I am currently rechecking the rules to see if there are still reboot parameters which may be responsible for this issue.

Please check the previous.ini in the config folder of the SDistTest and tell us which is the last sbi listed there, the most recent one should be like this:

[SDDT-Virtumonde-micha.sbi]
ID=4142
LastUpdate=2008-10-30 15:11:28

[Yodama]

We uploaded emptied versions of the sbi files which could be responsible for this behavior, some of them were pretty large and contained very cpu intensive rules.