MacBook Pro Late 2013 retina randomly freezing

Hi there,
I recently purchased a pretty tricked out MacBook Pro 15" Retina from the refurbished store. Totally stoked to have it, and I was really enjoying the machine.
However, I've been having these random lockups about once a day which is the only real fly in the ointment (but a pretty big one, my MacBook Air late 2013 or prior Microsoft Surface Pro were very dependable machines).
Here's some extra details about my system
Mavericks: 10.9.4
SMC version: 2.19f7
Model Identifier: MacBookPro11,3
Boot ROM version: MBP112.0138.B07
As far as I can tell, I'm on the latest available versions of everything (not including betas).
I have also performed the GeekBench Stress Test, an SSD stress test, a GPU stress test all of which the machine passed with flying colors. I have reset the SMC/NVRAM etc, performed the built in Hardware check with nothing but positive results (no issues found). There's no panics in the console log. Here's an excerpt from my latest freeze, which doesn't seem to have anything in common with prior freezes.
2014-09-09 3:32:52.064 PM sandboxd[474]: ([473]) CVMCompiler(473) deny mach-lookup com.apple.distributed_notifications@Uv3
2014-09-09 3:33:42.967 PM Adobe Photoshop CC 2014[369]: clip: empty path.
2014-09-09 3:33:42.968 PM Adobe Photoshop CC 2014[369]: clip: empty path.
2014-09-09 3:34:32.826 PM Adobe Photoshop CC 2014[369]: clip: empty path.
2014-09-09 3:34:32.827 PM Adobe Photoshop CC 2014[369]: clip: empty path.
2014-09-09 3:34:52.352 PM com.apple.launchd[1]: (com.adobe.fpsaud[478]) Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
2014-09-09 3:34:52.352 PM com.apple.launchd[1]: (com.adobe.fpsaud[478]) Job failed to exec(3) for weird reason: 2
2014-09-09 3:34:52.790 PM quicklookd[471]: [QL] _QLServerGetThumbnail: can't convert path to url
2014-09-09 3:34:52.790 PM Finder[171]: CreateWithFileInfo failed to create URL with FSRef, falling back to blank icon.
2014-09-09 3:34:52.811 PM quicklookd[471]: [QL] _QLServerGetThumbnail: can't convert path to url
2014-09-09 3:34:53.882 PM com.apple.IconServicesAgent[230]: main Failed to composit image for binding VariantBinding [0x369] flags: 0x8 binding: FileInfoBinding [0x547] - extension: png, UTI: public.png, fileType: PNGf.
2014-09-09 3:34:53.883 PM quicklookd[471]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0xa03] flags: 0x8 binding: FileInfoBinding [0x903] - extension: png, UTI: public.png, fileType: PNGf request size:128 scale: 1
2014-09-09 3:34:58.138 PM WindowServer[110]: disable_update_timeout: UI updates were forcibly disabled by application "Firefox" for over 1.00 seconds. Server has re-enabled them.
2014-09-09 3:34:58.191 PM WindowServer[110]: common_reenable_update: UI updates were finally reenabled by application "Firefox" after 1.05 seconds (server forcibly re-enabled them after 1.00 seconds)
2014-09-09 3:36:25.609 PM apsd[98]: Unrecognized leaf certificate
***This is where I did a hard reset after giving the machine time to possibly recover, with no discernible change***
2014-09-09 3:44:42.000 PM bootlog[0]: BOOT_TIME 1410302682 0
I'm still within the return window, however, I can't identify a specific hardware issue. I also have found that other individuals using MacBook Pros suffering from similar issues have had their machines & logic boards replaced with no improvement which leads me to believe the issue is in OSX or the EFI.
Any advice, tips or anything I might be missing is greatly appreciated.

