-
All replies
-
Helpful answers
-
Aug 12, 2015 10:05 PM in response to JohnBarrettby JohnBarrett,I've also done the SMC/PRAM resets and FCPX Preferences dump.
-
Aug 12, 2015 10:33 PM in response to JohnBarrettby David M Brewer,Sounds like you have some bad ram there.
-
Aug 13, 2015 1:47 AM in response to JohnBarrettby Karsten Schlüter,indeed, 3 beeps = RAM kaputt ...
-
Aug 13, 2015 5:07 AM in response to JohnBarrettby Russ H,Take out one of the sticks and see if it still crashes, If it does, swap that stick for the other and try again, IF you;'r using third party RAM, replace it with the original RAM. Hopefully it will limited to one faulty memory module.
Russ
-
Aug 13, 2015 9:40 AM in response to Karsten Schlüterby JohnBarrett,★HelpfulIt's actually not beeping at startup. It beeps just as the screen goes dark.
-
Aug 13, 2015 9:55 AM in response to JohnBarrettby Luis Sequeira1,★HelpfulJohnBarrett wrote:
It's actually not beeping at startup. It beeps just as the screen goes dark.
Still, it is quite possible that bad RAM is involved.
It may be that the quick test done as the system starts does not immediately detect a RAM problem (otherwise you'd get those beeps right away and your mac would not even boot), but as you work more and more RAM gets used by your system, up to a point where some bad ram area is accessed and the system bombs out.
I'd follow the advice you already got about testing the RAM chips.
-
Aug 13, 2015 12:35 PM in response to Luis Sequeira1by JohnBarrett,OWC suggested that I run Rember. Kelleycomputing.net/rember.
The test made the system exhibit the same issues that I'd experienced with FinalCutPro, corrupted displays and 3 beeps. It could not get through loop one in two consecutive try.
I pulled Bank1 and retested. No issues. I added a 2GB Apple simm to Bank 1 just to test the integrity of the bank. No issues.
So bad simm in Bank 1. OWC will replace.
Rember caught errors that the long version Apple Diagnostic Test didn't detect.
Thanks for everyone's suggestions.