jocago

Q: OS X crashes repeatedly

For three days, OS X has repeatedly crashed after about 15 minutes of uptime. I cannot detect a pattern as far as applications used before or while the crash happens. I have removed the two application I installed on the first day. Neither should run in the background and that has not fixed the problem. I also updated the command line tools the day before this started happening.

 

When the crash happens, I can be working in any application. The screen will go grey (as it does when booting) and, after about 30 seconds, the computer will turn off. When I restart, the applications can generally be restored.

 

I'm a fairly new convert to Mac and so I'm still trying to discover troubleshooting techniques. I am ignorant of in-depth system analysis so any help in that regard is appreciated.

 

Hardware Overview:

  Model Name: MacBook Pro

  Model Identifier: MacBookPro11,3

  Processor Name: Intel Core i7

  Processor Speed: 2.6 GHz

  Number of Processors: 1

  Total Number of Cores: 4

  L2 Cache (per Core): 256 KB

  L3 Cache: 6 MB

  Memory: 16 GB

System Software Overview:

  System Version:    OS X 10.11.4 (15E65)

  Kernel Version:    Darwin 15.4.0

  Boot Volume:    Macintosh HD

  Boot Mode:    Normal

  Secure Virtual Memory:    Enabled

  System Integrity Protection:    Enabled

  Time since boot:    2 minutes

 

I did discover Etre wich may be of some use if anyone is interested.

 

Thanks for the help.

MacBook Pro (Retina, 15-inch, Late 2013), OS X El Capitan (10.11.4)

Posted on May 8, 2016 10:45 PM

Close

