Jump to content

Recommended Posts

25 minutes ago, dcollins said:

This issue is from the Web Protection driver. If you disable Web Protection, the issue should go away. Downgrading to 3.4.5 should also work as it uses an older version of the driver that doesn't have this issue.

I just got a BSOD minutes ago.  I'm just going to downgrade to 3.4.5.

Share this post


Link to post
Share on other sites

I'm currently using 3.4.5.  I've tried turning off application updates but they won't stay turned off.

Share this post


Link to post
Share on other sites

Good afternoon. Let me start out by thanking you for providing your feedback on these blue screen issues with Malwarebytes. We are still trying to track down the root cause of the issue, but need a bit more information if possible. Specifically, can you please try the following:
1. Make sure you are on Malwarebytes 3.5.1 with Component Package version 1.0.374. You can check this under Settings -> About inside of Malwarebytes.
2. Disable the Web Protection, but leave all other protection modules enabled. You can do this under Settings -> Protection.
3. Use your computer normally and let us know if you get a blue screen or not.

Thanks for your feedback and patience while we work through this issue.

Share this post


Link to post
Share on other sites
2 hours ago, hopper15 said:

I just got a BSOD minutes ago.  I'm just going to downgrade to 3.4.5.

I unchecked web protection only, left the others checked on Saturday after a BSOD. I haven't had one since, but I'm not confident I won't. I've had 3 BSOD since June 15th. Looking back, I was watching/listening to a show on Youtube at the time or had one paused in another tab. I swear I read something before I found this thread that this netio.sys crash may have been caused by an outdated video driver, however mine is shown to be the best available driver. I haven't watched any youtube videos since and frankly I'm not willing to risk it yet.

As for reverting back to 3.4.5, wouldn't I have uninstall the current version? Saying revert back almost sounds like one could just apply that version without doing a uninstall. Or it could just be my understanding of terms used.

Edited by 1776blues

Share this post


Link to post
Share on other sites
13 minutes ago, dcollins said:

Good afternoon. Let me start out by thanking you for providing your feedback on these blue screen issues with Malwarebytes. We are still trying to track down the root cause of the issue, but need a bit more information if possible. Specifically, can you please try the following:
1. Make sure you are on Malwarebytes 3.5.1 with Component Package version 1.0.374. You can check this under Settings -> About inside of Malwarebytes.
2. Disable the Web Protection, but leave all other protection modules enabled. You can do this under Settings -> Protection.
3. Use your computer normally and let us know if you get a blue screen or not.

Thanks for your feedback and patience while we work through this issue.

Thanks, I did this as I noted recently

Share this post


Link to post
Share on other sites
1 hour ago, 1776blues said:

Confirmed 1.0.374

Confirmed Web Protection ONLY disabled.

Using this on my main PC, not the VM which I cannot reinstall due to errors posted earlier.

Thanks!

 

Share this post


Link to post
Share on other sites

I had installed 3.4.5 over the existing 3.5.1  and reinstalled NOD32 from Eset. Seemed to be working ok and then just now I got hit with a BSOD. 

 

On Mon 6/25/2018 6:59:05 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: eamonm.sys (eamonm+0x11C26)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034A05D0, 0xFFFFF8800A61EEA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\eamonm.sys
product: ESET Security
company: ESET
description: Amon monitor
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: eamonm.sys (Amon monitor, ESET).
Google query: eamonm.sys ESET SYSTEM_SERVICE_EXCEPTION

I have disabled ALL MBam shield and have and will keep MBAM from running even with everything disabled.

Edited by frozen

Share this post


Link to post
Share on other sites
34 minutes ago, frozen said:

I had installed 3.4.5 over the existing 3.5.1  and reinstalled NOD32 from Eset. Seemed to be working ok and then just now I got hit with a BSOD. 

 

On Mon 6/25/2018 6:59:05 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: eamonm.sys (eamonm+0x11C26)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034A05D0, 0xFFFFF8800A61EEA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\eamonm.sys
product: ESET Security
company: ESET
description: Amon monitor
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: eamonm.sys (Amon monitor, ESET).
Google query: eamonm.sys ESET SYSTEM_SERVICE_EXCEPTION

I have disabled ALL MBam shield and have and will keep MBAM from running even with everything disabled.

Curious if the BSOD after the installation of 3.4.5 over 3.5.1 could be caused by 3.5.1 entries/commands left in the registry. I'm no expert but this sounds plausible to me. Then again, I'm no expert.....oops I said that already. I''m waiting for the fix......patiently

Edited by 1776blues

Share this post


Link to post
Share on other sites

image.png.aeffde0dcc33261da8e9acd403b5f548.png

 

that is what it is showing in the version screen but as it currently stands it is moot since all protection is disabled and MBAM is shutdown aka it is just taking up space on my hard drive.

Share this post


Link to post
Share on other sites

The only way I have managed to make it past 2 days (aka 4 days) with MBAM 3.5.4 fully enabled was to uninstall ESET Antivirus. Then stupid me I did not feel that running a Windows7 system with only MBAM alone was sufficient security decided to downgrade 3.4.5 by installing it over top of 3.5.1 and install Eset NOD32. The machine lasted 2 days before a BSOD occurred.

 

Share this post


Link to post
Share on other sites

