Skip navigation

Kernel panics on my mac pro for almost a year-  I am at my wit's end

338 Views 9 Replies Latest reply: Nov 13, 2012 8:04 PM by gfaherty3 RSS
gfaherty3 Calculating status...
Currently Being Moderated
Nov 13, 2012 7:14 PM

So I have a mid 2010 Mac Pro.  12 Core, initially 16GB of Ram (Recently upgraded to 24GB of RAM).  Starting in January of 2012 my machine running Snow Leopard started to go to sleep and not wake up.  This would happen every few days but then would increase in frequency.  I scoured the boards for an answer but couldn't find one so I ended up taking teh machine to the local Apple Store.  They found nothing wrong with the machine but installed a clean copy of Snow Leopard and that seemed to help for a while.  The problem persisted.  I would reset PRAM and try different approaches in boards on line including repariing permissoins etc.  Nothing worked for long.  Desperate I tried upgrading to Lion but the problem persisted.  I took the machine back to the apple store (same location) and they suggested that carbonite was causing the problem.  I did a fresh install of Mountain lion this time, and then slowly added applications back one at a time to see if the problem was truly application based.  I never re installed carbonite.  I don't believe the problem is application based because I have a 2010 Mac Pro that has the identical software setup ( I freelance and when I work off site I use the laptop) and have never had an issue with any kernel panics.  Additionally I have a 2008 Mac pro with the exact same setup and no issues there either.  Before long the problem re-appeared but now with Lion and Mountain lion the machine restarts and I get a message that the machine was forced to re-start after an issue.  I called Apple support and got a very nice guy name Sean Thorpe who promised to help me.  I sent them crash logs, he sent me some applications to install or checks to run so that he could send my crash logs to the engineering department to debug.  Nothing.  no one has solved this problem.  Fed up I demanded a new machine.  I have apple care so I am covered but they refused.  Sean then suggested that I remove all of my drives and then partition the boot drive and install a clean copy of Mountain lion and see if the problem continues.  I did that.  Within 24 hours the machine crashed again.  It was running off the partition and I didn't install a single application.  I don't know that much but the problem has to be hardware.  It two visits to the apple store and a detailed study of crash logs by apple's engineers can't figure it out I figure that I just got a lemon.  I am fed up.  I spent a lot of money on this machine and it isn't dependenable.  I have owned at least four other macs and have loved every one of them and every one has been a great machine. 

 

I am at my whit's end and considering trying something desparate like trying to contact someone who runs customer service or Tim Cook himself.  I don't have any idea how I can get that contact information nor do I actually think it will get me anywhere so I am turning to this community for one last attempt to solve what ever is going on with my machine

Mac Pro (Mid 2010), OS X Mountain Lion (10.8.2)
  • Grant Bennet-Alder Level 8 Level 8 (48,110 points)

    Kernel panics happen for thousands of different reasons, they are not ONE problem. If you are having kernel panics, post the panic log here. Cut and paste the text, please, not a screenshot.

     

    Mac OS X: How to log a kernel panic

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
  • Grant Bennet-Alder Level 8 Level 8 (48,110 points)

    You have a memory problem.

     

    Mac Pro 65lb tower uses Error Correcting Code memory. Additional check bits are stored with every word in RAM memory. When read out, the Xeon Processor corrects single bit errors and some others, but uncorrectable double-bit errors cause a kernel panic such as the one you posted. It is distinctive in:

     

     

    Machine check

    ...

    Error enabled

       Uncorrected error

     

    ... and the module reporting the error is almost always:

    Kernel Extensions in backtrace:

             com.apple.driver.AppleIntelCPUPowerManagement(196.0)

     

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
  • Grant Bennet-Alder Level 8 Level 8 (48,110 points)

    The likelihood that Uncorrectable Memory errors are caused by something other than bad DIMMs is extremely small.

     

    Your Mac notes every correctable memory error. If you keep watching:

    About this Mac > ( More Info ) >  Memory

     

    Any DIMM reported at less than its actual size or status other than "OK" has seen errors since power-on. There may be a count of the number of correctable errors.

     

    It is not required to run memory tests on a computer with Error Correcting Code Memory. Every time you use the memory, it is checked by Hardware.

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
  • Grant Bennet-Alder Level 8 Level 8 (48,110 points)

    Yes, I mean you have a problem with one or more of your RAM DIMMs. Nothing else.

     

    It may not be the new one, especially if you have been having problems right along.

     

    Where did you get the new DIMM?

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.