BSODs cause by ntoskrnl.exe driver

There are different bugchecks.

The latest BSODs are pointing to Avast.

Code:

BugCheck C1, {fffff9803e944f10, fffff9803e944119, b340f8, 32}

*** WARNING: Unable to verify timestamp for aswStm.sys
*** ERROR: Module load completed but symbols could not be loaded for aswStm.sys
Probably caused by : aswStm.sys ( aswStm+4877 )

Followup: MachineOwner
---------

Uninstall Avast using Avast Uninstall Utility. At least as a test. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Last week, DS3 controllers caused BSODs there.

Code:

BugCheck 10D, {5, 0, 1202, fffffa800d00ec40}

*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+363a )

Followup: MachineOwner
---------

And it is the known issue for the latest driver, Version 0.7.1001.

Code:

    Image name: MijXfilt.sys
    Timestamp:        Sat May 12 09:57:12 2012 (4FADE6A0)

You need to get any other previous driver version to solve this particular issue, but unfortunately I dont know any source of it. One source was known to me, Playstation 3 controller(Dualshcok 3 or Sixaxis) driver for windows | MotioninJoy which does not work nowadays. You should search for any other alternative source.

Moreover, as there are multiple different bugchecks, it would be the best to test the health of the RAM modules. Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.