-
All replies
-
Helpful answers
-
-
Mar 12, 2012 4:33 AM in response to ElsaEby OGELTHORPE,Three beeps during the startup procedure is indicative of a RAM problem. You may try reseating the RAM. If that fails, you can take it to an Apple store for a definitive diagnosis. Be apprised that replacement RAM via third party sources should cost about $25 (4 GB) and an upgrade to 8 GB should be no more than $50. Apple prices will be significantly more.
Ciao.
-
Mar 12, 2012 6:47 AM in response to OGELTHORPEby ElsaE,Thank you both for the replies. However, while the description of the beeps in the links posted by Kappy is the same as what I've been experiencing, they haven't been happening during the startup process. In fact, they usually start occuring after the computer has been on for quite some time, with no apparent trigger (computer is under normal use, no downloads, no gaming, etc.) Is this still indicative of a RAM problem, even though the beeps & screen freeze aren't happening during startup?
-
Mar 12, 2012 8:42 AM in response to ElsaEby OGELTHORPE,I can only speculate what it may be. You might run an Apple Hardware Test to see if it gives a clue to the problem. I would make an appointment with the genius bar at the Apple store. They would be in the best position to solve your problem.
Ciao.
-
Jun 19, 2014 10:12 AM in response to ElsaEby Ricarado,Did you find the solution for this problem?
I am having the same issue with my macbook pro...
10.8.5
15-inch, Late 2011
Processor 2.4 GHz Intel Core i7
Memory 8 GB 1333 MHz DDR3
-
Mar 2, 2016 11:07 AM in response to Ricaradoby jsfenfen,Was experiencing something like this on an early 2011 Macbook Pro running OS X 10.8.5. Several minutes *after* startup the machine and screen would freeze, and would begin beeping three times (while the sleep light flashed in unison) every five seconds or so. This is slightly different than the un-seated RAM issues described elsewhere, which seem to happen at startup and result in a gray / green busted screen, but was also quite worrisome: it appeared that I had RAM that randomly became unreliable--or perhaps an even more dire hardware problem.
I found a thread on a Google Drive product forum that seemed similar, albeit for 10.6.8. Google engineers ultimately confirmed that the problem was repeatable, and as a result of Google drive. The thread was (unhelpfully) closed (I started a new one here). The best explanation of this came from @tallted, a user who reported replacing his RAM before taking the machine into the Apple genius bar. "the Apple Genius dove deeper into the Console logs. Apparently, the three-beep klaxon alarm happens anytime the machine can't *write* to RAM, which can be due to software *as well as* hardware failure."
This would seem to contradict Apple's official current guidance here, which, as of today, doesn't mention the possibility of a software problem. It just says that: "3 successive tones, a 5 second pause (repeating): This indicates RAM does not pass a data integrity check." Reports elsewhere on the internet suggest this has happened when installing parallels as well, presumably a software issue there as well.
That said, @tallted's genius' explanation does seem consistent, in a way; if google drive has (buggily) remapped the way data is written, perhaps an error in writing to their storage would look like an error to write to RAM.
What was especially nebulous about this problem was that there was no obvious link to google drive--my computer just froze and started beeping several minutes after startup. And yet erasing the google drive app seems to have resolved it.
System is similar to Ricarado above:
10.8.5
15-inch early 2011
Processor: 2 Ghz Intel Core i7
Memory: 4 GB 1333 MHz DDR3