After install, many grey screen crashes

I'm getting many system crashes with the grey screen telling me to reboot in about 4 or 5 languages. I originally installed on my 80gb ATA drive which I had my 10.4.x system loaded. After install, it would not start from that drive. I restarted with the install disk and installed Leopard on a smaller drive (18gb SCSI). Once up and running on the 18gb drive, I am experiencing many crashes. I've zapped pram, run disk utility to repair the disks and permissions and still can't keep it running after a period of time. I have tried to reinstall on my 80gb and the install crashes (once with 16 minutes to go).
Any ideas?????

Hi
See if anything at http://thexlab.com/faqs/kernelpanics.html helps.
Steve

Similar Messages

  • After install, get grey screen then immediate powerdown

    The computer started out as a 350MHz G4 AGP (Sawtooth). It now has a 1GHz Sonnet CPU. It has 1 Gb of RAM and plenty of hard disk. The display is an Apple 20" flat panel.
    Installed Leopard, upgrading from 10.4.10.
    On boot, the screen goes grey for about two-three seconds, then the computer powers down. Reinstalling Leopard produced no change.
    I've got a fresh install of 10.4.11 running on another disk, so I'm not dead, but I'm not running Leopard either.
    Has anyone seen this sort of misbehavior? Does anyone have any useful ideas?
    yours,
    Michael

    I have seen similar threads like yours in the G4 Section and the answer there seem to be an Archive and Install as opposed to a upgrade from Tiger.
    So my advise would be to first Erase and then Reformat the hard drive in Disk Utility to Mac OS Extended (Journal), now see if you can install Leopard. If not, try cloning your Mac OS 10.4.11 to that disk, then choose Option and do an Archive and Install when installing Leopard.
    Joe

  • Grey Screen Crashes/In 4 different languages

    I've been experiencing frequent grey screen crashes and I have to re-install the system software to restart my machine. What are the reasons for this crash? I need direction to solve this problem.
    Machine does this while using Adobe CS, InDesign mostly.
    MVH
    G5 Dual, 2.3GHz   Mac OS X (10.4.2)  

    Hi Peter!
    That is a Kernel Panic.
    See this Resolving Kernel Panics, authored by Dr Smoke, for possible remedies.
    Good Luck!
    ali b

  • HT4356 Mavric doesn't support my 5 years old Big Screen Display, OR? Tried to connect my Mac Book Pro after installing Mavric, The Screen didn't work as before. I could only see the Desktop but not the movies for example. What can I do?

    Mavric doesn't support my 5 years old Big Screen Display, OR? Tried to connect my Mac Book Pro after installing Mavric, The Screen didn't work as before. I could only see the Desktop but not the movies for example.
    <E-mail Edited by Host>

    It appears what happened is the installer though it was looking at a empty drive and just went ahead and installed.
    I of course am assuming here you didn't use Disk Utility to format the drive first before installing, that would wipe out your files and programs for sure.
    So what to do, what to do.
    Well there is hope for you as long as the drive wasn't Filevaulted.
    I'll explain. When a hard drive writes data for the first time to a drive, it starts at the very top and works it's way down.
    When OS X was installed the first time, it was at the top of the drive, unless you upgraded then the upgraded OS X could have been written elsewhere.
    Now when you just reinstalled OS X, the new OS went on the top of the drive, overwriting any data that was there previously, so what was there you have lost forever which is about 8GB or so. If it was the previous OS there, then your more in luck because only the old OS X was overwritten.
    The remaining space on the drive still can have a copy of your files, provided it's not overwritten yet.
    It's because when a hard drive deletes data or reformats, it doesn't remove the data off the drive or overwrites it immediately, it's just made so it's SPACE is available for new files to be written there.
    So technically one can recover the deleted data off a non-encrypted/scrubbed hard drive with special software.
    The way it does this is it reads the 1's and 0's of the files themselves, and through a lot of figuring out, can tell what that file is and what it belongs too.
    So what you will have to do is this:
    Create a data recovery/undelete external boot drive
    or if you don't have the skills, then take it to a local PC/Mac tech and they can do a direct image of the drive and then you can run Data Rescue on it to rebuild your files.

  • Camera app doesn't work after installing a new screen

    I have been fixing broken iPhone screens for quite some time now but have never come across something like this. After installing a new screen the camera app won't show the camera and the shutter never opens. I thought I didn't put one of the cables in right so I double checked and sure enough they were in good. I restored the phone and tried it again with no luck. I then switched out to another screen I found and the camera worked perfectly. This is so bizzarre to me but can anyone explain to me what is wrong? Or what has happened? I have never seen anything like this.

    I keep getting an error message of (0xE80000001)!
    Read here.   iPhone, iPad, iPod touch: Unknown error containing '0xE' when connecting

  • Hello! after installing lion my iPhoto crashes everytime i connect my iPhone?

    hello! after installing lion my iPhoto crashes everytime i connect my iPhone?

    hello! after installing lion my iPhoto crashes everytime i connect my iPhone?

  • After installing Lion , my computer crashes and the fan runs constantly on high

    After installing Lion , my computer crashes and the fan runs constantly on high. How is Apple resolving this problem?

    Try to reset your SMC, it fixed the same problem for me ;o)
    http://support.apple.com/kb/ht3964

  • Premiere Elements 8 Grey Screen/Crash

    When I attempt to open a saved or new project I get a blank grey screen.  I've been using this program for years and only recently (a few months ago) this has happened.  Also, when I attempt to open organizer it crashes.  I've uninstalled and reinstalled multiple times with no luck.  I'm using an HP Pavilion Slimline w/Windows Vista Home Premium OEMAct.  I've updated my latest NVIDIA driver and do not have MacFee security.  I'm not much of a tech guy so I'd be greatful for any help.  Any other suggestions?

    1. Preview Files. Are you on Vista 32 or 64 bit? In my Windows 7 64 bit, I would go to Libraries/Documents/Adobe/Premiere Elements/8.0 and, in the 8.0 Folder, empty out the Adobe Premiere Elements Preview Files Folder. Do you find such a folder on you computer hard drive?  I am in 64 bit.  I was able to find those files and clean them out.  They were pretty much empty since I recently re-installed the program.
    2. Conformed Audio Files. Here I would go to Libraries/Documents/Adobe/Premiere Elements/8.0 and, in the 8.0 Folder, empty out the Media Cache Files Folder. Do you find such a folder on your computer hard drive? The only two folders in the 8.0 folder is "Preview Files" (now empty) and "Encoded Files" (empty as well)
    3. Conformed Video Files. Here I would go to Local Disk C\Users\Owner\AppData\Roaming\Adobe\Common\Media Cache and clean out the Media Cache Folder. - Found these files and cleaned out a significant amount of files.
    After that we will be going after the Premiere Elements 8.0/8.0.1 settings file
    Local Disk C
    Users
    Owner
    AppData
    Roaming
    Adobe
    Premiere Elements
    8.0 Folder
    and in the 8.0 Folder is the Adobe Premiere Elements Prefs file that we delete. If that does not work, then we delete the whole 8.0 Folder in which the Adobe Premiere Elements Prefs file exists. Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see the complete path. - Found file and deleted both the Prefs and then went back and deleted the entire 8.0 folder.  I started up the program and the same issue occured.  I went back through these instructions and the 8.0 folder and Pref file had reappeared - not sure if that is supposed to happen?

  • After installing mavericks Finder keeps crashing

    After installing Mavericks I cannot use my Mac as he finder open and reopen continuously. Also in safe mode. I also cleaned the list of apps  starting after login,  but it keeps crashing. No way of solving this through other threads here.
    What can I do.

    I'm having similar problem with my MBP mid 2010 2.4 ghz, 6gb ram.
    In my case every time I point at Share combo box in a file contextual menu i get finder crashed and i have to force quitting.
    Looking at the log I managed to find that 'com.apple.ShareKitHelper' every 15 secs keeps on logging error messages.
    Can anyone give an hand on this?
    Thx
    Bruno

  • Cannot install leopard, grey screen

    When I click restart on the install dvd app, it restarts, then goes to the grey screen, and stays there forever. could it be bad ram module?

    Kevin Wyatt-Scott wrote:
    When I click restart on the install dvd app, it restarts, then goes to the grey screen, and stays there forever. could it be bad ram module?
    If it never gets to the DVD selftest, then it's either a hardware problem such as you mention, RAM, or a bad DVD or even a bad or marginal optical reader.
    I would reset PRAM and NV-RAM and also look at the DVD for scratches and/or dirt and clean it if necessary with a damp soft cloth, wiping from center to outside in a straight line.

  • After Installing More Ram, MBP Crashes When Using Battery Power

    I own a 2.16 Ghz MBP. Last night, I installed 4 Gigs of ram (2x2 Gigs)purchased from crucial.com into my MBP. (Yes, I realize that the MBP only utilizes about 3.3 Gigs of the ram, but I wanted the benefits of running with a matched pair).
    After installing the ram, my MBP recognizes the new ram and everything seemed fine. And, it was fine until I unplugged the MBP's power and went mobile. Then, after a few minutes of use, the MBP completely shut down and turned off. I tried turning it back on, but it would not. So, I plugged the MBP and it booted up fine. I unplugged it again, and again, after a few minutes of use, the MBP shut down completely. Being that the battery was fully charged, I don't know why it would behave this way.
    Any way, anybody have any ideas as to what might be wrong?
    Message was edited by: No Exit

    No Exit wrote:
    I own a 2.16 Ghz MBP. Last night, I installed 4 Gigs of ram (2x2 Gigs)purchased from crucial.com into my MBP. (Yes, I realize that the MBP only utilizes about 3.3 Gigs of the ram, but I wanted the benefits of running with a matched pair).
    After installing the ram, my MBP recognizes the new ram and everything seemed fine. And, it was fine until I unplugged the MBP's power and went mobile. Then, after a few minutes of use, the MBP completely shut down and turned off. I tried turning it back on, but it would not. So, I plugged the MBP and it booted up fine. I unplugged it again, and again, after a few minutes of use, the MBP shut down completely. Being that the battery was fully charged, I don't know why it would behave this way.
    Any way, anybody have any ideas as to what might be wrong?
    Message was edited by: No Exit
    It sounds as if you have a defective battery. I would call Apple and explain your MBP's symptoms. If the battery is swollen it is likely a candidate.

  • I have a Macbook Pro Early 2011 from the USA.  After installing Mavericks, Adobe CS6 crashes whenever it is plugged into a 27inch cinema display I purchased from the apple store in China (We moved to China). It works when not plugged into 27inch display.

    I have a Macbook Pro Early 2011 from the USA. It is now running Mavericks.  I connect it to a 27" Cinema Display that I bought in China after we moved to China.  Before I installed Mavericks, I could run all of the Adobe CS6 and Adobe CS5.5 applications on my Macbook Pro while connected to the cinema display. Now that I have Mavericks installed, whenever I am connected to my 27" CInema display my Adobe applications crash upon opening.  I know this is a rare scenario, but does anyone have any ideas how to fix this problem? Is there a new driver that needs installed?  I'd appreciate any help.

    I am also having a similar issue. I used Adobe Lightroom and my whole display goes black. Even my laptop screen and the lights on the keyboard go black. I can still hear the fan running, so I assume it is just the display. This is my first Mac and I have had nothing but issues. I think I am going back to Windows after this.

  • My imac often crashes after installing Yosemite. Keep crashes after return to Mavericks...

    So...
    After update my OS to Mavericks, my machine started off alone , without a defined reason. Hung in my work. On several occasions. I chose to redo a clean installation of Mavericks . But , the machine continues to hamper my life ... Keeps crashing...
    I tried to find a .panic log, but i can't find it...
    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.
    The only report that approaches to .panic is this .crash:
    Process:    
    com.apple.internetaccounts [237]
    Path:       
    /System/Library/PrivateFrameworks/InternetAccounts.framework/Versions/A/XPCServi ces/com.apple.internetaccounts.xpc/Contents/MacOS/com.apple.internetaccounts
    Identifier: 
    com.apple.internetaccounts
    Version:    
    1.0 (1)
    Code Type:  
    X86-64 (Native)
    Parent Process:  launchd [1]
    Responsible:
    com.apple.internetaccounts [237]
    User ID:    
    501
    Date/Time:  
    2015-01-13 00:42:48.992 -0300
    OS Version: 
    Mac OS X 10.9.5 (13F34)
    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
    0   libsystem_kernel.dylib  
    0x000000011297aa1a mach_msg_trap + 10
    1   libsystem_kernel.dylib  
    0x0000000112979d18 mach_msg + 64
    2   com.apple.CoreFoundation
    0x000000011033df15 __CFRunLoopServiceMachPort + 181
    3   com.apple.CoreFoundation
    0x000000011033d539 __CFRunLoopRun + 1161
    4   com.apple.CoreFoundation
    0x000000011033ce75 CFRunLoopRunSpecific + 309
    5   com.apple.HIToolbox     
    0x000000011484ea0d RunCurrentEventLoopInMode + 226
    6   com.apple.HIToolbox     
    0x000000011484e7b7 ReceiveNextEventCommon + 479
    7   com.apple.HIToolbox     
    0x000000011484e5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
    8   com.apple.AppKit        
    0x000000010e7ee24e _DPSNextEvent + 1434
    9   com.apple.AppKit        
    0x000000010e7ed89b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
    10  com.apple.AppKit        
    0x000000010e7e199c -[NSApplication run] + 553
    11  com.apple.AppKit        
    0x000000010e7cc783 NSApplicationMain + 940
    12  com.apple.XPCService    
    0x0000000119d52c0f _xpc_main + 385
    13  libxpc.dylib            
    0x0000000112ae7bde xpc_main + 399
    14  com.apple.Foundation    
    0x000000010fd65cdb -[NSXPCListener resume] + 108
    15  com.apple.internetaccounts  
    0x000000010e2e839f main + 157
    16  libdyld.dylib           
    0x00000001127e55fd start + 1
    Thread 1:: Dispatch queue: com.apple.internetaccounts.xpc.collection
    0   libsystem_kernel.dylib  
    0x000000011297aa6e semaphore_timedwait_trap + 10
    1   libdispatch.dylib       
    0x00000001127afd88 _dispatch_group_wait_slow + 147
    2   com.apple.internetaccounts  
    0x000000010e2e914f 0x10e2e7000 + 8527
    3   com.apple.internetaccounts  
    0x000000010e2eb671 0x10e2e7000 + 18033
    4   com.apple.internetaccounts  
    0x000000010e2ef795 0x10e2e7000 + 34709
    5   libdispatch.dylib       
    0x00000001127ac1bb _dispatch_call_block_and_release + 12
    6   libdispatch.dylib       
    0x00000001127a928d _dispatch_client_callout + 8
    7   libdispatch.dylib       
    0x00000001127ab673 _dispatch_queue_drain + 451
    8   libdispatch.dylib       
    0x00000001127ac9c1 _dispatch_queue_invoke + 110
    9   libdispatch.dylib       
    0x00000001127aaf87 _dispatch_root_queue_drain + 75
    10  libdispatch.dylib       
    0x00000001127ac177 _dispatch_worker_thread2 + 40
    11  libsystem_pthread.dylib 
    0x0000000112a87ef8 _pthread_wqthread + 314
    12  libsystem_pthread.dylib 
    0x0000000112a8afb9 start_wqthread + 13
    Thread 2:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib  
    0x000000011297f662 kevent64 + 10
    1   libdispatch.dylib       
    0x00000001127ab421 _dispatch_mgr_invoke + 239
    2   libdispatch.dylib       
    0x00000001127ab136 _dispatch_mgr_thread + 52
    Thread 3:: Dispatch queue: com.apple.root.default-priority
    0   libsystem_kernel.dylib  
    0x000000011297ab16 syscall_thread_switch + 10
    1   libsystem_platform.dylib
    0x0000000112a6ddf6 _OSSpinLockLockSlow + 63
    2   com.apple.CoreData      
    0x0000000110f815c4 generateReturnPointerMethod + 84
    3   com.apple.CoreData      
    0x0000000110f80c93 +[NSManagedObject(_PFDynamicAccessorsAndPropertySupport) classForEntity:] + 1075
    4   com.apple.CoreData      
    0x0000000110f806fb _PFFastEntityClass + 315
    5   com.apple.CoreData      
    0x0000000110f803d7 -[NSManagedObjectContext(_NSInternalAdditions) _retainedObjectWithID:optionalHandler:withInlineStorage:] + 103
    6   com.apple.CoreData      
    0x0000000110fbfcdc -[_NSFaultingMutableSet willRead] + 476
    7   com.apple.CoreData      
    0x0000000110fbfad4 -[_NSFaultingMutableSet countByEnumeratingWithState:objects:count:] + 36
    8   com.apple.CalendarPersistence     0x000000012144e247 +[CalManagedMessage messagesArrayForCalendarMainWindowWithManagedObjectContext:] + 647
    9   com.apple.CalendarPersistence     0x000000012144dd51 +[CalBadgeMonitor postMessageUpdateWithInserted:andDeleted:] + 103
    10  libdispatch.dylib       
    0x00000001127ac1bb _dispatch_call_block_and_release + 12
    11  libdispatch.dylib       
    0x00000001127a928d _dispatch_client_callout + 8
    12  libdispatch.dylib       
    0x00000001127ab082 _dispatch_root_queue_drain + 326
    13  libdispatch.dylib       
    0x00000001127ac177 _dispatch_worker_thread2 + 40
    14  libsystem_pthread.dylib 
    0x0000000112a87ef8 _pthread_wqthread + 314
    15  libsystem_pthread.dylib 
    0x0000000112a8afb9 start_wqthread + 13
    Thread 4:: Dispatch queue: com.apple.root.default-priority
    0   libsystem_kernel.dylib  
    0x000000011297aa56 semaphore_wait_trap + 10
    1   libdispatch.dylib       
    0x00000001127ad9f9 _dispatch_semaphore_wait_slow + 206
    2   libxpc.dylib            
    0x0000000112ade7ef xpc_connection_send_message_with_reply_sync + 195
    3   com.apple.AOSKit        
    0x000000011a404cca -[AOSAgentConnection sendMessageWithPayload:replyHandler:isAsync:] + 1002
    4   com.apple.AOSKit        
    0x000000011a3fbb7a +[AOSUtilities makeAgentRequestWithAccount:type:args:callback:maxRetries:] + 763
    5   com.apple.AOSKit        
    0x000000011a3e7d16 _AOSAccountRetrieveMailProperties + 344
    6   com.apple.Mail.framework
    0x0000000120c1bcb4 -[MFAosImapAccount(Internal) aoskitPropertyForKey:] + 196
    7   com.apple.Mail.framework
    0x0000000120d1604c -[MFMailAccount(Internal) iaSettingsIncludingPassword:] + 694
    8   com.apple.Mail.framework
    0x0000000120c1931c -[MFAosImapAccount iaSettingsIncludingPassword:] + 51
    9   com.apple.mail.iaplugin 
    0x000000011f0a1bac 0x11f0a0000 + 7084
    10  com.apple.internetaccounts  
    0x000000010e2ea4e6 0x10e2e7000 + 13542
    11  com.apple.internetaccounts  
    0x000000010e2e9339 0x10e2e7000 + 9017
    12  libdispatch.dylib       
    0x00000001127ac1bb _dispatch_call_block_and_release + 12
    13  libdispatch.dylib       
    0x00000001127a928d _dispatch_client_callout + 8
    14  libdispatch.dylib       
    0x00000001127ab082 _dispatch_root_queue_drain + 326
    15  libdispatch.dylib       
    0x00000001127ac177 _dispatch_worker_thread2 + 40
    16  libsystem_pthread.dylib 
    0x0000000112a87ef8 _pthread_wqthread + 314
    17  libsystem_pthread.dylib 
    0x0000000112a8afb9 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib  
    0x000000011297ee6a __workq_kernreturn + 10
    1   libsystem_pthread.dylib 
    0x0000000112a87f08 _pthread_wqthread + 330
    2   libsystem_pthread.dylib 
    0x0000000112a8afb9 start_wqthread + 13
    Thread 6:
    0   libsystem_kernel.dylib  
    0x000000011297aa1a mach_msg_trap + 10
    1   libsystem_kernel.dylib  
    0x0000000112979d18 mach_msg + 64
    2   com.apple.CoreFoundation
    0x000000011033df15 __CFRunLoopServiceMachPort + 181
    3   com.apple.CoreFoundation
    0x000000011033d539 __CFRunLoopRun + 1161
    4   com.apple.CoreFoundation
    0x000000011033ce75 CFRunLoopRunSpecific + 309
    5   com.apple.AppKit        
    0x000000010e98e05e _NSEventThread + 144
    6   libsystem_pthread.dylib 
    0x0000000112a86899 _pthread_body + 138
    7   libsystem_pthread.dylib 
    0x0000000112a8672a _pthread_start + 137
    8   libsystem_pthread.dylib 
    0x0000000112a8afc9 thread_start + 13
    Thread 7 Crashed:: Dispatch queue: com.apple.root.default-priority
    0   libsystem_kernel.dylib  
    0x000000011297e866 __pthread_kill + 10
    1   libsystem_pthread.dylib 
    0x0000000112a8735c pthread_kill + 92
    2   libsystem_c.dylib       
    0x00000001128b9b1a abort + 125
    3   libsystem_malloc.dylib  
    0x00000001129f3690 szone_error + 587
    4   com.apple.CoreFoundation
    0x0000000110305579 _CFArrayReplaceValues + 1433
    5   com.apple.CoreFoundation
    0x00000001102f8e2b CFArrayAppendValue + 123
    6   com.apple.CoreData      
    0x0000000110f8c3b4 generateAccessor + 212
    7   com.apple.CoreData      
    0x0000000110f889fc +[NSManagedObject(_PFDynamicAccessorsAndPropertySupport) resolveInstanceMethod:] + 6140
    8   libobjc.A.dylib         
    0x00000001100fcc21 _class_resolveInstanceMethod(objc_class*, objc_selector*, objc_object*) + 76
    9   libobjc.A.dylib         
    0x00000001101022c8 lookUpImpOrForward + 286
    10  libobjc.A.dylib         
    0x00000001100f5169 objc_msgSend + 233
    11  com.apple.CalendarStore 
    0x000000011f0c4434 +[CalGroup(CreationFromManagedObject) groupFromManagedObject:] + 871
    12  com.apple.CalendarStore 
    0x000000011f0ca94b -[CalCalendarStore(CalCalendarStore_Private) groups] + 348
    13  com.apple.calendar.iaplugin 
    0x0000000122a3d530 0x122a3b000 + 9520
    14  com.apple.internetaccounts  
    0x000000010e2ea377 0x10e2e7000 + 13175
    15  com.apple.internetaccounts  
    0x000000010e2e9339 0x10e2e7000 + 9017
    16  libdispatch.dylib       
    0x00000001127ac1bb _dispatch_call_block_and_release + 12
    17  libdispatch.dylib       
    0x00000001127a928d _dispatch_client_callout + 8
    18  libdispatch.dylib       
    0x00000001127ab082 _dispatch_root_queue_drain + 326
    19  libdispatch.dylib       
    0x00000001127ac177 _dispatch_worker_thread2 + 40
    20  libsystem_pthread.dylib 
    0x0000000112a87ef8 _pthread_wqthread + 314
    21  libsystem_pthread.dylib 
    0x0000000112a8afb9 start_wqthread + 13
    Thread 8:: Dispatch queue: com.apple.root.default-priority
    0   libsystem_kernel.dylib  
    0x000000011297aa56 semaphore_wait_trap + 10
    1   libdispatch.dylib       
    0x00000001127ad9f9 _dispatch_semaphore_wait_slow + 206
    2   com.apple.Notes.framework
    0x00000001229987d0 -[NFNotesMigratorClient sync_importMailAccounts] + 449
    3   com.apple.Notes.iaplugin
    0x0000000122951de7 0x122950000 + 7655
    4   com.apple.internetaccounts  
    0x000000010e2ea377 0x10e2e7000 + 13175
    5   com.apple.internetaccounts  
    0x000000010e2e9339 0x10e2e7000 + 9017
    6   libdispatch.dylib       
    0x00000001127ac1bb _dispatch_call_block_and_release + 12
    7   libdispatch.dylib       
    0x00000001127a928d _dispatch_client_callout + 8
    8   libdispatch.dylib       
    0x00000001127ab082 _dispatch_root_queue_drain + 326
    9   libdispatch.dylib       
    0x00000001127ac177 _dispatch_worker_thread2 + 40
    10  libsystem_pthread.dylib 
    0x0000000112a87ef8 _pthread_wqthread + 314
    11  libsystem_pthread.dylib 
    0x0000000112a8afb9 start_wqthread + 13
    Thread 9:: Dispatch queue: com.apple.root.default-priority
    0   libsystem_kernel.dylib  
    0x000000011297ab16 syscall_thread_switch + 10
    1   libsystem_platform.dylib
    0x0000000112a6ddf6 _OSSpinLockLockSlow + 63
    2   libsystem_malloc.dylib  
    0x00000001129f82e3 szone_malloc_should_clear + 96
    3   libsystem_malloc.dylib  
    0x00000001129fa868 malloc_zone_malloc + 71
    4   libsystem_malloc.dylib  
    0x00000001129fb27c malloc + 42
    5   libsystem_blocks.dylib  
    0x0000000112855538 _Block_copy_internal + 236
    6   com.apple.CoreData      
    0x0000000110f8c374 generateAccessor + 148
    7   com.apple.CoreData      
    0x0000000110f889fc +[NSManagedObject(_PFDynamicAccessorsAndPropertySupport) resolveInstanceMethod:] + 6140
    8   libobjc.A.dylib         
    0x00000001100fcc21 _class_resolveInstanceMethod(objc_class*, objc_selector*, objc_object*) + 76
    9   libobjc.A.dylib         
    0x00000001101022c8 lookUpImpOrForward + 286
    10  libobjc.A.dylib         
    0x00000001100f5169 objc_msgSend + 233
    11  com.apple.CalendarStore 
    0x000000011f0c4434 +[CalGroup(CreationFromManagedObject) groupFromManagedObject:] + 871
    12  com.apple.CalendarStore 
    0x000000011f0ca94b -[CalCalendarStore(CalCalendarStore_Private) groups] + 348
    13  com.apple.reminders.iaplugin
    0x0000000122a525d0 0x122a50000 + 9680
    14  com.apple.internetaccounts  
    0x000000010e2ea377 0x10e2e7000 + 13175
    15  com.apple.internetaccounts  
    0x000000010e2e9339 0x10e2e7000 + 9017
    16  libdispatch.dylib       
    0x00000001127ac1bb _dispatch_call_block_and_release + 12
    17  libdispatch.dylib       
    0x00000001127a928d _dispatch_client_callout + 8
    18  libdispatch.dylib       
    0x00000001127ab082 _dispatch_root_queue_drain + 326
    19  libdispatch.dylib       
    0x00000001127ac177 _dispatch_worker_thread2 + 40
    20  libsystem_pthread.dylib 
    0x0000000112a87ef8 _pthread_wqthread + 314
    21  libsystem_pthread.dylib 
    0x0000000112a8afb9 start_wqthread + 13
    Thread 10:
    0   libsystem_kernel.dylib  
    0x000000011297ee6a __workq_kernreturn + 10
    1   libsystem_pthread.dylib 
    0x0000000112a87f08 _pthread_wqthread + 330
    2   libsystem_pthread.dylib 
    0x0000000112a8afb9 start_wqthread + 13
    Thread 11:
    0   libsystem_kernel.dylib  
    0x000000011297ee6a __workq_kernreturn + 10
    1   libsystem_pthread.dylib 
    0x0000000112a87f08 _pthread_wqthread + 330
    2   libsystem_pthread.dylib 
    0x0000000112a8afb9 start_wqthread + 13
    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
    Logical CPU:
    0
    Error Code: 
    0x02000148
    Trap Number:
    133
    I do not know if these data help me
    Need to solve it alone. Technical support of apple me my city is horrible. 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 "google translator english". And Thank you so much!

    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.

  • 8530 White Screen AFTER Installing a new Screen

    Hi, my dog got hold of my 8530 and put a toothmark in the screen cover. The screen was also damaged meaning I could see white and grey stripes. I bought a new screen and replaced the old one. Now when I turn it on, I get the white screen and i cannot dial out or recieve calls. Basically the phone is dead. I was able to connect to my desktop and install the latest OS version. I put the old screen back in and I still cannot recieve or dial. I must have done something while taking it apart or putting back together? It is a very simple procedure so I would think it difficult to screw it up. Before I took it apart, i could get phone calls and dial out but i couldnt see the outgoing or incoming call screen. I took the battery out before I took it apart. Now when I connect to my desktop, the connection comes and goes as if you were plugging and plugping in the device. Any sugesstions would be greatly appreciated!!!
    Thanks!
    M

    Hello monkster926,
    Sorry about your condition, well I don't think it a good decision that you made by Replacing the Screen Cover
    by yourself unless and until you are qualified for it , cause you can't see the internal damage it suffered  from
    the dog bit  cause the force at which they bit are much more for example G.Shepherd produces over 238 pounds
    of force or a pitbull which produces over 235 pounds of force.
                 So now I think it is not just a software issue but a hardware issue and it will be better if you go and checked
    it by an authorized  BB Service Center.
    Good Luck
    Click " Like " if you want to Thank someone.
    If Problem Resolves mark the post(s) as " Solution ", so that other can make use of it.

  • After installing plug-ins, FCPX crashes, constantly.

    I recently installed fxfactory plug-ins.  After clicking on one during an editing session, FCPX started crashing.  I have removed the FCPX preferences and attempted to use it again, with the same, crashing, result.  
    I was forced to use iMovie to complete the project that had been open when FCPX began crashing.
    I have heard that fxfactory plug-ins are stable, but something seems to have gone awry in my situation.
    How can I regain control of my FCPX software?

    Trash your preferences. Repair permissions. Reboot. Hide all events and projects from FCP and then launch the application. Does it crash?
    If yes, contact an Apple service technician. If no, close the app, trash the event render files. Put the events back where they belong. Launch the application. Does it crash?
    If yes, report back. If no, close the application. Trash all the project render files and put the projects back where they belong. Launch the application. Does it crash?
    If yes, report back.

Maybe you are looking for