Frequest BSOD Dump Attached

Hi Everyone,

Attached you can find my latest 3 dump files.

I've been dealing with the problem for awhile now and I'm hoping someone on here will be kind enough to help me out.

I get a random BSOD every so often (about one a day). It doesn't matter what I am doing. I can be either playing a game or doing nothing and the computer will BSOD for whatever reason.

I've done memory checks and the RAM seems to be fine.

Also, here is the output from WinDbg for my last crash dump:

Loading Dump File [C:\Windows\Minidump\041810-17015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
Debug session time: Sun Apr 18 03:08:53.812 2010 (UTC - 7:00)
System Uptime: 0 days 5:14:18.069
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffe8008606010, 2, 0, fffff80002b6fa2f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
Followup: MachineOwner
---------
4: 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: fffffe8008606010, 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: fffff80002b6fa2f, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf50e0
fffffe8008606010
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiIdentifyPfn+23f
fffff800`02b6fa2f 4c8b7500 mov r14,qword ptr [rbp]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff880079f84f0 -- (.trap 0xfffff880079f84f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0a00000000000060
rdx=0000000000025680 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b6fa2f rsp=fffff880079f8680 rbp=fffffe8008606010
r8=00000000000058ac r9=0000000000000001 r10=0000000000000046
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MiIdentifyPfn+0x23f:
fffff800`02b6fa2f 4c8b7500 mov r14,qword ptr [rbp] ss:0018:fffffe80`08606010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002abcb69 to fffff80002abd600
STACK_TEXT:
fffff880`079f83a8 fffff800`02abcb69 : 00000000`0000000a fffffe80`08606010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`079f83b0 fffff800`02abb7e0 : 00000000`42506650 02000000`0013e77e 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`079f84f0 fffff800`02b6fa2f : 00000000`00000100 02000000`000275a6 00000000`000018c0 fffff800`02d851af : nt!KiPageFault+0x260
fffff880`079f8680 fffff800`02b7070b : 00000000`00000000 00000000`00000004 fffffa80`07a82370 fffffa80`07a82000 : nt!MiIdentifyPfn+0x23f
fffff880`079f8720 fffff800`02ecfc55 : fffffa80`07a82000 fffff880`079f8ca0 fffff880`079f87f8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`079f8760 fffff800`02e14f18 : 00000000`00000006 00000000`00000000 fffffa80`07a82000 fffff800`02a4d001 : nt!PfpPfnPrioRequest+0x115
fffff880`079f87b0 fffff800`02dbbfb3 : 00000000`00000000 fffff800`02a4d000 fffffa80`07c2f000 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x4759d
fffff880`079f8840 fffff800`02dbd149 : 00000000`0199bd88 fffff800`02ac3552 00000000`0199bde0 00000000`0199bda8 : nt!ExpQuerySystemInformation+0x11c2
fffff880`079f8be0 fffff800`02abc853 : fffffa80`07e42060 00000000`040b0cf0 00000000`040b0cf0 00000000`0199cf18 : nt!NtQuerySystemInformation+0x4d
fffff880`079f8c20 00000000`7703021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0199bca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7703021a

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiIdentifyPfn+23f
fffff800`02b6fa2f 4c8b7500 mov r14,qword ptr [rbp]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiIdentifyPfn+23f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f
BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f
Followup: MachineOwner
---------

Does anyone have any help as to why I might be getting these BSOD's?

Thank you all for your time!

Patrick