05-05-2013, 06:58 PM
GGD, your comments prompts me to investigate further.
I was already uneasy because of a lack of conclusive evidence of failure. An instruction I read for memtest indicated that a freeze or crash during testing is a sign of RAM failing.
But that strikes me as unsatisfactory, not conclusive enough to merit pulling out RAM, marking it failed, and shipping it back for replacement.
If it crashed while testing one module, but not the other, and I could isolate it, repeat that step, duplicate the results, and see a pattern, it would be more compelling. Both modules failing at once, it's less clear. And as you suggest, far less likely, and might even be evidence to the contrary.
Starting this morning--having tried the test in Single User Mode, originally--I've now done the test on one module, then both modules, using Terminal, running in Multiuser Mode. In Terminal in Multiuser Mode, the Mini doesn't crash, in fact, it passes the tests.
And to complicate things, those miniature brackets on each side of the RAM modules, for flipping up at an angle for access, then back down flat again, no longer work. The left bracket detached, and the right bracket also had a tiny piece fall off, it's compromised. It no longer flips back down into the flat position. It's permanently in the flipped up position.
(Those brackets are teeny, and were fragile. First time I've encountered that. It wasn't due to undue pressure from my fingers, it simply detached as I was gently handling it)
It doesn't appear to interfere with the Mini's booting up and operating. But it's still an undesirable complication.
But at this stage--seeing the RAM pass tests in Multiuser Mode--I'm no longer certain it's a problem of bad memory. Whatever caused the KP apparently lies elsewhere.
Bonus question: Should I be aware of any relevant difference between testing RAM in Single or Multiuser mode? Why would one method pass, and the other cause the system to crash?
I was already uneasy because of a lack of conclusive evidence of failure. An instruction I read for memtest indicated that a freeze or crash during testing is a sign of RAM failing.
But that strikes me as unsatisfactory, not conclusive enough to merit pulling out RAM, marking it failed, and shipping it back for replacement.
If it crashed while testing one module, but not the other, and I could isolate it, repeat that step, duplicate the results, and see a pattern, it would be more compelling. Both modules failing at once, it's less clear. And as you suggest, far less likely, and might even be evidence to the contrary.
Starting this morning--having tried the test in Single User Mode, originally--I've now done the test on one module, then both modules, using Terminal, running in Multiuser Mode. In Terminal in Multiuser Mode, the Mini doesn't crash, in fact, it passes the tests.
And to complicate things, those miniature brackets on each side of the RAM modules, for flipping up at an angle for access, then back down flat again, no longer work. The left bracket detached, and the right bracket also had a tiny piece fall off, it's compromised. It no longer flips back down into the flat position. It's permanently in the flipped up position.
(Those brackets are teeny, and were fragile. First time I've encountered that. It wasn't due to undue pressure from my fingers, it simply detached as I was gently handling it)
It doesn't appear to interfere with the Mini's booting up and operating. But it's still an undesirable complication.
But at this stage--seeing the RAM pass tests in Multiuser Mode--I'm no longer certain it's a problem of bad memory. Whatever caused the KP apparently lies elsewhere.
Bonus question: Should I be aware of any relevant difference between testing RAM in Single or Multiuser mode? Why would one method pass, and the other cause the system to crash?