S&D 1.5 Instability

[Rigatoni]

I have installed the latest version of S&D 1.5.1.15
and the TeaTimer component causes system instability due to page faults-at least this is what the error messages are telling me. I use the regular updates
and NOT the beta development ones.Any chance of a fix?

[spybotsandra]

Hello,

Perhaps you have not enough RAM?
We need some more informations.
Which operating system do you use?
Which Anti-Virus-Software do you run?
How much disk space do you have/CPU?

You can also see page faults in taskmanager:
taskmanager --> view --> select columns
There you can mark 'page faults'.

Best regards
Sandra
Team Spybot

[Rigatoni]

Hi.

I had plenty of ram before installing S&D1.5. There were
no such issues with version 1.4. I followed the procedure
to completely uninstall 1.4, including the registry edit posted in another thread on this site.

My system details are:

Windows 98SE
AMD Sempron 2400
512 MB RAM
78 GB HD (One volume, 4.8GB used)
Norton AV 8.0

Swap file is not limited and is handled by Windows.
Resource Meter indicates that I have plenty of RAM.

Nothing has changed in my system apart from the upgrade from S&D1.4 to S&D1.5.

Regards,
Rigatoni.

[PepiMK]

"Page faults" are not errors - see this Wikipedia article (http://en.wikipedia.org/wiki/Page_fault) for example.

What "error messages" exactly are telling you they would be?

[Rigatoni]

Page fault-usually something along the lines of "TeaTimer
caused a page fault in KERNEL32.DLL at..." This is of course
when I actually get to read anything as more often than not the system just freezes up and I have to do a hard reboot. As I said before, I have only had this problem since installing S&D 1.5.

[CharlesF]

I've started getting STOP blue screens since upgrading to 1.5.x. Although I not sure th 2 are related, disabling Teatimer seems to "fix" the problem.

I'll continue monitoring things and report back

FYI, my system is running XP SP2 with 2G RAM.

[Rigatoni]

disabling Teatimer seems to "fix" the problem.


I too have disabled TeaTimer and that HAS fixed the problem! Now, come on S&D team, write a proper fix for this.

[PepiMK]

"A proper fix" would have to be written by Microsoft ;)

What is causing a lot of page faults (which are usually NOT crashes, just a notification that some memory content that has been swapped into the swap file needs to be accessed) is a method to list all running processes (and while hooking into the function to start new processes might reduce that load, the full list needs to be queried to be sure that no one worked around the hook). Well actually there are two methods to do this, and the page fault heavy one should only be used on those OS versions where it is absolutely necessary.

CharlesF, ist that 64 bit XP SP2 or the old 32 bit one?

[CharlesF]

It's the 32bit version.

Regards,
Charles