I am getting a memory fault, and I can’t locate the source. I have run Memtest86+ for about 30 passes, and have tested individual modules of the 4 512mb memory modules for faults under windows memory tester and all passed. I have Minidumps out the wazoo, but I cant determine the cause of the fault. The faulting application is different each time. Here is my latest debug
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {a17df5cd, 1, 805b8f0b, 3}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
———
1: 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: a17df5cd, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 805b8f0b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000003, (reserved)
Debugging Details:
——————
Could not read faulting driver name
WRITE_ADDRESS: a17df5cd
FAULTING_IP:
nt!MiCloneProcessAddressSpace+37
805b8f0b f3ff8d8528ffff rep dec dword ptr [ebp-0D77Bh]
MM_INTERNAL_CODE: 3
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
MISALIGNED_IP:
nt!MiCloneProcessAddressSpace+37
805b8f0b f3ff8d8528ffff rep dec dword ptr [ebp-0D77Bh]
LAST_CONTROL_TRANSFER: from 8054086c to 805b8f0b
STACK_TEXT:
a17ecd48 8054086c 000000d8 0085ff00 0085fef0 nt!MiCloneProcessAddressSpace+0x37
a17ecd48 7c90eb94 000000d8 0085ff00 0085fef0 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0085fea8 7c90e31b 7c80a746 000000d8 0085ff00 0x7c90eb94
0085fed8 77e770d8 000000d8 0085ff10 0085ff00 0x7c90e31b
0085ff14 77e7721c 00007530 0085ff6c 0085ff70 0x77e770d8
0085ff80 77e772a4 0085ffa8 77e76a4d 0009f088 0x77e7721c
0085ff88 77e76a4d 0009f088 00000000 00bcfe28 0x77e772a4
0085ffa8 77e76c13 0009d990 0085ffec 7c80b683 0x77e76a4d
0085ffb4 7c80b683 000dbc98 00000000 00bcfe28 0x77e76c13
0085ffec 00000000 77e76bf9 000dbc98 00000000 0x7c80b683
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
5 errors : !nt (80576798-80576d98)
80576790 11 56 80 3b f8 72 02 89 *08 8b 07 89 07 a1 68 9d .V.;.r……..h.
…
805769b0 04 00 00 00 eb 09 e8 4b *86 09 00 c3 8b 65 e8 83 …….K…..e..
…
80576a10 8b f8 8b b7 50 05 00 00 *df 46 0c 8b ce e8 46 e9 ….P….F….F.
…
80576c90 50 6a 02 ff 75 08 e8 6f *22 04 00 89 45 c0 8b 4d Pj..u..o”…E..M
…
80576d90 57 bf 44 75 6d 70 57 6a *04 33 db 53 e8 c7 3b fd W.DumpWj.3.S..;.
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
———
I can post dumps if need be, in the meantime i updated the BIOS and did a chckdsk /f /r on the drive and no errors were found. It doesn’t seem like the video ram, since its not a graphics related exe that faults the memory, usually svchost or lsass. My least likely option is my AV software, Norton Internet Security 2007, which the fault predates. All video, soundcard and Mobo drivers are up to date, as well as windows and norton. Can anyone determine the source, be it HDD, RAM, Video Memory, Mobo or driver?
