[MbamElam.sys bsod and other issues]

11 hours ago, exile360 said:

Avast and Nord are still at the top of my list for suspects.  It might simply be that one of the products or even Malwarebytes itself updated too before you restarted, and once you rebooted, the issue emerged due to the new version.  As I mentioned earlier, we have seen issues with Avast recently, so I'm still leaning that way.

If you're using Glary to delay/manipulate the startup/timing of any of the security apps that could also be a factor, but seems less likely.  Dev/QA will likely analyze the memory dumps when they get the chance, but for now just make sure you have created a new restore point in case any more issues to show up so that you can roll back if needed without losing too many of your programs/changes you've made since then to the system.  You'll find instructions on how to create a restore point in this Microsoft support article if you need it.

I added exlusions based on recommendations online to avast and mbam, I can for nord as well think I will find them somewhere online.

[MbamElam.sys bsod and other issues]

Any ideas of what the cause was? Haven't restarted yet.

[MbamElam.sys bsod and other issues]

50 minutes ago, exile360 said:

One additional note; I also noticed that you have NordVPN installed, and recently Malwarebytes has had some compatibility issues with some third party VPN applications as well because they sometimes conflict with Malwarebytes' Web Protection component so you might also try uninstalling Nord if you do experience the issue again to see if that helps.

Okay, I'll keep that in mind too.

[MbamElam.sys bsod and other issues]

https://we.tl/t-0N7zFUjq0P

 

Here are the files... 👍

[MbamElam.sys bsod and other issues]

28 minutes ago, exile360 said:

Most likely, yes, just because Avast is likely to still load its drivers even when disabled.  Hopefully the issue was just a one time hiccup due to an update or recent change in the system, but please let us know if you encounter any further issues.

Two other things happened on the system since then from memory, I used cmd to try to bring the sidebar back on the desktop, glary utilities wanted to update to the latest version (haven't done that since I restored), and there may have been a win 10 update. The sidebar thing was the the last thing I done before it went awol, I restarted just after, do you think that you have caused it?

[MbamElam.sys bsod and other issues]

Here 👍

mbst-grab-results.zip

[MbamElam.sys bsod and other issues]

It's still running FRST, it's been on for like 15 mins, when it finishes i'll post back 👍. If it doesn't finish in the next 15 mins, I'll try to collect it again.

[MbamElam.sys bsod and other issues]

Hi,

I restored windows 10 back to 1am this morning, and mbam works again with the service running and set to "automatic" (apparently I can't change it access is denied), and avast free's ui didn't load for a little while but then it finally did, the service works and is also set to "automatic" (can't change again). So the system seems to be working.

Is uninstalling avast/mbam the only way to find out the cause? I was thinking changing one or the other to a delayed start but I can't. Thanks for replying.

[MbamElam.sys bsod and other issues]

Hi all, would seriously appreciate some help with this!

 

Recently after rebooting my pc, it says that my pc/device needs to be repaired because a critical system driver is missing or contains errors. \windows.old\WINDOWS/system32\DRIVERS\MbamElam.sys

 

I have tried disabling the Elam thing from startup (f8), it gets on windows, but mbam can't start the service, trying it manually from services.msc says (from memory) error 507, something about being unable to validate it. Avast free's UI also doesn't load, but apparently the shields are on. Win Def is on, I remember putting periodic scanning scanning on but not the AV. What could be the problem?

 

When I load windows, it gives me an option for either win 10 or win 10 pro, "pro" is the old version, the one that can't boot, never noticed this before, I can get to login with win 10 normal but haven't tried logging in, idk of this is relevant. I also looked in the driver folder and MbamElam.sys is there, why isn't it starting up?

 

Disabling Elam from startup probably has something to do with the AV/mbam being disabled, but it's the only way I can access win 10 pro. I can get into bootmode.

Recently I have installed a win areo application, a new screensaver, and some skins for classic start menu, as well as a new update. Restore might work here, although even though system protection is on I can't find a backup, although I think there was a one from the 18th with startup repair...

Any help?