Jump to content

gattaca

Members
  • Content Count

    14
  • Joined

  • Last visited

About gattaca

  • Rank
    New Member
  1. Hi, I have downloaded the beta. I uninstalled the regular version first, then clean booted. Then I installed the beta. The current status shows: 3.5.1.2522 1.0.418 1.0.6303 FWIW, the OLDER non-beta version, even with the real-time web turned off did BSOD in NETIO.SYS right before I did this... Was using Firefox. It had been a while but I figured it was a sign to go ahead and load the beta! Thanks!
  2. Thanks for posting how to turn the "Protection Turned Off" notifications. That's helpful! TY.
  3. DCollins and the MWAB team, Thank you for the steady updates and continuing to work on this issue!
  4. As a interim, I just added the MWAB extension to FF 61. FWIW, I've still not been able to reinstall MWAB into my test VM since removing it. I gotta think something did not get cleaned up in the registry and the MWAB "cleaner" is missing something with this newer version. I'm hoping the engineering teams find the root cause soon! TY and have a great upcoming holiday!
  5. I'm appending this here since it is related to the BSOD. After a number of BSOD, I uninstalled and then used the MWAB "cleaner" to remove all traces from my test VM. Since that time I have been unable to reinstall either the 3.5.1 or last attempt the 3.4.5 versions. Here's what the Windows logs say. So I'm thinking this is all related. Maybe this helps with all the BDOD too. At this point, I have no way of re-installing MWAB on my test VM until this is hashed out. Thanks! Faulting application name: mb-support.exe, version: 1.1.2.471, time stamp: 0x5b1acb80 Faulting module name: KERNELBASE.dll, version: 10.0.17134.112, time stamp: 0xc863c6f9 Exception code: 0xe0434352 Fault offset: 0x0010db52 Faulting process id: 0x238 Faulting application start time: 0x01d40a828d7d1942 Faulting application path: C:\Users\xxxxx\AppData\Local\Temp\mwbC70C.tmp\mb-support.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 589862df-e0c9-4759-99a3-215bfcc550fd Faulting package full name: Faulting package-relative application ID:
  6. Yeap. That is consistent with what I found. Turn them on = BSOD.
  7. Hi Guys, Ditto on this --> "The only major thing I can think of that happened around the same time was the June update for Windows 10 (1709 in my case) so I think Microsoft have changed something which now makes one of the MBAM modules incompatible. I know you were asking what changed between 3.4.5 and 3.5.1 if the former still works ok, but I thought I'd add this point as it seems many people starting having this issue about the same time Windows was updated." I too upgraded to 3.5.1 when it was offered and it worked fine on my 2 systems (PC + test VM) with SAV, Hitman Pro, Webroot, ... .until that June Windows update. That update patched a BUNCH of critical things. so I agree about the interaction b/c that IS when the BSOD started on my VM b/c it was patched first.... then as soon as I let the June update apply to my main PC system, the BSOD started there. I still have MBAM 3.5.1 installed on my PC (but not VM) but all 4 "real-time" protections are DISABLED on the PC. I'm running scans periodically hoping that's better than nothing. For my VM, MBAM is not present and won't reinstall per earlier and below. If backing off to 3.4.5 is working with the real-time protections, that may be an option and I am willing to try that for my VM. Is there an official download point from your site for this older version? I do not like downloading stuff via google references. Also, as I noted earlier in this thread, I removed MBAB 3.5.1 from my VM and then when I tried to reinstall it, it would not reinstall. It complained about strange registry issues so all those BSOD may have really hozed something - unclear. Be careful before you uninstall it. BTW, I even used MBAM's wipe tool and I still cannot reinstall MBAM 3.5.1 on my test VM. So I've been waiting for answer to the BSOD before even trying to raise the won't reinstall issue on my VM (VMware Workstation, current). Please keep all this in mind. This is also why I tried disabling the real-time protections on my PC first! I also agree that lots of people who like to defer the Windows Updates are starting to apply the June update. I usually get it on the first day. Thanks!
  8. Hi Guys, Any progress on the BSOD? Thanks!
  9. FWIW, I use FF 95% of the time. Always latest version, always up to date. Verified as Quantum 64 bit 60.0.2.
  10. I'm not seeing a memory.dmp file in c:\windows. could it be hiding somewhere else? Thanks! I also searched for on c:\ dir memory.dmp /s No files found.
  11. Yes sir. Real Time Protections on the first page. MWB Premium 3.5.1 1) Web Protection OFF 2) Exploit Protection OFF 3) Malware Protection OFF 4) Ransomware Protection OFF I'm sorry, I did not try just 1 or 2, figured I'd start maxed out OFF. I'm afraid to let it keep BSOD b/c of what I say below for what happened to my VM. As soon as I turned these off, the BOSD (like is screen capped later on) stopped. I made no other changes. The resaon I noticed this sequence is b/c I usually update first a VM, then it stated the BSOD. And for some reason I cannot remember, something flagged MWAB as the cause, so I removed it from the system. Then it would not cleanly uninstall, so then I used the MB-CLEAN to remove it all. After that, the BSOD in the VM stopped. However, now I cannot reinstall MWAB Pro 3.5.1 b/c it complains on the install with a really werid error. I'd say fix the BSOD first and then we can see why my reinstall is failing. I have a feeling they are related. Thanks!
  12. OK here's the one from the setup I did last. Currently all the real time protections are disabled in malwarebytes and the BSOD have stopped. I left it installed b/c after removing it and using the clean tool in the VM, I cannot get it to reinstall at all. Later. TY! mbst-grab-results.zip
  13. With this last Windows 10 update, I've been seeing multiple BSOD from the NetIO.SYS driver just as you have reported. I am / was running the latest versions. The only way I've been able to calm the system is to disable all of the real-time scanners in Malwarebytes first page. I also had Malwarebytes Pro in a VM and it started do the same thing.. BSOD, BSOD. It trapped that machine so many times I had to remove Malwarebytes. Then I used the clean-mb tool to remove, reboot etc.. after that the BSOD stopped...but now I cannot reinstall malwarebytes. Getting a "Class not registered" error and I am using "Run as Admin".. Go figure. There is something definitely up between even the latest Malwarebytes Pro and this last Windows 10 update which I applied recently. I also run SAV, and Webroot and never had a problem. I've disabled those and they don't seem to be the culprit..
×
×
  • 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.