Chances are you’ve never had any problems with your Mac and this guide to common Mac error messages won’t be of interest to you.
Just kidding. It’s much more likely that you’ve seen at least a few of these error messages when using your Mac; after all, we consider them somewhat common.
While the Mac operating system tries to make understanding error messages as easy as possible, sometimes the description leaves a bit to be desired. For this guide, we selected a number of common error messages and explained what they mean and how, when possible, to fix or avoid the condition that caused the error to occur.
So, in no particular order, let’s get started.
‘Your computer’s clock is set to a date before March 24th, 2001. This may cause some applications to behave erratically’
This error message can indicate that your Mac’s PRAM/NVRAM/CMOS battery has exhausted its charge and may need to be replaced. The battery in question was used primarily in previous generations of the Mac to keep the PRAM or NVRAM, as well as a few other important bits of silicon in the Mac, operating, even when the Mac was disconnected from a power source. This allowed your Mac to remember such things as the time and date, the time zone you’re in, and a number of basic settings, including volume and brightness.
For the most part, modern Macs have done away with the special battery and rely on a portable Mac’s main battery, as well as the use of solid-state non-volatile memory, to store this type of information. But that doesn’t mean you won’t ever see this error message. If you do, then the PRAM/NVRAM likely contains corrupt information and needs to be reset, and, depending on the Mac model, may need a PRAM/CMOS battery replacement.
‘Kernel Panic: You need to restart your Mac’
The dreaded kernel panic rears its ugly head by imposing a black or gray (depending on the version of the OS you’re using) rectangle over your Mac’s display, along with the words, “You need to restart your computer. Hold down the Power button for several seconds or press the Restart button.”
The best piece of advice we can give you if you find yourself in this situation is to resign yourself to your fate. Documents you had open at the time of the kernel panic likely won’t contain any of the more recent changes you made. At this point, there’s nothing you can do except restart your Mac.
So, what caused the kernel panic? It’s difficult to say. It’s possible to dig through the system logs and find out the last activity the processors were performing when the event occurred, but even this information may not shine a light on the real cause. Suffice it to say most kernel panics are one-off events that are not repeated on a regular basis. There’s a very good chance that the process of restarting your Mac, which will clear out memory and some caches, will be enough to keep the kernel panic from returning.
If it does return, you can try a few basic techniques to potentially resolve the issue so you can get back to work, including How to Use macOS Sierra Disk Utility to Verify or Repair Disks and Reset PRAM/NVRAM and SMC.
When your Mac starts back up, get back to work or play, and be thankful that you have current backups. You do maintain current backups, don’t you?
‘Your disk is almost full’
There are variations on this message, depending on the version of the OS you’re using. It may say, “Your startup disk is almost full.” No matter which message you see, you’ll be encouraged to make more space available by deleting files on the startup disk.
If you’re running a current version of the macOS, you may even have the option of using Managed storage to optimize storage space. Unless you’re already using this feature, we don’t advise jumping in headfirst right now, although it is a viable option after you determine just how much free space you have on the startup disk.
Start by dismissing the error message and then saving any open documents. Close all apps, and then restart your Mac. Once you’re back at the desktop, take a look at the amount of free space you have on the startup disk. You can do this by right-clicking the startup disk icon, either on the desktop or in a Finder sidebar, and selecting the Get Info menu item.
In the General area of the Get Info window, you’ll see the capacity of the startup disk, the free space (listed as Available), and the Used space. It’s a good idea not to let the free space fall below 10 to 15 percent of the disk capacity, but this is only a general guideline that needs to be evaluated for how you use your Mac. I prefer a larger amount of free storage space to ensure I always have enough room for new content, as well as the space the operating system needs for routine operations, including cache files, memory paging, print spooling files, app temporary space; the list goes on.
If you do need to delete some files to make room, make sure you have a current backup first, then take a look at these Rocket Yard Guides:
- What is Purgeable Space in macOS.
- Tech Tip: Seven Easy Ways to Free up Storage on Your Mac.
- Quick Tip: Skip ‘Taking Out the Trash’ When Deleting Files.
‘The application “Program Name” quit unexpectedly’
This can be a very common error message, depending on the applications you have installed. This is generally an application-specific issue, though it may involve related apps and utilities. An example would be Safari unexpectedly quitting because of a Safari plug-in or extension that was misbehaving.
The good news is this error usually doesn’t affect anything but the listed app, leaving the rest of your Mac and any open apps running normally. The bad news is you likely lost any unsaved data in any open documents related to the app that quit.
A common cause for this error is apps that are out of date and need to be updated. Check with the app developer to see if a more current version is available. This is especially true when a new version of the Mac operating system is released.
Another possible cause, though less likely, is limited resources available to the app; this can be in the form of storage space or available RAM. If you have a small amount of RAM installed, try closing some apps to free up space. If your Mac supports additional RAM, you may wish to consider beefing up the amount of RAM installed.
There are other problems that can cause an app to quit. You can find some tips in the “How to Fix Scary Issues That ‘Possess’ a Mac” article.
‘The application “Program Name” is not open anymore’
This is a strange one that can be quite befuddling. This error message occurs when you attempt to interact with an app that appears to be open; it may even have an open window or two on the desktop, and be listed on the Dock as open. But when you try to work with the app, the above message is displayed.
What has usually happened is the app in question has become busy with a task or is just unresponsive. At some point, the operating system will conclude the app has closed or crashed, even though there are still orphaned windows being shown.
To be able to work with the app again, you’ll need to force quit the app, and then re-launch it. If you haven’t force quit an app before, you’ll find the option under the Apple menu. Simply select the Force Quit option, and then select the affected app from the list of apps.
If the app in question doesn’t appear in the list, you can use Activity Monitor to kill an open window, running service, or app. If all else fails, you can save any work in progress, and then restart your Mac.
‘Safari web content quit unexpectedly’
This error is becoming more common, and we can be glad it is. Well, not completely glad, but it is an improvement over older versions of Safari that would just crash. Newer versions of Safari use a sandboxing technique to isolate each Safari window, and the associated webpage, from each other. In this way, when a website or add-on causes a problem, only that website window or tab is affected; the rest of Safari, and any other open windows or tabs, continue on unaffected. As for the offending site, Safari presents the error message above, and then reloads the affected web page, leaving you just about where you were before the error happened.
The issue is that if it continues to occur, you need to find out what the cause is. There are two likely candidates for this: a poorly constructed website that is consuming resources until Safari says no more, or a Safari extension, plug-in, or other third-party add-on that’s acting up.
If the problem only occurs repeatedly on a single website, it’s a good indication the site or some part of the site, usually an ad being displayed, is the cause, though it could still be an add-on that is being used with the site.
You can find out more about working with Safari extensions in the guide: How to Install, Manage, Delete Safari Extensions on a Mac. Use this guide to disable or uninstall add-ons a few at a time until you discover which one is causing the problem. You can then check with the developer for updates, or if it’s no longer supported, remove the offending add-on.
Numeric Error Codes
Have you ever noticed an error message that just gives an error code number, such as Error -36? Not very revealing is it. For the most part, the Mac operating system tries to shield you from these mostly meaningless error codes, but sometime they will squeak through, usually from poorly written apps, or even some of Apple’s own apps, though mostly older versions of them.
You can try using your favorite search engine to find out what it means. Be sure to enter the error code exactly as it appears in the error message. If you’re not able to find a match in the search results, or the search results aren’t very conclusive, with multiple answers given for the same error code, you can try using the Terminal app to decipher the error code.
We suggest the Terminal app as a last-ditch effort because the “macerror” app isn’t seeing active updates any longer, and the data it contains is somewhat out of date. But if you haven’t found the meaning of an error code any other way, it can’t hurt to give it a shot.
Launch Terminal, and then enter the following at the prompt:
where error code is the number given in the error message. As an example, to look up error -36 you would enter:
and then press enter or return to see a text description of the error’s meaning. In this case, it’s:
(ioErr): I/O error (bummers)
While not much better than the error code number, you can use the text for a more insightful Internet search to help decode the error message.
More Error Messages
What’s the most common error message you routinely encounter? Let us know in the comments below.
Leave a Reply