Crash & Restart (Specs Included)

Please go to http://www.etresoft.com/etrecheck — download and run EtreCheck, copying the status report to paste here. It'll show us what is currently on your system, and if there's anything causing the crashes you're experiencing, we'll see it and hopefully be able to advise you on how to fix it.

Please post the panic report

Kernel Panic reports

<http://support.apple.com/kb/ht2546>

<https://support.apple.com/en-us/HT201753>

After that, in a separate reply, please post the EtreCheck output as requested by pinkstones

If you're getting kernel panics, the relevant information is in the panic reports. Nowhere else.

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Please launch the Console application in any one 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.

If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

You have the crapware "MacKeeper" - thorougly uninstall it. You should probably do a clean install of the system.

Always stay away from that scam crapware.

For the love of all that his holy, please, please, PLEASE remove MacKeeper. How your computer even functions with that fraudulent piece of garbage on it is a miracle. Make sure you uninstall it according to the developer's instructions. That's how you avoid bits and pieces of it left on your hard drive.

I am not confusing - MacKeeper's case is notorious.

Their developers have been convicted in a user class action.

It is an abusive, intrusive software scam that no sane user should install on their macs.

Here a few reports on the rather talked about class action:

http://appleinsider.com/articles/15/08/10/mackeeper-to-pay-out-2m-in-proposed-cl ***-action-settlement

http://www.macrumors.com/2015/08/10/mackeeper-refund-settlement/

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.

