MBP 3 Beeps - RAM failure... already?!

Hey all.
So this evening I was mixing a song on my MacBook Pro when suddenly the screen flashed/went beserk, and now when I try to turn it on I get three beeps, which repeat over time. My research indicates that means a RAM failure. But... I literally got this computer yesterday! Are MacBook Pro's really that finicky? This isn't my first MBP, and not my first experience with such issues...

Take it back to your local Apple Store. I'm assuming that you bought Apple provided RAM? You're right, the 3-beeps indicate bad RAM. I've never had a problem with Apple provided RAM or any RAM that I've installed myself, for that matter. You're well within your 14-day 'grace period' to have your MBP replaced and that's what I would insist upon. Don't let them just try to reseat the RAM or put in new sticks - get a completely new machine.
Good luck,
Clinton

Similar Messages

After upgrading to ML, now a RAM Failure

I have a 2009 MacBook Pro. I use it for my business in a retail store. I upgraded it 2 months ago from 4gb to 8gb RAM. I even made sure the RAM was compatible. It is not made by Apple (RAM). Today I upgraded to Mountain Lion, and the computer won't turn on. When I try, it makes 3 loud beeps continuously. I tried to re-seat the RAM, with no luck. If i put the old 4gb (2 2GB sticks) RAM in, the computer boots fine and Mountain Lion runs. If I try to return to the upgraded RAM, it will not boot but give me a RAM failure audible beep. The 4GB is TOO SLOW! I'd rather have 8GB of RAM running on Lion then 4GB running on Mountain Lion. Has anyone had this issue or have any suggestions? I NEED this computer for my business and its SUPER important. I actually use it as my register. PLEASE!!

TravisCarterNY wrote:
I can't tell if its Value RAM or just regular. It doesnt say Value on it. As for an update, I have reset the PRAM and SMC with no luck. The only thing that does work, is leaving (1) of the old 2 GB sticks in with (1) of the new 4GB sticks. This for some reason works and the machine is testing OK with 6 GB of RAM. However, once I try to place the other new 4 GB stick in for the complete 8GB upgrade, I get the 3 Beep RAM failure on startup. Anyone have any ideas ?
Yes, return the Kingston Ram and order from www.crucial.com or www.macsales.com, reports of problems with Kingston Ram are commonplace.

RAM Failure? (3 Short Beeps, 3 Long Beeps, 3 Short Beeps)

Anyone have any idea what 3 Short Beeps, 3 Long Beeps, and 3 Short beeps when starting the computer mean? I heard it might be RAM failure? Could that be the case? How much has it been in the past? Computer's a Late 2010 13" Macbook Air with the Core 2 Duo. Thanks.

The following may help: Mac computers: About startup tones - Apple Support

RAM failure as one possible reason for MBP not booting up

Hello,
Just moving from an HP Win 7 laptop and got a brand new 11' MBP a month ago, which I must say was a bit disappointing in terms of overall performance, as I was clearly expecting more from a Mac.
Yesterday, after it went off out of battery, could not boot it back up despite plugging the charger: black screen, little white light on but nothing else. Tried anything I could find on this community pages (hard reboot, SMC, etc) without any success.
My IT support came this morning, and removed one of the two 4 Go RAM barr (from Samsung) and it rebooted magically. Apparently this is their second case of RAM failure on new MBP in 24 hours
Besides, I am now experiencing with a much faster computer on 4 Go of RAM instead of 8.
Bottom line, some recent Macs may have been equipped with defective RAM chips, you may want to consider this if running into a laptopt that stops bootting up.
Hope this helps
Cheers
Raphaël

I just noticed you said you'd erased your hard drive. That might be why there is nothing to see.
OK, try this -insert a system CD then power off. Switch on and hold down the alt key. Do you get the grey screen but with no drives appearing? If so, is the CD/DVD drive spinning and making a noise?
Wait for a minute or so and see if the CD/DVD appears on the screen as a boot option once it gets up to speed. It won't appear instantly.
if it does select it and see what happens. be patient. A boot DVD will be slow but you should hear the drive going if it's loading the software.

A thunderbolt-induced beeping RAM start-up error?

I'm running a brand new thunderbolt display on a ca. late 2011 17" MBP 2.2 GHz. If I shut the MBP down with the Tb display connected, and then try to restart the computer without the connection, I intermittently get the 3 beep RAM error at startup. Frozen UNLESS I start-up with the Tb display connected. Apple replaced the RAM sticks, but it happened again, so they're trying the logic board. Thought I would throw this out there....anyone else seen this?
ps, we have used every troubleshooting restart combo....

I would suggest running the Apple Hardware test that comes with your computer. You can run this by inserting Install Disk 1 and rebooting while holding down the D key. There should be instructions on the front of the disk for this.
Once you are in the hardware test, run the extended test and it will check your ram. I've already used this to verify that an expansion stick I bought was faulty.

Onboard RAM Failure

