Confirm head crash?

I have a 2.16 GHz, 2nd-gen black MacBook. I bought it last January at a reseller in Korea while on a short visit there.
I live in Japan now. The last head crash was in May, and I managed to find a PC support company nearby that replaced my hard drive under warranty. Unfortunately, I lost five month's worth of data.
And now this again. I'm not too sure this time, though - the last time, the clicks were distinct. This time, though it makes a very small grinding noise at regular intervals, it doesn't click. This happened after my Ubuntu system ran a disk check. After returning a screenful of errors, the disk check stalled. When I rebooted, it got stuck on the gray screen. PRAM reset didn't work, either.
Plugging in my external drive with OS X Leopard installed didn't work while the internal disk was still inside. I've taken out the internal disk and put it in the freezer for now.
I had backed up my data, but had temporarily erased it to make room for my dad's stuff while he reinstalled his system. Horrible timing. Among other things, I lost the TeX file for a 90-page document I wrote.
I'm fed up with this. Is this an inherent problem with MacBooks? I keep my laptop on my desk all day; it hasn't traveled outside since I bought it in January. Our house is air-conditioned pretty well so temperature shouldn't have been a problem. Both times, it was the internal drive that went. This seems to be happening with any drive that I put in the MacBook.
What's the policy on refunds/replacements? I read somewhere that a full refund is only possible within 14 days of purchase, but could I get a refund from the reseller? If it's true that this MacBook likes to eat hard drives, then it's practically useless. And I've only used it for eight months!
I would really appreciate advice and information.

