Stability issues. FX-6300 and . Frequent Freezes

Alright - I reloaded the machine with a different motherboard and it still crashed/froze so I know it's not the motherboard.
I ran Driver Verifier this morning and upon first boot got a BSOD. Here is the Windbg analysis of the dump. This is after a fresh reload with a few basic programs. Does this shed any light?

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: 00000000000001f0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002cda325, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0d100
GetUlongFromAddress: unable to read from fffff80002f0d1c0
00000000000001f0 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeSetEvent+1e3
fffff800`02cda325 488b00 mov rax,qword ptr [rax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0xA

PROCESS_NAME: System

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

TRAP_FRAME: fffff88003316950 -- (.trap 0xfffff88003316950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000001f0 rbx=0000000000000000 rcx=fffff880026f2210
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cda325 rsp=fffff88003316ae0 rbp=0000000000000000
r8=0000000000000000 r9=fffff88002fd7180 r10=00000000000001f0
r11=fffff80002e8d480 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt!KeSetEvent+0x1e3:
fffff800`02cda325 488b00 mov rax,qword ptr [rax] ds:00000000`000001f0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cd5169 to fffff80002cd5bc0

STACK_TEXT:
fffff880`03316808 fffff800`02cd5169 : 00000000`0000000a 00000000`000001f0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03316810 fffff800`02cd3de0 : 00000000`00000160 00000000`00000000 00000000`0000000d fffff880`026f2208 : nt!KiBugCheckDispatch+0x69
fffff880`03316950 fffff800`02cda325 : fffffa80`061a1402 fffffa80`061a1410 00000000`00000000 fffff980`14816ea0 : nt!KiPageFault+0x260
fffff880`03316ae0 fffff880`069aa817 : fffff880`00000000 fffff980`00000008 fffff800`02e83d00 fffffa80`06b6ca70 : nt!KeSetEvent+0x1e3
fffff880`03316b50 fffff880`00000000 : fffff980`00000008 fffff800`02e83d00 fffffa80`06b6ca70 fffffa80`061a1410 : MBfilt64+0x1817
fffff880`03316b58 fffff980`00000008 : fffff800`02e83d00 fffffa80`06b6ca70 fffffa80`061a1410 fffff800`0317d3fb : 0xfffff880`00000000
fffff880`03316b60 fffff800`02e83d00 : fffffa80`06b6ca70 fffffa80`061a1410 fffff800`0317d3fb fffffa80`061a1410 : 0xfffff980`00000008
fffff880`03316b68 fffffa80`06b6ca70 : fffffa80`061a1410 fffff800`0317d3fb fffffa80`061a1410 fffffa80`061a1410 : nt!ViPendingWorkers
fffff880`03316b70 fffffa80`061a1410 : fffff800`0317d3fb fffffa80`061a1410 fffffa80`061a1410 fffff980`14817000 : 0xfffffa80`06b6ca70
fffff880`03316b78 fffff800`0317d3fb : fffffa80`061a1410 fffffa80`061a1410 fffff980`14817000 fffff980`14816ea0 : 0xfffffa80`061a1410
fffff880`03316b80 fffff800`0317d47c : fffff800`02e83d60 00000000`00000080 fffffa80`036649e0 00000000`00000100 : nt!ViPendingCompleteAfterWait+0x7b
fffff880`03316bc0 fffff800`02f7173a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ViPendingWorkerThread+0x2c
fffff880`03316c00 fffff800`02cc68e6 : fffff800`02e50e80 fffffa80`036f0040 fffff800`02e5ecc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03316c40 00000000`00000000 : fffff880`03317000 fffff880`03311000 fffff880`033168d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
MBfilt64+1817
fffff880`069aa817 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: MBfilt64+1817

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: MBfilt64

IMAGE_NAME: MBfilt64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a7267b0

FAILURE_BUCKET_ID: X64_0xA_VRF_MBfilt64+1817

BUCKET_ID: X64_0xA_VRF_MBfilt64+1817

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xa_vrf_mbfilt64+1817

FAILURE_ID_HASH: {3414a0c9-f17d-f07d-746a-a89ad9b168e6}

Followup: MachineOwner

I put in faster RAM and it stopped the crashes. :)

G.SKILL 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Dual Channel Kit Desktop Memory Model F3-12800CL9D-4GBNQ


G.SKILL 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Dual Channel Kit Desktop Memory Model F3-12800CL9D-4GBNQ - Newegg.com

I am happy to report that I found the problem causing all of my stability issues - we had AVG 2012 and as soon as we updated our server/clients to AVG 2013 - the crashes stopped!

Thank you for all your help and time!