Memory errors on an Abit KR7A-133R

My brother has an Abit KR7A-133R with an AMD Athlon 1500+. He has
been getting many BSoDs in Windows XP. I have run MemTest-86 v3.2
several times. I got errors almost every time. The number of
errors varies and most of the time it is only test five that has
errors.

I have fooled around in the BIOS and have not been able to eliminate
the errors. These are the things I did that did not eliminate the
errors:

I set the memory timings to the fail safe defaults. I did a Google
newsgroup search and found one message saying that raising the DDR
DQS Input Delay and DDR DQS Output Delay by two would eliminate
memory errors on his motherboard. I did it and I get fewer errors
than in the test before. I raised them by two again and got even
fewer errors so I raised them again and got one test run with no
errors. Since then I have gotten memory errors every time I have
run the testing program. I tried raising the values of these two
items several more times but I could not eliminate the errors. I
raised the DDR voltage twice but still got errors. I also lowered
the memory buss speed to 100 mhz from the default of 133.

I switched the memory between his machine and mine. His computer
still gets errors with my memory which did not have errors in my
computer and my computer does not have errors with his memory. (My
computer is faster than his. I have a Barton 2500+ with a 167 mhz
memory buss speed and he has a Athlon 1500+ with a 133 mhz memory
buss speed. We both have PC3200 memory. His is Crucial and mine is
OCZ.)

Is there anything we can do to solve this problem other than
replacing his motherboard? Thank you in advance for all replies.

--
I just heard a TV commercial about an automobile that has a rear
entertainment system. I immediately wondered exactly how would an
automobile entertain one's rear and would it be safe to drive while
one's rear was being entertained.

"Daniel Prince" <neutrino1.TakeThisOut@comcast.net> wrote in message
news:v445h198chcph1h8m40u9g729dnhodguc9@4ax.com...
<snip>
>
> Is there anything we can do to solve this problem other than
> replacing his motherboard? Thank you in advance for all replies.

It seems to me you have a good handle on the problem.