Stop Code: System Service Exception, Windows 10 PC

Hi Karin,

Corrupted display driver is one of the possible reasons why you are having a blue screen error, System Service Exception. For us to better assist you, kindly answer the following questions:

• Which Version and OS Build number of Windows 10 is currently installed? To check, press the Windows key, type winver, and press the Enter key.
• Have you tried updating the drivers of your computer to its latest update?

Meanwhile, you can try to follow the troubleshooting steps on this link to resolve blue screen issues.

We will be looking forward to your response.

Hi Eric,

thanks so much for your quick reply.

I have Windows version 1703 (OS Build 15063.483).

Earlier today I checked for a Windows update but it said I had the latest version.

I don't know how to update all drivers, unless that is automatically done when updating windows.

If you can help me with instructions on how to do that, I would very much appreciate it.

As to the troubleshooting link. I had looked at that before. That's why I uninstalled everything related to my new printer, even though I had used it without any problems for a few month.

I always got the blue screen just out of the sudden (however, several times I came back to a computer that had restarted when I was just leaving it running).

The link mentions a clean boot. I have not done that yet. I am no computer wizard and honestly didn't feel comfortable doing something more "radical" without understanding the implications.

Thanks for your help,

Karin

Hi,

It may help to look at the minidump files from the blue screen crashes.

Can you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via a public folder on OneDrive or similar site.

Here's a link on using OneDrive:

http://windows.microsoft.com/en-ca/onedrive/share-file-folder

If you have problems zipping the minidump files copy the minidump files to another location such as a folder on the Desktop

Also, you do not necessarily have to zip up the minidump files, you can upload them one at a time.

Hi,

I have uploaded the mindump files. Sorry, I couldn't compress them.

Here is the link:

https://1drv.ms/f/s!AogWsR1oYdSohRLhec9mK77KOI39

Thanks!

Karin

The minidump files show a consistent SYSTEM_SERVICE_EXCEPTION (3b) stop error caused by the aswSnx.sys:

BugCheck 3B, {c0000005, fffff80248d5d49a, ffffb10205297820, 0}

*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys

Probably caused by : aswSnx.sys ( aswSnx+283b4 )

The process that is consistently crashing is the mbam.exe:

PROCESS_NAME:  mbam.exe

The aswSnx.sys is an Avast driver and the mbam.exe is a Malwarebytes process.

So there appears to be a conflict between Avast and Malwarebytes.

Going by the dates on Avast drivers Avast may have been updated around the time the blue screen errors appeared.

As the date of Malwarebytes drivers appear to be from 2015 the older Malwarebytes process may be causing the newer Avast driver(s) to crash.

Try uninstalling Malwarebytes and see if the crashes resolve.

Afterwards you could try reinstalling Malwarebytes using the latest version.

Also, using the free Malwarebytes version (without real-time protection) should not cause a conflict with Avast.

The minidump files show a consistent SYSTEM_SERVICE_EXCEPTION (3b) stop error caused by the aswSnx.sys:

BugCheck 3B, {c0000005, fffff80248d5d49a, ffffb10205297820, 0}

*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys

Probably caused by : aswSnx.sys ( aswSnx+283b4 )

The process that is consistently crashing is the mbam.exe:

PROCESS_NAME:  mbam.exe

The aswSnx.sys is an Avast driver and the mbam.exe is a Malwarebytes process.

So there appears to be a conflict between Avast and Malwarebytes.

Going by the dates on Avast drivers Avast may have been updated around the time the blue screen errors appeared.

As the date of Malwarebytes drivers appear to be from 2015 the older Malwarebytes process may be causing the newer Avast driver(s) to crash.

Try uninstalling Malwarebytes and see if the crashes resolve.

Afterwards you could try reinstalling Malwarebytes using the latest version.

Also, using the free Malwarebytes version (without real-time protection) should not cause a conflict with Avast.

Hi,

thank you for all your help. It seems like uninstalling Malwarebytes and doing some cleanup with Glary Utilities helped.

I haven't tried reloading Malwarebytes yet, but might try the free version.

I appreciate your help.

Karin