siliconman01 Posted November 20, 2006 Am running the latest SAS PRO with XP-SP2 HE (fully updated), 1.5 gbyte DRAM, 2.6 ghertz P4. Am curious why SAS spikes the CPU utilization to 38-45% every 1-2 seconds when certain MMC items such as System Properties, Add or Remove Programs, Windows Security Center, etc. windows are open. The spiking stops as soon as these windows are closed. Share this post Link to post Share on other sites
SUPERAntiSpy Posted November 20, 2006 Am running the latest SAS PRO with XP-SP2 HE (fully updated), 1.5 gbyte DRAM, 2.6 ghertz P4.Am curious why SAS spikes the CPU utilization to 38-45% every 1-2 seconds when certain MMC items such as System Properties, Add or Remove Programs, Windows Security Center, etc. windows are open. The spiking stops as soon as these windows are closed. Are you running another real-time protection system at the same time? Share this post Link to post Share on other sites
siliconman01 Posted November 20, 2006 I have NIS 2007, TrojanHunter TrojanGuard, and AVG 7.5.0.50 AS running. But if I disable them and close them down, the same spiking occurs by SAS. SAS typically spikes 3-4% with everything active and running. It's just when I open the utilities that I stated in the first post that causes SAS to start spiking up to 45%. Share this post Link to post Share on other sites
SUPERAntiSpy Posted November 20, 2006 I have NIS 2007, TrojanHunter TrojanGuard, and AVG 7.5.0.50 AS running. But if I disable them and close them down, the same spiking occurs by SAS. SAS typically spikes 3-4% with everything active and running. It's just when I open the utilities that I stated in the first post that causes SAS to start spiking up to 45%. We will have to investigate - this is the first report we have had of such an issue. Share this post Link to post Share on other sites
siliconman01 Posted November 20, 2006 Actually it looks like the spiking occurs on just about any of the .cpl (control panel) programs by Microsoft. Share this post Link to post Share on other sites
siliconman01 Posted January 11, 2007 This issue appears to be resolved in V3.5 Beta. Thanks much! Share this post Link to post Share on other sites
SUPERAntiSpy Posted January 11, 2007 This issue appears to be resolved in V3.5 Beta.Thanks much! Thanks for the update and testing! Share this post Link to post Share on other sites
