Hello,
My MacBook Air 13" mid-2013 is having a hard lock issue. It seems to be happening on a daily basis. What happens is when the display dims from inactivity, but it isn't quite in sleep mode, and someone rubs the trackpad or presses a key to brighten the display back up, the display just goes completely black then, but the keyboard backlight remains lit. The MacBook Air becomes completely unresponsive. There is no way to wake it, and it doesn't recover. The caps lock key light also does not eliminate when the button is pressed, this makes me think the logic board just goes completely offline. Holding the power button to force it off, then turing it back on fixes it, and everything runs fine for a day, then the issue happens again. I've tried a SMC reset, and verified the disk with disk utility. I have just done a PRAM reset and will see if that fixes it, but I'm doubtful. I've checked the logs as well, and no logs say theres an issue, and there are no kernel panic logs.
I've seen others with the same issue, but no real resolution, and what I read was a few months old. Has anyone else more recently had this issue?
My MacBook Air 13" mid-2013 is having a hard lock issue. It seems to be happening on a daily basis. What happens is when the display dims from inactivity, but it isn't quite in sleep mode, and someone rubs the trackpad or presses a key to brighten the display back up, the display just goes completely black then, but the keyboard backlight remains lit. The MacBook Air becomes completely unresponsive. There is no way to wake it, and it doesn't recover. The caps lock key light also does not eliminate when the button is pressed, this makes me think the logic board just goes completely offline. Holding the power button to force it off, then turing it back on fixes it, and everything runs fine for a day, then the issue happens again. I've tried a SMC reset, and verified the disk with disk utility. I have just done a PRAM reset and will see if that fixes it, but I'm doubtful. I've checked the logs as well, and no logs say theres an issue, and there are no kernel panic logs.
I've seen others with the same issue, but no real resolution, and what I read was a few months old. Has anyone else more recently had this issue?