My ibook started acting like a dinosaur a few weeks ago, and I finally nailed the problem down: The onboard 256Mb of RAM is bad, and is no longer recognized by the operating system. The computer is much slower now, as it is only recognizing the additional 256M chip, and it is also far far less stable than it used to be.
Would buying a 512 or 1gb chip be a really smart way to speed things up and keep my computer running? Or would it just be delaying the inevitable when one day it won't boot at all? Will it improve the stability of the system? Should I just replace the logic board entirely?
Any insight or experience would be much appreciated.
14" iBook 1.33 Mac OS X (10.3.9)

A defective RAM chip may be having an effect on the iBook besides just not being recognized. It could certainly be causing other problems as well. I would recommend you get it repaired/replaced. You can never have too much RAM, adding some more now might get you by for a little while longer. But the RAM failure could be a sign of other problems with your logic board.
-Doug

Should I go for a 13" retina MBP with 16GB Ram and 2.8ghz dualcore or a 15" Base model with 8 GB Ram and 2.0ghz Quadcore?

Should I go for a 13" retina MBP with 16GB Ram and 2.8ghz dualcore or a 15" Base model with 8 GB Ram and 2.0ghz Quadcore?
Strictly talking about performance/speed.
Thanks!

Hey, thanks for the response!
Heavy internet browsing and work online(30+ Tabs open at times)
Itunes Music
Iphoto video uploading
exploring Garageband
I really want this computer to last for a really long time, first-time investment in apple.
Thanks again!

3 beeps on start up, RAM failure?

I have seen some older posts similar to this, however they all seemed to be more for tech savvy people unlike me. 6 weeks ago a connector cable in my hard drive failed and when I got it back from the shop the next day the MacBook Pro randomly shut down and restarted with a message saying an error occurred. This happened a three more times over the next couple weeks, but then stopped. Until just now when it happened again, the computer restarted then random fuzzy green lines came across the screen. The computer restarted again and the beeps began. 3 consecutive beeps that repeat themselves every few seconds. I manually shut the computer down and turned it on again and I got to the load screen with the apple, then black lines came across the screen. The screen then went fully black and the beeping started... Any ideas?

Cranny91 wrote:
The computer restarted again and the beeps began. 3 consecutive beeps that repeat themselves every few seconds. I manually shut the computer down and turned it on again and I got to the load screen with the apple, then black lines came across the screen. The screen then went fully black and the beeping started... Any ideas?
Problem with RAM, either failed or not seated properly.
http://support.apple.com/kb/HT5860?viewlocale=en_US
Best.

MBP 2010 8gb ram Crashing on boot

I have tried to upgrade my 2010 13" MBP with the 8gb 1333 DDR3 corsair. I did this once already with my 2009 15" MBP and worked just fine without any problems. I have read many success stories for upgrading a 2010 13" with the exact same ram and it's begining to frustrate me because i can't figure out if it's hardware or software with the computer. I did try the new ram in 15" just to make sure the ram wasn't bad and it booted just fine. Back to the 13" it will either simply crash on boot and have a error messae wich i can try to add a link to later but i did get this crash report (see below) after i put in the old 2gb sticks running at 1033. But it will either simply crash or i will get the grey apple logo and the spinner will start spinning for about 10 seconds than freeze. I let it sit for about 10-20 minutes multiple times to see if it just needed to think but it didn't progress pass that. i've also tried just using one of the single sticks instead of having both in and that didn't help either. tried reseting pram and enter safe mode but both attempts ended in it crashing the same way. I also tried using a different harddrive from another 13 macbook that had Snow lion on it thinking that something rooted on the 13" MBP operating system was causing it not to boot properly with the ram, that also didn't work. I am up for any suggestions. Thank you - D
Interval Since Last Panic Report: 152 sec
Panics Since Last Report:          1
Anonymous UUID:                    A57408DC-841D-406F-8FF9-380E4C3B6437
Sun Apr 8 17:18:12 2012
panic(cpu 0 caller 0x2a0663): "Spinlock acquisition timed out: lock=0x45d85e0, lock owner thread=0x2000, current_thread: 0xd2873d4, lock owner active on CPU 0xffffffff"@/SourceCache/xnu/xnu-1504.15.3/osfmk/i386/locks_i386.c:374
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x7bafb7c8 : 0x21b837 (0x5dd7fc 0x7bafb7fc 0x223ce1 0x0)
0x7bafb818 : 0x2a0663 (0x59ccb0 0x45d85e0 0x2000 0xd2873d4)
0x7bafb858 : 0x279ec7 (0x45d85e0 0x1 0x849088 0x7b946c1c)
0x7bafb898 : 0x272ba8 (0xd8ab280 0xe60000 0x0 0xa50)
0x7bafbab8 : 0x274fbb (0xd8ab280 0xe60000 0x0 0x8000)
0x7bafbb98 : 0x5601ff (0x2fdb520 0x11e60000 0x1 0x7bafbc34)
0x7bafbc58 : 0x56052a (0xd74bf00 0x0 0x2ed05005 0x1)
0x7bafbc78 : 0x7b9898e2 (0xd74bf00 0x0 0x200 0x0)
0x7bafbd28 : 0x7b989b1d (0x5f8ee4 0xe000002 0x7bafbec4 0x0)
0x7bafbd48 : 0x30d6a4 (0xe000002 0x7bafbec4 0x0 0x2ed05)
0x7bafbdd8 : 0x2ff592 (0x7bafbdfc 0x3 0x7bafbe28 0x58a167)
0x7bafbe28 : 0x2f45e1 (0xd8a8784 0x7bafbec4 0x0 0x7bafbf54)
0x7bafbe78 : 0x49f5f9 (0xd67ef60 0x7bafbec4 0x0 0x7bafbf54)
0x7bafbf18 : 0x49fd75 (0x7bafbf54 0xd67ef60 0x11e60000 0x1)
0x7bafbf78 : 0x4f82fb (0xd649540 0xce82e28 0xce7d134 0x1)
0x7bafbfc8 : 0x2a251d (0xce82e24 0x0 0x2a17ab 0xce82e24)
      Kernel Extensions in backtrace (with dependencies):
         com.apple.iokit.IOStorageFamily(1.6.3)@0x7b97b000->0x7b993fff
