OSX Yosemite 10.10.1 Frequent computer crashes

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. Click Utilities, then Console in the icon grid.

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

You have the MacBookPro6,2—the Edsel of Macs. It may have the logic-board defect that was covered by this recall.

Make a "Genius" appointment at an Apple Store, or go to another authorized service provider, to have the machine tested. The routine hardware diagnostics used by service providers do not detect the fault. There is a specific test for this issue that Apple calls "VST" (for "Video Switching Test.") Ask for it. A "Failed" result means that the fault is present. However, according to reports, some units may pass the test, and yet still be deemed eligible for repair under the program. Your experience may vary.

Print the first page of the panic report, if any, and the support page linked above, and bring them with you.

Note that the recall only applies within three years of purchase. After that, Apple may refuse the service. In that case, you may be quoted a price of about $300 (in the U.S.) for a "depot repair," which involves shipping the unit to a central repair facility and takes about two weeks. For that flat fee, anything found wrong with it should be fixed, not just the logic board.

The model was discontinued on February 24, 2011, so the recall has nominally ended. Some units may have been sold after that date by Apple as refurbished, or by resellers as new, and they might still be covered.

Residents of the EU may be entitled to warranty service for up to six years after purchase.

Some owners report that their unit was repaired under the program after the deadline had passed. Others report that the repair was covered by the extended warranty from a credit-card issuer. Again, your experience may vary.

Sometimes the replacement part is also defective, so be prepared for that possibility. If you decide to pay for a new logic board, test thoroughly during the 90-day warranty period on the repair. Some owners have reported that they went through as many as three replacement boards before getting one that worked.

If it's too late for your unit to be repaired free of charge, and you don't want to pay for the service, you may (or may not) be able to stop the panics by disabling automatic graphics switching. To use the discrete graphics processor, you'll need a third-party utility to switch to it manually.

Often the problems start after an OS upgrade. If the upgrade was recent, and you have backups, then you can revert to a previous OS X version.

If you're dissatisfied with Apple's response, please keep in mind that no one here represents the company or can help with customer-service issues.

Back up all data on the internal drive(s) before you hand over your computer to anyone. 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.

*An SSD doesn't need to be zeroed.

Erasing the disk will have no effect. It's just a waste of time. The technician may not have run the VST test, in which case he would have failed to detect the fault.

Hello , I am Brazilian and I do not speak English. But , I have the same problem presented above. I can not find the message " .panic " in the console .

I have an Imac . And after you upgrade to Yosemite it turns off by itself several times a day . There is some support in Portuguese ?

Thank U

Authorized Service Provider

Thank's, Eric!!!

But here the service is not the best... Maybe I try do a Yosemite's clean install.

I have the same issue and Linc you've been helping me before. I will try and take to the Apple Store/Genius Bar.

Brand New MBP Retina - Finder crashing - Color Wheel

Hi, Linc

I have the same problem. =/

I tried to find a .panic log, but i can't find it...

So, I did a clean install from Yosemite to Mavericks, bu the machine keeps crashing...

So I searched the time the machine caught and hung up (00:35:00), and found this:

Jan 13 00:34:51 iMac-de-Igor-Caie.local Installer[715]: Error loading /System/Library/CoreServices/InstallerStatusNotifications.bundle/Contents/MacOS /InstallerStatusNotifications: dlopen(/System/Library/CoreServices/InstallerStatusNotifications.bundle/Content s/MacOS/InstallerStatusNotifications, 265): no suitable image found. Did find:

/System/Library/CoreServices/InstallerStatusNotifications.bundle/Contents/MacOS /InstallerStatusNotifications: mach-o, but wrong architecture

Jan 13 00:35:06 iMac-de-Igor-Caie.local launchservicesd[77]: Application App:"Instalador" asn:0x0-4b04b pid:715 refs=7 @ 0x7fbb8b716d50 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x50050 pid=759 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100005/0x186a5 queue

Jan 13 00:35:06 iMac-de-Igor-Caie.local WindowServer[91]: [cps/setfront] Failed setting the front application to Instalador, psn 0x0-0x4b04b, securitySessionID=0x186a5, err=-13066

Jan 13 00:35:07 iMac-de-Igor-Caie.local launchservicesd[77]: Application App:"Final Cut Pro" asn:0x0-47047 pid:666 refs=7 @ 0x7fbb8d1263f0 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x50050 pid=759 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100005/0x186a5 queue

Jan 13 00:35:07 iMac-de-Igor-Caie.local WindowServer[91]: [cps/setfront] Failed setting the front application to Final Cut Pro, psn 0x0-0x47047, securitySessionID=0x186a5, err=-13066

