Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 6 subscribers
  • Views 21095 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

MBP crashes while scanning

Dwood1

Hi all,

I downloaded SAV two days ago and have tried running a scan several times but every time I do it stops after a certain amount of time and the computer completely freezes up.  When I say freezes up I mean if I click on anything or try navigating to a different application I get the spinning wheel.  I think that it is a certain file that the scan is reaching that is causing the hold up (I believe it stopped at the same number of "remaining files" each time)  although I should try the scan again before saying that definitively.

Some details about what I'm using:

15" MBP (mid 2012)

Mountain Lion 10.8.4

Bootcamp partition with Windows 7 Home Premium

SAV version: 9.0.1, engine: 3.45.0

The last time I scanned I had Activity Monitor open as well and everything was running smoothly and then all disk activity flatlines.  After about 20 seconds or so it shows finder as not responding and I have to restart the computer.  I have tried deleting SAV and redownloading it but the problem persisted.

Any help would be much appreciated,

Dwood

:1013160


This thread was automatically locked due to age.
Parents
  • 0
    Dwood wrote:

    I have tried deleting SAV

    How did you do that?   Properly uninstalling and reinstalling?

    I assume you are running a 'Scan This Mac' scan? And hence all local drives are being scanned.  Is it just the main hard drive it's scanning or are there one or more secondary drives or USB/FireWire drives attached?

    Is there anything in the Console log that hints at where the scan got to?  Example of opening the log:

    If it's just the main hard drive then you could break down the problem with custom scans and scan just certain folders (ie just add one item at a time like /Users and see if you can recreate the problem).  You could create a custom scan to check the entire hard, but on the 'Options' tab uncheck the 'Scan archives and compressed files' option.

    If you wanted to run a scan with sweep (the command line version) you could log to a file all the file names being scanned with...

    sudo sweep / -dn 2> ~/Desktop/manualscan.txt

    If/when the computer hangs the problematic file may be listed need the bottom of the log.

    And finally (or maybe this should have been the first thing :smileylol:)...you could close all other applications and leave the computer alone while it does the scan.  Having one or more applications open may lock some files and when the scanner gets to them it tries so hard to scan them that it pulls down the computer's resource to the point where Finder stops responding.

    Good luck.

    :1013162
Reply
  • 0
    Dwood wrote:

    I have tried deleting SAV

    How did you do that?   Properly uninstalling and reinstalling?

    I assume you are running a 'Scan This Mac' scan? And hence all local drives are being scanned.  Is it just the main hard drive it's scanning or are there one or more secondary drives or USB/FireWire drives attached?

    Is there anything in the Console log that hints at where the scan got to?  Example of opening the log:

    If it's just the main hard drive then you could break down the problem with custom scans and scan just certain folders (ie just add one item at a time like /Users and see if you can recreate the problem).  You could create a custom scan to check the entire hard, but on the 'Options' tab uncheck the 'Scan archives and compressed files' option.

    If you wanted to run a scan with sweep (the command line version) you could log to a file all the file names being scanned with...

    sudo sweep / -dn 2> ~/Desktop/manualscan.txt

    If/when the computer hangs the problematic file may be listed need the bottom of the log.

    And finally (or maybe this should have been the first thing :smileylol:)...you could close all other applications and leave the computer alone while it does the scan.  Having one or more applications open may lock some files and when the scanner gets to them it tries so hard to scan them that it pulls down the computer's resource to the point where Finder stops responding.

    Good luck.

    :1013162
Children
No Data