Yes the reseller had a stock of the older MacBooks they were trying to get rid of for a lower price. At the time, I thought it was a bargain, but as it turns out, buying a 2nd-gen wasn't such a good idea.
Yesterday, I took the drive out of the freezer to see if it would be recognized. Not much luck, as it made the same sounds it had before, eventually beginning to screech; I presume that would be the head gouging into the platters. gparted (Linux partition editor) managed to see the partitions, though, as well as a few directories - for five seconds before conking out again.
Could it be that it's because this drive isn't Apple-specific? I purchased it off of OWC, but it doesn't have the apple logo on it.
Yes, it's difficult to get much support here - I don't know the language, and the Japanese do not know much English. It took a while to find the PC support center in Osaka (the nearest Genius Bar is in Tokyo, and even that's several hours away by Shinkansen).
If I send this in to Apple for a repair or refund, do I have to send the broken drive? Last time, the Japanese repair person said he'd return it along with the new drive, but for some reason it didn't come back. I'd like to keep it and open it up..
Also, during the last repair, he asked me for the laptop's serial number. When I told him, he said something about it being purchased in mid-2007, which isn't exactly true. I guess that's because it was imported, but would they change that to January if I fax/email them the receipt?
Thanks for your responses so far!
Message was edited by: undefined117

Similar Messages

  • Text type on Confirmation header

    Hi! Does anyone know whether it is possible to configure the text type on the Confirmation Header, under Documents?
    Basically, we have turned on confirmation approval and if we reject a confirmation, we will be given a choice to enter the rejection reason code and some texts. I noticed that there are 2 text types - Internal Note and Rejection Notification. Ideally, it makes more sense to Rejection Notification. However, this is not the default text type on the screen and to make it more user friendly, we are hoping that we can change the default text type to Rejection Notification.
    Appreciate any advice on the above.
    Cheers!
    Siow Fong

    Hi,
    You can change the description for the STandard Text in SPRO.
    SPRO>SUPPLIER RELATIONSHIP MANAGEMENT>CROSS APPLICATION SETTINGS-->TEXT SCHEMA
    BR,
    Disha.
    Pls reward points for useful answers

  • Flash player Crashes every time 3 items or more running...

    Since I updated to Flash Player 11,7,700,169 every time 3 or more Flash player items run, Flash Player crashes.
    This happens in either Firefox or IE!
    Eg.If the problem occurs in Firefox when I also have IE open then it affects IE & Vice Versa...
    Is there a fix for this as it's becoming ridiculous now with the amount of crashes happening?
    My system:
    Acer Aspire 7735Z
    Intel Pentium Duo T4200 2.0Ghz
    Ram: 4Gb
    Windows 8 Pro 64bit
    Installed Browsers:
    Internet Explorer Version 10.0.9200.16540 Update Versions: 10.0.4
    Firefox 20.0.1
    Screenshot of dump file attached...
    regards,
    John
    Dump Summary
    Dump File:    446db98f-8bbe-4954-9378-0b450c27034e-flash2.dmp : C:\Users\John\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending\446db98f-8bbe-4954-9378-0b450c27034e-flash2.dmp
    Last Write Time:    06/05/2013 22:39:46
    Process Name:    FlashPlayerPlugin_11_7_700_169.exe : C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerPlugin_11_7_700_169.exe
    Process Architecture:    x86
    Exception Code:    not found
    Exception Information:   
    Heap Information:    Not Present
    System Information
    OS Version:    6.2.9200
    CLR Version(s):   
    Modules
    Module Name    Module Path    Module Version
    FlashPlayerPlugin_11_7_700_169.exe    C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerPlugin_11_7_700_169.exe    11.7.700.169
    ntdll.dll    C:\Windows\System32\ntdll.dll    6.2.9200.16420
    kernel32.dll    C:\Windows\System32\kernel32.dll    6.2.9200.16384
    KERNELBASE.dll    C:\Windows\System32\KERNELBASE.dll    6.2.9200.16451
    wininet.dll    C:\Windows\System32\wininet.dll    10.0.9200.16540
    crypt32.dll    C:\Windows\System32\crypt32.dll    6.2.9200.16384
    oleaut32.dll    C:\Windows\System32\oleaut32.dll    6.2.9200.16384
    imm32.dll    C:\Windows\System32\imm32.dll    6.2.9200.16384
    user32.dll    C:\Windows\System32\user32.dll    6.2.9200.16420
    advapi32.dll    C:\Windows\System32\advapi32.dll    6.2.9200.16384
    shell32.dll    C:\Windows\System32\shell32.dll    6.2.9200.16548
    ole32.dll    C:\Windows\System32\ole32.dll    6.2.9200.16451
    shlwapi.dll    C:\Windows\System32\shlwapi.dll    6.2.9200.16384
    userenv.dll    C:\Windows\System32\userenv.dll    6.2.9200.16384
    urlmon.dll    C:\Windows\System32\urlmon.dll    10.0.9200.16537
    winmm.dll    C:\Windows\System32\winmm.dll    6.2.9200.16384
    psapi.dll    C:\Windows\System32\psapi.dll    6.2.9200.16384
    secur32.dll    C:\Windows\System32\secur32.dll    6.2.9200.16384
    mpr.dll    C:\Windows\System32\mpr.dll    6.2.9200.16384
    gdi32.dll    C:\Windows\System32\gdi32.dll    6.2.9200.16433
    winspool.drv    C:\Windows\System32\winspool.drv    6.2.9200.16384
    comdlg32.dll    C:\Windows\System32\comdlg32.dll    6.2.9200.16384
    msvcrt.dll    C:\Windows\System32\msvcrt.dll    7.0.9200.16384
    rpcrt4.dll    C:\Windows\System32\rpcrt4.dll    6.2.9200.16384
    iertutil.dll    C:\Windows\System32\iertutil.dll    10.0.9200.16540
    msasn1.dll    C:\Windows\System32\msasn1.dll    6.2.9200.16384
    combase.dll    C:\Windows\System32\combase.dll    6.2.9200.16420
    msctf.dll    C:\Windows\System32\msctf.dll    6.2.9200.16496
    sechost.dll    C:\Windows\System32\sechost.dll    6.2.9200.16384
    profapi.dll    C:\Windows\System32\profapi.dll    6.2.9200.16384
    WINMMBASE.dll    C:\Windows\System32\WINMMBASE.dll    6.2.9200.16384
    comctl32.dll    C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9200.16384_ none_bf100cd445f4d954\comctl32.dll    5.82.9200.16384
    sspicli.dll    C:\Windows\System32\sspicli.dll    6.2.9200.16420
    CRYPTBASE.dll    C:\Windows\System32\CRYPTBASE.dll    6.2.9200.16384
    SHCore.dll    C:\Windows\System32\SHCore.dll    6.2.9200.16433
    bcryptPrimitives.dll    C:\Windows\System32\bcryptPrimitives.dll    6.2.9200.16384
    uxtheme.dll    C:\Windows\System32\uxtheme.dll    6.2.9200.16537
    pcContextHook_DSR.dll    C:\Program Files (x86)\Common Files\Motive\pcContextHook_DSR.dll    7.1.0.5
    dwmapi.dll    C:\Windows\System32\dwmapi.dll    6.2.9200.16384
    setupapi.dll    C:\Windows\System32\setupapi.dll    6.2.9200.16496
    cfgmgr32.dll    C:\Windows\System32\cfgmgr32.dll    6.2.9200.16384
    devobj.dll    C:\Windows\System32\devobj.dll    6.2.9200.16384
    ntmarta.dll    C:\Windows\System32\ntmarta.dll    6.2.9200.16384
    NPSWF32_11_7_700_169.dll    C:\Windows\System32\Macromed\Flash\NPSWF32_11_7_700_169.dll    11.7.700.169
    version.dll    C:\Windows\System32\version.dll    6.2.9200.16384
    dsound.dll    C:\Windows\System32\dsound.dll    6.2.9200.16384
    ws2_32.dll    C:\Windows\System32\ws2_32.dll    6.2.9200.16384
    mscms.dll    C:\Windows\System32\mscms.dll    6.2.9200.16384
    powrprof.dll    C:\Windows\System32\powrprof.dll    6.2.9200.16384
    nsi.dll    C:\Windows\System32\nsi.dll    6.2.9200.16384
    clbcatq.dll    C:\Windows\System32\clbcatq.dll    2001.12.10130.16384
    mlang.dll    C:\Windows\System32\mlang.dll    6.2.9200.16384
    MMDevAPI.dll    C:\Windows\System32\MMDevAPI.dll    6.2.9200.16420
    AudioSes.dll    C:\Windows\System32\AudioSes.dll    6.2.9200.16451
    d3d9.dll    C:\Windows\System32\d3d9.dll    6.2.9200.16384
    igdumd32.dll    C:\Windows\System32\igdumd32.dll    8.15.10.2702
    wintrust.dll    C:\Windows\System32\wintrust.dll    6.2.9200.16420
    mswsock.dll    C:\Windows\System32\mswsock.dll    6.2.9200.16433
    dnsapi.dll    C:\Windows\System32\dnsapi.dll    6.2.9200.16420
    rasadhlp.dll    C:\Windows\System32\rasadhlp.dll    6.2.9200.16384
    IPHLPAPI.DLL    C:\Windows\System32\IPHLPAPI.DLL    6.2.9200.16420
    winnsi.dll    C:\Windows\System32\winnsi.dll    6.2.9200.16384
    FWPUCLNT.DLL    C:\Windows\System32\FWPUCLNT.DLL    6.2.9200.16465
    cryptsp.dll    C:\Windows\System32\cryptsp.dll    6.2.9200.16384
    rsaenh.dll    C:\Windows\System32\rsaenh.dll    6.2.9200.16384
    dxva2.dll    C:\Windows\System32\dxva2.dll    6.2.9200.16384
    comctl32.dll    C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16384_n one_893961408605e985\comctl32.dll    6.10.9200.16384
    avrt.dll    C:\Windows\System32\avrt.dll    6.2.9200.16420

    Hi Chris,
    I'm not the original reporter, but I can confirm IE9 crashes in my wife's Windows 7 computer every time, on this site: http://dk.timefor.tv after latest update. Whenever she presses the "TV-Guide" link, it'll crash. It also happens if she opens the http://dk.timefor.tv/tv-guide directly, but in that case not until she leaves the page or closes the browser. Other sites are not quite as consistent, but after the update she sees a _lot_ of crashes, to the point that she's had to disable the plugin and use Chrome for sites using Flash instead.
    IE9 in my own computer doesn't have the same problem (Both are 64-bit Windows 7, her computer is a T420 with a Core i5-2410M and 4 GB RAM).
    I'm sending you the dump now (John, please note that you need to use -f * instead of -f "" to actually get it to create the dump, -f "" just shows that there was an exception, it wont dump it).
    A funny thing I noticed is that her add-on manager thought that the plugin was 10.x (can't remember the exact version), even though more information said that the file was "Flash32_11_7_700_169.ocx" until I completely removed the Flash plugin installation and installed it again. However, the crash persists, even though the version is correct now (the dump is from the freshly installed version).
    Another difference I saw between our machines was that the Flash updater on my PC did not require IE to be closed, but hers did, both when trying to re-update and doing the fresh install.
    Best regards,
    Dennis Du Krøger

  • (PC and Surface 8.1)bad pool header error: remote debugging using ARM device

    Tools used:
    Microsoft Visual Studio Professional 2013
    Remote Debugger Monitor (Surface RT 8.1)
    I have successfully activated the developer license as administrator.
    I have attempted to run the test app on remote device but my pc crashes before or when reaching certification.
    So far, I have attempted to run an app software for the ARM device; however, ever since I have upgraded the surface to 8.1, I constantly get the bad pool header crash, even after successfully connecting the pc to rt device.
    is there any way I can resolve the issue so I can successfully to remote debugging?
    any help is appreciated.

    Hi,
    Considering that the issue should be related to Windows RT 8.1, and  Since we have limited testing environment, I suggest you submit a new case on Windows RT forum as they will be more professional on your issue:
    This is the Windows RT 8.1 forum link.
    http://answers.microsoft.com/en-us/windows/forum/windowsrt8_1?sort=lastreplydate&dir=desc&tab=Threads&status=&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&tm=1392101458999
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.  Thank you for your understanding.
    Regards,
    Kelvin hsu
    TechNet Community Support

  • Issue in setting IBASE component of service confirmation item

    Hello Experts,
                   I am facing a problem while creating a service confirmation item with reference to Service order items.  I am using CRM_ORDER_MAINTAIN
    bapi.  Issue is in the Ibase component of the service confirmation items as it is always taking the Ibase component of Confirmation Header even though
    i am explicitly passing the Ibase component of service conf item of  with IT_SERVICE_OS parameter. I am making sure that i fill up MARKED_OBJECT correctly.
    in CRMD_ORDER  i can see the Ibase component of  header and item both but Header one is the marked as main reference object.
    Any idea why Component can not be set explicitly for for service confirmation item.

    To achieve the above, try the below fix:
    var buttonBar:ButtonBar = new ButtonBar();
    buttonBar.requireSelection = true;
    Hopefully this works for you . Cheers!!

  • How can I get my data out of a crashed drive?

    I need help. Crashed hard drive. How can I get the data out?

    First have to define what a 'crashed drive' is, so we'll know how to respond.
    If you boot to an installer DVD does Disk Utility see the drive? What does it tell you about the drive?
    If the drive is showing up but not mounting it may be possible to repair it and get the data off yourself -
    But if it isn't even showing up then you may need to take it to a recovery specialist to get the data off it. This is costly and not guaranteed to always work.
    Did you replace the drive in the MBP and install a new OS on a new drive?
    Or is it still in the MBP and you are trying to recover it from there?
    One type of 'crash' is a head crash, usually caused by a impact or jarring to the drive while it is spinning which bounces the heads off the platters. This removes some of the magnetic media off the platters typically rendering it unrecoverable.
    So first priority is tell us precisely where you are with this drive, what you see, what you have tried, what the symptoms are, and what you need to accomplish.
    Rick

  • Abiword 3.0 - crash when save as pdf

    Recently I have upgraded Abiword to 3.0. When save a document in pdf format Abiword crashes and leaves 2 files in the directory:
    .gsf-save-XXXXXX
    documentname.abw.saved
    Is it an issue with the new 3.0 version or something is wrong with my system? In previous version the pdf conversion worked fine. Thanks!

    Abiword 3.0 is a mess!
    I can confirm abiword crashes when trying to save a document as *.pdf on 3.12.7-2-ARCH x86_64 + i686 + 3.8.13.1-1-ARCH armv7l, GNU/Linux, Openbox, LXDE.
    Furthermore the top ruler is covered by a grey bar as soon as you click into the text window so you cannot use tabulators nor indentation. (Bugzilla Bug 13582)
    The system wide theme and appearance settings are ignored and abiword appears in a very ugly GTK standard theme.
    Seems like abiword 3.0 has inherited all the long known bugs from its 2.9.X antecessors.
    IMHO it was a bad decision to put abiword 3.0 into the repositorys as it is unstable and buggy.
    The only way is to downgrade to last stable 2.8.6-9 version until abiword becomes usable again.
    EDIT: Another annoying bug: *.odt files created and saved with abiword 2.8.X cannot be opened with abiword 3.X!!
    Last edited by renegat (2014-02-03 00:35:12)

  • Skype 6.20 Windows XP SP3 crashes at launch

    I upgraded from Skype 6.old to 6.20 because I couldn't log in.  Now, whenever it starts it immediately pops up a crash "Skype has encountered a problem and needs to close.".
    I have the latest updates for Windows XP SP3, no firewall, and AVG Free virus scanner that only complains about 'tracking' cookies.
    I also tried installing skype 6.13, which I had floating on another computer, but that has the same crash as skype 6.20.
    Curiously though, as long as I don't close the crash dialog, Skype appears to work normally and I can use every feature, including webcams.
    The report in the event viewer is as follows:
    Spoiler (Highlight to read)
    Event Type:    Error
    Event Source:    Application Error
    Event Category:    None
    Event ID:    1000
    Date:        2014-09-28
    Time:        11:45:56
    User:        N/A
    Computer:    ZOM-B-LAPTOP
    Description:
    Faulting application skype.exe, version 6.20.32.104, faulting module skype.exe, version 6.20.32.104, fault address 0x00c079fe.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 6c707041 74616369 206e6f69 6c696146
    0010: 20657275 796b7320 652e6570 36206578
    0020: 2e30322e 312e3233 69203430 6b73206e
    0030: 2e657079 20657865 30322e36 2e32332e
    0040: 20343031 6f207461 ****************
    0050: 39373063 0a0d6566
    Event Type:    ErrorEvent Source:    Application ErrorEvent Category:    NoneEvent ID:    1000Date:        2014-09-28Time:        11:45:56User:        N/AComputer:    ZOM-B-LAPTOPDescription:Faulting application skype.exe, version 6.20.32.104, faulting module skype.exe, version 6.20.32.104, fault address 0x00c079fe.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 6c707041 74616369 206e6f69 6c6961460010: 20657275 796b7320 652e6570 362065780020: 2e30322e 312e3233 69203430 6b73206e0030: 2e657079 20657865 30322e36 2e32332e0040: 20343031 6f207461 ****************0050: 39373063 0a0d6566

    dakeyras wrote:
    I have the same problem.
    Windows XP SP3.
    No real-time antivirus but PC scanned periodically, 100% virus free.
    No firewall.
    Skype worked ok until last month (version 6.5).
    Now, I can't connect and I need to update.
    Tried all the latest versions: 6.18, 6.19, 6.20.
    Skype crashes on startup with a KERNEL32 error message.
    If I not confirm the crash report, skype seems to go online, but if I try to send a call or a message it does not work.
    I tried for several days: installation, remove, re-installion, clean all the file in "skype" folder, create a new user, reinstallation from the new user, reinstallation IE, reinstallation DirectX, etc.
    It is impossible to make it work.
    I need it to work and family and now I'm stuck.
    Please resolve this problem or let me the permission to use of an old version.
    Please,  run the DirectX diagnostics tool (32-bit version).
    Go to Windows Start and in the Run box type dxdiag.exe and press the OK button. This will start the DirectX diagnostics program. Run this diagnostics and save the results to a file. Please, attach this file to your post.
    Be aware that you will have to zip this file before attaching it here.

  • FCP 5.1 on Mac Pro Crashing regularly

    Dear All,
    we purchased two new Mac Pro systems each with 3Ghz Xeons, 8GB RAM, and 1Tb onboard storage with 2X 500 Gb disks. These systems are being used for Final Cut Pro Studio 5.1 and we seem to be having what seems to me to be a MAJOR issue. The systems are hanging hard when the user is using Final Cut Pro. The user is not doing anything complicated or out of the ordinary, The usual tasks have been done for years on the PPC architecture with only 2Gb of RAM without issue. It appears from the panic logs in the system that the kernel is panicing after reaching a 32bit limit for addressing memory. Please correct me if I'm wrong but OSX is 64bit and the new MacIntel hardware is supposed to be 64 bit as well so why are we running into issues when trying address memory above the 32bit limit??? I've cut and paste the panic data below for your perusal. From first glance, it looks like the problem MAY be related to the decklink driver but I am unsure. Please give me some insigh t as to what I can do to make these systems stable. They are hanging at least once an hour while the operators are trying to work.
    Could you please advise?
    Thanks a million
    Waddah

    At some future moment they may decide to draw the line and move everything to 64bit - but for the time being - FCP remains mostly 32 bit.
    Did you ever figure this out? If so, please post the solution.
    If you didn't, please post the error log - just the section that is headed "crashed thread'.
    x

  • Table for Confirmation numbers

    Hi
    Can any one provide the Table exclusive which show the Operation number and Confirmation numbers for a given Order.
    Provide Table other than AFRU and AFVC .
    AFVC does not have the input field AUFNR (Production Order)
    AFRU only prodes the completed Confirmation for order.
    Need Exclusive information for list of confirmation numbers and Operation number for given production order with
    Thanks and Regards
    Chakrapani

    Dear
    Please check the following table :
    AFVC          Order Operations Detail
    AFRU          Order Completion Confirmations
    AFRH          Confirmations -- Header Info for Confirmation Pool
    AFRV          Confirmation Pool
    You have beutful reports like COOIS-Sleect Operation -Select Standard Profile -Enter Order Type and Plant -Exectute -It will list down all the operation with confoirmation number .You can also select Order hedares -Standrad Profile  and proceedd in the same way , it will list order details.Goto Select Lay out -Change lay out -Select the Display column and DragConfirmation field  from hidden column  to display in the list and SAVE.
    Beside that you can try COHV /CO46  to get the details
    Regards
    JH

  • ITunes 11.1 crashing with no activity

    Over the last 3 days, iTunes 11.1 has crashed a total of 7 times. All crashes happened when my iMac was idle, and I was away. I always leave iTunes running in the background, and when I come back, and if it's not running, I check the logs using the Console utility and confirm it crashed.
    Does anyone know what's going on?
    Attached is a sample console log crash dump
    Process:         iTunes [22057]
    Path:            /Applications/iTunes.app/Contents/MacOS/iTunes
    Identifier:      com.apple.iTunes
    Version:         11.1 (11.1)
    Build Info:      iTunes-1111011001000126~1
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [285]
    User ID:         501
    Date/Time:       2013-09-29 18:20:08.924 -0700
    OS Version:      Mac OS X 10.8.5 (12F37)
    Report Version:  10
    Crashed Thread:  0  iTunes main  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: EXC_I386_GPFLT
    Thread 0 Crashed:: iTunes main  Dispatch queue: com.apple.main-thread
    0   com.apple.iTunes                        0x0000000106a2ffef 0x105f15000 + 11644911
    1   com.apple.iTunes                        0x0000000106a2cca4 0x105f15000 + 11631780
    2   com.apple.iTunes                        0x0000000106ce5ddf 0x105f15000 + 14487007
    3   com.apple.iTunes                        0x0000000106ce5299 0x105f15000 + 14484121
    4   com.apple.iTunes                        0x00000001060975cd 0x105f15000 + 1582541
    5   com.apple.iTunes                        0x0000000105f6316b 0x105f15000 + 319851
    6   com.apple.iTunes                        0x000000010607b8be 0x105f15000 + 1468606
    7   com.apple.iTunes                        0x000000010607b7b6 0x105f15000 + 1468342
    8   com.apple.iTunes                        0x000000010607b758 0x105f15000 + 1468248
    9   com.apple.iTunes                        0x0000000105f63012 0x105f15000 + 319506
    10  com.apple.iTunes                        0x0000000105f62ecc 0x105f15000 + 319180
    11  com.apple.iTunes                        0x0000000105f62e29 0x105f15000 + 319017
    12  com.apple.CoreFoundation                0x00007fff8911eb31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
    13  com.apple.CoreFoundation                0x00007fff8911e455 __CFRunLoopDoSources0 + 245
    14  com.apple.CoreFoundation                0x00007fff891417f5 __CFRunLoopRun + 789
    15  com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    16  com.apple.HIToolbox                     0x00007fff84425eb4 RunCurrentEventLoopInMode + 209
    17  com.apple.HIToolbox                     0x00007fff84425c52 ReceiveNextEventCommon + 356
    18  com.apple.HIToolbox                     0x00007fff84425ae3 BlockUntilNextEventMatchingListInMode + 62
    19  com.apple.AppKit                        0x00007fff837f8533 _DPSNextEvent + 685
    20  com.apple.AppKit                        0x00007fff837f7df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
    21  com.apple.AppKit                        0x00007fff837ef1a3 -[NSApplication run] + 517
    22  com.apple.iTunes                        0x00000001060c69e7 0x105f15000 + 1776103
    23  com.apple.iTunes                        0x00000001060c6870 0x105f15000 + 1775728
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib                  0x00007fff854e5d16 kevent + 10
    1   libdispatch.dylib                       0x00007fff8a2e9dea _dispatch_mgr_invoke + 883
    2   libdispatch.dylib                       0x00007fff8a2e99ee _dispatch_mgr_thread + 54
    Thread 2:: Dispatch queue: com.apple.root.default-priority
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.mobiledevice                  0x000000010c4ab701 __thr_AMRegisterForCallbacks + 217
    7   libdispatch.dylib                       0x00007fff8a2e70b6 _dispatch_client_callout + 8
    8   libdispatch.dylib                       0x00007fff8a2e81fa _dispatch_worker_thread2 + 304
    9   libsystem_c.dylib                       0x00007fff83451cdb _pthread_wqthread + 404
    10  libsystem_c.dylib                       0x00007fff8343c191 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff854e50fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff83453fb9 _pthread_cond_wait + 869
    2   com.apple.iTunes                        0x0000000105f2e298 0x105f15000 + 103064
    3   com.apple.iTunes                        0x0000000105f2dd5d 0x105f15000 + 101725
    4   com.apple.iTunes                        0x0000000105f2d73c 0x105f15000 + 100156
    5   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    6   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    7   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 5:: com.apple.CFSocket.private
    0   libsystem_kernel.dylib                  0x00007fff854e5322 __select + 10
    1   com.apple.CoreFoundation                0x00007fff89180f46 __CFSocketManager + 1302
    2   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    3   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 6:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x0000000105f520f0 0x105f15000 + 250096
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 7:
    0   libsystem_kernel.dylib                  0x00007fff854e50fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff83453fb9 _pthread_cond_wait + 869
    2   com.apple.iTunes                        0x0000000105f2e298 0x105f15000 + 103064
    3   com.apple.iTunes                        0x0000000105f52017 0x105f15000 + 249879
    4   com.apple.iTunes                        0x0000000106070f6e 0x105f15000 + 1425262
    5   com.apple.iTunes                        0x0000000106070eb9 0x105f15000 + 1425081
    6   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    7   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    8   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 8:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.iTunes                        0x000000010607b933 0x105f15000 + 1468723
    3   com.apple.iTunes                        0x0000000105f6331d 0x105f15000 + 320285
    4   com.apple.iTunes                        0x000000010607c3bf 0x105f15000 + 1471423
    5   com.apple.iTunes                        0x0000000106167554 0x105f15000 + 2434388
    6   com.apple.iTunes                        0x0000000106c51b9b 0x105f15000 + 13880219
    7   com.apple.iTunes                        0x000000010606f54f 0x105f15000 + 1418575
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 9:
    0   libsystem_kernel.dylib                  0x00007fff854e4996 __accept + 10
    1   com.apple.iTunes                        0x0000000106b20ba7 0x105f15000 + 12630951
    2   com.apple.iTunes                        0x0000000106b06f93 0x105f15000 + 12525459
    3   com.apple.iTunes                        0x0000000106b06ed6 0x105f15000 + 12525270
    4   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    5   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    6   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 10:
    0   libsystem_kernel.dylib                  0x00007fff854e4996 __accept + 10
    1   com.apple.iTunes                        0x0000000106b20ba7 0x105f15000 + 12630951
    2   com.apple.iTunes                        0x0000000106b06f93 0x105f15000 + 12525459
    3   com.apple.iTunes                        0x0000000106b06ed6 0x105f15000 + 12525270
    4   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    5   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    6   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 11:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 12:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 13:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 14:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 15:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 16:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 17:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 18:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 19:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 20:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 21:
    0   libsystem_kernel.dylib                  0x00007fff854e50fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff83453fb9 _pthread_cond_wait + 869
    2   com.apple.iTunes                        0x0000000105f2e298 0x105f15000 + 103064
    3   com.apple.iTunes                        0x0000000106b7ca21 0x105f15000 + 13007393
    4   com.apple.iTunes                        0x00000001060e97a1 0x105f15000 + 1918881
    5   com.apple.iTunes                        0x0000000106749ea5 0x105f15000 + 8605349
    6   com.apple.iTunes                        0x0000000106751c5d 0x105f15000 + 8637533
    7   com.apple.iTunes                        0x0000000106751503 0x105f15000 + 8635651
    8   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    9   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    10  libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 22:
    0   libsystem_kernel.dylib                  0x00007fff854e50fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff83453fb9 _pthread_cond_wait + 869
    2   com.apple.iTunes                        0x0000000105f2e298 0x105f15000 + 103064
    3   com.apple.iTunes                        0x0000000106b7ca21 0x105f15000 + 13007393
    4   com.apple.iTunes                        0x00000001060e97a1 0x105f15000 + 1918881
    5   com.apple.iTunes                        0x0000000106749ea5 0x105f15000 + 8605349
    6   com.apple.iTunes                        0x0000000106751c5d 0x105f15000 + 8637533
    7   com.apple.iTunes                        0x0000000106751503 0x105f15000 + 8635651
    8   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    9   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    10  libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 23:
    0   libsystem_kernel.dylib                  0x00007fff854e50fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff83453fb9 _pthread_cond_wait + 869
    2   com.apple.iTunes                        0x0000000105f2e298 0x105f15000 + 103064
    3   com.apple.iTunes                        0x0000000106b7ca21 0x105f15000 + 13007393
    4   com.apple.iTunes                        0x0000000105f60fc7 0x105f15000 + 311239
    5   com.apple.iTunes                        0x0000000105f60e35 0x105f15000 + 310837
    6   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    7   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    8   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 24:
    0   libsystem_kernel.dylib                  0x00007fff854e5322 __select + 10
    1   com.apple.AirTrafficHost                0x0000000111e960de _readDictionary + 246
    2   com.apple.AirTrafficHost                0x0000000111e96892 ATProcessLinkCopyMessageFromChild + 182
    3   com.apple.AirTrafficHost                0x0000000111e9563a ATHostConnectionReadMessage + 82
    4   com.apple.iTunes                        0x00000001062340db 0x105f15000 + 3272923
    5   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    6   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    7   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 25:
    0   libsystem_kernel.dylib                  0x00007fff854e5322 __select + 10
    1   com.apple.AirTrafficHost                0x0000000111e960de _readDictionary + 246
    2   com.apple.AirTrafficHost                0x0000000111e96892 ATProcessLinkCopyMessageFromChild + 182
    3   com.apple.AirTrafficHost                0x0000000111e9563a ATHostConnectionReadMessage + 82
    4   com.apple.iTunes                        0x00000001062340db 0x105f15000 + 3272923
    5   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    6   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    7   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 26:
    0   libsystem_kernel.dylib                  0x00007fff854e50fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff83453fb9 _pthread_cond_wait + 869
    2   com.apple.iTunes                        0x0000000105f2e298 0x105f15000 + 103064
    3   com.apple.iTunes                        0x0000000106b7ca21 0x105f15000 + 13007393
    4   com.apple.iTunes                        0x0000000105f60fc7 0x105f15000 + 311239
    5   com.apple.iTunes                        0x0000000105f60e35 0x105f15000 + 310837
    6   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    7   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    8   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 27:
    0   libsystem_kernel.dylib                  0x00007fff854e50fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff83453fb9 _pthread_cond_wait + 869
    2   com.apple.iTunes                        0x0000000105f2e298 0x105f15000 + 103064
    3   com.apple.iTunes                        0x0000000106b7ca21 0x105f15000 + 13007393
    4   com.apple.iTunes                        0x0000000105f60fc7 0x105f15000 + 311239
    5   com.apple.iTunes                        0x0000000105f60e35 0x105f15000 + 310837
    6   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    7   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    8   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 28:
    0   libsystem_kernel.dylib                  0x00007fff854e50fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff83453fb9 _pthread_cond_wait + 869
    2   com.apple.iTunes                        0x0000000105f2e298 0x105f15000 + 103064
    3   com.apple.iTunes                        0x0000000106b7ca21 0x105f15000 + 13007393
    4   com.apple.iTunes                        0x0000000105f60fc7 0x105f15000 + 311239
    5   com.apple.iTunes                        0x0000000105f60e35 0x105f15000 + 310837
    6   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    7   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    8   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 29:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 30:
    0   libsystem_kernel.dylib                  0x00007fff854e50fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff83453fb9 _pthread_cond_wait + 869
    2   com.apple.iTunes                        0x0000000105f2e298 0x105f15000 + 103064
    3   com.apple.iTunes                        0x0000000106b7ca21 0x105f15000 + 13007393
    4   com.apple.iTunes                        0x0000000105f60fc7 0x105f15000 + 311239
    5   com.apple.iTunes                        0x0000000105f60e35 0x105f15000 + 310837
    6   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    7   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    8   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 31:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff8913c233 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff89141916 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff891410e2 CFRunLoopRunSpecific + 290
    5   com.apple.CoreFoundation                0x00007fff8914fdd1 CFRunLoopRun + 97
    6   com.apple.iTunes                        0x000000010607f0fa 0x105f15000 + 1483002
    7   com.apple.iTunes                        0x0000000105f1a97b 0x105f15000 + 22907
    8   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    9   libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 32:
    0   libsystem_kernel.dylib                  0x00007fff854e3686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff854e2c42 mach_msg + 70
    2   com.apple.iTunes                        0x000000010607b933 0x105f15000 + 1468723
    3   com.apple.iTunes                        0x0000000105f6331d 0x105f15000 + 320285
    4   com.apple.iTunes                        0x000000010607c3bf 0x105f15000 + 1471423
    5   com.apple.iTunes                        0x000000010609755d 0x105f15000 + 1582429
    6   com.apple.iTunes                        0x000000010607c176 0x105f15000 + 1470838
    7   com.apple.iTunes                        0x000000010607b971 0x105f15000 + 1468785
    8   com.apple.iTunes                        0x000000010606f561 0x105f15000 + 1418593
    9   libsystem_c.dylib                       0x00007fff8344f772 _pthread_start + 327
    10  libsystem_c.dylib                       0x00007fff8343c1a1 thread_start + 13
    Thread 33:
    0   libsystem_kernel.dylib                  0x00007fff854e56d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff83451f1c _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff83451ce3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff8343c191 start_wqthread + 13
    Thread 34:
    0   libsystem_kernel.dylib                  0x00007fff854e56d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff83451f1c _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff83451ce3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff8343c191 sta

    Hey all  I figured out what solved this issue for me.  It just surprises me that Apple doesn't take a more active role in these posts and chime in.  The solution for me was to remove all of my devices from iTunes that were automatically setup to sync over wifi. I had about 10 devices. I was using this feature to update apps and songs over wifi.  I like this feature because it is great for managing my children's devices.  But after I changed each one to not "sync with this iPad over Wi-FI" iTunes has been stable and no more crashes.  I am sad that I had to disable this feature but happy that iTunes is stable once again.  Hope this helps you all!

  • Fresh Install after boot drive crashed... advice needed plaese

    So wake up today turn on my tower and all I get is a grey screen and a clicking boot drive. Sounds like the other three drives are mounting fine. Or my tower is need of some Snow.
    So I know enough to say bye bye boot drive.... my question is-
    I now have purchased Snow Leopard and will start fresh. Should I take out the remaining three drives while I handle a clean install. Any advice to make this process a bit more painless? I back up all drives expect my boot UGH... I am going to start using time machine.... learned a lesson.

    There's no way to know how long a delay will be while waiting for a 'time-out'. It depends on how well or how poorly the OS is able to communicate with the drive, and how bad the controller chips on the drive are. You can view the problem as a Quality of Service issue. Your Mac is trying to communicate with the drive, determine it's size/type/format/timing etc, while also verifying the quality of the data. CRC error checking takes place along with a host of quality control measures implemented with each new version of Mac OS. Leopard made some drives fail due to poorly designed firmwares on the controller chips. SL got even pickier.
    During this process, that's failing, the problem could be any part of the driver verification system.
    On the other hand, if the drive quits spinning or the controller chips don't answer back at all, the 'time-out' will probably end sooner.
    It's luck of the draw when you try to determine the exact cause of a drive failure - controller chips, drive motor, head crash platter damage, r/w head... I just call it 'bad' and throw the drives into a bin where they will get speared with a digging bar before going to recycle

  • DM 4.5 fake crashes

    One user has started experiencing major synch problems.  I downloaded the most recent Desktop Manager, Uninstalled the old, and installed 4.5 on a couple of computers.  While synching, the program will crash, bringing up the Microsoft Error Reporter prompt to send or not send the error, but in the background, Desktop Manager is still synching data.  Once I confirm it crashed, Desktop Manager shuts down.  This happens with multiple machines synching to different BB's, all using BIS.  Logs show that everything went smoothly.  Sometimes the crash is an actual crash, and the synch is incomplete.  Once in a while, it's a fake, as the data keeps synching. 
    any ideas as to why it crashes?  (XP SP2, BB Pearl Rogers, BB 7100i Telus, DM 4.2-4.5)
    Thanks

    One user has started experiencing major synch problems.  I downloaded the most recent Desktop Manager, Uninstalled the old, and installed 4.5 on a couple of computers.  While synching, the program will crash, bringing up the Microsoft Error Reporter prompt to send or not send the error, but in the background, Desktop Manager is still synching data.  Once I confirm it crashed, Desktop Manager shuts down.  This happens with multiple machines synching to different BB's, all using BIS.  Logs show that everything went smoothly.  Sometimes the crash is an actual crash, and the synch is incomplete.  Once in a while, it's a fake, as the data keeps synching. 
    any ideas as to why it crashes?  (XP SP2, BB Pearl Rogers, BB 7100i Telus, DM 4.2-4.5)
    Thanks

  • I'm afraid Time Machine use to crash hard drives

    Now it happened again - this time a Time Machine partion on my Seagate FreeAgent 500 GB external drive is damaged.
    I can see Backups.backupdb but can't copy it on another hard drive. Restore is also impossible. There's no owner, the error message says. And the partition is marked as unwritable.
    Since I use Time Machine this is the second hard drive with troubles.
    Am I the only one with this problem?
    Cheers

    Vanderhellen wrote:
    Thanks for this hint. I wouldn't have written in this forum if I haven't tried all possibilities.
    You'd be surprised how rare that is!
    What errors did DU find that it couldn't fix?
    My Mac is running on a german system - so maybe the words are not exactly the same as in the english version after my translation.
    First error message was shown like "Disk utility can't repair, save your data immediately" - so I've tried to copy the database to another volume - which failed. In the meantime the disk is writeprotected and the error messages says: "can't copy because there is no owner".
    That sounds like the messages here: http://support.apple.com/kb/HT3275?viewlocale=de_DE
    I can usually figure out which is which by comparing the English version and picking out the handful of German words I know, but this one seems to be arranged differently than the English version. See if what you're seeing in German is the rough equivalent of +"The disk (volume name) was not repairable by this computer. it is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible."+
    If so, then your backups are corrupted and your disk may be failing.
    You can't copy TM backups via the Finder in Leopard anyway, and if they're corrupted, you probably can't copy them with the Restore tab of Disk Utility either.
    If you have a heavy-duty 3rd-party disk repair app like +Disk Warrior+ (version 4.1.1 or later), it might be able to repair them. If you don't, it's probably not worth the expense (DW is about $100 U.S.) to get it just for this.
    You might be able to reformat the drive and let TM start over, but even if that works, I don't think I'd trust my backups to it if I were you.
    The whole disaster seems to be a physical problem. Somebody in another forum is talking about that Time Machine prevents the parking of the heads - head crashes are more likely.
    Rubbish. Since Time Machine runs hourly at most, the drive isn't used most of the time. And if you'd had a head crash, the disk would be totally unusable -- DU wouldn't even see it.

  • Hard Drive Crashed - Non-Recoverable - Reasons for Crash?

    Hi, My hard drive crashed this week and was not recoverable. It was running on Tiger 10.4.
    I have since bought a new hard drive, maxxed out my RAM, installed Leopard, and am reinstalling all my apps. QUESTION: does anyone know the reasons that would cause a hard drive to crash?
    My specific concern is that I had some kind of bug in the system. If I reinstall all my old files (primarily Word docs, mp3s, and photos) will that trigger a second crash on my NEW hard drive?

    Hard drive failures are often simply random. Most times when the heads touch the platters, maybe a little bit of data is destroyed or maybe none at all. If the head crashes really hard it can do all sorts of bad things including taking out the system area (sort of the mother of all head crashes).
    There are things you can do to reduce the chances of a crash. Minimize movement of the drive when it's in operation (it's generally safe to move when the heads are parked where there's no data). Some head crashes are caused by sudden environmental changes. It's important that the breather hole in the drive isn't blocked so that it can adjust to pressure changes. The heads are flying on a cushion of air, and abrupt changes in pressure can increase the chance of a head crash.
    Of course the future may be in solid-state drives replacing hard drives for mobile applications. They're already highly resistant to shock and "best in class" SSDs outperform even the fastest 10,000 RPM mobile hard drives in read speeds.

Maybe you are looking for