Jan 13 00:38:31 localhost bootlog[0]: BOOT_TIME 1421120311 0

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.appstore" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".

Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.authd" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.bookstore" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.eventmonitor" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.install" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.iokit.power" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.mail" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.MessageTracer" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.performance" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Jan 13 00:38:52 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.securityd" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Jan 13 00:38:52 --- last message repeated 6 times ---

Jan 13 00:38:52 localhost kernel[0]: Longterm timer threshold: 1000 ms

Jan 13 00:38:52 localhost kernel[0]: PMAP: PCID enabled

Jan 13 00:38:52 localhost kernel[0]: PMAP: Supervisor Mode Execute Protection enabled

Jan 13 00:38:52 localhost kernel[0]: Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64

Jan 13 00:38:52 localhost kernel[0]: vm_page_bootstrap: 8167121 free pages and 188719 wired pages

Jan 13 00:38:34 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***

Jan 13 00:38:52 localhost kernel[0]: kext submap [0xffffff7f807a9000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff80007a9000]

Jan 13 00:38:52 localhost kernel[0]: zone leak detection enabled

Jan 13 00:38:52 localhost kernel[0]: "vm_compressor_mode" is 4

Jan 13 00:38:52 localhost kernel[0]: standard timeslicing quantum is 10000 us

Jan 13 00:38:34 localhost com.apple.launchd[1]: *** Shutdown logging is enabled. ***

Jan 13 00:38:52 localhost kernel[0]: standard background quantum is 2500 us

Jan 13 00:38:52 localhost kernel[0]: mig_table_max_displ = 74

Jan 13 00:38:52 localhost kernel[0]: TSC Deadline Timer supported and enabled

Jan 13 00:38:52 localhost kernel[0]: SAFE BOOT DETECTED - only valid OSBundleRequired kexts will be loaded.

maybe can help me......

need to solve it alone. Technical support of apple me my city *****. And it would take days to deliver the machine running . If not invent bigger problems to increase the price of the service.

Sorry for the english. And Thank you so much!

The only report that approaches to .panic is this .crash:

Parent Process: launchd [1]

Report Version: 11

Anonymous UUID: 4F4E86D2-XXXXXXXXXXXXXXXXXXXX

Crashed Thread: 7 Dispatch queue: com.apple.root.default-priority

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:

abort() called

*** error for object 0x7f8dd0668ba0: double free

Thread 0:: Dispatch queue: com.apple.main-thread

Thread 1:: Dispatch queue: com.apple.internetaccounts.xpc.collection

Thread 2:: Dispatch queue: com.apple.libdispatch-manager

Thread 3:: Dispatch queue: com.apple.root.default-priority

8 com.apple.CalendarPersistence 0x000000012144e247 +[CalManagedMessage messagesArrayForCalendarMainWindowWithManagedObjectContext:] + 647

9 com.apple.CalendarPersistence 0x000000012144dd51 +[CalBadgeMonitor postMessageUpdateWithInserted:andDeleted:] + 103

Thread 4:: Dispatch queue: com.apple.root.default-priority

Thread 5:

Thread 6:

Thread 7 Crashed:: Dispatch queue: com.apple.root.default-priority

Thread 8:: Dispatch queue: com.apple.root.default-priority

Thread 9:: Dispatch queue: com.apple.root.default-priority

Thread 10:

Thread 11:

Thread 7 crashed with X86 Thread State (64-bit):

rax: 0x0000000000000000 rbx: 0x0000000122ea3000 rcx: 0x0000000122ea18c8 rdx: 0x0000000000000000

rdi: 0x000000000000a207 rsi: 0x0000000000000006 rbp: 0x0000000122ea18f0 rsp: 0x0000000122ea18c8

r8: 0x0000000000000010 r9: 0x00000000fffffff0 r10: 0x000000000c000000 r11: 0x0000000000000202

r12: 0x000000010e308000 r13: 0x00000001102bf000 r14: 0x0000000000000006 r15: 0x0000000000000000

rip: 0x000000011297e866 rfl: 0x0000000000000202 cr2: 0x00000001128b9a9d

THANK'S AGAIN! =]

These are not the same issue. You should start your own new thread rather than piling on one that's months old.

sorry, Bro!

I'm new here!

I will starts a new. thank

My problem , it seems, is the summer ! My room has no air conditioning and this time the heat increases greatly . As new Imacs not get hot out , you can not realize how much the machine is suffering .

I bought a powerful fan and apparently the issue is resolved.