Viper113869 said:
here is something that might help
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00000008, 0x00000002, 0x00000001, 0x8051e17d). A dump was saved in: C:\WINDOWS\Minidump\Mini081905-06.dmp.
i attached some files... please help!
thank you so much!!!
Hi Viper,
Obviously, this is the faulty RAM. Two bits were lost can cause bugcheck code 4E.
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: 0000008f, The free or zeroed page listhead is corrupt
Arg2: c001bbd1, new page
Arg3: 0001bbd1, old page <--- (the high order byte shoud be c and it is 0. Two bits were lost and it is two bits corruption)
Arg4: 00000000, 0
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x4E
LAST_CONTROL_TRANSFER: from 80518891 to 804f8925
STACK_TEXT:
f8a80804 80518891 0000004e 0000008f c001bbd1 nt!KeBugCheckEx+0x1b
f8a80844 8068466d 825ca788 00000000 00000044 nt!MmZeroPageThread+0x123
f8a80dac 805c4a06 80087000 00000000 00000000 nt!Phase1Initialization+0x1145
f8a80ddc 80540fa2 80683528 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
nt!MmZeroPageThread+123
80518891 cc int 3
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MmZeroPageThread+123
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1d
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_nt!MmZeroPageThread+123
BUCKET_ID: 0x4E_nt!MmZeroPageThread+123