BummerMan
-
Posts
20 -
Joined
-
Last visited
-
Totally agreed over here. It's not that I've spent countless hours on re-installing all software and drivers I could think of, stress-testing the system, basically going to the brink of losing my sanity, sending one report + bundle of log files one after another to MBAM, and all that's just the quality time / hours spent, if you value it at $0/hr ... In addition, I've bought a new PSU, a new SSD, new controller interface cards and what the F*** not. And still, I'm stuck with the same issue. How many months have gone by now? I am running Malwarebytes Premium on Win7 / 64bit Ultimate. The setup has all the bells and whistles I can think of, as well as no remnants of old drivers or software hanging around no more. And yeah, none of the workarounds that have been offered to me from MBAM did work, either. ... Well, the exception that being to quit using MBAM completely and just use whatever antivirus software you have for the time being. I'd like MBAM to put a bit more effort and pressure on this issue, honestly. And that's putting my opinion mildly. I appreciate all the effort put into this issue thus far, but the reality is that MBAM is unusable as for now, in my case at least, and I think the same goes for many other users as well.
-
Typo correction: "The system freezes that YOU've been experiencing are symptomatically ~1:1 similar to what I've been experiencing." Cheers,
-
I have the same issue with my Win7 / 64 bit Ultimate w/ all the latest updates, done exactly the same routines as you have to check out what could be the culprit and whatnot. I've been trying just about everything in terms of hardware and software and the likely culprit is MBAM v.s. ESET v.s. Microsoft's own code spaghetti. Been bombarding the MBAM customer support for quite the while now, and they seem to be scratching their heads in silence. The system freezes that I've been experiencing are symptomatically 1:1 similar to what I've been experiencing. The only difference in my case was that I thought everything was fine since I didn't have any freeze-ups for a couple of days, until I noticed that the MBAM application had completely frozen up all on its own, that's why I had been able to be back in business with no problems. *sigh and a tired laughter* Sure would be nice if they'd come up with a solution; I'm running out of ideas back here, too. Keep us posted if you come up with anything! Cheers!
-
Now that I've ran the computer for a while, again I am in a situation where I'm getting intermittent freeze-ups, esp. during times of high utilization, esp. web browsing seems to correlate with the freeze-up problem. Then again, as we're back to square one, I've noticed the same freezing with all USB devices plugged out apart from the keyboard and mouse, the culprit is either some next level-whack-a-mole malware or a conflict between ESET and MBAM that's extremely hard to pinpoint. So, the reason why my Windows 7 OS seemed to run OK for a while had apparently been caused by MBAM not utilizing correctly during start-up. That problem is now "fixed", and thus; back to square one with the freeze-ups. One idea would be to go through the possible suspects module-by-module - if someone could answer this question: should I run MBAM's self protection module on Windows' early start? I remembered that I didn't have it on that mode for some reason the last time I checked it out.
-
Situation update: The Threat Scan in MBAM after running Repair Tool finished without any problems (or detections), but now the Windows 7 task bar and its icons (incl. system tray) are frozen in the usual manner as they have done for some while now. I have filed two support tickets over this issue, as mentioned in my previous posts ( the first one being # 2476090 and the second one that I filed just now is # 2476090 ). All help kindly appreciated. Thank you.
-
The MBAM main window is now unfrozen from its stupor and is now going through the filesystem. However, upon trying to use the MBAM Repair Tool 's separate log gathering feature, I got this "AutoIt Error" message again (username omitted from the screencap): Might want to look into it. Thanks.
-
OK, I got a support ticket in the mail, it's # 2478469 . You can basically treat it as being in the same continuation with my previous support ticket, # 2476090 , so that there is no confusion over that. I'm running the MBAM Premium's Threat Scan right now. Its scanning process seems to be running forward just fine for a while, then it gets stuck, (i.e. right now the program's progress progress indicator's green-colored wheel has become stuck and inanimate on the "Scanning memory objects" section.) I took a backup of the MBAM Repair Tool logs+findings, can send them over as a separate .zip file if necessary. Thanks so much.
-
Update: I ran the MBAM Repair Tool again. Re-downloaded it from the link to make sure it was the latest version [Repair Tool version 1.5.3.553]. I can now get to the MBAM main window. The desktop alert is still warning about the protection modules being turned off. And, as it MBAM is checking for updates, it is once again frozen the OS in the same manner as described previously/aboce, i.e. everything else but the active window, which in this case is the MBAM main window, is stuck. I'll wait it out and see what happens. I already used the Repair Tool to send a ticket w/ a description of the s(h)ituation, but it too is now stuck. Might be 5-15 mins once more until it clears up, will have to wait and see. Meanwhile, and during all of this ordeal - ESET has not been giving any troubles. Its latest modules+db updates are from today, and so forth. Will keep you posted and post the support req. ticket # once I get it, if I get it. Thanks.
-
After a few mins more of further waiting, I got the alert box that the real-time threat protection modules were off, the task bar icons as well as all other icon in the system tray work once more, except MBAM. I can right click on the MBAM icon to get the usual drop-down list of modules in use (all of them show up as they'd been checked active), but the program itself doesn't open the main window. Sheesh ...
-
P.P.S. If it's of any valuable knowledge, the system is showing the same symptoms that it had previously. I have the regular mouse pointer, but as I move it on top of the task bar and/or system tray, it becomes that good'ole rolling wheel-busy symbol. Everything WAS working just fine up until a certain point of this year, and from there on, after the exclusion lists that we just went thru with exile360 the past week (see post above), things were working again in a seemingly normal fashion. And now, I'm once more stuck in the same mud. *sigh*
-
OK, to clarify things; just checked out the tray icons altogether and it seems that none of them are working, MBAM seems to have parked itself into the driver's seat of the OS with around ~20% CPU utilization as I checked just a minute or so ago. So, everything seems to be unresponsive as for now, will keep you posted.
-
After 5-10 mins of waiting in the busy-limbo as I tried to launch MBAM after having just booted the machine, I get the MBAM tray icon, but can't click on it. Neither left- nor right click does anything at all.
-
OK, well.This is interesting. It seems that the reason for the outstandingly fast performance on my desktop sort of came into a more proper light when I noticed that MBAM isn't turning on any longer. It used to after I ran the fix tool, but now iAt's not appearing on the Win7 system tray upon startup Furthermore, when I try to start MBAM after a reboot manually, I get the same previously mentioned stuck/frozen up Windows UI. ( = the mouse cursor turns into the rolling "Busy" wheel symbol.) After the initial fix with the Support Tool and the exclusion lists, it worked just fine -- apparently, until the next reboot, and I didn't notice that. Now I'm waiting for what it is that MBAM is about to do next as I started it manually just now. Been a few minutes that it's been stuck in with that busy-cursor wheel'a'rollin'.
-
(P.S. To clarify my point: Everything is working as it should now, and has been for the past 24 hours or so. I am grateful and happy. Now I can get back to work! "Hooray!")
-
An old coder friend of mine once said; being a complete pessimist can only bring positive surprises. Well ... he was RIGHT. After adding MBAM to ESET's exclusion list and vice versa as instructed (by exile360), I haven't had a single freeze-up for around 24 hours now. Ran all kinds of heavy duty software to check out if that'd happen. So far, so good! :-) Now, the only thing that is left for this matter, for now, in my pessimistic viewpoint is that I still think everybody should keep an eye out for everybody (how does THAT make me sound? Hehe--); meaning, that one antivir/anti-malware software should seriously keep a basic tab on the other one if you should have one of each installed (i.e., in my case, MBAM + ESET). I am not a fan of exclusion lists - it easily serves as a vulnerability of its own. But enough of that. Until further notice, I thank you all for the good work you've done, and especially exile360 for helping me out. Never give up, and keep pushing forward. Thank you so much. All the best.
