Jump to content

MBAM High CPU usage, fixed by re-install -- ramifications?


Recommended Posts

Within the last few days (days shortly after a re-install of a system image, where I had not had any high cpu problems .. and this didn't happen immediately ...however, I had transferred data from a Vista to a Win8 machine via a couple of different USB keys.) MBAM's CPU usage was 20-30%.

 

I googled, and found the comments about doing the clean removal, etc, did that ... and now all is well.

Ran MSRT as well, which ran clean, along with scans (I have MBAM & Norton IS -- paid.)

What I am curious about is what is generally happening, why does MBAM suddenly start taking up more CPU -- I'm trying to do a risk assessment here -- as there were some oddnesses with my paid password keeper during this time

Thanks!

 

MarketersGeek

Link to post
Share on other sites

Hi:
 
It's hard to say without more information (e.g. diagnostic logs).
However, it has long been the case for Windows that "system restore" can "break" the metadata of certain programs, especially security applications, such as MBAM and anti-virus programs, that rely on frequent, timed database updates, etc..
As a general rule, it's preferable to temporarily uninstall the security program BEFORE undertaking a system rollback, and then to reinstall it after.

I suppose the same advice might hold for a system image, as well.
 
If I understand your description correctly, you transferred "data" (including programs???) from Vista to a Win8 machine, after a system image reinstall?
 
I am just a home user, but if that's the case, it would not surprise me that something might have subtly "broken" during the process.  If you experienced issues with other software, as well, then that would further heighten my suspicion.
 
If everything is working OK now, then I wouldn't worry.
If you do have concerns, it would help us to see a bit of system info.

 

Please read the following and attach to your next reply the 3 requested logs - Diagnostic Logs (the 3 logs are: FRST.txt, Addition.txt and CheckResults.txt)

 

NOTE: More info about v2.1.6 HERE; User Guide ONLINE; User Guide PDF; FAQ: Common Questions, Issues, and their Solutions

Thanks,

Link to post
Share on other sites

Thanks, Dale ...

A system image is simply an image of selected folders along with the Windows OS ...

...it's not like system restore...at ALL...

It's a complete replacement of whatever was on my machine with a currently updated version of Windows & whatever programs are installed (at least the way I do it.).  Part of the process (an option when installing the system image) is to reformat the drive ...which I do.
...Every time I install from a system image, I update all the important items -- eg, mbam, Norton IS, Windows, (I look to see what's been updated in my installed programs since the last time I did a system image install.) and then make a new system image.

I'm not concerned too much about how my system is now; more concerned about what data might have been vulnerable during the time of high cpu use by mbam ... does that mean mbam was actually infected in some way?  I'm guessing not, but I'd kinda like a bit more information, if the information is to be had.

I know a bit about windows malware (started a malware training program, taken classes,etc) -- but I do know quite a bit about website hacks, as I have been cleaning up website hacks for 6 years now.

So, in short, I'm most curious, not about the stability of my system atm, but more about what has been discovered about what causes mbam to take up high cpu.  This is the first time it's happened to me.  As you might guess, I tend to run a pretty tight ship.

 

Thanks again,

 

MarketersGeek!

 

Link to post
Share on other sites

Don't see where to edit my post -- meant to add -- restoring from a system image is basically the same process as doing a clean install, except the image you install from is a currently updated windows version, and configured with the programs & their options which were installed at the time of making the image.

For a year I was doing clean installs, and when I got to the point I'd have to install over 1G of windows updates, I knew I needed a different process!!!

...and the files transferred were simply data files.  I need to find the info which stops auto-runs on USB keys ... :)

Link to post
Share on other sites

Hi:

 

I understand the difference between system restore and imaging. :)

 

I'm just saying that something might have been subtly corrupted during the process.

A clean reinstall of MBAM takes only a few minutes and is often the fastest way to get back up and running, resolving minor issues.

If you browse the forum here, you'll see that is often the case.

 

In any event, it's just educated speculation.

There is no way to know for sure without diagnostic info.

If you'd like the forum staff and experts to evaluate your system, then I suggest posting back with the diagnostic logs.

Perhaps they will point to something on the system.

 

Perhaps the forum staff will be able to provide more feedback for you when they spot this thread.

 

Thanks for your patience,

 

P.S. Sorry. Because of prior abuse by others, new forum members cannot edit their posts. :(

Link to post
Share on other sites

oops. misread that ... not quite 5 years.  29th of this month will be 5.
And I would agree, a system image install would make sense if the high cpu usage had been immediately coincident with the system image install ... but it wasn't ... it started happening a few days later ... :)

Thanks again, Dale!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.