Well, as before it turned out to be a bad stick of PC32000 DDR. Corsair, TwinX1024-3200C2Pro, Dual Channel Set. One bad stick in slot 3 that failed at about the 690MB mark.

I took it back to the store and they replace the set. Funny thing is the new set also had a bad stick (even worse than the first stick). Drove right back and the third set checked out 100%. Running memtest86. No errors since replacing with the 100% set.

Thanks Roman, wow this tool makes a great RAM checker... ;)

Matt

> > Hmmm...new system (about 3 months). I guess it could be my RAM timing since
> > currently I am remote desktop'd in, running ClrMame Pro, and Media player.
> The
> > CPU does heat up under load...no doubt about that.
> >
> > I'll check my RAM timing. Thanks Roman.
> >
> > Matt
> >
> > > > Any ideas? One day it works and the next it fails? I have not changed
> any
> > > > hardware/software on my pc other than mame.
> > >
> > > Random checksum errors normally appear when your system becomes unstable
> under
> > > cpuload. Bad ram, bad ram timing, overclocked systems, bad ide cables, buggy
> > via
> > > chipsets, etc...
> > >
> > > ClrMamePro uses Aaron's routine from chdman core to verify the chds...so
> > chdman
> > > and clrmamepro do the same things.
> > >
> > >
> > > Check cables, ramtiming, try to disable other tasks and try again.....
> > >
> > > That it worked with chdman can be caused by the less cpu activity. When
> using
> > > clrmamepro, the scanner has already heaten up your cpu...
> > >
> > > Roman Scherzer
> > > ClrMamePro
> > >
> >
>
>
> Also check the ide cable ;) ...usually if you buy a new pc you get lousy
> ones.....
>
> Roman Scherzer
> ClrMamePro
>