I looked at your three most recent dumps. All three are Driver Verifier enabled dumps and all three blame Windows system drivers, which are very unlikely to be the cause. Turn off Driver Verifier: Driver Verifier - Enable and Disable. I also looked at the three dumps previous to those which are not Verifier enabled dumps. All three of those are bugcheck A. They blame ntkrnlmp.exe, a Windows system core file and very unlikely to the real cause. All three reference memory.
What AV and firewall are you using? Your perfmon report does not show either one.
I suggest that you test your RAM with Memtest following the instructions in this tutorial: RAM - Test with Memtest86+. Run Memtest from a cold boot after your computer has been off for an hour or so. Let it run for a minimum of seven passes. This will take 6-8 hours. Post back with your results.
Code:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0281a000 PsLoadedModuleList = 0xfffff800`02a57e50
Debug session time: Tue Feb 1 12:22:59.528 2011 (GMT-5)
System Uptime: 0 days 0:03:04.074
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffffffffff7ff, 0, fffff8000288e6a6, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!zzzWakeInputIdle+c7 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffffffffff7ff, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000288e6a6, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac20e0
fffffffffffff7ff
FAULTING_IP:
nt!KeSetEvent+16
fffff800`0288e6a6 f6037f test byte ptr [rbx],7Fh
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x50
PROCESS_NAME: plugin-contain
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800836c7d0 -- (.trap 0xfffff8800836c7d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c070ace0 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000288e6a6 rsp=fffff8800836c960 rbp=fffff8800836cca0
r8=0000000000000000 r9=00000000ffffffff r10=0000000000002407
r11=fffff900c070ace0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KeSetEvent+0x16:
fffff800`0288e6a6 f6037f test byte ptr [rbx],7Fh ds:c910:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000290af14 to fffff8000288a740
STACK_TEXT:
fffff880`0836c668 fffff800`0290af14 : 00000000`00000050 ffffffff`fffff7ff 00000000`00000000 fffff880`0836c7d0 : nt!KeBugCheckEx
fffff880`0836c670 fffff800`0288882e : 00000000`00000000 ffffffff`fffff7ff fffff8a0`02006c00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`0836c7d0 fffff800`0288e6a6 : 00000000`00000001 00000000`00000001 00000000`00000001 fffff960`000ebe00 : nt!KiPageFault+0x16e
fffff880`0836c960 fffff960`000f4197 : 00000000`026af400 ffffffff`00000001 00000000`026af000 00000000`00000000 : nt!KeSetEvent+0x16
fffff880`0836c9d0 fffff960`000e9c79 : fffff900`c22ac010 fffff880`0836cca0 00000000`00000000 8b300000`973f7867 : win32k!zzzWakeInputIdle+0xc7
fffff880`0836ca00 fffff960`000e9efd : 00000000`00000000 fffff800`000025ff 00000000`00000000 fffffa80`ffffffff : win32k!xxxRealInternalGetMessage+0x65d
fffff880`0836cae0 fffff960`000e2973 : 00000000`757a2450 00000000`0044f150 00000000`0044fd20 00000000`7efd8001 : win32k!xxxInternalGetMessage+0x35
fffff880`0836cb20 fffff800`02889993 : fffffa80`0510e120 00000000`0044e7c8 fffff880`0836cbc8 00000000`757a2450 : win32k!NtUserPeekMessage+0x77
fffff880`0836cbb0 00000000`757efbda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0044e7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x757efbda
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!zzzWakeInputIdle+c7
fffff960`000f4197 488b4f10 mov rcx,qword ptr [rdi+10h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: win32k!zzzWakeInputIdle+c7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cbe5d3e
FAILURE_BUCKET_ID: X64_0x50_VRF_win32k!zzzWakeInputIdle+c7
BUCKET_ID: X64_0x50_VRF_win32k!zzzWakeInputIdle+c7
Followup: MachineOwner
---------
Debug session time: Fri Jan 28 00:09:25.599 2011 (GMT-5)
System Uptime: 0 days 0:11:51.238
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff800028853c5}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2a5 )
Followup: MachineOwner
---------
0: 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: 0000000000000000, 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: fffff800028853c5, address which referenced memory
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'lltdio' and 'Rt64win7.sys' overlap
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab30e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiTimerWaitTest+2a5
fffff800`028853c5 488b6d00 mov rbp,qword ptr [rbp]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9c3d0 -- (.trap 0xfffff80000b9c3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028853c5 rsp=fffff80000b9c560 rbp=0000000000000000
r8=fffff800029f8001 r9=0000000000000003 r10=0000000000000017
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!KiTimerWaitTest+0x2a5:
fffff800`028853c5 488b6d00 mov rbp,qword ptr [rbp] ss:0018:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000287aca9 to fffff8000287b740
STACK_TEXT:
fffff800`00b9c288 fffff800`0287aca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c290 fffff800`02879920 : fffff800`029f8080 fffffa80`05b35428 fffff800`00b9c600 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c3d0 fffff800`028853c5 : ffffffff`fffb6c20 fffff800`0288729e fffff800`00000010 fffff800`00000000 : nt!KiPageFault+0x260
fffff800`00b9c560 fffff800`02886d7d : fffffa80`05b35420 00000000`0000b216 00000000`00000000 00000000`00000102 : nt!KiTimerWaitTest+0x2a5
fffff800`00b9c5e0 fffff800`028874be : 00000001`a7ee5134 fffff800`00b9cc58 00000000`0000b217 fffff800`029f8568 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00b9cc30 fffff800`02886cb7 : 00000000`7c18efc2 00000000`0000b217 00000000`7c18ef6a 00000000`00000017 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02883eea : fffff800`029f5e80 fffff800`02a03c40 00000000`00000000 fffff880`04887db0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTimerWaitTest+2a5
fffff800`028853c5 488b6d00 mov rbp,qword ptr [rbp]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiTimerWaitTest+2a5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+2a5
BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+2a5
Followup: MachineOwner
---------