Hey Linc Davis,
It was not a hardware issue. I use a lot of refurbished hardware (iPhone 5, this MacBook Pro), and there's no discernible difference in dependability between refurbished and new. Apple's Refurbishment processes are stringent. I would like it if they were clearer about their refurbished warranty. I have purchased several Apple computers new, some of which displayed hardware faults out of the box (Late 2008 15" MacBook Pro), some of which didn't. Some issues only showed after some use (iBook G4).
Solution: I completely formatted the SSD and used the recovery partition to download a fresh copy of Mavericks from Apple. I then recovered my important data from a Time Machine backup, and re-installed the latest versions of my applications straight from the vendors. I did not do a "Migrate from backup" or anything like that, I treated it as an entirely fresh install. I believe migration from backups was the core of my issue.
Since then, I have not had a single freeze and the machine is more performant than before. My console is also a lot tidier. It's likely the install that came on the computer was faulty, Migration Assistant broke something, or some other bug appeared in the interim.
I'm very happy I don't need to waste time with a lengthy & tiresome replacement process. I hope this helps anyone else suffering from this issue.

Similar Messages

  • MacBook Pro Late 2013 retina Nightmare

    Hi guys. I am a recent convert, moved to Mac from PC just one month back and I must say that I was thoroughly enjoying my Macbook until 1 week back, a few days after upgrading to 10.9.3 from 10.9.2 when it started misbehaving. First, it started randomly switching off after closing the lid(I had to press the power button for several seconds for it to restart), then it started just restarting/switching off while on and working. Tried SMC, PRAM reset, fixing permissions to no avail. Finally decided to roll back to 10.9.2 , the system my Mac shipped with, using internet recovery but even after wiping the mac os partition, during installation using internet recovery, it just switched off or restarted.
    I have run a diagnostics test which says the hardware is ok and have taken it back to the IShop I bought it from, but they said that they couldn't find anything wrong....
    Any ideas guys?

    Hey Linc Davis,
    It was not a hardware issue. I use a lot of refurbished hardware (iPhone 5, this MacBook Pro), and there's no discernible difference in dependability between refurbished and new. Apple's Refurbishment processes are stringent. I would like it if they were clearer about their refurbished warranty. I have purchased several Apple computers new, some of which displayed hardware faults out of the box (Late 2008 15" MacBook Pro), some of which didn't. Some issues only showed after some use (iBook G4).
    Solution: I completely formatted the SSD and used the recovery partition to download a fresh copy of Mavericks from Apple. I then recovered my important data from a Time Machine backup, and re-installed the latest versions of my applications straight from the vendors. I did not do a "Migrate from backup" or anything like that, I treated it as an entirely fresh install. I believe migration from backups was the core of my issue.
    Since then, I have not had a single freeze and the machine is more performant than before. My console is also a lot tidier. It's likely the install that came on the computer was faulty, Migration Assistant broke something, or some other bug appeared in the interim.
    I'm very happy I don't need to waste time with a lengthy & tiresome replacement process. I hope this helps anyone else suffering from this issue.

  • Macbook pro Late 2013 retina display battery questions and issues

    Hi,
    So I was a bit suspicious about my macbook pro 2013 13 inch retina display models battery, its the latest macbook pro 13 inch. The website says that it will last for 9 hours but mines lasted for only 6.19 hours. All the apps I used were probably Xcode (doing coding projects), Photoshop, Safari and Notes. I did keep the brightness high and also had bluetooth on for a while. Is this a good battery life for my mac or should I go back to the Apple Store and tell them to fix my battery?
    I have all the battery logs below:
    Standby Time: 1:13 PM
    Battery Percent: 90%
    Usage Time Starting: 3:10 PM      Battery Percent: 87%
    Usage Time Ending:  4:01 PM      Battery Percent: 75%
    Apps Used:  Safari, Notes, Xcode,
    Usage Time Starting: 5:00 PM       Battery Percent: 74%
    Usage Time Ending:  5:56  PM       Battery Percent: 64%
    Apps Used: Safari, xcode
    Usage Time Starting: 6:53  PM      Battery Percent: 63% 
    UsageTime Ending: 7:19   PM      Battery Percent: 57%
    Apps Used: Safari
    Usage Time Starting: 7:46 PM      Battery Percent: 56%
    Usage Time Ending: 9:02 PM             Battery Percent: 40% 
    Apps Used: Photoshop, Safari, xcode
    Day 2:
    Usage Time Starting: 10:56 AM        Battery Percent: 38% 
    Usage Time Ending: 11:09 AM     Battery Percent:  39% 
    Apps Used:  Safari
    Usage Time Starting: 12:09 PM        Battery Percent: 36% 
    Usage Time Ending: 12:14    Battery Percent: 35% 
    Apps Used: Photoshop, Safari
    Usage Time Starting: 12:42 PM     Battery Percent: 35% 
    Usage Time Ending: 3:06     Battery Percent: 4% 
    Apps Used: Photoshop, Safari
    Bluetooth also added using mouse
    I wasn't using it for one day straight by the way, I used it for 2 days without charging with these logs.

    Fayk1,
    carefully review that Web site’s claim; under what conditions does it claim that a charge would last for up to nine hours? (Note those key words — “up to”.) Did your conditions exactly match those conditions? If you want a charge to last as long as possible, then make the display as dim as you can stand it, and minimize your use of Bluetooth and energy-hungry apps like Photoshop and Xcode compilers. To maximize the battery’s life, start recharging it when it gets down to 20%.

  • Macbook Pro late 2013 retina "clicks" on underside

    Started clicking a week ago.  any pressure applied to the underside of my MBP (right under the right/middle of the trackpad) now produces an annoying click.  Any ideas??

    Hey Linc Davis,
    It was not a hardware issue. I use a lot of refurbished hardware (iPhone 5, this MacBook Pro), and there's no discernible difference in dependability between refurbished and new. Apple's Refurbishment processes are stringent. I would like it if they were clearer about their refurbished warranty. I have purchased several Apple computers new, some of which displayed hardware faults out of the box (Late 2008 15" MacBook Pro), some of which didn't. Some issues only showed after some use (iBook G4).
    Solution: I completely formatted the SSD and used the recovery partition to download a fresh copy of Mavericks from Apple. I then recovered my important data from a Time Machine backup, and re-installed the latest versions of my applications straight from the vendors. I did not do a "Migrate from backup" or anything like that, I treated it as an entirely fresh install. I believe migration from backups was the core of my issue.
    Since then, I have not had a single freeze and the machine is more performant than before. My console is also a lot tidier. It's likely the install that came on the computer was faulty, Migration Assistant broke something, or some other bug appeared in the interim.
    I'm very happy I don't need to waste time with a lengthy & tiresome replacement process. I hope this helps anyone else suffering from this issue.

  • Macbook pro late 2013 retina whit Nvidia

    I have a new macbook pro retina whit nvidia integrate, when i'm playing the temperature come really up and the computer in 2h of playing reboot, cools work normally (very fast and making a lot of noise of course).
    It's normal? It isn't a computer to play? :O

    What computer program are you playing, and for how long? What's the absolutely highest temperature?
    It's really, really important to get accurate figures for this.
    It's normal? It isn't a computer to play?
    It's perfectly normal to enjoy playing games on your computer. However, there's a difference between a desktop system and a laptop like the MacBook Pro. The MacBook has an aluminum case, and doesn't vent heat as efficiently as, say, an iMac or iPad. Don't stop playing games, but never exceed a temperature of 160F.

  • Macbook Pro Late 2013 Retina

    MacBook Pro11,2 (intel iris pro HD5200 igpu only) october 2013
    moved to: https://wiki.archlinux.org/index.php/MacBookPro11,x
    edit:
    acpi -V now shows correct design capacity
    Last edited by hrod (2015-04-14 09:06:29)

    I get occasional hangs that last anywhere from 20s to a minute or so. There's always an accompanying set of logs from dmesg like the below:
    [ 68.369215] ata1.00: exception Emask 0x0 SAct 0x7ffe3fff SErr 0x0 action 0x6 frozen
    [ 68.369334] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.369411] ata1.00: cmd 60/88:00:d8:41:d3/00:00:0d:00:00/40 tag 0 ncq 69632 in
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.369612] ata1.00: status: { DRDY }
    [ 68.369664] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.369739] ata1.00: cmd 60/00:08:a8:05:e3/04:00:0d:00:00/40 tag 1 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.369940] ata1.00: status: { DRDY }
    [ 68.369993] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.370066] ata1.00: cmd 60/00:10:a8:25:e3/04:00:0d:00:00/40 tag 2 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.370270] ata1.00: status: { DRDY }
    [ 68.370321] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.370391] ata1.00: cmd 60/00:18:a8:2d:e3/04:00:0d:00:00/40 tag 3 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.370583] ata1.00: status: { DRDY }
    [ 68.370632] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.370703] ata1.00: cmd 60/00:20:a8:31:e3/04:00:0d:00:00/40 tag 4 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.370895] ata1.00: status: { DRDY }
    [ 68.370945] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.371015] ata1.00: cmd 60/00:28:a8:35:e3/04:00:0d:00:00/40 tag 5 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.371206] ata1.00: status: { DRDY }
    [ 68.371256] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.371327] ata1.00: cmd 60/00:30:a8:39:e3/04:00:0d:00:00/40 tag 6 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.371518] ata1.00: status: { DRDY }
    [ 68.371568] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.371638] ata1.00: cmd 60/00:38:a8:3d:e3/04:00:0d:00:00/40 tag 7 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.371830] ata1.00: status: { DRDY }
    [ 68.371880] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.371950] ata1.00: cmd 60/00:40:a8:41:e3/04:00:0d:00:00/40 tag 8 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.372141] ata1.00: status: { DRDY }
    [ 68.372191] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.372262] ata1.00: cmd 60/00:48:a8:45:e3/04:00:0d:00:00/40 tag 9 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.372464] ata1.00: status: { DRDY }
    [ 68.372514] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.372585] ata1.00: cmd 60/40:50:68:b2:77/00:00:31:00:00/40 tag 10 ncq 32768 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.372777] ata1.00: status: { DRDY }
    [ 68.372827] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 68.372899] ata1.00: cmd 61/a8:58:d8:b3:37/00:00:11:00:00/40 tag 11 ncq 86016 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.373091] ata1.00: status: { DRDY }
    [ 68.373141] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 68.373213] ata1.00: cmd 61/78:60:b8:b3:77/00:00:27:00:00/40 tag 12 ncq 61440 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.373406] ata1.00: status: { DRDY }
    [ 68.377217] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.381029] ata1.00: cmd 60/08:68:e0:d1:f7/00:00:0e:00:00/40 tag 13 ncq 4096 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.388335] ata1.00: status: { DRDY }
    [ 68.391932] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.395355] ata1.00: cmd 60/08:88:a8:b4:33/01:00:14:00:00/40 tag 17 ncq 135168 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.402358] ata1.00: status: { DRDY }
    [ 68.405696] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.409009] ata1.00: cmd 60/00:90:a8:f1:e2/04:00:0d:00:00/40 tag 18 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.415754] ata1.00: status: { DRDY }
    [ 68.418938] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.422133] ata1.00: cmd 60/00:98:a8:f5:e2/04:00:0d:00:00/40 tag 19 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.428597] ata1.00: status: { DRDY }
    [ 68.431680] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.434751] ata1.00: cmd 60/00:a0:a8:f9:e2/04:00:0d:00:00/40 tag 20 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.440945] ata1.00: status: { DRDY }
    [ 68.443932] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.446894] ata1.00: cmd 60/00:a8:a8:fd:e2/04:00:0d:00:00/40 tag 21 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.452878] ata1.00: status: { DRDY }
    [ 68.455756] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.458618] ata1.00: cmd 60/00:b0:a8:01:e3/04:00:0d:00:00/40 tag 22 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.464391] ata1.00: status: { DRDY }
    [ 68.467182] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.469951] ata1.00: cmd 60/00:b8:a8:09:e3/04:00:0d:00:00/40 tag 23 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.475547] ata1.00: status: { DRDY }
    [ 68.478245] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.480929] ata1.00: cmd 60/00:c0:a8:0d:e3/04:00:0d:00:00/40 tag 24 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.486342] ata1.00: status: { DRDY }
    [ 68.488964] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.491567] ata1.00: cmd 60/00:c8:a8:11:e3/04:00:0d:00:00/40 tag 25 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.496827] ata1.00: status: { DRDY }
    [ 68.499365] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.501892] ata1.00: cmd 60/00:d0:a8:15:e3/04:00:0d:00:00/40 tag 26 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.506991] ata1.00: status: { DRDY }
    [ 68.509539] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.512072] ata1.00: cmd 60/00:d8:a8:19:e3/04:00:0d:00:00/40 tag 27 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.517194] ata1.00: status: { DRDY }
    [ 68.519738] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.522278] ata1.00: cmd 60/00:e0:a8:1d:e3/04:00:0d:00:00/40 tag 28 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.527430] ata1.00: status: { DRDY }
    [ 68.529980] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.532558] ata1.00: cmd 60/00:e8:a8:21:e3/04:00:0d:00:00/40 tag 29 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.537699] ata1.00: status: { DRDY }
    [ 68.540273] ata1.00: failed command: READ FPDMA QUEUED
    [ 68.542825] ata1.00: cmd 60/00:f0:a8:29:e3/04:00:0d:00:00/40 tag 30 ncq 524288 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 68.547961] ata1.00: status: { DRDY }
    [ 68.550517] ata1: hard resetting link
    [ 68.935620] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 68.935981] ata1.00: unexpected _GTF length (8)
    [ 68.936372] ata1.00: unexpected _GTF length (8)
    [ 68.936441] ata1.00: configured for UDMA/133
    [ 68.936445] ata1.00: device reported invalid CHS sector 0
    [ 68.936447] ata1.00: device reported invalid CHS sector 0
    [ 68.936449] ata1.00: device reported invalid CHS sector 0
    [ 68.936451] ata1.00: device reported invalid CHS sector 0
    [ 68.936452] ata1.00: device reported invalid CHS sector 0
    [ 68.936453] ata1.00: device reported invalid CHS sector 0
    [ 68.936455] ata1.00: device reported invalid CHS sector 0
    [ 68.936456] ata1.00: device reported invalid CHS sector 0
    [ 68.936458] ata1.00: device reported invalid CHS sector 0
    [ 68.936459] ata1.00: device reported invalid CHS sector 0
    [ 68.936461] ata1.00: device reported invalid CHS sector 0
    [ 68.936462] ata1.00: device reported invalid CHS sector 0
    [ 68.936464] ata1.00: device reported invalid CHS sector 0
    [ 68.936465] ata1.00: device reported invalid CHS sector 0
    [ 68.936467] ata1.00: device reported invalid CHS sector 0
    [ 68.936469] ata1.00: device reported invalid CHS sector 0
    [ 68.936470] ata1.00: device reported invalid CHS sector 0
    [ 68.936472] ata1.00: device reported invalid CHS sector 0
    [ 68.936473] ata1.00: device reported invalid CHS sector 0
    [ 68.936474] ata1.00: device reported invalid CHS sector 0
    [ 68.936476] ata1.00: device reported invalid CHS sector 0
    [ 68.936477] ata1.00: device reported invalid CHS sector 0
    [ 68.936479] ata1.00: device reported invalid CHS sector 0
    [ 68.936480] ata1.00: device reported invalid CHS sector 0
    [ 68.936482] ata1.00: device reported invalid CHS sector 0
    [ 68.936483] ata1.00: device reported invalid CHS sector 0
    [ 68.936485] ata1.00: device reported invalid CHS sector 0
    [ 68.936486] ata1.00: device reported invalid CHS sector 0
    [ 68.936510] sd 0:0:0:0: [sda]
    [ 68.936512] Result: hostbyte=0x00 driverbyte=0x08
    [ 68.936513] sd 0:0:0:0: [sda]
    [ 68.936515] Sense Key : 0xb [current] [descriptor]
    [ 68.936517] Descriptor sense data with sense descriptors (in hex):
    [ 68.936518] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 68.936525] 00 00 00 00
    [ 68.936528] sd 0:0:0:0: [sda]
    [ 68.936528] ASC=0x0 ASCQ=0x0
    [ 68.936530] sd 0:0:0:0: [sda] CDB:
    [ 68.936531] cdb[0]=0x28: 28 00 14 33 b4 a8 00 01 08 00
    [ 68.936537] end_request: I/O error, dev sda, sector 338932904
    [ 68.940271] ata1: EH complete

  • Sound stops working while using headphones on Retina Macbook Pro (late 2013)

    I have a brand new Retina Macbook Pro (late 2013) with OSX 10.9.1 installed. The sound continuously stops working when I'm using my headphones (which I use on a daily basis). I've noticed that when I unplug the headphones, the sound from the internal speakers and the headphone port stops working.
    I've already checked other answers and have tried their suggestions:
    I've looked at the sound settings and it is not set to mute.
    I've tried unplugging the headphones several times in a row and that still doesn't work.
    I don't see a red light in the headphone port.
    I've checked the headphones and there is nothing wrong with them (I use them with other devices).
    I've tried using different headphones, but the problem persists.
    The only way to get the sound working again is by restarting my laptop which is very inconvenient. I use this laptop for working and having to restart it every time I unplug my headphones is just not a solution. I honestly have no idea what is going on. This is a very new laptop (and my first Macbook); I've had it for less than 3 months. The laptop stays on my desk and has not been dropped or damaged in any way. This is a very expensive laptop and the last thing I would expect is for there to be a problem like this.
    If anyone has a solution to get rid of this problem once and for all, please let me know!
    Thank you.

    I have a brand new Retina Macbook Pro (late 2013)
    Please read the warranty paperwork that came w/your computer.  You have 14 days to return the computer w/no questions asked.  You have 90 days of FREE phone tech support on top of your standard 1 year warranty unless you also purchased AppleCare which gives you an additional 2 years of coverage plus FREE phone support.  Strongly suggest that you take FULL advantage of the above before it runs out.  Let Apple deal w/the problems.  If you DIY and mess up, your warranty will be VOIDED! 

  • Retina Macbook Pro (late 2013) screen blinking

    I recently got a Retina Macbook Pro (late 2013), and the screen has been spontaneously blinking. It's exceptionally distracting, and I've been unable to correlate it to any running program. Has anyone else had this issue?

    Welcome to Apple Support Communities
    Your MacBook is in warranty, so take it to an Apple Store or reseller to get the MacBook repaired or replaced free of charge. It looks like a hardware issue, so it's better to do this

  • MacBook Pro late 2013 does not show login window after waking from sleep

    MacBook Pro late 2013 does not always prompt for login, but opens directly to desktop, even though security settings are setup to prompt for password after 5 minutes. Up to now, this only has happened on battery, machine goes to sleep or lid is closed, 10 minutes pass, lid is opened and desktop is shown instead of lock screen. Console shows, that the machine was actually sleeping (10 min no log entries) and also does not show any error in regards to login window.
    This behaviour occurs randomly and I could not track down any root cause/behaviour, yet. Sometimes everything behaves as it should.
    Any ideas?
    Thanks
    marcus

    Count me in, I have the same issue, and from what I read here, it looks like a Yosemite/SSD related issue ?
    I'm not 100% sure if it started when I put a SSD in my old iMac 2009 (as a fusion drive) or if that's after that when I upgraded to Yosemite...
    I did disable auto poweroff like suggested in another thread : Mac freeze during the night sleep.
    sudo pmset -a autopoweroff 0
    We'll see if it helps.
    It happens toughly a couple of times a week.

  • Design flaw in Macbook Pro late 2013?

    Hi,
    Looks like Macbook Pro late 2013 has a weakness, due to a design flaw. Let me explain:
    My Macbook Pro late 2013 (13inch, Model: A1502) developed a dent (see attachment) and an Apple Store (Genius Bar) technician told me that this is a result of "excessive pressure" on the bottom case. He also mentioned that because the case is made of soft aluminium and it is only supported around the border (about where the screws are located), any "excessive" pressure in the middle may result into the aluminum case being damaged by the internal components; in this case  the damage appears to have been caused by an internal bracket.
    There is no sign of the bottom case being pushed inwards, there hasn't been any accident and I haven't stepped, or sat on, or otherwise mistreated my laptop, so I very surprised! Most of the time, it's sitting flat on a desk and only carried insider a padded pouch, inside a laptop-grade (padded) backpack! As you'll notice in the photo (and I can provide more photos, if needed), there is absolutely no other sign of damage, the curves look perfect, and the back plate is flat.
    This is just a cosmetic damage and replacing the bottom case is the obvious solution but I still need to better understand the circumstances; I need to understand what went wrong and, if possible, how to prevent this from happening in the future .
    I visited iFix it web site and carefully looked at the internals of the laptop, here:
    https://www.ifixit.com/Teardown/MacBook+Pro+13-Inch+Retina+Display+Late+2013+Tea rdown/18695
    It looks like the bottom base is only supported around its border. The middle of the bottom case has no backing to support it. While Apple could have designed a support structure around the battery cells and over the motherboard (logic board) and the back case, there is no support structure at all. Hence, pressing on the back of the laptop uniformly (e.g. while in a loaded backpack) will probably result to the back case being pushed inwards and, while aluminium does have some degree of elasticity, it can get damaged when hitting on a sharp object, such as an internal bracket. Hence, I guess the Apple technician is right, this is what probably happened to my laptop and I think this may have happened only in my backpack. But, how “excessive” can the pressure be on a Macbook Pro inside a high-quality, padded backpack?
    If there are other MBPr users who have experienced this problem under normal everyday use, i.e. not due to an accident, could you please let me know?
    I'd be grateful if Apple:
    * Looked into this and provided a workaround, e.g. a more durable bottom case.
    * Considered replacing our damaged cases for free.
    * Published some numbers, to inform prospective customers about the durability of the laptop's case, e.g. in N/cm^2
    * Took our experience into consideration when designing their new laptops.
    Kind regards.

    " I need to understand what went wrong and, if possible, how to prevent this from happening in the future"
    So what's underneath the area w/ the "blister"?
    "It looks like the bottom base is only supported around its border. The middle of the bottom case has no backing to support it."
    That's pretty much been the case w/ every MBP I've ever had apart. Nothing past 2012 however.
    " While Apple could have designed a support structure around the battery cells and over the motherboard (logic board) and the back case, there is no support structure at all"
    In earlier versions of the MBP there is a "separator" between two areas of the upper case but it doesn't supply any support to the bottom case.
    So here's my take on this; Apple has made these MBPs thinner and thinner. In the MBPs I've taken apart 2008 - 2012. In the 2010 I have here the bottom case is very thick and judging by tapping on it is definitely tempered (or heat hardened or stress hardened). I don't have the proper caliper but the edge reads .044 Inch.
    There have been other issues on these communities that relate to the thinness of the top or the bottom cases in these newer machines.
    Never seen a newer machine but my feeling is judging by the issues seen around here is that the materials are much thinner and probably not as hardened or tempered.
    " how “excessive” can the pressure be on a Macbook Pro inside a high-quality, padded backpack?"
    To help prevent this from happening again and if this were my MBP I would use/make a hardened case just for the laptop. Say two sheets of 1/4" hardboard w/ a 1/4" separator of  high density foam. Wait I'm describing a high quality laptop case.
    As Ogelthorpe says, backpacks are not the most delicate way of transporting a laptop. I've seen damage worse than this to laptops, iPads, iPhones, Kindles etc. Especially at the school where I was the main tech. I would say: "What happened to this?" and the kid would say: "I dunno it was just in my backpack".
    I've watched backpacks fall from shelves, get stuck in lockers and get smashed into each other in the hallway.
    I'm sure you're much more delicate w/ your MBP but as the saying goes ".... happenes!"

  • Installing bootcamp on macbook pro late 2013 fails on 64% files expansion

    I am trying to install Windows 7 on macbook pro late 2013 but everytime, it gets stucked on 64% while expanding the files. I used the same disk on a non retina macbook, and all installed well. What can be the issue?

    The Boot Camp help manuals are located here: http://www.apple.com/support/bootcamp/
    The Boot Camp Discussion Community is located here: https://discussions.apple.com/community/windows_software/boot_camp

  • Macbook pro late 2013's Ram

    Can you upgrade a macbook pro late 2013's model Ram from 8 gb to 16 gb?

    Gnomish8 wrote:
    Yes. It looks like the maximum supported memory for the 15 inch retina is 16GB.
    You can find your systems tech specs here.
    The RAM is soldered into the Logic Board......So technically the RAM can NOT be upgraded on the rMBP.

  • How to clean install os x on macbook pro late 2013 using usb (offline) (without recovery direct download)

    hi,
         Im trying to clean install OS X from last month using inbuild recovery partition method. Due to slow internet connection Im unable to complete the installation. I tried many times using this intallation process but it failled to complete the installation. My internet connection is steady but due to "time out" the whole installation process is skiping. So Im not able to use my brand new macbook pro late 2013 from last month beginning. Please provide an alternative solution to install os x.

    For several years now, Apple has acted as if everyone on the planet has high speed Internet access. That is obviously not the case for many people, and for them installing or reinstalling any OS X version since Lion has been a problem.
    I can only suggest that you take your MacBook Pro to a location that has a faster, publicly accessible Internet connection and download it there. An Apple Store would be ideal, but if that is not an option, a public library may offer high speed Internet, as do many hotels, coffee shops, or similar locations where you may have to pay a small fee.
    When the download completes, you can copy the Install OS X Mavericks icon to another folder or an external storage device such as a flash drive, where it will remain available to use again, as often as you wish. Do that before proceeding with the Mavericks upgrade, otherwise the installer will erase the file.
    The installer icon resembles the following
    (Launchpad)
    The following will also appear in /Applications:
    Copy that to another location, such as Documents, by holding an option key while you drag it there.
    Of course, every time Apple releases an OS X update you will need to download another, rather large file.

  • Have iPhone 5s setup on windows 7 machine and in iCloud. now have 15" macbook pro late 2013

    I want to start using my macbook pro late 2013 loaded up laptop to start using my iphone 5s with. I have transferred all music and apps virtually everything is in the versionof itunes on laptop and has been authorized.
    now how do I use it as when i plug phone in it sees it as mass usb storage ie.... i can transfer pictures not much else.
    any help appreciated.
    thanks

    Hi chevysales!
    If you iPhone is not appearing in iTunes on your MacBook, you will want to see this article for troubleshooting steps:
    iOS: Device not recognized in iTunes for Mac OS X
    http://support.apple.com/kb/ts1591
    Once your iPhone is recognized in iTunes, you can use this article for information on how to sync:
    iOS: Syncing your data with iTunes
    http://support.apple.com/kb/ht1386
    Thanks for using the Apple Support Communities. Have a good one!
    -Braden

  • After installing the new Yosemite OS on my Macbook pro late 2013 touch trap has its own mind. Any others with this problem? What should we do?

    After installing the new Yosemite OS on my Macbook pro late 2013 touch trap has its own mind. Any others with this problem? What should we do?
    Even I tried to get back to Maverick but the touch pad doesn't work again. well, it works for a couple hours then start doing things but its own. it is so annoying.

    Hello josefromlaie,
    Thank you for using Apple Support Communities. 
    The following article provides some effective steps to troubleshoot trackpad issues:
    Intel-based Mac notebooks: Troubleshooting unresponsive trackpad issues
    Regards,
    Jeff D. 

Maybe you are looking for