-
All replies
-
Helpful answers
-
Aug 26, 2015 11:34 PM in response to not so brightby D.Cohen,Hi! Below you will find basic troubleshooting steps:
- Shut down your Mac
- Wait until your computer turns off and after that press the Power button
- Right after you hear the startup tone, press and hold the Shift key
- Release the Shift key when you see a grey Apple sign and the progress bar below this sign
- After your Mac boots up, restart it as you usually do.
If this doesn't help, follow the instructions below:
- Shut down your Mac
- Wait until your computer turns off and after that press the Power button
- Right after you hear the startup tone, press and hold the Shift key
- Release the Shift key when you see a grey Apple sign and the progress bar below this sign
- Once you see Desktop, start a Disk Utility scan to detect and repair file system errors (don't forget to choose your main hard drive)
- Click on Verify Disk and then, if asked to fix problems, on Repair Disk
- After this, click on Verify Disk Permissions and then on Repair Disk Permissions
- After the process is finished, shut down your Mac and turn it back on after about 30 seconds
Apart from that, take a look at this Apple article and follow the instructions on Resetting NVRAM shown there: How to Reset NVRAM on your Mac - Apple Support
Try resetting the System Management Controller: https://support.apple.com/en-us/HT201295
Hope this helps!
-
Aug 26, 2015 11:54 PM in response to D.Cohenby not so bright,Thanks D Cohen for your quick and detailed reply.
I will try your tips on disk Utility regardless - though as my computer shut down yesterday it re-started on its own. Not sure if this is a good sign or of no consequence - but just letting you know.
-
Aug 26, 2015 11:58 PM in response to not so brightby D.Cohen,You are welcome!
BTW, your Mac is still under warranty, so you can ask Apple for help.
-
Aug 27, 2015 12:01 AM in response to D.Cohenby not so bright,
I called Apple and they basically send me one of their 'things-to-do'. -
Aug 27, 2015 12:13 AM in response to not so brightby Paul_31,It's possible that you have some incompatible software installed that is causing problems. You could download and run the free EtreCheck and post the content of its report here. Someone here may spot something and offer some suggestions to try and resolve the problem:
-
Aug 27, 2015 3:51 AM in response to not so brightby Mike Sombrio,Mac OS X: How to log a kernel panic - Apple Support
Copy and paste the panic report here. EtreCheck is good too but the panic report can show exactly when the panic begins.
-
Aug 27, 2015 9:09 AM in response to not so brightby Linc Davis,These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console 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 and start typing the name.
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
When you post the report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.
-
Aug 31, 2015 11:18 PM in response to Linc Davisby not so bright,Thanks Linc for your advice. I could not paste the contents on this forum, as you rightly pointed out, as it comes with 'invalid characters' message. I followed your suggestion through doing it on Pastebin - and here is the link. Though being not smart with these things - I hope it gives you the info to look at. Let me know if this is of any help please.