The test works on OS X 10.7 ("Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.

Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.

2. If you don't already have a current backup, please back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.

There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.

You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.

In this case, however, there are ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the requisite skill can verify what it does.

You may not be able to understand the script yourself. But variations of it have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.

Another indication that the test is safe can be found in this thread, and this one, for example, where the comment in which I suggested it was recommended by one of the Apple Community Specialists, as explained here.

Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.

4. Here's a general summary of what you need to do, if you choose to proceed:

☞ Copy a particular line of text to the Clipboard.

☞ Paste into the window of another application.

☞ Wait for the test to run. It usually takes a few minutes.

☞ Paste the results, which will have been copied automatically, back into a reply on this page.

These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.

5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is intermittently slow, run the test during a slowdown.

You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual before running it. If you can only test in safe mode, do that.

6. If you have more than one user, and only one user is affected by the problem,, and the affected user is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.

7. Load this linked web page (on the website "Pastebin.") Press the key combination command-A to select all the text, then copy it to the Clipboard by pressing command-C.

8. Launch the built-in Terminal application in any one 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.

Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.

9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter

exec bash

and press return. Then paste the script again.

10. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.

If the test is taking much longer than usual to run because the computer is very slow, you might be prompted for your password a second time. The authorization that you grant by entering it expires automatically after five minutes.

If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.

11. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:

Test started

Part 1 of 4 done at: … sec
…
Part 4 of 4 done at: … sec

The test results are on the Clipboard.

Please close this window.

The intervals between parts won't be exactly equal, but they give a rough indication of progress.

Wait for the final message "Please close this window" to appear. If you don't see it within about 15 minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it. Then go to the next step. You'll have incomplete results, but still something. If you close the Terminal window while the test is still running, the partial results won't be saved and you'll have to start over.

12. When the test is complete, or if you stopped it because it was taking too long, quit Terminal. The results will have been saved to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.

At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "close this window" message. Please wait for it and try again.

If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.

13. When you post the results, 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 software that runs this website. Please post the test results on Pastebin, then post a link here to the page you created.

If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you're told to do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.

______________________________________________________________

Copyright © 2014, 2015 by Linc Davis. As the sole author of this work (including the referenced "Diagnostic Test"), I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Luis Sequeira1 Don't for forget

<http://www.macrumors.com/2015/12/14/mackeeper-data-leak/>

Kosmic_Kayy your Mac does not need Anti-virus, Mac cleaners, nor memory cleaners. These products do not protect OS X, and they actively interfere with its normal operation.

Over and over again, there are reports in these forums where this class of products has causes kernel panics, system slowness, network connection issues, etc... The members of this forum that frequently contribute are not fans of any of these products.

With respect to your system crash, any one of the following are suspect, simply because they are OS X kernel extensions

Kernel Extensions: (What does this mean?)

/Library/Application Support/MacKeeper/AntiVirus.app

[not loaded] net.kromtech.kext.AVKauth (2.3.9 - SDK 10.10) [Click for support]

[not loaded] net.kromtech.kext.Firewall (2.3.9 - SDK 10.10) [Click for support]

/Library/Extensions

[not loaded] com.caiaq.driver.NIUSBAudio2DJDriver (2.8.0 - SDK 10.9) [Click for support]

[not loaded] com.caiaq.driver.NIUSBAudio4DJDriver (2.8.0 - SDK 10.9) [Click for support]

[not loaded] com.caiaq.driver.NIUSBHardwareDriver (2.8.0 - SDK 10.9) [Click for support]

[not loaded] com.caiaq.driver.NIUSBTraktorAudio2Driver (2.8.0 - SDK 10.9) [Click for support]

[not loaded] com.caiaq.driver.NIUSBTraktorKontrolS4Driver (2.8.0 - SDK 10.9) [Click for support]

[not loaded] com.caiaq.driver.NIUSBTraktorKontrolX1Driver (2.8.0 - SDK 10.9) [Click for support]

[not loaded] com.rane.driver.sl4.10.6 (1.0.3f1 - SDK 10.6) [Click for support]

/System/Library/Extensions

[not loaded] com.native-instruments.driver.NIUSBDeviceHelper (1.0.8) [Click for support]

[not loaded] com.steelseries.ssenext.driver (0.80 - SDK 10.8) [Click for support]

[not loaded] jp.co.pioneer.driver.DJM-2000Audio (1.1.0) [Click for support]

Remove any of these that you are no longer use via the vendor's uninstall instructions.

If you still using any of these for your work, then make sure you have a version that is compatible with El Capitan.

If you are still having system crashes, then consider booting into Safe mode (as an experiment)

<http://support.apple.com/kb/ht1564>

This will NOT load any 3rd party kernel extensions, launch daemons, nor launch agents. If your system still crashes, then it might not be software, but rather hardware.

Did you upgrade your RAM ? RAM upgrades have been known to cause problems.

Also try removing any and all external devices, assuming you have anything plugged into your Mac.

I am making guesses, because without a kernel panic report, it is just a guessing game. Actually it is a guessing game WITH a kernel panic report, but there are clues in the report that help narrow down the suspects.

Kosmic_Kayy wrote:

Hey guys,

I think you are conflicting Mac Defender with Mac Keeper. I have been using MacKeeper for a very long time and I have never encountered any issues until I upgraded to El Capitan. 😕

Please elaborate on why Mac Keeper is a problem, as what I understand that people confuse Mac Defender, which is the actual spam ware with Mac Keeper.

Regards,

No one is confusing anything. MacKeeper is garbage. It's worse than garbage, it's insidious, fraudulent malware for all intents and purposes. All you need to do is Google the class-action lawsuit that's been taken out against it for fraudulent businesses practices. Why would you want something like that on your computer? I really don't care how wonderful you think it is or how long you've used it. It's no different than CleanMyMac or any other "maintenance" program that exists — their main purpose is to separate consumers from their money. Macs don't need "cleaners," "optimizers," "refreshers," "organizers," or anything else of the like. They don't need anti-virus programs, firewalls, or anything else like that either. When you load your hard drive full of these extraneous third-party programs, you're just increasing the likelihood of something happening to your hard drive.

Given that you have a RANE audio product, this may provide some insight: RANE/Serato Hardware SL2 SL3 SL4 Core Audio Port Issue with El Capitan