BSD process name corresponding to current thread: fsck_hfs
Mac OS version:
10K549
Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacBookPro7,1 (Mac-F222BEC8)
System uptime in nanoseconds: 30863821997
unloaded kexts:
(none)
loaded kexts:
com.apple.driver.AppleUSBTCButtons          201.6 - last loaded 1982567428
com.apple.driver.AppleIRController          303.8
com.apple.driver.AppleUSBTCKeyEventDriver          201.6
com.apple.driver.AppleUSBTCKeyboard          201.6
com.apple.driver.AppleUSBCardReader          2.6.1
com.apple.iokit.SCSITaskUserClient          2.6.8
com.apple.iokit.IOAHCIBlockStorage          1.6.4
com.apple.BootCache          31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.driver.AppleEFINVRAM          1.4.0
com.apple.driver.AppleAHCIPort          2.1.7
com.apple.driver.AirPortBrcm43xx          423.91.27
com.apple.driver.AirPortBrcm43224          428.42.4
com.apple.driver.AppleFWOHCI          4.7.3
com.apple.iokit.AppleBCM5701Ethernet          3.0.5b8
com.apple.driver.AppleUSBHub          4.2.4
com.apple.driver.AppleUSBEHCI          4.2.4
com.apple.driver.AppleUSBOHCI          4.2.0
com.apple.driver.AppleHPET          1.5
com.apple.driver.AppleRTC          1.3.1
com.apple.driver.AppleSmartBatteryManager          160.0.0
com.apple.driver.AppleACPIButtons          1.3.6
com.apple.driver.AppleSMBIOS          1.7
com.apple.driver.AppleACPIEC          1.3.6
com.apple.driver.AppleAPIC          1.4
com.apple.driver.AppleIntelCPUPowerManagementClient          142.6.0
com.apple.security.sandbox          1
com.apple.security.quarantine          0
com.apple.nke.applicationfirewall          2.1.14
com.apple.driver.AppleIntelCPUPowerManagement          142.6.0
com.apple.driver.BroadcomUSBBluetoothHCIController          2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController          2.4.5f3
com.apple.iokit.IOBluetoothFamily          2.4.5f3
com.apple.driver.AppleUSBMultitouch          207.7
com.apple.iokit.IOUSBHIDDriver          4.2.0
com.apple.iokit.IOUSBMassStorageClass          2.6.7
com.apple.iokit.IOSCSIBlockCommandsDevice          2.6.8
com.apple.iokit.IOSCSIMultimediaCommandsDevice          2.6.8
com.apple.iokit.IOBDStorageFamily          1.6
com.apple.iokit.IODVDStorageFamily          1.6
com.apple.iokit.IOCDStorageFamily          1.6.1
com.apple.driver.XsanFilter          402.1
com.apple.driver.AppleUSBMergeNub          4.2.4
com.apple.driver.AppleUSBComposite          3.9.0
com.apple.iokit.IOAHCISerialATAPI          1.2.6
com.apple.iokit.IOSCSIArchitectureModelFamily          2.6.8
com.apple.driver.AppleFileSystemDriver          2.0
com.apple.iokit.IOAHCIFamily          2.0.6
com.apple.iokit.IO80211Family          320.1
com.apple.iokit.IOFireWireFamily          4.2.6
com.apple.iokit.IONetworkingFamily          1.10
com.apple.iokit.IOUSBUserClient          4.2.4
com.apple.driver.AppleMCP89RootPortPM          1.11
com.apple.iokit.IOUSBFamily          4.2.4
com.apple.driver.NVSMU          2.2.7
com.apple.driver.AppleEFIRuntime          1.4.0
com.apple.iokit.IOHIDFamily          1.6.6
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.TMSafetyNet          6
com.apple.kext.AppleMatch          1.0.0d1
com.apple.driver.DiskImages          289
com.apple.iokit.IOStorageFamily          1.6.3
com.apple.driver.AppleACPIPlatform          1.3.6
com.apple.iokit.IOPCIFamily          2.6.5
com.apple.iokit.IOACPIFamily          1.3.0
Model: MacBookPro7,1, BootROM MBP71.0039.B0B, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.62f6
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.131.42.4)
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Serial ATA Device: FUJITSU MHY2080BH, 74.53 GB
Serial ATA Device: MATSHITADVD-R   UJ-898, 7.8 GB
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0x24600000 / 2
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0x26100000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06600000 / 4
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8213, 0x06610000 / 5
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x06500000 / 3
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0236, 0x06300000 / 2

