Solved Blue Screen Dump File

This just started yesterday...Five Blue screens so far..Here the Debug tool report..
Can anyone help?

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\Mini031509-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`00c61000 PsLoadedModuleList = 0xfffff800`00e26db0
Debug session time: Sun Mar 15 18:25:48.437 2009 (GMT-5)
System Uptime: 0 days 3:31:49.278
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {200000046, 2, 0, fffff80000d466f2}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+6f2 )
Followup: MachineOwner
---------
1: 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: 0000000200000046, 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: fffff80000d466f2, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80000e8a080
0000000200000046
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiIdentifyPfn+6f2
fffff800`00d466f2 498b5b40 mov rbx,qword ptr [r11+40h]
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffffa600c9f4630 -- (.trap 0xfffffa600c9f4630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0200000000000000 rbx=0000000000000000 rcx=0000000000000006
rdx=0000000000928190 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80000d466f2 rsp=fffffa600c9f47c0 rbp=fffffa600c9f4800
r8=0200000000000000 r9=0000000000000246 r10=fffffa800949f580
r11=0000000200000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MiIdentifyPfn+0x6f2:
fffff800`00d466f2 498b5b40 mov rbx,qword ptr [r11+40h] ds:18c0:00000002`00000046=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80000cb60ee to fffff80000cb6350
STACK_TEXT:
fffffa60`0c9f44e8 fffff800`00cb60ee : 00000000`0000000a 00000002`00000046 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0c9f44f0 fffff800`00cb4fcb : 00000000`00000000 00000000`0011d0e9 00000049`fa5e0f00 00000580`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`0c9f4630 fffff800`00d466f2 : 00000000`00000000 00000000`00000000 fffff800`00000001 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`0c9f47c0 fffff800`00d60ffe : 00000000`00125032 fffffa80`0596c0c0 fffffa80`0886b060 00000000`00000000 : nt!MiIdentifyPfn+0x6f2
fffffa60`0c9f4860 fffff800`0104fd75 : fffffa80`0596b000 fffffa60`0c9f4ca0 fffffa60`0c9f4928 00000000`00000000 : nt!MmQueryPfnList+0x13e
fffffa60`0c9f48a0 fffff800`00f972dc : fffffa80`0596c8b8 00000000`00000000 fffffa80`0596b000 00000000`0501df01 : nt!PfpPfnPrioRequest+0x115
fffffa60`0c9f48f0 fffff800`00f2c54a : 00000000`00000000 00000000`0501dff0 00000000`0297f030 fffff800`0104fd01 : nt! ?? ::NNGAKEGL::`string'+0x46bea
fffffa60`0c9f4960 fffff800`00cb5df3 : fffffa80`0886b060 00000000`0501dff0 00000000`00000000 00000000`00000000 : nt!NtQuerySystemInformation+0xd0a
fffffa60`0c9f4c20 00000000`77605dda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0297ef88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77605dda

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiIdentifyPfn+6f2
fffff800`00d466f2 498b5b40 mov rbx,qword ptr [r11+40h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiIdentifyPfn+6f2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+6f2
BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+6f2
Followup: MachineOwner
---------
1: kd> lmvm nt
start end module name
fffff800`00c61000 fffff800`01179000 nt (pdb symbols) c:\websymbols\ntkrnlmp.pdb\149C563625CA49CEA2881CEDF5D55CCF2\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: c:\websymbols\ntoskrnl.exe\48D1BA35518000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Wed Sep 17 21:17:25 2008 (48D1BA35)
CheckSum: 0047E2D2
ImageSize: 00518000
File version: 6.0.6001.18145
Product version: 6.0.6001.18145
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.0.6001.18145
FileVersion: 6.0.6001.18145 (vistasp1_gdr.080917-1612)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

The stack suggests corruption in the PFN (Page Frame Number) linked list.

Given that your ntoskrnl is up-to-date and that the MS KB claims no knowledge of any similar issues (all of our Vista SP1 machines would be crashing), it's most likely a hardware problem.

Are you over-clocking or under-cooling?

You might want to run some RAM tester utilities for a few hours.

Fixed ... Ballastic Memory... Problem found with Vista memory test....Pulled memory ...reseated and retested...Fixed...No problems found...

Thanks....