BSOD avastsvc.exe & aswmonflt.sys

Sorry if this is a double-post, but I got an error in the forums on the first try.

Anyway, I have a Gateway FX7026 with a clean install of Windows 7 Pro 64-bit, with Avast Home Free, CCleaner, Malwarebytes Free, Office 2007 Enterprise, and league of Legends. Three days in to the new install, and I get a BSOD, for which the windbg crash analysis is pasted below. Any help on the cause/solution would be fantastic. Thanks in advance!

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002efe932, address which referenced memory

Debugging Details:

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ff100
0000000000000002

CURRENT_IRQL: 2

FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02efe932 48890a mov qword ptr [rdx],rcx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: AvastSvc.exe

TRAP_FRAME: fffff88005fb8e10 – (.trap 0xfffff88005fb8e10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000019 rbx=0000000000000000 rcx=fffff88005fb9040
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002efe932 rsp=fffff88005fb8fa0 rbp=0000000000000000
r8=fffff88005fb9040 r9=0000000000000006 r10=0000007c40004048
r11=0000007ffffffff8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KxWaitForLockOwnerShip+0x12:
fffff80002efe932 48890a mov qword ptr [rdx],rcx ds:0206:0000000000000002=???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ecd2e9 to fffff80002ecdd40

STACK_TEXT:
fffff88005fb8cc8 fffff80002ecd2e9 : 000000000000000a 0000000000000002 0000000000000002 0000000000000001 : nt!KeBugCheckEx
fffff88005fb8cd0 fffff80002ecbf60 : fffffa8000000000 0000000000000000 0000000000000000 fffff80003102d68 : nt!KiBugCheckDispatch+0x69
fffff88005fb8e10 fffff80002efe932 : 0000000000000000 fffffa8006aff4e0 0000000000000000 fffff80003042e80 : nt!KiPageFault+0x260
fffff88005fb8fa0 fffff80002ed6e1e : fffff80003102d68 fffff80003095f20 0000000000000000 fffff9800fb0003f : nt!KxWaitForLockOwnerShip+0x12
fffff88005fb8fd0 fffff80002eecfab : 0000000000000000 00000000000d5c18 fffff80003102d48 00000000000d8a97 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x7e
fffff88005fb9020 fffff80002edd05c : 2aaaaaaaaaaaaaab fffffa8002814480 0000058000000000 fffffa8002814480 : nt!MiInsertPageInList+0x12b
fffff88005fb9070 fffff80002ef115f : 000000000023f000 fffffa8002814480 0000000000000000 fffff88005fb9368 : nt!MiPfnShareCountIsZero+0x19c
fffff88005fb90e0 fffff800031dd9a9 : fffff98010380000 fffff8a00d201980 fffff8a000000000 0000000000000000 : nt!MmUnmapViewInSystemCache+0x51f
fffff88005fb93c0 fffff80002ef098b : 0000000000200000 fffffa80066302d0 0000000000000000 0000000000300000 : nt!CcUnmapVacb+0x5d
fffff88005fb9400 fffff80002ee3219 : fffff98010680001 0000000000300000 fffffa8006bae6e0 fffffa8006630e10 : nt!CcUnmapVacbArray+0x1bb
fffff88005fb9490 fffff800031b6aa2 : 0000000000000000 0000000000300000 fffff88005fb9560 fffff88005fb95f0 : nt!CcGetVirtualAddress+0x38a
fffff88005fb9520 fffff880012c4f08 : fffff88000000000 0000000000000005 fffffa8006bc1d60 fffffa8000080001 : nt!CcCopyRead+0x132
fffff88005fb95e0 fffff8800103b098 : fffffa80069408c0 fffffa8006bc1cf8 0000000000000000 0000000000000001 : Ntfs!NtfsCopyReadA+0x1a8
fffff88005fb97c0 fffff8800103e8ba : fffff88005fb98b8 fffffa8009957203 fffff88005fb9a00 0000000000000000 : fltmgr!FltpPerformFastIoCall+0x88
fffff88005fb9820 fffff8800104c1a0 : 0000000000000004 0000000000000000 fffffa80069408c0 0000000000000000 : fltmgr!FltpPassThroughFastIo+0xda
fffff88005fb9860 fffff88004850633 : fffffa80067c1880 fffffa8000000000 0000000000000001 fffffa800a1866f0 : fltmgr!FltReadFile+0x260
fffff88005fb9940 fffffa80067c1880 : fffffa8000000000 0000000000000001 fffffa800a1866f0 fffff88007ed0020 : aswMonFlt+0x7633
fffff88005fb9948 fffffa8000000000 : 0000000000000001 fffffa800a1866f0 fffff88007ed0020 fffffa8000000004 : 0xfffffa80067c1880 fffff88005fb9950 0000000000000001 : fffffa800a1866f0 fffff88007ed0020 fffffa8000000004 fffff88005fb9a08 : 0xfffffa8000000000
fffff88005fb9958 fffffa800a1866f0 : fffff88007ed0020 fffffa8000000004 fffff88005fb9a08 0000000000000000 : 0x1
fffff88005fb9960 fffff88007ed0020 : fffffa8000000004 fffff88005fb9a08 0000000000000000 0000000000000000 : 0xfffffa800a1866f0 fffff88005fb9968 fffffa8000000004 : fffff88005fb9a08 0000000000000000 0000000000000000 fffffa8006652f30 : 0xfffff88007ed0020
fffff88005fb9970 fffff88005fb9a08 : 0000000000000000 0000000000000000 fffffa8006652f30 0008000000000004 : 0xfffffa8000000004 fffff88005fb9978 0000000000000000 : 0000000000000000 fffffa8006652f30 0008000000000004 0000000000000000 : 0xfffff88005fb9a08

STACK_COMMAND: kb

FOLLOWUP_IP:
aswMonFlt+7633
fffff880`04850633 ?? ???

SYMBOL_STACK_INDEX: 10

SYMBOL_NAME: aswMonFlt+7633

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: aswMonFlt

IMAGE_NAME: aswMonFlt.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f56a56f

FAILURE_BUCKET_ID: X64_0xA_aswMonFlt+7633

BUCKET_ID: X64_0xA_aswMonFlt+7633

Followup: MachineOwner

0: kd> lmvm aswMonFlt
start end module name
fffff88004849000 fffff88004880000 aswMonFlt T (no symbols)
Loaded symbol image file: aswMonFlt.sys
Image path: ??\C:\Windows\system32\drivers\aswMonFlt.sys
Image name: aswMonFlt.sys
Timestamp: Tue Mar 06 16:01:51 2012 (4F56A56F)
CheckSum: 0001E1F5
ImageSize: 00037000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Hi Mordeen,

I’m just a forum member, But I’m going to give you some suggestions.

First things first, Is Avast and the Operating system fully updated?

Can you reproduce this error? for example does it happen when you do something specific?

Try disabling the the sandbox, if the BSOD still occurs switch it back on.

Then try disabling Shields one by one to see if one of them are at fault.

How often does this BSOD error occur?

Regards,
Hellion