I know that it says that it likes 1033 but..... when i had read around to upgrad my 15" people said it would work and would just clock the ram speed down from 1333 to 1033. I installed it and to a shocking suprise it didn't even clock it down to 1033. My frustration is that this 13" MBP is a year newer and isn't even wanting to boot with the ram. I would assume, and be glad with it booting and just clocking the RAM down. i wouldn't see why that wouldn't be a problem. Thank you though for youru suggestion. Thanks - DJ

Snow Leopard and MBP 8GB of Ram?

We know already that the late 2008 2.4GHz MBP Unibody supports up to 6GB of ram. The 2.53 and 2.6 support 8GB.
The question is will this same MBP support 8GB of ram when Snow Leopard is released? Is it a hardware or 32-bit/64-bit addressing problem that limits the 2.4GHz MBP?

"Is it a hardware or 32-bit/64-bit addressing problem that limits the 2.4GHz MBP?"
Are you referring to the memory limitation? No.

MBP 3 beeps issue

My MBP recently starting giving me the beachball at odd times - not seemingly related to heavy demands on the system. Before I ran any diagnostics, I decided to go ahead and update software, which hadn't been done for a while. Machine totally froze during system update, and now will not boot up. Simply powers on, goes to gray loading screen, and then shuts down after a few seconds.
I CAN boot in recovery mode just fine, but when I try to reinstall Lion from the recovery partition, it tells me the system HD is locked. So over to the Disk Utility... Verify Disk shows "invalid node structure". Repair disk works for a minute, logs "Volume repair complete", and then says it can't repair the disk and to reformat it. So, on to plan C:
I created a bootable USB drive with a Disk Warrior dmg, hoping that I could make some forward progress that way. However, when I choose the Disk Warrior volume as the boot disk, the mouse freezes, and I get the dreaded beeps. In groups of three.
Am I out of options besides booting in target mode to backup my files and then reformatting the system drive?

I know that's what the 3 beeps supposedly means, but it makes no sense to me that it happens only when I try to boot from the USB volume, and every time I do if it's a corrupted RAM issue.

I dropped my computer, it made the 3-beep "RAM is screwed" noises, but it seems to be working fine now. What should I do?

I'm bad at computers so be patient with me ... I dropped my 2.5 year old MacBook Pro from about waist height onto a concrete floor (I know!). Worst feeling in the world, especially after I had the hard drive replaced a couple weeks ago. Now the case has a little dent on the corner but no other visible damage. After I dropped it it started doing the "beep beep beep -- pause -- beep beep beep" noise, which after some googling I see is to do with something wrong with the RAM. I powered off and restarted it, and after the restart it seems to have nothing wrong with it; turned on fine, screen is fine, no error messages, no slower than usual. I checked the memory stuff in System Report and it says both sticks are OK. I also ran the "verify disk" thing to check my hard drive and got no errors.
Can somebody tell me what the odds are of this computer surviving for the next couple months? I would take it to an Apple store, but this is complicated by me being in Rwanda, which means getting my computer fixed or even looked at is highly unlikely. I've got a friend coming to visit in a week and she could just buy me a new computer and bring it over, but I really, really don't want to have to buy a new one if this one's going to work. On the other hand, I'm terrified that this one is going to up and die on me before I get back to the US in August. Still, it seems to be working OK -- but is it going to die out of nowhere? Would you buy a new computer, if it were you? Does anybody have any ideas about what might happen to this one over the next few weeks? Thanks!

