DG
Ok Are you over clocking? How much ram?
the first five dumps are virtually identical. they all are caused by memory corruption. I dont know if you have added memory or changed something. I would first download memtest86 and thoroughly test the ram. If that passes try pulling the ram and re-seating it. It still BSOD take out all b ut 1-2 gigs. If bsod stops with less ram its either the ram or cpu.
ken
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Mini092609-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x82407000 PsLoadedModuleList = 0x8251ec70
Debug session time: Sat Sep 26 15:42:12.335 2009 (GMT-4)
System Uptime: 0 days 0:01:25.116
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {7, 1e8ef, 10, 0}
Probably caused by : memory_corruption ( nt!MiPfnReferenceCountIsZero+2a )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000007, A driver has unlocked a page more times than it locked it
Arg2: 0001e8ef, page frame number
Arg3: 00000010, current share count
Arg4: 00000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_7
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: msnmsgr.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 824844d1 to 824be2cf
STACK_TEXT:
a5a889e0 824844d1 897a5b70 89926020 000000a2 nt!MiPfnReferenceCountIsZero+0x2a
a5a88a30 82487fdd 8992cf20 00000000 00000000 nt!MiWaitForInPageComplete+0xafd
a5a88a44 826121ad 00000000 9c395be4 9c395bb0 nt!MiPfCompletePrefetchIos+0x1a
a5a88a70 825c0dec 000000a3 acb2fae0 00000001 nt!MmPrefetchPages+0x1c3
a5a88ae8 825c001c 00a88b0c 00000000 00000000 nt!PfSnPrefetchSections+0x34b
a5a88c64 825d35f0 9c394000 a5a88c94 a5a88ca0 nt!PfSnPrefetchScenario+0x121
a5a88cf8 825d3690 82621687 8972a638 a5a88d50 nt!PfSnBeginAppLaunch+0x382
a5a88d08 82621236 a0001870 00000000 00000000 nt!PfProcessCreateNotification+0x65
a5a88d50 82445efe 00000000 776f5e58 00000001 nt!PspUserThreadStartup+0x116
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiPfnReferenceCountIsZero+2a
824be2cf f6470801 test byte ptr [edi+8],1
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiPfnReferenceCountIsZero+2a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_7_nt!MiPfnReferenceCountIsZero+2a
BUCKET_ID: 0x4E_7_nt!MiPfnReferenceCountIsZero+2a
Followup: MachineOwner
---------