If you still with to run Malwarebytes but want an AV that will function without issues alongside it until this conflict is resolved then you may install Microsoft Security Essentials if you're running Windows Vista or Windows 7 or of course you can just enable Windows Defender if you're running Windows 8/8.1 or Windows 10.

There are also a few other free alternatives out there that I've heard good things about including the recently released free version of Kaspersky, Avast! and Avira.

Any of those should do the trick until the problem with ESET is resolved so that you may continue to use an AV layer in the meantime if you wish.

Share this post


Link to post
Share on other sites
12 minutes ago, exile360 said:

If you still with to run Malwarebytes but want an AV that will function without issues alongside it until this conflict is resolved then you may install Microsoft Security Essentials if you're running Windows Vista or Windows 7 or of course you can just enable Windows Defender if you're running Windows 8/8.1 or Windows 10.

There are also a few other free alternatives out there that I've heard good things about including the recently released free version of Kaspersky, Avast! and Avira.

Any of those should do the trick until the problem with ESET is resolved so that you may continue to use an AV layer in the meantime if you wish.

I have Avast Internet Security and still had 3 BSOD'S since the update I performed on June 14.

Share this post


Link to post
Share on other sites

So now I do not know if I try to get MBAM which is at 3.5.1 to auto update back to 3.5.4 and uninstall NOD32 and go to with MS Security Essentials or just leave MBAM 3.5.1 totally disable and run NOD32. 

Share this post


Link to post
Share on other sites

It's totally up to you, but either way hopefully the fix for this issue will be released soon.  I haven't heard anything new about the next version yet but I do expect that it won't be too long before it gets released so hopefully you won't have a long wait regardless of what you decide to do.

Share this post


Link to post
Share on other sites

Installing 3.4.5 over top 3.5.1 is a puzzling decision.  But whatever works for you I guess.

Edited by Sfrush

Share this post


Link to post
Share on other sites

@frozen installing 3.4.5 over top of 3.5.1 will lead to strange circumstances, in fact I'm surprised it worked at all. The real test would be to remove 3.5.1 and then install 3.4.5. I believe that's why you're still seeing the blue screen, because we didn't have any reports of this type of issue with 3.4.5.

Share this post


Link to post
Share on other sites

I checked for updates within the MBAM app last night and I am now sitting at 

image.png.ae708cd3d895d94a8c0720cedcfd484d.png

I have Eset Antivirus installed and have web protection disabled.

Share this post


Link to post
Share on other sites
1 hour ago, benvl said:

Of course one should remove 3.5.1 before installing 3.4.5.

 

regards Ben

Thanks, I thought so, but wasn't sure cause you never know for sure.

Share this post


Link to post
Share on other sites
15 hours ago, frozen said:

I had installed 3.4.5 over the existing 3.5.1  and reinstalled NOD32 from Eset. Seemed to be working ok and then just now I got hit with a BSOD. 

 

On Mon 6/25/2018 6:59:05 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: eamonm.sys (eamonm+0x11C26)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034A05D0, 0xFFFFF8800A61EEA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\eamonm.sys
product: ESET Security
company: ESET
description: Amon monitor
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: eamonm.sys (Amon monitor, ESET).
Google query: eamonm.sys ESET SYSTEM_SERVICE_EXCEPTION

I have disabled ALL MBam shield and have and will keep MBAM from running even with everything disabled.

Note - this isn't the same BSOD and seems to be related to ESET, not MBAM. I run these two side by side but I installed ESET first. It might be worth completely uninstalling both MBAM (as seuggested by the other posts) and ESET. Then reinstall ESET first, followed by MBAM 3.4.5 and make sure both apps have exclusions for each other.

Share this post


Link to post
Share on other sites

Believe me I have been dealing with these BSOD for almost a month now and its MBAM interacting with other software not just Eset. I lost count on how many times I have seen Windows7 BSOD. Sometimes these BSOD have no reference to Eset whatsoever . Both of Eset and MBAM worked fine for months without any exclusions and others here have BSOD and they do not even have ESET installed. As with all software testing one should not change multiple items/settings as that does not help indicate what has fixed the issue. Currently using MBAM 3.5.1 without web protection and ESET without any exclusions for each other. The BSOD may take several days before it occurs on this Windows7 computer.

Share this post


Link to post
Share on other sites

Hi,

 

Just uninstall 3.5.1 and reinstall 3 .4.5 all protections enabled and wait until they have solved it. See my previous comment for download link.

regards Ben

Edited by benvl

Share this post


Link to post
Share on other sites
On 6/25/2018 at 6:09 PM, dcollins said:

Good afternoon. Let me start out by thanking you for providing your feedback on these blue screen issues with Malwarebytes. We are still trying to track down the root cause of the issue, but need a bit more information if possible. Specifically, can you please try the following:
1. Make sure you are on Malwarebytes 3.5.1 with Component Package version 1.0.374. You can check this under Settings -> About inside of Malwarebytes.
2. Disable the Web Protection, but leave all other protection modules enabled. You can do this under Settings -> Protection.
3. Use your computer normally and let us know if you get a blue screen or not.

Thanks for your feedback and patience while we work through this issue.

This worked for me, however I am very uncomfortable with this sate of protection.  Is there no ETA yet as to a fix?

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • 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.