
Yeah... I don't think it's supposed to be doing that?
mbam.exe does the same thing after it takes its merry 20-30 seconds to start up (with 3gb RAM and 100% of one core CPU).
This happened before and after updating the database (with no errors). No other (redundant, in my opinion) AV software is installed on this system, so no exceptions apply.
But I'm pretty sure this is one of the most extreme cases you guys have seen? I use MBAM Pro on my computer at home, and while its resource consumption does get a little... unruly... at times... it never resorted to this extreme an amount of runaway memory gobbling.
I tried "/debug" but it never offered to save a log, it just started and exited like normal. Not sure how to get that function to work...

Sign In
Create Account
Back to top











