SAS = BSOD for my “overlaiden” security set up, however each of my components are suggested to work with SAS so it might conflict with the whole combo of 1 resident AV + 3 on demand AVs, FW, + running A-M/A-S and 5 on demand back ups which I alternate using plus 1 credible system Cleaner. However, I thought that may have been the case a year ago and I now remember installing SAS with just one AV (running), a FW and nothing else and still getting BSODs, both on XP and W7. I also thought it might have been a bad download from my regular download site, so I changed to taking it from multiple “legitimate” places including SAS itself and was still getting the BSODs, including again just now a year later, with my current set up.

That includes me having tried SAS with a FW and just Avast!5 last year and still getting BSODs, so if other people are not crashing then it might be my system, so could be a mobo driver issue or something else peculiar but not related to any of my security combinations.

Interestingly, I configured cookies to how Daris has it with “prompt for first party” and when I tried to download SAS from Cnet it “offerred” to use an unsecured pathway/connection for the download so I blocked it and tried elsewhere. I ran many scans to see if I could get one of my applications to remove the cookie/temp-trace this placed since Hitman found it as a low risk Virus or Trogen IIRC. Finally Spyware Terminator got ride of it, even if it possibly was only a false positive - then I used CCleaner to be sure anyway, but this showed that even some oldies can work better (may be) than advanced others against things although this was only a low niggle example.

If I run a scan with SAS I have a BSOD in about 30 seconds roughly which means I can’t use it, so it seems I have to just go without SAS that a lot of people swear by.