MacBook Pro (Early 2011) Startup Issue

[mudwick]

Good morning...

Have a Early 2011 MBP. 2.2 Intel. Upgraded to Yosemite over the weekend. Seemed all good.

Installed a new Crucial SSD and upgraded the factory installed 4gb of RAM to 8gb. Both hardware updates were done following step by step instruction from the Apple "Mac Tips" articles.

Macbook started just fine, and was running awesome all night. Shut it down and restarted two to three times to insure full operation.

Shut down before bed. Boot up this morning and the system ****s down shortly after the Apple logo appears.

No start command works...cannot start in Safe Mode, or Recovery mode. Diagnostics does not work as well.

Get the "Apple/Support -6002f" error code.

I have my original HD at home that I might be able to boot off of.

Sounds like a hardware issue? RAM? But it seemed to take the new modules just fine last night.

Thoughts? Genius Bar time?

 

[MacInWin]

If it's convenient, or you can call Apple support to find out what the code means.

 

[dtravis7]

I searched for that code and the error codes seem to stop in the high 5000 numbers. I would take it into Apple if you can.

 

[chscag]

I would swap out the Crucial SSD and put back the original hard drive to see if the machine will boot. I don't think it's a memory problem but you can never tell. If you still have the original 2 GB modules you can try putting them back in also.

 

[pigoo3]

Upgraded to Yosemite over the weekend. Seemed all good.

Installed a new Crucial SSD and upgraded the factory installed 4gb of RAM to 8gb.

If I'm understanding things correctly…three things were done to this computer rather close in time:

- Upgraded to Yosemite
- Upgraded the ram
- Installed an SSD

Same idea as chscag mentioned. Any one of these three could be an issue (although the Yosemite upgrade should be the least of the problems). I would put the old ram and HD back in…then see if everything is ok with just the Yosemite upgrade.

Then install either the ram or SSD…test again…etc. etc. Until the "main" issue is found.

- Nick