Memory module problem?

I 'm getting following annoying system log message from kernel on and on and on.


kernel AppleTyMCEDriver ReadCorrectable : Detected 1
errors on channel 2 dimm 0 package 0


Is it mean that one of my Mac Pro early2009's memory module is something wrong?

Mac Pro Early 2009, Mac OS X (10.5.7), 2.66GHz Quad-Core Intel Xeon

Posted on May 26, 2009 10:28 AM

Reply
Question marked as ⚠️ Top-ranking reply

Posted on May 26, 2009 11:53 AM

Hi Kaz,

In System Profiler, under Memory, scroll down your list of DIMMs and see if one is reporting an error.

Welcome to the Apple Discussions.
86 replies
Sort By: 

May 28, 2009 10:10 AM in response to Samsara

Hi, samsara. Thank you for your reply.

System Profiler says DIMM in slot-3 get ECC error(ECC correctable error : 177), so I attempted to swap DIMM one another between the DIMM which is supposed to be bad and the DIMM is supposed to be OK, though system Profiler always says DIMM in slot-3 is bad.

Is it just DIMM problem, or other hardware trouble?

This is single quad-core 2.66GHz Xeon system.
Reply

May 28, 2009 10:59 AM in response to kaz-k

Hi Kaz,

I'd wait a bit for more reliable and better advice, I don't know a lot about memory woes. But what I do know is that I put some new RAM in my machine recently and in SP one Dimm read something like yours. I didn't look into it then but the next day the message had disappeared.
It could be the Dimm, on the other hand it could be the slot. A call to the manufacturer in the first case, a call to Apple if the second. It's a new Mac, don't settle for less than perfection.

Also, there's a little free utility you might want to try called Rember that checks on RAM. You can google it. If you can stand the wait time of the program it might show something to take action on.
Good luck!
Reply

May 28, 2009 12:15 PM in response to Samsara

Hi, samsara,

I checked with Rember, as well as AHT, and they say everything is OK.

And I had the very first panic last Tuesday, and I found a person who post about panic which almost same panic I had.
he said that the logic board died shortly thereafter.

Well, this is stock Mac Pro, so I'd call to Apple, anyway.

Thank YOU again for your reply.
Reply

May 28, 2009 12:24 PM in response to kaz-k

Hi Kaz,

You're most welcome. Just wish there was a way to troubleshoot it from your end. Yeah, new machine, it may be a pain, but the ball is in Apple's court, you shouldn't be having any problems.
Well, again, Welcome to the Boards, and come round more often, y'hear? 😉
Reply

May 28, 2009 1:50 PM in response to kaz-k

Early on I bought some 3rd party RAM.... very rare and expensive back in Sept '06... and had a couple parity errors kicking out. But in the next couple days they went into 1000 range and returned them, but the damage was done. I had errors show up each time I ran and reran Disk Warrior on my backups and clones.

Eventually the only cure was to reinstall the OS from scratch. Otherwise, I would see symptoms that looked like driver extension conflicts, probably from writing bad data to those files, files that change often, cache files and such, and it was taking too much time and effort. The fresh format and install was actually easier in the long run. And after that I was careful to test and what I bought as far as memory goes.

Rember puts a GUI around Memtest. Memtest though can be run concurrently, so you can test 20 chunks of memory in small bits of 256MB or whatever you want, run 4-5 cycles, and have it done in two hours instead of testing 4GB or someting in one long pass at a time. Some people do pull half the memory, test that, then swap and try the other half, too.

One reason to buy from someone that sells a lot of Mac Pro memory. And at least DDR3, even ECC, isn't as exotic as the older DDR2 FBDIMMs.
Reply

May 28, 2009 5:27 PM in response to The hatter

Curiously, when I just booted from a freshly made clone, the memory checker came up to say there were problems with the memory in one of the slots. It said the slot was vacant. I'll check it out further tomorrow but for now I just took two out of the modules and I'll do some more three channel testing. But why my main startup disk didn't report any errors, I don't know.
Reply

May 29, 2009 8:27 AM in response to The hatter

Computers sometimes like to play mind games.

_I knew it!_ I just didn't want to say so out loud... 😉

Edit: Yes, indeed, the machine knew something was going on:
9 error-reporting banks threshold-based error status present extended corrected memory error handling present Machine-check status 0x0000000000000004

And it goes on...

Message was edited by: Samsara
Reply

May 29, 2009 7:06 PM in response to The hatter

Hi, The hatter and samsara. Thanks for your response.

I tried extended Apple Hardware Test several times in a row today, and first attempt was everything OK, though since second try, it reported error codes like following.

"4MEM/65/40000006: 0x7a429c98"
"4MEM/66/40000006: 0x7a420f18"
"4MEM/4/40000006: 0x7a420f18"
"4MEM/64/40000006: 0x7a420f18"
"4MEM/64/40000006: 0x7a420f18"

I'm not sure what these error code mean, though related to memory module or something?

kernel is still saying "AppleTyMCEDriver ReadCorrectable : Detected 1 errors on channel 2 dimm 0 package 0", however couple of hours after booting.
Reply

May 29, 2009 7:52 PM in response to kaz-k

Hi Kaz,

For my part I don't know what that means at all. Strange that AHT just decided to pick up on it though.
I still think your best bet is having Apple take a look at your machine. I know it's a big pain if they make you bring it in yourself, which they probably will, but I think they would either fix it quickly or replace it for you.
After I bought my RAM from a company called OWC here in the States, after I ran across that error message, I called their support staff and they sent me a list of things to try, some more applicable to our machines than others. If you'd like me to forward that email to you I'd be glad to do so. Just click on my profile and you'll see my address.
Good luck.
Reply

Jun 3, 2009 7:07 AM in response to kaz-k

Hi
I have the same symptoms on my machine I bought on friday 29. of may.
Kernel panics on migration and compressing video files.
Exchanging RAM did not help. Always eec error on 3. and 4. slot. But only after running for some time. Not directly after startup. Very hard to prove the dealer the malfunction. Only have kernel panic logs and a screenshot of system profiler.
I wish I could get another machine.
Working now for six days on this problem.
Reply

Jun 3, 2009 8:39 AM in response to cigame2

Did you run Memtest and Apple Hardware Test?
Monitor the temps with one of the utilities (Hardware Monitor is one I trust the most).

Deal with a vendor like Crucial that will help and exchange RAM when there are errors. Panic logs and system log should be more than enough.
Reply

Jun 3, 2009 11:02 AM in response to cigame2

Cigame2,

You are well, well, within your rights to get a new machine. Don't take "no" for an answer. Go over the dealers head and call Apple directly if you have to. Do it for yourself, and do it for the rest of us.
There's no reason, none, that you should spend 6 days trying to sort out a problem like this on a brand new machine.
Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Memory module problem?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.