I've always noted that RAM based problems are very unpredictably, and rarely log well. Usually it's a freeze, blue screen or a dump with either bad mem, or CPU. Sometimes with some file corruption.
If I do have a question, it's usually not much problem to swap a DIMM around here and there and do some process of elimination testing. It's rare to have memory chips fail intermittently, but it is possible for a portion of one in a high address area to fail, and only show itself when accessed. Anecdote: I once put two different sized DIMMS in one of those Macs you needed to pair up in. The machine worked up right up until it tried to address the first bit that wasn't actually there. Robert -----Original Message----- From: Roland Dumas [mailto:[EMAIL PROTECTED] Sent: Monday, February 09, 2004 11:34 AM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: Crashes on OS X Can anyone tell me if this is evidence of RAM problems? The crashed thread records tend to be rather consistent in what they're writing and where they are writing it, as far as my uneducated eyes can tell. > On Feb 6, 2004, at 10:05 AM, Ben Johansen wrote: > >> Disclaimer: Not a Mac Guy ;-) >> >> This sounds a lot like a RAM module going bad. >> >> This can be intermittent for several reasons >> -the ram chip is fail intermittently >> -the failed location on the ram chip is in a high mem address and only >> is reached under higher loads. >> >> One thing you can do when looking at those funny number is to see if >> you >> see a consistent funny number :) > > OK: you can tell me if this constitutes a consistent funny number. I > grabbed the crash log, clipped out the crashed thread and here are a > few. Definitely recurring numbers in the "in" (is that a memory > location or something?) > > Thread 10 Crashed: > #0 0x94f92e68 in _iodbcdm_driverload > #1 0x94f94f64 in SQLDriverConnect > #2 0x0016b8e0 in 0x16b8e0 > #3 0x00047570 in 0x47570 > #4 0x000685b8 in 0x685b8 > #5 0x00024ec0 in 0x24ec0 > #6 0x00025278 in 0x25278 > #7 0x0001949c in 0x1949c > #8 0x00019e24 in 0x19e24 > #9 0x00017ac8 in 0x17ac8 > #10 0x0001a910 in 0x1a910 > #11 0x0014e09c in 0x14e09c > #12 0x90020c28 in _pthread_body > > Thread 2 Crashed: > #0 0x94f92e68 in _iodbcdm_driverload > #1 0x94f94f64 in SQLDriverConnect > #2 0x0016b8e0 in 0x16b8e0 > #3 0x00047570 in 0x47570 > #4 0x000685b8 in 0x685b8 > #5 0x00024ec0 in 0x24ec0 > #6 0x00025278 in 0x25278 > #7 0x0001949c in 0x1949c > #8 0x00019e24 in 0x19e24 > #9 0x0001830c in 0x1830c > #10 0x0007cba0 in 0x7cba0 > #11 0x0009dd18 in 0x9dd18 > #12 0x0009d780 in 0x9d780 > #13 0x00019750 in 0x19750 > #14 0x00019e54 in 0x19e54 > #15 0x00017ac8 in 0x17ac8 > #16 0x0001a910 in 0x1a910 > #17 0x0014e09c in 0x14e09c > #18 0x90020c28 in _pthread_body > > Thread 14 Crashed: > #0 0x94f92e68 in _iodbcdm_driverload > #1 0x94f94f64 in SQLDriverConnect > #2 0x0016b8e0 in 0x16b8e0 > #3 0x00047570 in 0x47570 > #4 0x000685b8 in 0x685b8 > #5 0x00024ec0 in 0x24ec0 > #6 0x00025278 in 0x25278 > #7 0x0001949c in 0x1949c > #8 0x00019e24 in 0x19e24 > #9 0x00017ac8 in 0x17ac8 > #10 0x0001a910 in 0x1a910 > #11 0x0014e09c in 0x14e09c > #12 0x90020c28 in _pthread_body > > Thread 20 Crashed: > #0 0x94f92e68 in _iodbcdm_driverload > #1 0x94f94f64 in SQLDriverConnect > #2 0x0016b8e0 in 0x16b8e0 > #3 0x00047570 in 0x47570 > #4 0x000685b8 in 0x685b8 > #5 0x00024ec0 in 0x24ec0 > #6 0x00025278 in 0x25278 > #7 0x0001949c in 0x1949c > #8 0x00019e24 in 0x19e24 > #9 0x00017ac8 in 0x17ac8 > #10 0x0001a910 in 0x1a910 > #11 0x0014e09c in 0x14e09c > #12 0x90020c28 in _pthread_body > > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