Q: OS X crashes repeatedly

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis May 9, 2016 7:52 AM in response to jocago
    Level 10 (207,963 points)
    Applications
    May 9, 2016 7:52 AM in response to jocago

    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.

    Step 1

    For this step, the title of the Console window should be All Messages. If it isn't, select

              SYSTEM LOG QUERIES All Messages

    from the log list on the left. If you don't see that list, select

              View Show Log List

    from the menu bar at the top of the screen.

    In the top right corner of the Console window, there's a search box labeled Filter. Enter "BOOT_TIME" (without the quotes.)

    Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

    For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.

    If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

    When posting a log extract, be selective. A few dozen lines are almost always more than enough.

    Some private information, such as your name, may appear in the log. Anonymize before posting.

    Please don't indiscriminately dump thousands of lines from the log into this discussion.

    Please don't post screenshots of log messages—post the text.

    Step 2

    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 crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.

    I know the report is long, maybe several hundred lines. Please post all of it anyway.

    If you don't see any reports listed, but you know there was a crash or 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—they're very long and rarely helpful.

    When you post the log extract or the crash 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.

  • by jocago,

    jocago jocago May 9, 2016 1:20 PM in response to Linc Davis
    Level 1 (8 points)
    Mac OS X
    May 9, 2016 1:20 PM in response to Linc Davis

    Thank you Linc. I tried these steps several times to see if there is a pattern I could detect. I don't think there is, other than a python crash file every time the computer shuts down. I'm not sure if this is a cause so much as an byproduct, but I'm looking into it.

     

    Here is the last crash report: http://pastebin.com/aWiPQCHP

     

    And here are the prior lines of the log file before the reboot.

     

    -----------------

    All Messages

    -----------------

     

     

    5/9/16 3:39:33.568 PM WD App Manager[548]: Vendor = '' TXTVersion =

    5/9/16 3:39:33.568 PM WD App Manager[548]: Officejet Pro 8600 [B54919] was not added to nasDevices because it is not a WDC device.

    5/9/16 3:39:33.568 PM WD App Manager[548]: Resolve count = 1

    5/9/16 3:39:33.568 PM WD App Manager[548]: in netServiceDidStop - NetService Record = <NSNetService 0x7f8810e01f50> local. _http._tcp. Officejet Pro 8600 [B54919]

    5/9/16 3:39:34.794 PM WD App Manager[548]: in netServiceWillResolve - NetService Record = <NSNetService 0x7f8812a7b870> local. _http._tcp. HP Officejet Pro 8610 [4AF5B7]

    5/9/16 3:39:34.821 PM WD App Manager[548]: TXT Data          = {

    } Length = 0

    5/9/16 3:39:34.821 PM WD App Manager[548]: Vendor = '' TXTVersion =

    5/9/16 3:39:34.821 PM WD App Manager[548]: HP Officejet Pro 8610 [4AF5B7] was not added to nasDevices because it is not a WDC device.

    5/9/16 3:39:34.821 PM WD App Manager[548]: Resolve count = 1

    5/9/16 3:39:34.822 PM WD App Manager[548]: in netServiceDidStop - NetService Record = <NSNetService 0x7f8812a7b870> local. _http._tcp. HP Officejet Pro 8610 [4AF5B7]

    5/9/16 3:39:36.201 PM WindowServer[221]: _CGXRemoveWindowFromWindowMovementGroup: window 0x33 is not attached to window 0x86

    5/9/16 3:39:39.450 PM WindowServer[221]: _CGXRemoveWindowFromWindowMovementGroup: window 0x33 is not attached to window 0x86

    5/9/16 3:39:49.924 PM iconservicesagent[461]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7fc4027058f0>.

    5/9/16 3:39:49.924 PM quicklookd[687]: Error returned from iconservicesagent: (null)

    5/9/16 3:39:49.926 PM iconservicesagent[461]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7fc403903850>.

    5/9/16 3:39:49.926 PM quicklookd[687]: Error returned from iconservicesagent: (null)

    5/9/16 3:39:51.902 PM WindowServer[221]: _CGXRemoveWindowFromWindowMovementGroup: window 0x33 is not attached to window 0x86

    5/9/16 3:39:58.587 PM WindowServer[221]: _CGXRemoveWindowFromWindowMovementGroup: window 0x33 is not attached to window 0x86

    5/9/16 3:40:04.770 PM WindowServer[221]: _CGXRemoveWindowFromWindowMovementGroup: window 0x33 is not attached to window 0x86

    5/9/16 3:40:04.880 PM com.apple.WebKit.WebContent[851]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 8 bytes @ 23877 took 2.670343 secs. to complete, 1 reads >= 1 sec.

    5/9/16 3:40:04.963 PM com.apple.WebKit.WebContent[851]: [15:40:04.963] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/LegibleOutput/FigAgglomerator.c line 92

    5/9/16 3:40:04.966 PM com.apple.WebKit.WebContent[851]: [15:40:04.966] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fc392969800) rejecting report of layer being serviced - IQ has not yet begun to update

    5/9/16 3:40:06.034 PM com.apple.WebKit.Plugin.64[855]: Failed to connect (colorGridView) outlet from (NSApplication) to (NSColorPickerGridView): missing setter or instance variable

    5/9/16 3:40:06.034 PM com.apple.WebKit.Plugin.64[855]: Failed to connect (view) outlet from (NSApplication) to (NSColorPickerGridView): missing setter or instance variable

    5/9/16 3:40:08.150 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec 1.(null). Failed codec specific check.

    5/9/16 3:40:08.150 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec 1

    5/9/16 3:40:08.150 PM com.apple.WebKit.WebContent[851]: [15:40:08.150] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec 1) at  line 1921

    5/9/16 3:40:08.150 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec 1

    5/9/16 3:40:08.150 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec 1.(null). Failed codec specific check.

    5/9/16 3:40:08.150 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec 1

    5/9/16 3:40:08.150 PM com.apple.WebKit.WebContent[851]: [15:40:08.150] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec 1) at  line 1921

    5/9/16 3:40:08.150 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec 1

    5/9/16 3:40:10.278 PM com.apple.WebKit.WebContent[851]: [15:40:10.278] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fc392969800) rejecting report of layer being serviced - IQ has not yet begun to update

    5/9/16 3:40:10.377 PM sandboxd[160]: ([855]) com.apple.WebKit(855) deny system-fsctl 0x682f

    5/9/16 3:40:10.606 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec 1.(null). Failed codec specific check.

    5/9/16 3:40:10.606 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec 1

    5/9/16 3:40:10.606 PM com.apple.WebKit.WebContent[851]: [15:40:10.606] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec 1) at  line 1921

    5/9/16 3:40:10.606 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec 1

    5/9/16 3:40:10.606 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec 1.(null). Failed codec specific check.

    5/9/16 3:40:10.606 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec 1

    5/9/16 3:40:10.606 PM com.apple.WebKit.WebContent[851]: [15:40:10.606] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec 1) at  line 1921

    5/9/16 3:40:10.606 PM com.apple.WebKit.WebContent[851]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec 1

    5/9/16 3:40:10.760 PM Safari[425]: KeychainGetICDPStatus: keychain: -25300

    5/9/16 3:40:10.760 PM Safari[425]: KeychainGetICDPStatus: status: off

    5/9/16 3:40:15.152 PM sandboxd[160]: ([855]) com.apple.WebKit(855) deny ipc-posix-sem SandboxingDetectionTest

    5/9/16 3:41:56.000 PM bootlog[0]: BOOT_TIME 1462822916 0

  • by Linc Davis,

    Linc Davis Linc Davis May 9, 2016 1:24 PM in response to jocago
    Level 10 (207,963 points)
    Applications
    May 9, 2016 1:24 PM in response to jocago

    The problem may be caused by a bug in OS X, triggered by "Flash Player."

    If Flash is installed and you haven't already done so, please update to the latest version by opening the Flash Player pane in System Preferences and selecting the Updates tab.

    If Flash is already up to date, or if the update doesn't solve the problem, open the Safari preferences window and select the Security tab. Uncheck the box marked

              Allow Plug-ins

    See whether there's an improvement.

    You can watch videos on YouTube and some other sites without using Flash by installing the "ClickToFlash" or "ClickToPlugin" Safari extension. That's not an endorsement. You must always do your own research to determine the safety and effectiveness of any third-party software before using it.

  • by jocago,

    jocago jocago May 9, 2016 2:47 PM in response to Linc Davis
    Level 1 (8 points)
    Mac OS X
    May 9, 2016 2:47 PM in response to Linc Davis

    Thank you.

     

    I check flash and it says it's up to date. I then rebooted to normal mode, disabled plug-ins in Safari, rebooted to normal mode again, and let it run without loading anything. It took a while, but it crashed again.

     

    I took another look at the log. I do frequently see the WD app on  the list, but usually not right ahead of the crash. I also updated that app today as part of my troubleshooting.

     

    5/9/16 5:28:53.319 PM WD App Manager[441]: Officejet Pro 8600 [949846] was not added to nasDevices because it is not a WDC device.

    5/9/16 5:28:53.319 PM WD App Manager[441]: Resolve count = 1

    5/9/16 5:28:53.319 PM WD App Manager[441]: in netServiceDidStop - NetService Record = <NSNetService 0x7fe6e8712e50> local. _http._tcp. Officejet Pro 8600 [949846]

    5/9/16 5:28:53.320 PM WD App Manager[441]: TXT Data          = {

    } Length = 0

    5/9/16 5:28:53.320 PM WD App Manager[441]: Vendor = '' TXTVersion =

    5/9/16 5:28:53.320 PM WD App Manager[441]: HP Officejet Pro 8610 [4A59F5] was not added to nasDevices because it is not a WDC device.

    5/9/16 5:28:53.320 PM WD App Manager[441]: Resolve count = 0

    5/9/16 5:28:53.320 PM WD App Manager[441]:

    ------  0 WDC NAS devices found ------

    (

    )

    5/9/16 5:28:53.320 PM WD App Manager[441]: in netServiceDidStop - NetService Record = <NSNetService 0x7fe6e870da90> local. _http._tcp. HP Officejet Pro 8610 [4A59F5]

    5/9/16 5:28:56.369 PM WD App Manager[441]: in netServiceWillResolve - NetService Record = <NSNetService 0x7fe6eab27a00> local. _http._tcp. Officejet Pro 8600 [B5493F]

    5/9/16 5:28:56.369 PM WD App Manager[441]: in netServiceWillResolve - NetService Record = <NSNetService 0x7fe6eab402f0> local. _http._tcp. Officejet Pro 8600 [B54938]

    5/9/16 5:28:56.397 PM WD App Manager[441]: TXT Data          = {

    } Length = 0

    5/9/16 5:28:56.397 PM WD App Manager[441]: Vendor = '' TXTVersion =

    5/9/16 5:28:56.397 PM WD App Manager[441]: Officejet Pro 8600 [B5493F] was not added to nasDevices because it is not a WDC device.

    5/9/16 5:28:56.397 PM WD App Manager[441]: Resolve count = 1

    5/9/16 5:28:56.398 PM WD App Manager[441]: in netServiceDidStop - NetService Record = <NSNetService 0x7fe6eab27a00> local. _http._tcp. Officejet Pro 8600 [B5493F]

    5/9/16 5:28:56.398 PM WD App Manager[441]: TXT Data          = {

    } Length = 0

    5/9/16 5:28:56.398 PM WD App Manager[441]: Vendor = '' TXTVersion =

    5/9/16 5:28:56.398 PM WD App Manager[441]: Officejet Pro 8600 [B54938] was not added to nasDevices because it is not a WDC device.

    5/9/16 5:28:56.398 PM WD App Manager[441]: Resolve count = 0

    5/9/16 5:28:56.398 PM WD App Manager[441]:

    ------  0 WDC NAS devices found ------

    (

    )

    5/9/16 5:28:56.398 PM WD App Manager[441]: in netServiceDidStop - NetService Record = <NSNetService 0x7fe6eab402f0> local. _http._tcp. Officejet Pro 8600 [B54938]

    5/9/16 5:28:59.552 PM Dock[404]: -[UABestAppSuggestionManager notifyBestAppChanged:type:options:bundleIdentifier:activityType:dynamicIdentifi er:when:confidence:deviceName:deviceIdentifier:deviceType:] [redacted] UserActivity com.apple.Safari/NSUserActivityTypeBrowsingWeb opts={

    } when=2016-05-09 21:28:59 +0000 confidence=1 from=[redacted] (UABestAppSuggestionManager.m #319)

    5/9/16 5:29:13.377 PM Dock[404]: -[UABestAppSuggestionManager notifyBestAppChanged:type:options:bundleIdentifier:activityType:dynamicIdentifi er:when:confidence:deviceName:deviceIdentifier:deviceType:] [redacted] UserActivity com.apple.Safari/NSUserActivityTypeBrowsingWeb opts={

    } when=2016-05-09 21:29:13 +0000 confidence=1 from=[redacted] (UABestAppSuggestionManager.m #319)

    5/9/16 5:29:21.159 PM Dock[404]: -[UABestAppSuggestionManager notifyBestAppChanged:type:options:bundleIdentifier:activityType:dynamicIdentifi er:when:confidence:deviceName:deviceIdentifier:deviceType:] [redacted] UserActivity com.apple.Safari/NSUserActivityTypeBrowsingWeb opts={

    } when=2016-05-09 21:29:21 +0000 confidence=1 from=[redacted] (UABestAppSuggestionManager.m #319)

    5/9/16 5:29:24.778 PM Dock[404]: -[UABestAppSuggestionManager notifyBestAppChanged:type:options:bundleIdentifier:activityType:dynamicIdentifi er:when:confidence:deviceName:deviceIdentifier:deviceType:] [redacted] UserActivity com.apple.Safari/NSUserActivityTypeBrowsingWeb opts={

    } when=2016-05-09 21:29:24 +0000 confidence=1 from=[redacted] (UABestAppSuggestionManager.m #319)

    5/9/16 5:29:32.280 PM Dock[404]: -[UABestAppSuggestionManager notifyBestAppChanged:type:options:bundleIdentifier:activityType:dynamicIdentifi er:when:confidence:deviceName:deviceIdentifier:deviceType:] [redacted] UserActivity com.apple.Safari/NSUserActivityTypeBrowsingWeb opts={

    } when=2016-05-09 21:29:32 +0000 confidence=1 from=[redacted] (UABestAppSuggestionManager.m #319)

    5/9/16 5:29:32.000 PM syslogd[53]: ASL Sender Statistics

    5/9/16 5:30:43.000 PM bootlog[0]: BOOT_TIME 1462829443 0

  • by Linc Davis,

    Linc Davis Linc Davis May 9, 2016 3:02 PM in response to jocago
    Level 10 (207,963 points)
    Applications
    May 9, 2016 3:02 PM in response to jocago

    Please remove the Western Digital software (which you don't really need) and test.

    Any third-party software that doesn't install from the App Store or by drag-and-drop into the Applications folder, and uninstall by drag-and-drop to the Trash, is a system modification.

    Whenever you remove system modifications, they must be removed completely, and the only way to do that is to use the uninstallation tool, if any, provided by the developers, or to follow their instructions. If the software has been incompletely removed, you may have to re-download or even reinstall it in order to finish the job.

    I never install system modifications myself, and except as stated in this comment, I don't know how to uninstall them. You'll have to do your own research to find that information.

    Here are some general guidelines to get you started. Suppose you want to remove something called “BrickMyMac” (a hypothetical example.) First, consult the product's Help menu, if there is one, for instructions. Finding none there, look on the developer's website, say www.brickmymac.com. (That may not be the actual name of the site; if necessary, search the Web for the product name.) If you don’t find anything on the website or in your search, contact the developer. While you're waiting for a response, download BrickMyMac.dmg and open it. There may be an application in there such as “Uninstall BrickMyMac.” If not, open “BrickMyMac.pkg” and look for an Uninstall button. The uninstaller might also be accessed by clicking the Customize button, if there is one.

    Back up all data before making any changes.

    You will generally have to restart the computer in order to complete an uninstallation. Until you do that, there may be no effect, or unpredictable effects.

    If you can’t remove software in any other way, you’ll have to erase and install OS X. Never install any third-party software unless you're sure you know how to uninstall it; otherwise you may create problems that are very hard to solve.

    Trying to remove complex system modifications by hunting for files by name often will not work and may make the problem worse. The same goes for "utilities" such as "AppCleaner" and the like that purport to remove software.

  • by jocago,

    jocago jocago May 9, 2016 4:45 PM in response to Linc Davis
    Level 1 (8 points)
    Mac OS X
    May 9, 2016 4:45 PM in response to Linc Davis

    I was really hopeful on that one as I've had WD app problems before. I removed all WD components (which are for my personal cloud backup, so I'll have to replace that) and restarted. I got about 30 minutes in before it crashed which is twice as long as I've had for four days.

     

    --------All Messages--------

     

    5/9/16 7:34:11.911 PM Safari[2838]: KeychainGetICDPStatus: status: off

    5/9/16 7:34:13.821 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec 1.(null). Failed codec specific check.

    5/9/16 7:34:13.821 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec 1

    5/9/16 7:34:13.824 PM com.apple.WebKit.WebContent[2963]: [19:34:13.824] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec 1) at  line 1921

    5/9/16 7:34:13.912 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec 1

    5/9/16 7:34:13.913 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec 1.(null). Failed codec specific check.

    5/9/16 7:34:13.913 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec 1

    5/9/16 7:34:13.913 PM com.apple.WebKit.WebContent[2963]: [19:34:13.913] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec 1) at  line 1921

    5/9/16 7:34:13.913 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec 1

    5/9/16 7:34:20.643 PM Safari[2838]: KeychainGetICDPStatus: keychain: -25300

    5/9/16 7:34:20.643 PM Safari[2838]: KeychainGetICDPStatus: status: off

    5/9/16 7:34:21.454 PM com.apple.WebKit.WebContent[2963]: [19:34:21.454] mv_ValidateRFC4281_avc1 signalled err=-12955 (kFigMediaValidatorError_VideoProfileNotSupported) (Unsupported avc1 profile 88 and/or level 30) at  line 3779

    5/9/16 7:34:21.454 PM com.apple.WebKit.WebContent[2963]: [19:34:21.454] mv_ValidateRFC4281_avc1 signalled err=-12955 (kFigMediaValidatorError_VideoProfileNotSupported) (Unsupported avc1 profile 88 and/or level 30) at  line 3779

    5/9/16 7:34:21.454 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec samr.(null). Failed codec specific check.

    5/9/16 7:34:21.454 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec samr

    5/9/16 7:34:21.454 PM com.apple.WebKit.WebContent[2963]: [19:34:21.454] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec samr not found (lookup)) at  line 1921

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec samr.(null). Failed codec specific check.

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec samr

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: [19:34:21.457] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec samr not found (lookup)) at  line 1921

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec mp3.(null). Failed codec specific check.

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec mp3

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: [19:34:21.457] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec mp3) at  line 1921

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec mp3

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec mp3.(null). Failed codec specific check.

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec mp3

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: [19:34:21.457] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec mp3) at  line 1921

    5/9/16 7:34:21.457 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec mp3

    5/9/16 7:34:22.168 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec 1.(null). Failed codec specific check.

    5/9/16 7:34:22.168 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec 1

    5/9/16 7:34:22.168 PM com.apple.WebKit.WebContent[2963]: [19:34:22.168] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec 1) at  line 1921

    5/9/16 7:34:22.168 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec 1

    5/9/16 7:34:22.168 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_ValidateRFC4281CodecId: Unrecognized codec 1.(null). Failed codec specific check.

    5/9/16 7:34:22.168 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_LookupCodecSupport: Unrecognized codec 1

    5/9/16 7:34:22.168 PM com.apple.WebKit.WebContent[2963]: [19:34:22.168] mv_LowLevelCheckIfVideoPlayableUsingDecoder signalled err=-12956 (kFigMediaValidatorError_VideoCodecNotSupported) (video codec 1) at  line 1921

    5/9/16 7:34:22.168 PM com.apple.WebKit.WebContent[2963]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec 1

    5/9/16 7:34:26.609 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:34:32.914 PM Safari[2838]: KeychainGetICDPStatus: keychain: -25300

    5/9/16 7:34:32.914 PM Safari[2838]: KeychainGetICDPStatus: status: off

    5/9/16 7:34:34.993 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:34:35.727 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:34:38.277 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:34:43.944 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:34:47.261 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:34:52.828 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:34:53.962 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:35:02.779 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:35:06.163 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:35:09.706 PM Safari[2838]: KeychainGetICDPStatus: keychain: -25300

    5/9/16 7:35:09.706 PM Safari[2838]: KeychainGetICDPStatus: status: off

    5/9/16 7:35:14.948 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:35:15.915 PM WindowServer[235]: _CGXRemoveWindowFromWindowMovementGroup: window 0xd0 is not attached to window 0xd1

    5/9/16 7:37:41.000 PM bootlog[0]: BOOT_TIME 1462837061 0

  • by Linc Davis,

    Linc Davis Linc Davis May 9, 2016 5:07 PM in response to jocago
    Level 10 (207,963 points)
    Applications
    May 9, 2016 5:07 PM in response to jocago

    Please read this whole message before doing anything.

    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.

    Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

    Test while in safe mode. Same problem?

    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • by ~Bee,

    ~Bee ~Bee May 9, 2016 6:43 PM in response to jocago
    Level 7 (31,787 points)
    Mac OS X
    May 9, 2016 6:43 PM in response to jocago

    Hi there, jocago --

     

    Yes, please do download the EtreCheck app that you've already found.  Then copy and Paste the results here.

    IMHO, it's much more to the  point, and helpful,

     

    Thanks very much!

  • by jocago,

    jocago jocago May 10, 2016 7:02 AM in response to Linc Davis
    Level 1 (8 points)
    Mac OS X
    May 10, 2016 7:02 AM in response to Linc Davis

    Working in safe mode does not cause the shutdown issue. Every once and a while, it does lock up, but I've noticed that is immediately after restoring a session. I'm not sure if that's related, but it's a different behavior so I'm looking at it individually right now.

     

    I've been working in safe mode in order to get work done as working in normal mode invariably ends suddenly.

  • by jocago,

    jocago jocago May 10, 2016 7:10 AM in response to ~Bee
    Level 1 (8 points)
    Mac OS X
    May 10, 2016 7:10 AM in response to ~Bee

    Thanks, ~Bee. I've been taking snapshots as I've made changes. Here is the most recent.

     

    http://pastebin.com/4A9WeXj9

  • by Linc Davis,

    Linc Davis Linc Davis May 10, 2016 7:18 AM in response to jocago
    Level 10 (207,963 points)
    Applications
    May 10, 2016 7:18 AM in response to jocago

    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.8 ("Mountain 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 procedure is easy to do right, but it's also easy to do wrong, so I've made the instructions very detailed. 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 who understands the code 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 many times over a period of years. 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.

    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 the text of a particular web page (not this one) 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 ("Terminal") 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'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.

    10. 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—again, usually within a few minutes. If you don't see that message within about 30 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.

    In order to get results, the test must either be allowed to complete or else manually stopped as above. If you close the Terminal window while the test is still running, the partial results won't be saved.

    11. When the test is complete, or if you stopped it manually, 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.

    12. 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.

    13. When you're done with the test, it's gone. There is nothing to uninstall or clean up.

    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 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.

    15. The linked UNIX shell script bears a notice of copyright. Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

  • by jocago,

    jocago jocago May 10, 2016 1:13 PM in response to Linc Davis
    Level 1 (8 points)
    Mac OS X
    May 10, 2016 1:13 PM in response to Linc Davis

    Thanks Linc. The system crashed several times during the test, but I was able to run it once through.

     

    http://pastebin.com/Tj1QnaHp

  • by Linc Davis,Solvedanswer

    Linc Davis Linc Davis May 10, 2016 2:58 PM in response to jocago
    Level 10 (207,963 points)
    Applications
    May 10, 2016 2:58 PM in response to jocago

    Although there are several configuration issues, I don't think any of them is contributing to the problem you asked about.

    There have been several abnormal shutdowns in the last few days. A negative shutdown code may indicate a hardware problem. The precise meaning of the codes is not publicly documented.

    If you haven't already done so, you can try resetting the System Management Controller. You can also try disconnecting the trackball. Otherwise, or if those steps have no effect, see below.

    Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. You may have to leave the machine there for several days.

    Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional—ask if you need guidance.

    If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.

    Keep your confidential data secure during hardware repair.

    Apple recommends that you deauthorize a device in the iTunes Store before having it serviced.

    *An SSD doesn't need to be zeroed.

  • by jocago,

    jocago jocago May 12, 2016 7:36 AM in response to Linc Davis
    Level 1 (8 points)
    Mac OS X
    May 12, 2016 7:36 AM in response to Linc Davis

    Thank you. I contacted Apple support yesterday and they walked me through several forms of resetting the system. That did not work and so we reinstalled the OS. That, too, did not work, so now I've been asked to bring it in.

     

    Thanks for the great help.