Memory Management BSOD

Experiencing completely random BSODs with 'Memory Management' error. These occur out of nowhere, usually after a few hours, even on unintensive tasks such as browsing web. Tested each RAM stick individually in memtest86+, 10+ passes no errors. Using one stick, I have yet to crash. The crashes only occur when combined, tried placing them paired and unpaired, the latter resulted in a crash much faster than usual. Set BIOS timings manually to 5-5-5-18-23, values reported by CPU-Z prior. Have yet to run a test on multiple sticks together.

Specs:
Windows 7 Ultimate x64
500W Antec Earthwatts
4GB Elixir RAM + 2GB AData (any combination of 2 or more sticks inevitably results in crash)
ASUS P5N-SLI
Intel Q6600 2.4GHz quad
Gigabyte GTX460 (single)

PSU and GPU are new, rest are a couple years old

appreciate any help

Your Avast Security software is the cause, please remove it and use MSE

Your Old Brother printer is obsolete and the driver it is currently using is out of date
Please visit the manufacturer's website and update the driver

Code:

BrPar64a.sys        fffff880`08624000    fffff880`0862e000    0x0000a000    0x40e17e92    29/06/2004 18:37:06

Faulting driver:

Code:

aswSnx.SYS        fffff880`042af000    fffff880`0432f000    0x00080000    0x4d65203b    23/02/2011 18:56:59

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8884, fffffa80033307b0, fffffa8003330bd0, 4}

Unable to load image \SystemRoot\System32\Drivers\aswSnx.SYS, Win32 error 0n2
*** 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+1b2f0 )

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa80033307b0
Arg3: fffffa8003330bd0
Arg4: 0000000000000004

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_8884

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f3c756 to fffff80002e98640

STACK_TEXT:  
fffff880`097c61a8 fffff800`02f3c756 : 00000000`0000001a 00000000`00008884 fffffa80`033307b0 fffffa80`03330bd0 : nt!KeBugCheckEx
fffff880`097c61b0 fffff800`02f9c9a5 : fffffa80`0620d348 fffffa80`06202000 00000000`00000000 00000000`00000020 : nt!MiRelinkStandbyPage+0xc6
fffff880`097c6220 fffff800`032a6b74 : fffffa80`0620c000 fffff880`097c65c0 fffff880`097c62f8 00000000`0214bb01 : nt!MmSetPfnListPriorities+0x175
fffff880`097c6270 fffff800`033085ea : 00000000`00000020 00000000`00000000 fffffa80`0620c000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`097c62c0 fffff800`0330ce2a : 00000000`00000000 00000000`0000004f 00000000`00000000 00001f80`00000001 : nt!PfSetSuperfetchInformation+0x199
fffff880`097c63a0 fffff880`042ca2f0 : 00000000`00000000 00000000`0214bbc8 fffffa80`0620c000 fffff800`42506650 : nt!NtSetSystemInformation+0xc8d
fffff880`097c6510 00000000`00000000 : 00000000`0214bbc8 fffffa80`0620c000 fffff800`42506650 fffffa80`0922e040 : aswSnx+0x1b2f0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswSnx+1b2f0
fffff880`042ca2f0 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  aswSnx+1b2f0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSnx

IMAGE_NAME:  aswSnx.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d65203b

FAILURE_BUCKET_ID:  X64_0x1a_8884_aswSnx+1b2f0

BUCKET_ID:  X64_0x1a_8884_aswSnx+1b2f0

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

wow, never would have thought of that.
will try this out, thanks!

ok replaced avast, but still crashed.
fresh dump attached

1651694 said:

ok replaced avast, but still crashed.
fresh dump attached

Uninstall your old printer driver since it is obsolete
Enable Driver Verifier since dumps show no probable causes
Driver Verifier - Enable and Disable
Then upload the newly created dumps

just checked windows update, says there is an update for my printer driver. should I install that first?
also about driver verifier, does my computer need to be on for 24 hours straight?

1651694 said:

just checked windows update, says there is an update for my printer driver. should I install that first?
also about driver verifier, does my computer need to be on for 24 hours straight?

Install the new update. Nope the process will normally take 1-2 hours max

after a couple driver verifier crashes at boot, hung at boot screen (glowing windows icon) for about 5 minutes, so booted into safe mode + networking. did not achieve full boot under driver verifier.
dump attached (no perfmon due to safe mode)

You can safely turn off driver verifier from safe mode

ASACPI.sys the 2005 version is a huge cause of BSODs

   Information

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005)

Code:

ASACPI.sys        fffff880`05421000    fffff880`05429000    0x00008000    0x42476c4c    28/03/2005 06:30:36

You will need to remove any LogMeIn software since the driver it is using is outdated

Code:

lmimirr.sys        fffff880`05429000    fffff880`05430000    0x00007000    0x461c108d    11/04/2007 02:32:45

done. will report back if problems continue.

thanks for all the help so far!