jesusfromswe

Q: Finder quit unexpectedly (Help!)

After an usual crash I had with Logic Pro X and after I rebooted my mac I got this error: Finder Quit Unexpectedly. No matter how many time I click "Reopen" or "Ok" it keep crashing every second.

I have seen tons of discussions on this. I have also tried using Disk Utility, Terminal and everything but can't find a solution for my problem. I even tried using Time Machine to do a Back Up but it doesn't work...

Hope you can help me!

MacBook Pro with Retina display, OS X Mavericks (10.9.1), Finder Crashes.

Posted on Dec 27, 2013 4:26 AM

Close

Q: Finder quit unexpectedly (Help!)

  • All replies
  • Helpful answers

Page 1 of 3 last Next
  • by arthur,

    arthur arthur Dec 27, 2013 5:09 AM in response to jesusfromswe
    Level 5 (5,193 points)
    iBooks
    Dec 27, 2013 5:09 AM in response to jesusfromswe

    Have you tried booting from your recovery partition (restart, hold down ⌘R until you see the Apple logo), and use Disk Utility to repair your hard drive? Repair permissions too while you're there. OS X: About OS X Recovery

  • by jesusfromswe,

    jesusfromswe jesusfromswe Dec 27, 2013 5:18 AM in response to arthur
    Level 1 (0 points)
    Dec 27, 2013 5:18 AM in response to arthur

    Should I click Repair Disk on: "121.33 GB APPLE SSD" or down "Macintosh HD"?

  • by jesusfromswe,

    jesusfromswe jesusfromswe Dec 27, 2013 6:02 AM in response to arthur
    Level 1 (0 points)
    Dec 27, 2013 6:02 AM in response to arthur

    Alright I've done as you said but after I clicked on Repair Disk Permissions I get:

    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.

    Might be this the problem?

    Please answer

  • by arthur,

    arthur arthur Dec 27, 2013 6:29 AM in response to jesusfromswe
    Level 5 (5,193 points)
    iBooks
    Dec 27, 2013 6:29 AM in response to jesusfromswe

    Sorry, I was out shoveling the roof.

    If Macintosh HD is your normal boot partition (it probably is), then that would be the one to repair. It wouldn't hurt to run Disk Utility on the SSD too, though.

    The SSD (which sounds like it is the topmost level) is the whole drive; the Macintosh HD is a partition on that drive.

    If your mac is now running well after you reboot it I wouldn't worry too much about that SUID file thing. The permissions repair function will occasionally find things like this and make these reports, and usually they don't mean much, if your mac is running well. "If it ain't broke, don't fix it",applies.

    If your mac is still misbehaving, then I would try another repair with Disk Utility in recovery mode. If that doesn't work, then I would use TechTool Pro to try and repair the HD. Techtool Pro 7  is one third-party utility that is worth having. It can occasionally fix something that Disk Utility can't.

  • by jesusfromswe,

    jesusfromswe jesusfromswe Dec 27, 2013 6:52 AM in response to arthur
    Level 1 (0 points)
    Dec 27, 2013 6:52 AM in response to arthur

    Mh, I see that it's not a free software and also how can I execute it if I can't use Finder.

    I tried also to download Maintenance by seeing other posts related to this problem but still it's not possible to open it.

  • by arthur,

    arthur arthur Dec 27, 2013 7:38 AM in response to jesusfromswe
    Level 5 (5,193 points)
    iBooks
    Dec 27, 2013 7:38 AM in response to jesusfromswe

    TechTool can be run from its installer disc. It can install its own bootable recovery partition (called the eDrive).

    Just to clarify:

    1. did you boot from your recovery partition and repair your HD with Disk Utility from the recovery partition?
    2. then did you restart from your boot partition?

    3. If you did, and the problem is still there, try a safe boot (restart, hold down shift until you see the Apple logo). If this eliminates the symptom, then you know the problem is with some third-party software you have installed. Mac OS X: What is Safe Boot, Safe Mode?
      1. safe boot doesn't fix anything; it just tells you that the problem is with third-party software.
      2. then you have to find the third-party software that is causing the problem and remove it.
      3. if you can, from safe mode, download and run etrecheck.  Etresoft: EtreCheck is a small, free app developed by one of the contributors to this forum which will generate a system report on your computer (no personal info). If you can paste the report in a response here we could try to figure out what the misbehaving third party item is.
    4. If a safe boot doesn't eliminate the symptom, then the problem is with OSX itself. If your recovery partition can't fix the problem, the next step would be to see if Internet Recovery can repair your HD:
      1. Hands on with Mountain Lion's OS X Recovery and Internet Recovery | Macworld
        1. This reference is for ML but it also applies to Mavericks.
    5. If Internet recovery cannot repair your HD I'd try TechTool.
    6. another option at that point would be single-user mode and fsck: Try to boot into single user mode (restart, hold down ⌘S until you see a black screen with white text) and repair your hard drive. Here's a reference with directions: Repair Your Hard Disk in Single User Mode | Everything Macintosh
    7. yet another option would be recovery disk assistant: If you have another (working) mac and a USB thumb drive, you can make an external recovery disk with OS X Recovery Disk Assistant v1.0
    8. if none of that works then you may have to try the nuclear option: erase your HD and reinstall Mavericks from scratch (from internet recovery or from a bootable USB installer flash drive, for example, which you could make if you have a friend with a working mac, an 8 GB flash drive, and DiskMaker X (formerly Lion DiskMaker) , and then reinstall your documents from your backup.
      1. note that it has to be a clean install, i.e., from scratch. If you reinstall damaged system files from a backup you'll just reinstall your problem.
    9. If that doesn't work, it sounds like your HD is failing and may need to be replaced.
  • by jesusfromswe,

    jesusfromswe jesusfromswe Dec 27, 2013 8:03 AM in response to arthur
    Level 1 (0 points)
    Dec 27, 2013 8:03 AM in response to arthur

    Hi, thanks for the reply.

    For the Recovery Partition thing what do I exactly have to do? Create another partition on SSD or using another external Hard Drive? As I told you before Time Machine doesn't work and can't Back Up anything..

    Otherwise I already pressed cmd+r and did what you said.

  • by jesusfromswe,

    jesusfromswe jesusfromswe Dec 27, 2013 10:10 AM in response to arthur
    Level 1 (0 points)
    Dec 27, 2013 10:10 AM in response to arthur

    So in conclusion:

     

    1. Recovery Mode says that Macintosh HD appears to be OK.
    2. Safe Boot still doesn't resolve the problem nor let me access to Finder so I can download EtreCheck.
    3. I used Internet Recovery and after it downloaded everything from Apple Servers it takes me back to Recovery Mode and even if I click on "Repair Disk" and "Repair Disk Permissions" the problem persists.
    4. I tried also Single User Mode and after I followed the commands the article gives it says: The volume "Macintosh HD" appears to be OK.
    5. I don't have an other Mac in order to use Recovery Disk Assistant.

     

    Only the last critical steps I have not tried. What do you suggest me to do?

  • by arthur,

    arthur arthur Dec 27, 2013 12:41 PM in response to jesusfromswe
    Level 5 (5,193 points)
    iBooks
    Dec 27, 2013 12:41 PM in response to jesusfromswe

    Your OSX installation has problems that Disk Utility can't fix.

    This would be a good situation to try TechTool, but if you don't want to do that:

    See if you can (via internet recovery or the recovery partition) reinstall Mavericks over your current installation.

    If that doesn't work, you've run out of options, except for the nuclear option:

    I would go ahead and (via Internet recovery) erase your HD and reinstall Mavericks.

    Do you have any of the following installed on your mac:

    1. Antivirus software
    2. "Utilities" like
      1. MacKeeper
      2. CleanMyMac
      3. anything else that purports to "optimize",  "clean", "accelerate", "monitor", "enhance", or "protect" your Mac?

    If so, don't reinstall them. That's probably what's causing the problem.

  • by jesusfromswe,

    jesusfromswe jesusfromswe Dec 27, 2013 1:18 PM in response to arthur
    Level 1 (0 points)
    Dec 27, 2013 1:18 PM in response to arthur

    No, I don't have any software like that on my Mac. I have to consider spending 99$ for a software that I'll use very few times. Since I'm using a slow internet connection via Personal Hotspot from iPhone I don't know if re-downloading Mavericks is a good option..

  • by Linc Davis,

    Linc Davis Linc Davis Dec 27, 2013 6:38 PM in response to jesusfromswe
    Level 10 (207,926 points)
    Applications
    Dec 27, 2013 6:38 PM in response to jesusfromswe

    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.

     

    Step 1

     

    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

    View Show Log List

    from the menu bar.

    Enter the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).

    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

    Please do not indiscriminately dump thousands of lines from the log into this discussion.

     

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

     

    Step 2

     

    In the Console window, look under User Diagnostic Reports for crash reports related to the crashed process. The report name starts with the name of the process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. 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 not helpful.

  • by jesusfromswe,

    jesusfromswe jesusfromswe Dec 28, 2013 4:24 AM in response to Linc Davis
    Level 1 (0 points)
    Dec 28, 2013 4:24 AM in response to Linc Davis

    Step 1:

     

    I've changed my name to Anonym, the Finder keep crashing every second so I'm unable to select 12 strings from the Console. This is what I could come up with:

     

    26/12/13 14:56:59,837 ReportCrash[208]: Saved crash report for Finder[427] version 10.9.1 (10.9.1) to /Users/Anonym/Library/Logs/DiagnosticReports/Finder_2013-12-26-145659-1_Anonyms -MacBook-Pro.crash

     

    26/12/13 14:56:59,837 ReportCrash[208]: Saved crash report for Finder[427] version 10.9.1 (10.9.1) to /Users/Anonym/Library/Logs/DiagnosticReports/Finder_2013-12-26-145659-1_Anonyms -MacBook-Pro.crash

     

    Step 2?:

     

    The Console crashes when I select one of the strings under User Diagnostic Reports

     

    The only information I could retrieve is from the "Problem Report for Finder":

     

    Process:         Finder [1980]

    Path:            /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder

    Identifier:      Finder

    Version:         10.9.1 (10.9.1)

    Code Type:       X86-64 (Native)

    Parent Process:  launchd [169]

    Responsible:     Finder [1980]

    User ID:         501

     

     

    Date/Time:       2013-12-28 13:20:03.042 +0100

    OS Version:      Mac OS X 10.9.1 (13B42)

    Report Version:  11

     

     

     

     

     

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

     

     

    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018

     

     

    VM Regions Near 0x18:

    -->

        __TEXT                 0000000103e40000-0000000104307000 [ 4892K] r-x/rwx SM=COW  /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder

     

     

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

    0   com.apple.CoreServicesInternal          0x0000000114bf4528 _FSURLCopyResourcePropertyValuesAndFlags + 350

    1   com.apple.CoreFoundation                0x0000000107cf9573 _CFURLCopyResourcePropertyValuesAndFlags + 147

    2   com.apple.desktopservices               0x00000001044418e6 TFSInfo::FetchProperties() + 230

    3   com.apple.desktopservices               0x000000010443d033 TFSInfo::Initialize(__CFURL const*, bool) + 291

    4   com.apple.desktopservices               0x0000000104441791 TFSInfo::GetVolumeInfo(short, unsigned int, FSVolumeInfo&, TCountedPtr<TFSInfo>*) + 115

    5   com.apple.desktopservices               0x000000010443fdab TFSVolumeInfo::Initialize(TCountedPtr<TVolumeSyncThread> const&, short, unsigned char, bool&) + 485

    6   com.apple.desktopservices               0x000000010443f88f TFSVolumeInfo::AddVolume(TCountedPtr<TVolumeSyncThread> const&, short, unsigned char, TCountedPtr<TFSVolumeInfo>&, bool&) + 131

    7   com.apple.desktopservices               0x0000000104441595 ___ZN12TGlobalNodes8BootNodeEv_block_invoke + 74

    8   libdispatch.dylib                       0x000000010a3862ad _dispatch_client_callout + 8

    9   libdispatch.dylib                       0x000000010a38621c dispatch_once_f + 79

    10  com.apple.desktopservices               0x000000010444148c TGlobalNodes::BootNode() + 242

    11  com.apple.desktopservices               0x0000000104441386 TNode::GetBootNode() + 14

    12  com.apple.desktopservices               0x000000010443db65 __NodeContextOpen_block_invoke + 94

    13  libdispatch.dylib                       0x000000010a3862ad _dispatch_client_callout + 8

    14  libdispatch.dylib                       0x000000010a38621c dispatch_once_f + 79

    15  com.apple.desktopservices               0x000000010443dac6 NodeContextOpen + 152

    16  com.apple.finder                        0x0000000103e486c3 0x103e40000 + 34499

    17  com.apple.finder                        0x0000000103e465e8 0x103e40000 + 26088

    18  com.apple.finder                        0x0000000103e464c9 0x103e40000 + 25801

    19  libdyld.dylib                           0x000000010a3c15fd start + 1

     

     

    Thread 1:

    0   libsystem_kernel.dylib                  0x000000010a553e6a __workq_kernreturn + 10

    1   libsystem_pthread.dylib                 0x000000010a660f08 _pthread_wqthread + 330

    2   libsystem_pthread.dylib                 0x000000010a663fb9 start_wqthread + 13

     

     

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

    0   libsystem_kernel.dylib                  0x000000010a554662 kevent64 + 10

    1   libdispatch.dylib                       0x000000010a38843d _dispatch_mgr_invoke + 239

    2   libdispatch.dylib                       0x000000010a388152 _dispatch_mgr_thread + 52

     

     

    Thread 3:

    0   libsystem_kernel.dylib                  0x000000010a553e6a __workq_kernreturn + 10

    1   libsystem_pthread.dylib                 0x000000010a660f08 _pthread_wqthread + 330

    2   libsystem_pthread.dylib                 0x000000010a663fb9 start_wqthread + 13

     

     

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

      rax: 0x0000000114c10e30  rbx: 0x0000000000000000  rcx: 0x00007fff5bdbcf50  rdx: 0x000000000001ffff

      rdi: 0x0000000000000004  rsi: 0x0000000000000003  rbp: 0x00007fff5bdbdbc0  rsp: 0x00007fff5bdbcb50

       r8: 0x0000000000000001   r9: 0x0000000000000000  r10: 0x00007fff5bdbcb70  r11: 0x0000000000000010

      r12: 0x00007fff5bdbcb50  r13: 0x000000000001ffff  r14: 0x00007fff5bdbd330  r15: 0x00007fff5bdbcb70

      rip: 0x0000000114bf4528  rfl: 0x0000000000010202  cr2: 0x0000000000000018

     

    Logical CPU:     3

    Error Code:      0x00000004

    Trap Number:     14

     

    I selected a small part, hope it's enough.

  • by Linc Davis,

    Linc Davis Linc Davis Dec 28, 2013 7:27 AM in response to jesusfromswe
    Level 10 (207,926 points)
    Applications
    Dec 28, 2013 7:27 AM in response to jesusfromswe
    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. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
       
    Safe mode is much slower to boot 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 boot 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, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.
  • by jesusfromswe,

    jesusfromswe jesusfromswe Dec 28, 2013 7:51 AM in response to Linc Davis
    Level 1 (0 points)
    Dec 28, 2013 7:51 AM in response to Linc Davis

    Alright, I'm sure that FileVault is disabled but can you tell me how to check firmware password and if the boot volume is a software RAID?

Page 1 of 3 last Next