venicespent,
Boot into your Mavericks Recovery partition by hold down the command and R keys whilst booting. You'll see a screen that looks like this:
Click on the Disk Utility item to open Disk Utility. You should see your boot drive (usually named "Macintosh HD" unless you've changed it) in the column on the left of the screen. Select your boot partition and click on the "Verify" button. Let your Mac do it's thing - if you get green text telling you that everything seems to be OK, then your disk should not be damaged. If, however, you get red text telling you that the disk needs to be repaired, click on the "Repair" button. If the disk can be repaired, you should be good to go. If the disk cannot be repaired then the drive is damaged.
But before you do anything, make certain that you have backups!!!
Clinton
MacBook Pro (15-inch Late 2011), OS Mavericks 10.9.4, 16GB RAM, 960GB SSD, 27” Apple Thunderbolt Display

MacBook Pro Three beeps - RAM Test passed

Hey,
my MacBook Pro (Early 2011, 2.0 GHz, Mountain Lion 10.8.4, 8 GB RAM, 256 GB SSD + 500 GB HDD) recently began to freeze or power off and then playing three beeps instead of turning on again.
The problems began some weeks ago, as the file system on my SSD (I've switched the Superdrive with my HDD and put in an additional SSD myself) broke and could not be repaired by Disk Utility. So I formatted the partition and reinstalled Mountain Lion. Since then my Mac crashed three times with (logged) Kernel Panics.
In the interim it's running quite stable, but it froze in the past two or three days several times while I was using it (for example playing a YouTube video or a MP4-File saved on my harddrive) and then began to beep three times. I know this should indicate some kind of RAM issue.
The first time the beeping occured, my Mac began to work again after I carried it over to a friend without opening it at all. Then I ran the Apple Hardware Test (short version) and it passed, later I also ran the extended version and it passed as well. The memtest utility also finds no error.
The latest crash was a bit harder. I took out the 8 GB RAM (I've upgraded from original 4 GB) and reinstalled the original "Apple" 4 GB RAM that came with my MacBook - still three beeps. So I took them out and just put in one bar of my RAM (so one of the two 4 GB bars) and it booted just fine. I wanted to rule out a defect of my logic board, so I tried the following combinations of installed RAM:
first bar in the first slot - boots
first bar in the second slot - boots
second bar in the first slot - boots
second bar in the second slot - boots
both bars installed - boots
Another thing that happened recently: I put my Mac to sleep with ~25% battery left, it was then laid to the ground. After I picked it up maybe an hour later it didn't power on when I opened the lid and also didn't when I hit the power button. So i plugged it in and it loaded the saved memory from the SSD - but the display just showed a resolution of about 800 by 600 pixels. It booted to the login screen, I entered my password and then it restarted automatically (still with low resolution), booted with the apple logo, crashed again and booted directly to the recovery partition. I tried to choose the Mountain Lion partition to reboot from, but it wasn't listed (instead I just saw the Bootcamp partition on my HDD). I powered it off and on again, hitting the option key to see all my drives and voilà, all partitions were listed (ML, Bootcamp and Recovery) and the Mac booted successfully to the login screen, where it restored the correct resolution of 1680*1050.
I don't know what to do, since the RAM bars don't seem to be the problem (since they are passing the test, running fine in between and the original RAM also produced three beeps). It seems to be the logic board, but the crashes occur quite random and it's not as if one RAM slot was totally broken. As the problems started with a broken file system, could it also be the SSD (although the SMART-Status is still verified)?
I hope anyone can help me or at least give a useful advice.

I would like to give you few pointers that may give you some relief. First, your problems sound almost identical to mine. The timeline is almost identical as well. After following the advice from the Apple Support Tech, we finally arrived at the conclusion that it is a hardware problem with my late model MacBook Pro 2011. The Apple support tech asked me to take it in for service. Since I had over 10 hours before my appointment, I did some additional diagnostic and made some discoveries. I will outline my steps below to show how I arrived at my conclusion.
Problem: MacBook beeps 3 times and freezes, BSD dump on screen or frezzes and restarts with appropriate fail message.
Apple: Use original 8gig Apple ram, Boot into Diagnostic utility and restore 10.7 OS, restore backup from time machine.
Solution: Everything worked fine, no more crashes. Restored TimeMachine backup using Diagnostic utility.
Problem: Booted fine, after 15 minutes, went into recursive white screen of death, as I like to call it.
Apple: Sounds like a hardware issue, scheduled Apple Store visit.
Solution: Removed SSHD (seagate hybrid) and reinstalled MacBook HD. Updated to current OS, 10.8.4, did not restore any of TimeMachine backups. Running CPU, ram, HD stress tests for several hours without a crash or freeze.
Called Apple support and cancelled my Apple store visit and determined to allow more stress tests to run over night and also testing the SSHD outside using SeaTools for any problems with the drive. So far none after 4 hours of testing.
Conclusion: During the past several months as Apple has been updating the OS, I belive the applications and utilities that are running on my machine may be causing the crashes of the MacBook pro. My suggestion is to Make a backup if you do not do this daily. Restore OS from Diagnostic utility and update OS. Do not install any third party utilities that alter OS or enhance the OS operations. Reinstall your programs from scratch. Use migrations utility to restore only the data associated with your programs. I believe that you will avoid restoring any programs that might cause your crashes. I also suggest you run a day or two without restoring anything just to confirm your MacBook is operating well. I will keep you posted after I finish in two days as to the outcome. But I am certain it is not a hardware issue at this point.

Has anyone received their C2D MBP with 3GB RAM?

For those that have ordered a 15" C2D MBP with 3GB of RAM:
a) have you received their order yet, and if so, did it take a while to ship (mine's taking forever to ship);
b) do you feel that the extra 1GB was worthwhile paying for in terms of performance under programs such as photoshop CS2 etc.
Powerbook G4 Mac OS X (10.4.8) 667 MHz PPC

Yes, I received my 15-incher with 3gb of RAM and 160gb HD. I ordered about an hour after the store came back up with the updated specs on 10/24, it shipped late on 10/26, and I received it on 10/30.
I've not tried CS2 - I have that but currently run it on my Dell desktop. I'll be migrating my photography workflow over to the Mac next spring, when Adobe univeral binaries become available, at which time I'll replace the Dell with a Mac Pro.
I can say, having started working with the Aperture trial and Parallels running Windows XP (to which I have a gig of RAM dedicated when running the VM), that the extra memory seems to make a significant difference. I'm not at all sorry I bit the bullet for that extra gig - especially since Apple's price vis-a-vis that upgrade seems very reasonable relative to the aftermarket memory providers.
Good luck on receiving yours soon. This is a wonderful machine...

Safari does not open me, that leaves unexpectedly closed. but it is always so. No matter if you reboot the laptop. I have MBP 13 "8GB ram, 2.4 GHz processor

hello.
safari does not open me, that leaves unexpectedly closed. but it is always so. No matter if you reboot the laptop. help please.
how do I remove Safari and reinstall it because when I go to delete the application from the finder, goes that you can not perform this action because OS X does not leave.
There leave something that leaves me open to give the safari:
Process:         Safari [704]
Path:            /Applications/Safari.app/Contents/MacOS/Safari
Identifier:      com.apple.Safari
Version:         7.0.2 (9537.74.9)
Build Info:      WebBrowser-7537074009000000~3
Code Type:       X86-64 (Native)
Parent Process: launchd [143]
Responsible:     Safari [704]
User ID:         501
Date/Time:       2014-03-24 21:42:17.094 -0500
OS Version:      Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: 8151A932-FF73-155E-135A-1ECFBF824217
Sleep/Wake UUID: 8A361AC7-3227-463F-A0D8-A245BB1474E4
Crashed Thread: 14
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Thread 0:: Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib                         0x000000011294a3b5 lookUpImpOrForward + 523
1   libobjc.A.dylib                         0x000000011294a198 lookUpImpOrNil + 20
2   libobjc.A.dylib                         0x000000011293f919 class_getMethodImplementation + 40
3   com.apple.AppKit                        0x0000000113ea589f _NSSubclassOverridesSelector + 38
4   com.apple.AppKit                        0x0000000113ea578f _NSLogOverriddenIdentifierForObject + 68
5   com.apple.AppKit                        0x0000000113eca5e4 -[NSView setUserInterfaceItemIdentifier:] + 54

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. All it does is to collect information about the state of the computer. That information goes nowhere unless you choose to share it. However, you should be cautious about running any kind of program (not just a shell script) at the request of a stranger on a public message board. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them. Ask for other options.
Here's a summary of what you need to do, if you choose to proceed: Copy a line of text from this web page into the window of another application. Wait for the script to run. It usually takes a few minutes. Then paste the results, which will have been copied automatically, back into a reply on this page. The sequence is: copy, paste, wait, paste again. Details follow.
4. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
5. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
6. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
Triple-click anywhere in the line of text below on this page to select it:
PATH=/usr/bin:/bin:/usr/sbin:/sbin; clear; Fb='%s\n\t(%s)\n'; Fm='\n%s\n\n%s\n'; Fr='\nRAM details\n%s\n'; Fs='\n%s: %s\n'; Fu='user %s%%, system %s%%'; AC="com.autodesk.AutoCAD com.evenflow.dropbox com.google.GoogleDrive"; H='^[[:space:]]*((127\.0\.0\.1|::1|fe80::1%lo0)[[:space:]]+local|(255\.){3}255[[:space:]]*broadcast)host[[:space:]]*$'; NS=networksetup; PB="/usr/libexec/PlistBuddy -c Print"; A () { [[ a -eq 0 ]]; }; M () { find -L "$d" -type f | while read f; do file -b "$f" | egrep -lq XML\|exec && echo $f; done; }; AT () { o=`file -b "$1" | egrep -v '^(A.{16}t$|cann)'`; Ps "${1##*/} format"; }; Pc () { o=`grep -v '^ *#' "$2"`; l=`wc -l <<< "$o"`; [[ l -gt 25 ]] && o=`head -n25 <<< "$o"`$'\n'"[$((l-25)) more line(s)]"; Pm "$1"; AT "$1"; }; Pm () { [[ "$o" ]] && o=`sed -E '/^ *$/d;s/^ */   /;s/[-0-9A-Fa-f]{22,}/UUID/g;s/(ochat)\.[^.]+(\..+)/\1\2/;/Shared/!s/(\/Users\/)[^/]+/\1-/g' <<< "$o"` && printf "$Fm" "$1" "$o"; }; Pp () { o=`$PB "$2" | awk -F'= ' \/$3'/{print $2}'`; Pm "$1"; }; Ps () { o=`echo $o`; [[ ! "$o" =~ ^0?$ ]] && printf "$Fs" "$1" "$o"; }; R () { o=; [[ r -eq 0 ]]; }; SP () { system_profiler SP${1}DataType; }; id -G | grep -qw 80; a=$?; A && sudo true; r=$?; t=`date +%s`; clear; { A || echo $'No admin access\n'; A && ! R && echo $'No root access\n'; SP Software | sed -n 's/^ *//;5p;6p;8p'; h=(`SP Hardware | awk '/ Id/{print $3}; /Mem/{print $2}'`); o=$h; Ps "Model"; o=$((h[1]<4?h[1]:0)); Ps "Total RAM (GB)"; o=`SP Memory | sed '1,5d;/[my].*:/d'`; [[ "$o" =~ s:\ [^O]|x([^08]|0[^2]|8[^0]) ]] && printf "$Fr" "$o"; o=`SP Diagnostics | sed '5,6!d'`; [[ "$o" =~ Pass ]] || Pm "POST"; p=`SP Power`; o=`awk '/Cy/{print $NF}' <<< "$p"`; o=$((o>=300?o:0)); Ps "Battery cycles"; o=`sed -n '/Cond.*: [^N]/{s/^.*://p;}' <<< "$p"`; Ps "Battery condition"; for b in FireWire Thunderbolt USB; do o=`SP $b | sed -En '/:$/{s/ *:$//;x;s/\n//;s/\n.*//;/\)/p;};/^ *(V.+ [0N]|Man).+ /{s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;};/Apple|Broadcom|Genesy|Intel|SMSC/{s/.//g;h;}'`; Pm $b; done; o=`pmset -g therm | sed 's/^.*C/C/'`; [[ "$o" =~ No\ th|pms ]] && o=; Pm "Thermal conditions"; o=`pmset -g sysload | grep -v :`; [[ "$o" =~ =\ [^GO] ]] || o=; Pm "System load advisory"; o=`nvram boot-args | awk '{$1=""; print}'`; Ps "boot-args"; fdesetup status | grep -q On && o=on || o=; Ps "FileVault"; a=(/ ""); A=(System User); for i in 0 1; do o=`cd ${a[$i]}L*/Lo*/Diag* || continue; for f in *.{cr,h,pa,s}*; do [[ -f "$f" ]] || continue; d=$(stat -f%Sc -t%F "$f"); [[ "$f" =~ h$ ]] && grep -lq "^Thread c" "$f" && f="$f *"; echo "$d ${f%%_2*} ${f##*.}"; done | sort | tail`; Pm "${A[$i]} diagnostics"; done; grep -lq '*$' <<< "$o" && printf $'\n\t* Code injection\n'; o=`syslog -F bsd -k Sender kernel -k Message CReq 'caug|GPU |hfs: Ru|last value [1-9]|n Cause: -|NVDA\(|pagin|proc: t|Roamed|rror|ssert|Thrott|timed? ?o|WARN' -k Message Ane 'SMC:' | tail -n25 | awk '/:/{$4=""; $5=""};1'`; Pm "Kernel messages"; o=`df -m / | awk 'NR==2 {print $4}'`; o=$((o<5120?o:0)); Ps "Free space (MiB)"; o=$(($(vm_stat | awk '/eo/{sub("\\.",""); print $2}')/256)); o=$((o>=1024?o:0)); Ps "Pageouts (MiB)"; s=( `sar -u 1 10 | sed '$!d'` ); [[ s[4] -lt 85 ]] && o=`printf "$Fu" ${s[1]} ${s[3]}` || o=; Ps "Total CPU usage" && { s=(`ps acrx -o comm,ruid,%cpu | sed '2!d'`); n=$((${#s[*]}-1)); c="${s[*]}"; o=${s[$n]}%; Ps "CPU usage by process \"${c% ${s[$((n-1))]}*}\" with UID ${s[$((n-1))]}"; }; s=(`top -R -l1 -n1 -o prt -stats command,uid,prt | sed '$!d'`); n=$((${#s[*]}-1)); s[$n]=${s[$n]%[+-]}; c="${s[*]}"; o=$((s[$n]>=25000?s[$n]:0)); Ps "Mach ports used by process \"${c% ${s[$((n-1))]}*}\" with UID ${s[$((n-1))]}"; o=`kextstat -kl | grep -v com\\.apple | cut -c53- | cut -d\< -f1`; Pm "Loaded extrinsic kernel extensions"; R && o=`sudo launchctl list | awk 'NR>1 && !/0x|com\.(apple|openssh|vix\.cron)|org\.(amav|apac|calendarse|cups|dove|isc|ntp|openld|post[fg]|x)/{print $3}'`; Pm "Extrinsic daemons"; o=`launchctl list | awk 'NR>1 && !/0x|com\.apple|org\.(x|openbsd)|\.[0-9]+$/{print $3}'`; Pm "Extrinsic agents"; o=`for d in {/,}L*/Lau*; do M; done | egrep -v 'com\.apple\.(CSConfig|server)' | while read f; do ID=$($PB\ :Label "$f") || ID="No job label"; printf "$Fb" "$f" "$ID"; done`; Pm "launchd items"; o=`for d in /{S*/,}L*/StartupItems; do M; done`; Pm "Startup items"; sys=`pkgutil --regexp --only-files --files com.apple.pkg.* | sort | uniq | sed 's:^:/:'`; b=`sed -E '/^.+Lib.+\/Contents\/Info.plist$/!d;s/\/Info.plist$//;/Contents\/./d' <<< "$sys"`; l=`egrep '^/usr/lib/.+dylib$' <<< "$sys"`; [[ "$b" && "$l" ]] && { o=`find -L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Compon,Ex,In,iTu,Keyb,Mail/B,P*P,Qu*T,Scripti,Sec,Servi,Spo}* -type d -name Contents -prune | grep -Fv "$b" | while read d; do test -f "$d/Info.plist" || continue; ID=$($PB\ :CFBundleIdentifier "$_") || ID="No bundle ID"; printf "$Fb" "${d%/Contents}" "$ID"; done`; Pm "Extrinsic loadable bundles"; o=`find /usr/lib -type f -name *.dylib | grep -Fv "$l"`; Pm "Extrinsic shared libraries"; :; } || echo $'\nReceipts missing'; o=`for e in INSERT_LIBRARIES LIBRARY_PATH; do launchctl getenv DYLD_$e; done`; Pm "Inserted dylibs"; o=`find -L {,/u*/lo*}/e*/periodic -type f -mtime -10d`; Pm "Modified periodic scripts"; o=`scutil --proxy | grep Prox`; Pm "Proxies"; o=`scutil --dns | awk '/r\[0\] /{if ($NF !~ /^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./) print $NF; exit}'`; i=`route -n get default | awk '/e:/{print $2}'`; I=`$NS -listnetworkserviceorder | sed -En '/ '$i'\)$/{x;s/^$.+$ //p;q;};x'`; n=`$NS -getdnsservers "$I" | awk '!/^T/{printf "not "; exit}'`; Ps "DNS (${n}from DHCP)"; o=`$NS -getinfo "$I" | awk '/k:/{if ($3 !~ "(255\.){3}0") print}; /v6:/{if ($2 !~ "A") print}'`; Pm "TCP/IP"; R && o=`sudo profiles -P | grep : | wc -l`; Ps "Profiles"; f=auto_master; [[ `md5 -q /etc/$f` =~ ^b166 ]] || Pc $f /etc/$f; for f in fstab sysctl.conf crontab launchd.conf; do Pc $f /etc/$f; done; f=/etc/hosts; Pc "hosts" <(egrep -v "$H" $f ); AT $f; Pc "User launchd" ~/.launchd*; R && Pc "Root crontab" <(sudo crontab -l); Pc "User crontab" <(crontab -l); R && o=`sudo defaults read com.apple.loginwindow LoginHook`; Pm "Login hook"; LD="$(`find /S*/*/F* -type f -name lsregister | head -n1` -dump)"; o=`for ID in $AC; do [[ "$LD" =~ $ID ]] && echo $ID; done`; Pm "Application check"; Pp "Global login items" /L*/P*/loginw* Path; Pp "User login items" L*/P*/*loginit* Name; Pp "Safari extensions" L*/Saf*/*/E*.plist Bundle | sed -E 's/(\..*$|-[1-9])//g'; o=`find ~ $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $ | wc -l`; Ps "Restricted user files"; cd; o=`find . -maxdepth 1 -exec basename {} + | while read f; do [[ ("$f" =~ ^\.. && ! "$f" =~ ^\.(adobe|android|bash.+|CFU.+|cache|config|cups|dropbox|DS_Store|font.+|git.+|profile|rnd|sh_.+|ssh|subv.+|Trash(es)?|zprofile|zsh.+)$) || ($(stat -f%f "$f") -ge 32768 && "$f" != Library) ]] && ls -Fd "$f"; done`; Pm "Hidden user files"; o=`SP Fonts | egrep 'id: N|te: Y' | wc -l`; Ps "Font problems"; o=`find L*/{Con,Pref}* -type f ! -size 0 -name *.plist | while read f; do plutil -s "$f" >&- || echo $f; done`; Pm "Bad plists"; d=(Desktop L*/Keyc*); n=(20 7); for i in 0 1; do o=`find "${d[$i]}" -type f -maxdepth 1 | wc -l`; o=$((o<=n[$i]?0:o)); Ps "${d[$i]##*/} file count"; done; o=; [[ UID -eq 0 ]] && o=root; Ps "UID"; o=$((`date +%s`-t)); Ps "Elapsed time (s)"; } 2>/dev/null | pbcopy; exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
7. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Click anywhere in the Terminal window and paste (command-V). The text you pasted should vanish immediately. If it doesn't, press the return key.
8. If you see an error message in the Terminal window such as "syntax error," enter
exec bash
and press return. Then paste the script again.
9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
[Process completed]
to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report the results. No harm will be done.
11. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
12. When you post the results, you might see the message, "You have included content in your post that is not permitted." It means that the forum software has misidentified something in the post as a violation of the rules. If that happens, please post the test results on Pastebin, then post a link here to the page you created.
Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Terms of Use of the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

MBP 3 Beeps - RAM failure... already?!

Similar Messages

Maybe you are looking for