New WinXP Pro BSODs

[cdistasi]

Hi all,

First a little background. About 2.5 years ago, I built a new system. At the time, I bult it with W2K Pro and one WD PATA drive. It never quite worked right, but I figured I'd installed the OS incorrectly...

About a month ago, I experienced a drive crash and decided it was time to overhault a bit. I bought 2 Seagate SATA drives and 1 Seagate PATA drive. I installed Windows XP Pro SP2 on the SATA in RAID 1 and use the PATA for backups (using the software included with the Seagate drives - BounceBack Express).

Since rebuilding, I've been plagued by BSOD. While I would have frequent problems using the prior W2K build, never so many BSOD...

I've looked at the minidumps and noted that several have said memory_corruption, but I'm hoping maybe I'm missing something.

I've run memtest86 through 7 passes with no errors. I've cleaned my case of dust using compressed air and reseat the memory. Still, no such luck.

Can someone please look at my minidumps and maybe confirm (or deny) what I fear to be true - memory (or worse yet, CPU)?

My system specs are in my profile.

Thanks,
Chris

 

[cdistasi]

Additional MDs

more minidumps, see attached...

 

[cpc2004]

Hi cdistasi,

Your minidumps has two code corruption and one memory corruption. The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram

Your debug report
Mini101805-02.dmp BugCheck 1000008E, {c0000005, 8054ae2d, b89aba48, 0}
Mini101805-02.dmp DEFAULT_BUCKET_ID: DRIVER_FAULT
Mini101805-02.dmp Probably caused by : SiWinAcc.sys ( SiWinAcc+325 )

Mini101805-03.dmp BugCheck 24, {1902fe, f360a580, f360a27c, f767dd46}
Mini101805-03.dmp DEFAULT_BUCKET_ID: DRIVER_FAULT
Mini101805-03.dmp Probably caused by : Ntfs.sys ( Ntfs!NtfsLookupHashEntry+42 )

Mini101905-01.dmp BugCheck 1000007E, {c0000005, 804e4bae, f7c96cb0, f7c969ac}
Mini101905-01.dmp DEFAULT_BUCKET_ID: DRIVER_FAULT
Mini101905-01.dmp Probably caused by : memory_corruption ( nt!MiSegmentDelete+c )

Mini102005-01.dmp BugCheck 1A, {41284, ca4b5001, 1120b, c0c00000}
Mini102005-01.dmp DEFAULT_BUCKET_ID: DRIVER_FAULT
Mini102005-01.dmp Probably caused by : memory_corruption ( nt!MiLocateWsle+c0 )

Mini102005-03.dmp BugCheck 1000008E, {c0000005, bf823973, f6ee2c74, 0}
Mini102005-03.dmp DEFAULT_BUCKET_ID: CODE_CORRUPTION
Mini102005-03.dmp Probably caused by : memory_corruption

Mini102005-04.dmp BugCheck 1000008E, {c0000005, f1eab69a, f2ace8a0, 0}
Mini102005-04.dmp DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
Mini102005-04.dmp Probably caused by : portcls.sys ( portcls!DispatchDeviceIoControl+3e )

Mini102105-01.dmp BugCheck 1000000A, {10, 2, 1, 804fe2db}
Mini102105-01.dmp DEFAULT_BUCKET_ID: DRIVER_FAULT
Mini102105-01.dmp Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+a5 )

Mini102005-02.dmp BugCheck 10000050, {ffffffc1, 0, bf8a2973, 0}
Mini102005-02.dmp DEFAULT_BUCKET_ID: CODE_CORRUPTION
Mini102005-02.dmp Probably caused by : memory_corruption