I would recommend running memtest first to find out if it is actually a memory issue. Otherwise you might just mask the issue and think that moving the memory around made it go away when it actually is something else but hard to trigger.
If memtest finds errors, then you know with some certainty that there was no bug. uriel On Nov 23, 2007 12:04 AM, Steve Simon <[EMAIL PROTECTED]> wrote: > > ...i'm more inclined to suspect memory problems. > > Thanks Russ for the very detailed analysis. > > I will start by reseating the RAM and if that fails > I will petition my boss for a new machine (bout time really). > > -Steve >
