Jump to content


  • Content Count

  • Joined

  • Last visited

About boshy

  • Rank
  1. thanks for this response, sorry for late reply, Ive slightly ran out for sorting this out atm - I'll send some logs over via email, but they dont seem to show up much to me - a few adaware cookies etc. Im running more tests, have done some windows updating. Things are still erratic.
  2. As an example, this morning I woke up the problem unit, and SAS was running at 14k . I then watched it climb to 158k. It then sat at around 130k. I woke the other similar unit and SAS was 9k, and did not climb at all, it remained constant at 9k. I appreciate that when SAS updates the database it will use more memory, but not that much, not constantly.
  3. this is highly unusual and not just an occasional variation. As I state in previous comments, the other very similar unit runs with no issues and as a comparison stays within 6-12k working set memory. It NEVER goes into the 100k amount. The problem unit stays at very high levels for no reason at all. The fans kick in and this was the reason I began to invesitage this issue in the first place. Im now thinking it could be a software conflict, or some other issue so will report back. BTW telling me to ignrore a problem I thought sufficient to report here isnt really that helpful. I understand if you cant think of a solution, but please, Im not here to waste my own time.
  4. Update: FYI (in case others may read this). I first did an uninstall/reinstall of SAS premium under normal boot. That way, if it made no difference, I could then do under safe mode. After reinstalling a fresh instance (in normal boot), I noticed something very odd: I had the processes window open after I had reinstalled. Immediately on finishing and entering my reg number, SAS working set memory began to climb from 9k to 100k+. I opened the SAS app window to change my preset scan settings to once per week, and clicked 'done' to return to the main window interface. As soon as I clicked 'done', the working set memory decreased rapidly to approx 9k. I left the processes window open to see if it would climb again. It did. I opened the app again and clicked on one of the areas for settings, made no changes, clicked 'done' again - immediately the working set memory decreased back to 9k or lower. It then remained at a low rate for some time. Later on in the day the working set memory had climbed back again to 100k+, so I did the same thing - opened the app, clicked on a window, made no changes, then clicked 'done'. Again, the memory had decreased rapidly back to 9k or less. This seems to imply that it is something to do with how it is running in the background.
  5. Yes Im going to try to do that today. BTW this is a lifetime premium acct, the non problem unit is just an annual premium acct. Do you think it could be something to do with the reg key?
  6. Hi. I run real time protection for both. Daily virus updates for both. One thing I noticed was that on the problem unit, the !SASCORE service was stopped, and set to manual. When I compared that to the setting for !SASCORE on the other machine, it was set to automatic and running, so I've changed that on the problem unit. I also had to manually update the software itself on the problem unit to the latest version as it wasnt updating. The total ram on the non-problem unit is 4gb (3.73 usable), on AMD E-450, and the problem unit only has 4gb (3.00 usable) on AMD 330, according to the properties. Bear in mind these machines do hardly any work, they are there for basic browsing/extra screen monitoring of work, social media, and a bit of media streaming. I woke the problem machine up just now and SAS is using 117k working set mem, the non-problem unit is using 9k.
  7. Hi. Im looking for advice. I have 2 old Win 7 Home Premium service pack 1 Acer Revo nettops I use for bits n bobs, no heavy lifting. I run SAS premium on both. On one of them, the working set memory is 10k. On the other its persistently really high, 110k or more. Ive made sure they are both fully updated, for software and definitions. I ran a scan on the offending unit, but it came up with nothing. Why is one unit so different from the other when they are such similar machines doing next to nothing? Any thoughts gratefully received.
  8. I put my PC to sleep at night, rather than shutting down. When I wake it in the morning, SuperAntiSpyware has crashed. It never used to do this, and has only started since i ran the latest version. It isn't caused because it has tried to wake the PC up to perform a scan, as whether or not it has performed scans, I always get the same error message when I wake up the PC about sending a crash report and whether or not I want to restart SuperAntiSpyware. So if it's done a scan while the PC was asleep I can then see the scan results underneath the error message window (when I wake thePC up again), which is frustrating as I cant then remove whats its found and have to restart SuperAntiSpyware, run another scan and then remove them. How can I stop it crashing when I wake up the PC? I run Win7 service pack 1 fully updated I have SuperAntiSpyware Pro, version 6.0.1204
  • Create New...