Jump to content

ptoye

Members
  • Content Count

    7
  • Joined

  • Last visited

Everything posted by ptoye

  1. Home-built. It was taking a long time from booting to being able to use it (about 2 mins sometimes). Since turning off the EFS service it's now usually OK, but once or twice it's been slow. When this happens there's an automatic login and then the desktop comes up OK but mouse clicks don't do anything. Then, after the delay, the mouse clicks all take effect. I think this started happening when I installed SP1 but Microsoft decided to update my keyboard and mouse software at the same time. It was fine before that. I brought this up on the Microsoft answers forum and they recommended running SAS. Which I'm still trying to do! It might be a driver taking ages to initialise itself (possibly my Netgear wireless dongle), but it's difficult to separate cause and effect here.
  2. 64 bit Windows Home Premium SP1. 4GB RAM. Intel i5 760 4-processor CPU. What else do you need to know?
  3. Memory test ran OK. Mouse driver was out of date - updated. Ran SAS again in normal mode as Admin and it hung again on the same file as before. This is getting silly.
  4. I've been a bit busy recently, and haven't had tme to try scanning until today (by which time, no doubt, other tracking cookies will have infiltrated themselves). Rather worrying - in the middle of the scan in Normal mode (logged in as Admin), SAS stopped working with a Microsoft-generated message: Problem signature: Problem Event Name: APPCRASH Application Name: SUPERAntiSpyware.exe Application Version: 4.51.0.1000 Application Timestamp: 4daf023f Fault Module Name: SUPERAntiSpyware.exe Fault Module Version: 4.51.0.1000 Fault Module Timestamp: 4daf023f Exception Code: c0000005 Exception Offset: 00000000000512b4 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 2057 Additional Information 1: 7a94 Additional Information 2: 7a94651b1e2ddd1ff4c4e0be08587722 Additional Information 3: e111 Additional Information 4: e1118dbe9eb111f1aaef37726316bcf7 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
  5. Very interesting. Firstly, I made sure that it had the latest definitions. (6908:4720) 1) Then ran in normal mode as Admin. It found one tracking cookie on the C: drive before hanging. Then booted in Safe mode and logged in as Admin. 2) Ran again - it did a sudden exit. There was nothing in the Event log at that time. Unchecked all 3 boxes and ran. Same. 3) I went back into Preferences/Options and found that the boxes were ticked, so unticked them again. This time it completed normally with 1 tracking cookie. 4) Ticked just Direct Disk Access. Result as (3) 5) Ticked just Kernel Direct File Access. Result as (3) 6) Ticked just Kernel Direct Registry Access. Result as (3) 7) Ticked all boxes. Result as (3)! At this point I'd used up the entire afternoon (it takes 20 minutes to do a scan) and gave up to do something productive. This morning (UK time) I booted into Safe mode, logged in as Admin, made sure all the boxes were ticked and ran. Same again - it completed without problems. So now I'm totally confused (as I expect are you). And don't know how to continue, if at all. Any ideas welcome!
  6. 1. The latest version announced itself while I was running the tests - so I updated & started again. 2. I didn't know this. I assumed that the latest version installed itself everywhere. Seems a bit odd to have a computer-based (rather than user-based) tool being user-sensitive. Design problem? Is the updater sensitive to whether I'm in normal or safe mode? Because I tend to run safe mode without networking which makes updating a mite difficult. 3. I'll do this separately. 4. Win 7 home premium SP1 5. My thought entirely - already did it - no problems found. Thanks for the ideas and help. But it's the hangs and sudden exits that worry me most.
  7. I'm trialling SAS Free, and am having some problems. Firstly, it hangs when file scanning. In safe mode this seems to happen when I'm logged into my user account, but not when logged in as Admin. When I tell it to scan the folder that it's hanging in it doesn't hang and reports that it's scanned 2 files, which is odd as there are 4 files (all with the .dat extension) in the folder. I have to use Task Manager to kill it, and then of course there isn't a log file to examine. Secondly, in safe mode, when I log in as user it finds 5 tracking cookies before it hangs. As Admin it finds a different tracking cookie and 2 purported Trojans (which are odd - they're in a VB .exe file which I wrote myself). Is SAS meant to get different results for different logins, or have I got a really interestingly nasty piece of malware? If I run it in normal mode it hangs whatever the login. I've used another malware scanners and it doesn't find any trojans, by the way. [Later] Tried again in safe mode logged in as Admin. The first time it exited without giving any log or report. I think it was in the middle of a scan. The next time it completed the scan without hanging. Maybe I've got a duff disk.
×
×
  • Create New...