Jump to content

Antimalware release 2.1.8 sys driver crashes in windows 8

Recommended Posts

Antimalware release 2.1.8 sys driver crashes in windows 8, and causes blue screen on death with error code SYSTEM_SERVICE_EXCEPTION (tcpip). The mini dumpfile created by windows on crash identifies the sys driver of Antimalware as source of crash.

I assume the solution is that Antimalwarebytes needs to update its driver. Or is there antother solution?

Link to post
Share on other sites

Hello and :welcome: :


Version 2.1.8 has been released for several weeks without reports of BSOD on undamaged, uninfected systems.

In addition to driver issues, BSOD can also be caused by hardware problems or even malware (e.g. rootkits).


So, for starters, let's please start first with the basic 3 Diagnostic Logs -- please attach them to your next reply here in this thread.


Depending on what the logs show, the forum staff and experts may request additional information (e.g. the minidumps or full dumps and other data).


And they may likely refer you (or move this post) for deeper work, either in the special BSOD forum section or in the Malware Removal section.


Thank you,

Link to post
Share on other sites



There were only 2 diagnistic logs in the link you supplies, not 3. The files are attached. The FRST was run today. The mbam-check tool was run yesterday.


I have been experiencing the blue screen problem for a few weeks now. I didn't know it may have been connected to Antimalwarebytes before yesterday, when I found a dumpfile Reader that mentioned the sys driver of Antimalware. That's why I haven't posted the problem in this forum earlier.


Thank you for all the help I can get.





Link to post
Share on other sites



There were only 2 diagnistic logs in the link you supplies, not 3. The files are attached.


2 tools (FRST and mbam-check) to produce 3 logs (FRST.txt, Addition.txt and CheckResults.txt). :)

And it looks as if all 3 logs were successfully posted. :)


There is quite a bit going on with the system, including lots of PUPs in quarantine, evidence of infection and possible damage therefrom.


We'll need to wait for a staff member to review the logs and to advise you on how best to proceed.

Deep work for malware removal or BSOD repair is not permitted in this section of the forum.

Normally, with infected systems, we would suggest starting with the advice here: Available Assistance for Possibly Infected Computers

The next step would be to post these same logs in a new, separate topic in the malware removal forum section.

One of the malware experts will assist you there with scanning, cleanup and repair.

That's probably the best step at this time.


But let's wait to make sure the forum staff agree with that plan, rather than moving to the BSOD forum section.


Thanks for your patience,





Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
  • 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.