Scan running very slow, stops

[Tj56]

Ran Farbar - files attached.  Recommendations?

Addition.txt

FRST.txt

[daledoc1]

Hi:
 
Welcome.
Until the staff members have a chance to formally review your logs, a couple of things come to mind:

• "Running very slow" is rather non-specific -- it would help to have more data, such as a scan log.
•  MBAM 2 has a more powerful, more complete scanning engine & other capabilities (such as anti-rootkit scanning) not available in version 1, so it is perfectly normal for scans to take a bit longer; this is nothing to worry about.
• Disabling anti-rootkit (ARK) scanning and archive scanning can speed up scan times -- scanning within large archives (zip, rar) can take time and it may appear that the scan has stopped, even though it is still working.
• You might want to set mutual exclusions between WSA and MBAM -- the files to exclude in WSA are >>HERE<<; let us know if you need help with that. The attached screen shot shows an example (of a different AV, obviously) of how to exclude WSA in MBAM.
• Sometimes slowdowns may be the result of older hardware, insufficient RAM, cluttered or damaged disks, excessively tight security settings, etc.
• MANY, MANY factors contribute to scan times -- these include:

Size of disk
Disk type
Disk speed
Disk caching
CPU speed
Controller type and speed
Operating System used
Amount of files (including temp files!)
Amount of folders
Amount of archived files such as zip, rar, sfx, etc. (if this is enabled)
Rootkit scan or not (if this is enabled)
PUM/PUP scans
Other security programs running at the same time that may potentially be monitoring all file accesses by any other process.
Drive integrity - if a drive is failing it can take a long time to ignore and bypass sectors on a disk or simply fail period and hang the scan.
Other ongoing disk I/O processes
System being infected can also affect speed of scans
Also note that changes in the MBAM database can also cause scan times to increase or decrease, so that's another factor to consider, as mentioned => HERE <=

 

It would help if we could see a bit more information about your MBAM installation and the scans.

So, if possible, please attach to your next reply the following items:

1. A checkresults.txt log file from MBAM-check -- the instructions are here: Diagnostic Logs
2. An MBAM scan log or two -- please let us know if you need help attaching and uploading it.

Thanks,

[Tj56]

The situation is getting worse.  I tried to run MBAM today with the intent to provide you with some specific run times for each module.  Here is a brief synopsis of what occured.

CheckResults.txt

[Tj56]

Sorry, I meant to post the following:

 

I started the scan and it ran for 10 minutes and then my screen went black.  I moved the mouse and hit the space bar, but the screen remained black.  I let the computer run for another 15 minutes and then the computer shut down altogether. I hit the power button and the "Rusuming Windows" appeared on the screen.  The monitor came back to life and MBAM resumed running.  The timer on the program display showed approximately 5 minutes has passed (odd, since it had been running for much longer than that).  At that point the PreScan finished and went on to Memory (1-2 min.) and then Startup (1 min.).  Then "2 objects found" appeared on the MBAM status screen.  Before I could click the link to check on the 2 object found the computer monitor went black again. I waited 10 minutes and then the computer shut off completely.  This time, I needed to log on as if I had shut off the computer manually.  After logging back on, MBAM was closed.  At that point, I ran the program to output the CheckResults.txt file which I just attached in the previous posting.

 

Any thoughts on how to proceed?

[daledoc1]

Hi:

 

I have escalated your case to our forum staff.

One of the staff members will review your logs and posts and advise you further.

 

Thanks for your patience,

[AdvancedSetup]

In order to proceed further we'll need to run various scans and get logs. As those cannot be run in this section of the forum please do the following and we'll at least initially treat it as an infection until otherwise rules out.

 

I would suggest following the advice from the topic here Available Assistance for Possibly Infected Computers and having one of the Experts assist you with looking into your issue.

Thank you