MacPro keeps killing hard drives!

Hi all,
I had a search on here beforehand to see if anyone else has had this issue. I couldn't find a close match, but my apologies if I missed one.
I have an early model Mac Pro (v1.1) and last week the original hard drive (a good 6 years old) suddenly died. It was without any warning as previously the computer had been working fine. The only problem I noticed was immediately before the drive died, Firefox locked up my Mac to the point where I had to do a hard reset. When I turned the Mac back on, it would hang at the Blue screen with a spinning beachball.
I booted from the Snow Leopard install disk and did a HDD repair, where I learnt the drive was dead.
Promptly I bought a brand spanking new WD 1TB HDD, and reinstalled everything. I then tried to use a data recovery app (Disk Driller) to copy what it could off the old HDD, which was running off one of the internal SATA conenctions. This seemed to cause problems again, locking up the computer and so forth, to the point where again I had to reinstall Snow Leopard.
Now, I have the original dead 250gb HDD in an external case, attempting a restore by backing it up as a DMG to the new HDD. AGAIN, this froze over night while it was doing it's thing. Ordinarily I'd give up, but there was 30gb of photos on this drive as well as old work I wanted to keep.
SO: Now it appears my new HDD is dead.
I don't know that I've explained this very well, but here's my question. Is it possible there is something in my MacPro (software -- I'm looking at you Disk Driller!) or otherwise that is killing my HDDs?
The first HDD was getting on, so I can see how that could have died (although, it was suspiciously sudden). However, my new HDD is now only FOUR DAYS OLD and when I run Disk Utility from my install disk, it warns that the HDD has failed and to back up what I can.
Appreciate any help I can get!
Dave

AHT does not necessarily mean that a test with no error reported is a clean bill of health.
If you have a system drive that is corrupted directory it WILL or can block booting - from any device, even from DVDs.
External is fine, turn it on after boot. Turn it on after Disk Warrior is running.
And my lecture point: always have bootable backup clones and even if it was owrking it was old slow and out of warranty and your new WD Black 1TB is much faster. But then buy a data drive, one for backup too.
You should never need to reinstall an OS other than when a new OS to start clean (and use Setup Assist to import your old apps).
So play with just the new drive and leave the other to rest.
Do NOT copy data or recvover to your good drive.
Need a recovery drive for that.
you don't need to use a sparse disk image.
Most people try Data Rescue 3 demo to see if it will read and chance to recovery before buying $99.
Use Carbon Copy Cloner to make copies of your drives and be able to boot from.
http://macperformanceguide.com/Mac-HowToClone-backup.html

Similar Messages

  • I turned off my fire vault by accident and is there a way to stop it from decrypting cause that is going to take a long time and i want to keep my hard drive encrypted

    I turned off my fire vault by accident and is there a way to stop it from decrypting cause that is going to take a long time and i want to keep my hard drive encrypted.
    is there a way to stop it in the middle so it does not go through the whole process

    It's called, "FileVault." If there is no option to stop the process, then the best bet would be to wait until decrypting is finished. Otherwise you run the risk of borking the whole thing. It's hard to imagine how you can accidentally turn off FileVault.

  • IPhone kills hard drive

    My iPhone 5 did this every now and then if my phone was sitting on my MacBook Pro, on top of hard drive area, and received a call or text. Now my iPhone 5s, with newly updated firmware, keeps killing my hard drive if it is within a foot of my laptop. Does anyone know why? And how to prevent this. This is absolutely frustrating. I have to keep turning my MacBook back on and loose everything I'm working on. I have owned every iPhone and am now starting to consider venturing out because this is rediculous!

    I see, well your post is in the macbook Air forum.
    It still nevertheless wouldnt be your HD, as I have well over 100 HD,  theres never been a report in any mention in history in recollection of cellphone EMI or RFI causing shutdown of same.
    I can output 50 full watts of power from UHF and not affect a HD operation (this has been tested actually).
    cellphones put out absolutely nothing even CLOSE to this level.
    It would have to be another component in your macbook Pro.  There can only be a faulty RFI sensitive (since you now mention talking on your phone) component on the logic board.
    However even at typical peak your phone is only putting out about 200mw to 250mw of power, which is almost nothing.

  • Use of MacPro as networked hard drive for time machine

    I recently purchased a Macbook Air and would like to use one of the hard drives in my Mac Pro as the time machine backup drive via network file sharing. The issue is that time machine on the MacBook Air will only find hard drives connected via thunderbolt, usb (ect.) or time capsule devices.
    I turned on file sharing and can access all my files on my Mac Pro with my Macbook and I just copy and overwrite the files from a specific folder where I keep my school work every week. This works, but it'd be nice if it was automated.
    Thanks.
    Max

    You can use 3rd party software to automate the syncing/backup - Chronosync is one such program that I know will work and allows you to set automated backups based on time of day or automatically when  a drive is mounted.

  • My 13" black macbook keeps having hard drive failures -- I'm on my third hard drive

    The first one lasted 2 years. It failed within the special warranty period that Apple offered because so many computers like mine were also having hard drive failures. I didn't know about the special warranty they were offering, even after contacting Apple and telling them about my problem and describing the exact symptoms of the problem they were fixing for free. Thank you for that. So I went to a local store and paid ~$130 to have it fixed. This time I was paranoid about not moving my computer, and if I did have to move it, make sure it was off. Then without warning, it happens again less than 2 years later. I would expect a computer hard drive, especially one that is taken care of as well as mine, to last more ~20 months (less than 2 years) TWICE. It seems that this is a problem not with the hard drive but with the computer. I'm pretty upset that hard drives are now basically disposable -- I'm afraid to use it now unless absolutely necessary, otherwise I'll feel like I'm making its clock tick closer and closer to the next time it fries the hard drive. For as much as I paid for this computer, I expect a bit more than that. Unless there is some magical fix to this, I can safely say my next computer will be a super cheap net book.
    Does anyone have any more info on this, any ways to avoid frying more hard drives, or has any one had any luck resolving this issue with Apple? I greatly appreciate any help. Thank you!

    Mechanical hard drives have moveable parts and they are going to fail eventually. Every drive has an MTBF (Mean Time Between Failure) rating in the thousands of hours, but that is an average (half will fail sooner, half will fail later) not an absolute longevity guarantee.
    I've used an original (Apple-OEM Fujitsu 120Gb 5400rpm), a Hitachi 320Gb 7200rpm, and currently a Seagate 500Gb 7200rpm drive in my mid-2007 MacBook. I replaced the 120Gb because I was running out of room. I still use it as an external backup for certain files. The 320Gb Hitachi failed after less than two years, but had a three-year-warranty, so it was replaced at no charge. I'm using the Hitachi replacement externally to clone my current drive in order to test OS X and software updates before installing them 'for keeps' on my working system.
    A solid-state (SSD) drive might be less prone to mechanical failure, but that is still no absolute guarantee that it won't EVER fail, and SSD's are still about double or more the cost of mechanical drives. 
    The best thing is to simply be prepared for the eventual failure with a strategy for frequent and reliable backups.

  • AppleCare Keeps Your Hard Drive?

    My wife has a MacBook which stopped working. She has Apple Care. Took it in to the local Apple Store, a week later it's ready to pick up.
    They said the hard drive died and they replaced it. She asked to have the old drive back, just in case, as there are photos etc... that weren't backed up and has hope they may be recoverable.
    They absolutely refused to give her back the dead drive, the explanation being that Apple makes them send replaced hardware in as part of the Apple Care agreement "or they wouldn't make any money off Apple Care and couldn't afford to offer it anymore."
    It's after hours here so I can't talk to an Apple Customer Service Rep.
    It seems like madness that it should be my concern if Apple can profit from their warranty service.
    Anyone else had this happen to them? They told my wife she should have made recovery attempts before bringing it in, but perhaps they could have told us that when we dropped it off? Keep in mind we didn't even know what was wrong with it at the time...
    It just seems to me that the laptop and everything in it was ours at time of purchase, they have no right to hold onto it just because they were forced to honor a warranty claim.

    Kappy wrote:
    The hard drives are not returned when they are replaced. The dead drives will be returned to their manufacturer where they will be refurbished if possible. However, if the bad drive is accessible you can ask the Apple store that replaced the drive to transfer your data to the new drive. They should be able to do that for you. I've even heard that they may be willing to recover data from a corrupted drive if data are recoverable. I don't know if they do this free of charge, however.
    I can't think of any hard drive manufacturer that would actually want to refurbish a returned hard drive when it would be far cheaper to just make a new one on an assembly line than take apart an old one to repair it. What they might want a dead hard drive for is failure analysis.
    However - after Seagate's little dustup with the Apple OEM Firmware 7.01 drives, Seagate has instituted an OEM hard drive warranty program. They used to just make OEM hard drives the sole responsibility (without warranty) of the computer seller. Now they'll take back failed OEM drives during the warranty term for an exact replacement or credit towards new drive purposes.
    http://www.seagate.com/www/en-us/support/warranty&_returns_assistance/oem_warrantystatements/
    But if the old drive is completely inaccessible then your data are lost. The only chance you might have had would be to send the drive to a data recovery service. Such service is generally very expensive. However, you would have had to handle that on your own. Once you have Apple replace the drive they will keep the old drive and return it to the manufacturer.
    I noted that this would not be unique to Apple. Their warranty and AppleCare terms recommend backing up all data before sending any equipment for repair.
    You will need to talk with the store manager to see what they can do to help you. You can qalso call AppleCare and talk with a service representative. And, yes, they have every right to keep the old drive. Perhaps you should have told them you had data you needed to recover before you left the computer for the service. The door swings both ways, you know. But I think if you talk with the store manager about the situation they may be able to work something out to help you, especially if you ask nicely.
    I'm guessing that by now they have no idea where that drive would be. It's probably in a pile awaiting return to the drive manufacturer.

  • Keeping your Hard Drive tidy

    Hi Folks,
    I hope i am in the right forum to post this, apologies in advance if I am not. So after a recent Hard-drive failure I plan to treat my Mac with a bit more TLC. I have upgraded to Snow leopard, is there any utility software available to 'defrag' my Hard Drive to keep it mean and clean?
    Thanks in advance for your help.

    In addition leave your machine on 24/7 as Apple recommends in your owners manual. The only time to shut it off is if you are going to be away from it for a few days.
    OS X run's daily, weekly and monthly maintenance routines in the middle of the night. These maintenance routines are normally enough to keep your machine in good running condition.
    Of course the advice on using Time Machine is wise, this helps you in the event of a HD crash or if you accidentally delete a file. If you haven't use haven't read it before there is a FAQ Pondini, a generous poster on these forums has put together. Here is the link to it:
    http://discussions.apple.com/forum.jspa?forumID=1227
    Roger

  • 10.6.6 update killed Hard Drive - endless problems

    Like most people posting here the 10.6.6 update went fine at first, the App Store worked perfectly (of course...), then I tried to move a file to my External HDD and I got Error -36.
    I rebooted. Grey Screen with the spinning wheel never ending. Ran all sorts of Disk Utility things and various error messages came up (Signal 8, I/O ballsed-up - stuff I don't normally deal with so don't know about), then reading forums and this site in particular led to no avail. So, re-installed, losing a ton of stuff (yes, I know...). So far, so fairly pi$$ed off.
    So I'm back with 10.6 trying to update using 10.6.6 at first, then 10.6.5 (both normal and combo update) - nothing works. The Software Update fails when it tries to update before restarting, then each DMG file from Apple has an invalid checksum.
    So, for the chance to buy another version of Angry Birds I lose tons of work and my MBP is knackered.
    Can anyone suggest a next step? Merci in advance,

    That's why I'm thinking the drive really is going bad. If it can't write/read from those areas, then you're not going to get a good download unless it finds and area that has no problems.
    First, open Disk Utility and repair permissions. You'll probably see lots of things that aren't repaired. That's normal.
    Second, boot from the Install disk and repair the disk using DU.
    Then, try the update again.
    Also, on the original gray install disk that came with your computer is the Apple Hardware Test. If you boot to that disk while holding down the D key, it should start the hardware test. You can then run all the diagnostics to see if it finds anything. I haven't run them, so I'm not sure what options are available, but if it has an extensive test for the hard drive, that's probably what you want to do. But, don't exclude any other hardware tests, it could be something else interfering.
    Even if it says the Disk is OK and the SMART status in DU is Verified, the drive still could be failing.
    I had a drive that was acting up only when accessing certain files. I repaired, erased, installed, repaired, … Finally, the SMART status indicated the drive was failing. That was over several days of pulling my hair out trying to repair/restore etc. My point being it is hard to tell when/if a drive is going bad. Yours may be fine. You may suffer like I did for several days trying to get it working, eventually finding out you've been wasting your time.
    Since it sounds like you don't have a backup, you might consider purchasing an external drive, installing Snow Leopard on that, and then boot from it. If everything works fine on that, you can blame the internal drive. If it is still wonky, then there's something else going on. You've still got a good backup drive to use in the future, either way.

  • Disk installation keep crashing - Hard Drive corrupt

    Hi,
    I tried to fix a hard disk problem on my 2010 macbook pro.
    When I verify my disk with disk utility, it reports that 'The volume Macintosh HD was found corrupt and needs to be repaird'.
    So I follow the instruction by using the install disk to fix it using disk utility, however before it manage to go to the disk utility, it always crash with grey screen telling me to restart the computer.
    I cant even do clean install of the operating system, since it says that there's a bad sector.
    Can someone help me?
    thanks,
    Joseph

    Shootist007 wrote:
    If it gets bad sectors it need to be replaced.
    Then you will have to ship every drive back, because they ALL have bad sectors, it's almost impossible to not have at least one.
    The drive firmware has a system in place to map off bad sectors automatically, and one can force the issue with a zero erase procedure in special problematic cases.
    I have multiple drives in every system I have never had bad sectors showing up unless the drive is starting to fail.
    Well that's true for most people as the automatic system "**usually**" works.
    But one can have bad sectors on a brand new drive from the factory, or they can occur out of the blue and corrupt data or lose files, or can occur if the heads strike the platters.
    A zero erase cures these and it doesn't necessarily mean the drive is mechanically failing in each and every case.
    If the drive has issues after the zero erase, then yes it's time to replace the drive.
    Don't believe me, believe the drive makers
    Why would I want to Zero Fill my drive?
    The most common reasons to Zero Fill a SATA or ATA (IDE) hard drive are:
    to remove a virus that cannot be removed without destroying the boot sector.
    to change from one operating system to another and wish to remove everything from the drive.
    to erase confidential information for privacy reasons.
    to scan for bad sectors that can be detected and replaced with good spare sectors when writing to the sectors.
    By design, modern disc drives maintain spare sectors for reallocation purposes.   **Usually**, sectors become difficult to read long before they become impossible to read. In this situation the actual data bytes in the sector are preserved and transferred to the new spare during a sector reallocation. Similarly, when a disc drive writes data (like a zero fill erase procedure) and encounters a problem, the drive firmware retires the problem sector and activates a replacement before giving successful write status.
    http://knowledge.seagate.com/articles/en_US/FAQ/203931en
    Writing zeros to a drive is recommended any time an operating system is to be reinstalled on a boot drive or whenever a blank drive is desired.
    https://wdc.custhelp.com/app/answers/detail/a_id/1211/~/how-to-low-level-format- or-write-zeros-%28full-erase%29-to-a-wd-hard-drive-or-solid

  • MBP keeps crash, hard drives keep dying

    Around a year ago i purchased a lemon of a macbook pro.
    In the past 12 months the hard drive has failed twice, i am currently on hard drive number 3.
    Apple tell me that I have just had a run of bad luck.
    Now since the latest hard drive replacement, the machine simply dies / crashes for no reason - sometimes when I am not even using it.
    I have pasted a crash report below, if anyone can shed any light on this, it might help me get to the bottom of the issue. I dont believe it is a hard drive issue. I think Apple are replacing the symptom without looking for the cause.
    Thanks
    Interval Since Last Panic Report:  116385 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    5F83EDE6-4363-EDBF-45F9-8948E3BF36C5
    Tue Apr 16 07:56:13 2013
    panic(cpu 0 caller 0xffffff802b0b7e95): Kernel trap at 0xffffff802b08779c, type 14=page fault, registers:
    CR0: 0x000000008001003b, CR2: 0x0000000000001028, CR3: 0x000000002da3a000, CR4: 0x00000000000606e0
    RAX: 0x0000000000000001, RBX: 0x0000000000001000, RCX: 0xffffff804d41c000, RDX: 0x0000000000000821
    RSP: 0xffffff81fb0b3860, RBP: 0xffffff81fb0b3880, RSI: 0x0000000023ae758e, RDI: 0xffffff80300f6b88
    R8:  0x0000000000000001, R9:  0x0000000000000001, R10: 0xffffff802b6bcc20, R11: 0x0000000000000000
    R12: 0xffffff80300f6b88, R13: 0xffffff81fb0b3b00, R14: 0xffffff8069b339a0, R15: 0x000000000015a000
    RFL: 0x0000000000010206, RIP: 0xffffff802b08779c, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0x0000000000001028, Error code: 0x0000000000000000, Fault CPU: 0x0
    Backtrace (CPU 0), Frame : Return Address
    0xffffff81fb0b3500 : 0xffffff802b01d626
    0xffffff81fb0b3570 : 0xffffff802b0b7e95
    0xffffff81fb0b3740 : 0xffffff802b0cd4dd
    0xffffff81fb0b3760 : 0xffffff802b08779c
    0xffffff81fb0b3880 : 0xffffff802b081b46
    0xffffff81fb0b3bd0 : 0xffffff802b05e254
    0xffffff81fb0b3c30 : 0xffffff802b45234f
    0xffffff81fb0b3d20 : 0xffffff802b452552
    0xffffff81fb0b3d50 : 0xffffff7face56e47
    0xffffff81fb0b3d70 : 0xffffff7face57aea
    0xffffff81fb0b3db0 : 0xffffff7face53546
    0xffffff81fb0b3de0 : 0xffffff7face583e9
    0xffffff81fb0b3e10 : 0xffffff7faba822a4
    0xffffff81fb0b3e30 : 0xffffff7faba82237
    0xffffff81fb0b3e60 : 0xffffff7face51cc3
    0xffffff81fb0b3e90 : 0xffffff7face5713c
    0xffffff81fb0b3ed0 : 0xffffff7face55951
    0xffffff81fb0b3ef0 : 0xffffff802b4467a8
    0xffffff81fb0b3f30 : 0xffffff802b4452aa
    0xffffff81fb0b3f80 : 0xffffff802b4453d9
    0xffffff81fb0b3fb0 : 0xffffff802b0b2977
          Kernel Extensions in backtrace:
             com.apple.iokit.IOAcceleratorFamily(30.14)[8CAD17E4-8359-3015-BCFC-F1964357CBFE ]@0xffffff7face44000->0xffffff7face8efff
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fab666000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fabbbf000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fabb7c000
             com.apple.iokit.IOSurface(86.0.4)[C1007599-42D0-32FF-9F2F-C63F4E6C1DEB]@0xfffff f7faba7e000->0xffffff7faba8ffff
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    12D78
    Kernel version:
    Darwin Kernel Version 12.3.0: Sun Jan  6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
    Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
    Kernel slide:     0x000000002ae00000
    Kernel text base: 0xffffff802b000000
    System model name: MacBookPro8,2 (Mac-94245A3940C91C80)
    System uptime in nanoseconds: 110172536523906
    last loaded kext at 61996499270710: com.apple.filesystems.msdosfs          1.8 (addr 0xffffff7fad47d000, size 65536)
    last unloaded kext at 62843859106160: com.apple.iokit.IOUSBMassStorageClass          3.5.1 (addr 0xffffff7fad46c000, size 69632)
    loaded kexts:
    com.vmware.kext.vmnet          3.0.0
    com.vmware.kext.vmioplug          3.0.0
    com.vmware.kext.vmci          3.0.0
    com.vmware.kext.vmx86          3.0.0
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.driver.AudioAUUC          1.60
    com.apple.iokit.IOBluetoothSerialManager          4.1.3f3
    com.apple.driver.AGPM          100.12.87
    com.apple.driver.AppleMikeyHIDDriver          122
    com.apple.driver.AppleHDA          2.3.7fc4
    com.apple.kext.AMDFramebuffer          8.1.0
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AppleUpstreamUserClient          3.5.10
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.AMDRadeonAccelerator          1.0.6
    com.apple.driver.AppleMikeyDriver          2.3.7fc4
    com.apple.driver.AppleMuxControl          3.3.0
    com.apple.driver.AppleLPC          1.6.0
    com.apple.driver.AppleIntelHD3000Graphics          8.1.0
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.AppleMCCSControl          1.1.11
    com.apple.driver.AppleSMCPDRC          1.0.0
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.ApplePolicyControl          3.3.0
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.1.3f3
    com.apple.driver.AppleIntelSNBGraphicsFB          8.1.0
    com.apple.driver.AppleSMCLMU          2.0.3d0
    com.apple.driver.SMCMotionSensor          3.0.3d1
    com.apple.driver.AppleUSBTCButtons          237.1
    com.apple.driver.AppleUSBTCKeyboard          237.1
    com.apple.driver.AppleIRController          320.15
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          34
    com.apple.iokit.SCSITaskUserClient          3.5.5
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.3.1
    com.apple.driver.AppleUSBHub          5.5.5
    com.apple.driver.AppleSDXC          1.4.0
    com.apple.iokit.AppleBCM5701Ethernet          3.6.0b1
    com.apple.driver.AirPort.Brcm4331          614.20.16
    com.apple.driver.AppleFWOHCI          4.9.6
    com.apple.driver.AppleAHCIPort          2.5.1
    com.apple.driver.AppleUSBEHCI          5.5.0
    com.apple.driver.AppleEFINVRAM          1.7
    com.apple.driver.AppleSmartBatteryManager          161.0.0
    com.apple.driver.AppleACPIButtons          1.7
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleHPET          1.8
    com.apple.driver.AppleSMBIOS          1.9
    com.apple.driver.AppleACPIEC          1.7
    com.apple.driver.AppleAPIC          1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
    com.apple.nke.applicationfirewall          4.0.39
    com.apple.security.quarantine          2
    com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
    com.apple.iokit.IOSerialFamily          10.0.6
    com.apple.driver.DspFuncLib          2.3.7fc4
    com.apple.iokit.IOAudioFamily          1.8.9fc11
    com.apple.kext.OSvKernDSPLib          1.6
    com.apple.kext.triggers          1.0
    com.apple.iokit.IOSurface          86.0.4
    com.apple.iokit.IOAcceleratorFamily          30.14
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.iokit.IOBluetoothFamily          4.1.3f3
    com.apple.kext.AMD6000Controller          8.1.0
    com.apple.kext.AMDSupport          8.1.0
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.AppleHDAController          2.3.7fc4
    com.apple.iokit.IOHDAFamily          2.3.7fc4
    com.apple.driver.AppleSMBusController          1.0.11d0
    com.apple.driver.AppleSMBusPCI          1.0.11d0
    com.apple.driver.IOPlatformPluginFamily          5.3.0d51
    com.apple.driver.AppleGraphicsControl          3.3.0
    com.apple.iokit.IONDRVSupport          2.3.7
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.1.3f3
    com.apple.iokit.IOGraphicsFamily          2.3.7
    com.apple.driver.AppleSMC          3.1.4d2
    com.apple.driver.AppleThunderboltDPInAdapter          1.8.9
    com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.9
    com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.6
    com.apple.driver.AppleUSBMultitouch          237.3
    com.apple.iokit.IOUSBHIDDriver          5.2.5
    com.apple.driver.AppleUSBMergeNub          5.5.5
    com.apple.driver.AppleUSBComposite          5.2.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.5
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOAHCISerialATAPI          2.5.1
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.5
    com.apple.driver.AppleThunderboltNHI          1.6.3
    com.apple.iokit.IOThunderboltFamily          2.2.6
    com.apple.iokit.IOUSBUserClient          5.5.5
    com.apple.iokit.IOEthernetAVBController          1.0.2b1
    com.apple.iokit.IO80211Family          522.4
    com.apple.iokit.IONetworkingFamily          3.0
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOAHCIFamily          2.3.1
    com.apple.iokit.IOUSBFamily          5.5.5
    com.apple.driver.AppleEFIRuntime          1.7
    com.apple.iokit.IOHIDFamily          1.8.1
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          220.2
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.DiskImages          345
    com.apple.iokit.IOStorageFamily          1.8
    com.apple.driver.AppleKeyStore          28.21
    com.apple.driver.AppleACPIPlatform          1.7
    com.apple.iokit.IOPCIFamily          2.7.3
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0
    Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.4 GHz, 16 GB, SMC 1.69f4
    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
    Graphics: AMD Radeon HD 6770M, AMD Radeon HD 6770M, PCIe, 1024 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x04CD, 0x46412D3133333343392D3847535100000020
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x04CD, 0x46412D3133333343392D3847535100000020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.16)
    Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: TOSHIBA MK7559GSXF, 750.16 GB
    Serial ATA Device: MATSHITADVD-R   UJ-8A8
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 3
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfa100000 / 2
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0xfa120000 / 5
    USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 8
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfd100000 / 2
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3

    Hi folks
    I have had another crash....i was wondering if someone would be kind enough to see if they cam make any suggestions on what it may be?
    Fri Apr 19 12:35:39 2013
    panic(cpu 0 caller 0xffffff800a4b7e95): Kernel trap at 0xffffff7f8c252ca6, type 14=page fault, registers:
    CR0: 0x0000000080010033, CR2: 0x0000000000000068, CR3: 0x000000002f3c504a, CR4: 0x00000000000606e0
    RAX: 0x0000000000000000, RBX: 0xffffff8047941400, RCX: 0x0000000000000001, RDX: 0x0000000000000000
    RSP: 0xffffff81da5a39b0, RBP: 0xffffff81da5a39e0, RSI: 0xffffff802c3efa00, RDI: 0xffffff8047941400
    R8:  0xffffff80444cef00, R9:  0xffffff8209e10000, R10: 0x0000000000000001, R11: 0x0000000000000000
    R12: 0x0000000000000000, R13: 0xffffff7f8c64f7d0, R14: 0xffffff802c3efa00, R15: 0xffffff8047941400
    RFL: 0x0000000000010246, RIP: 0xffffff7f8c252ca6, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0x0000000000000068, Error code: 0x0000000000000002, Fault CPU: 0x0
    Backtrace (CPU 0), Frame : Return Address
    0xffffff81da5a3650 : 0xffffff800a41d626
    0xffffff81da5a36c0 : 0xffffff800a4b7e95
    0xffffff81da5a3890 : 0xffffff800a4cd4dd
    0xffffff81da5a38b0 : 0xffffff7f8c252ca6
    0xffffff81da5a39e0 : 0xffffff7f8c2a9fbc
    0xffffff81da5a3a10 : 0xffffff7f8c266f2f
    0xffffff81da5a3a40 : 0xffffff7f8c267efd
    0xffffff81da5a3a70 : 0xffffff7f8c2d1230
    0xffffff81da5a3ab0 : 0xffffff7f8c26803a
    0xffffff81da5a3ae0 : 0xffffff7f8c25ad48
    0xffffff81da5a3b40 : 0xffffff7f8c266990
    0xffffff81da5a3ba0 : 0xffffff800a865ab3
    0xffffff81da5a3bc0 : 0xffffff800a86668d
    0xffffff81da5a3c20 : 0xffffff800a86408f
    0xffffff81da5a3d70 : 0xffffff800a4984a1
    0xffffff81da5a3e80 : 0xffffff800a420aed
    0xffffff81da5a3eb0 : 0xffffff800a410448
    0xffffff81da5a3f00 : 0xffffff800a41961b
    0xffffff81da5a3f70 : 0xffffff800a4a5dd6
    0xffffff81da5a3fb0 : 0xffffff800a4cdd43
          Kernel Extensions in backtrace:
             com.apple.iokit.IOAcceleratorFamily(30.14)[8CAD17E4-8359-3015-BCFC-F1964357CBFE ]@0xffffff7f8c244000->0xffffff7f8c28efff
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8aa66000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7f8afbf000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f8af7c000
             com.apple.AMDRadeonAccelerator(1.0.6)[1DDF899D-B472-36DF-A08D-365D3221F6CE]@0xf fffff7f8c29a000->0xffffff7f8c650fff
                dependency: com.apple.iokit.IOAcceleratorFamily(30.14)[8CAD17E4-8359-3015-BCFC-F1964357CBFE ]@0xffffff7f8c244000
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8aa66000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7f8afbf000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f8af7c000
    BSD process name corresponding to current thread: WebProcess
    Mac OS version:
    12D78
    Kernel version:
    Darwin Kernel Version 12.3.0: Sun Jan  6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
    Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
    Kernel slide:     0x000000000a200000
    Kernel text base: 0xffffff800a400000
    System model name: MacBookPro8,2 (Mac-94245A3940C91C80)
    System uptime in nanoseconds: 36154562884826
    last loaded kext at 24168199608710: jp.co.yamaha.driver.YamahaSteinbergUSBAudio          1.6.4f1 (addr 0xffffff7f8c869000, size 200704)
    last unloaded kext at 25813318732584: jp.co.yamaha.driver.YamahaSteinbergUSBAudio          1.6.4f1 (addr 0xffffff7f8c869000, size 98304)
    loaded kexts:
    com.vmware.kext.vmnet          3.0.0
    com.vmware.kext.vmioplug          3.0.0
    com.vmware.kext.vmci          3.0.0
    com.vmware.kext.vmx86          3.0.0
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.driver.AudioAUUC          1.60
    com.apple.driver.AGPM          100.12.87
    com.apple.driver.AppleMikeyHIDDriver          122
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AppleHDA          2.3.7fc4
    com.apple.iokit.IOBluetoothSerialManager          4.1.3f3
    com.apple.driver.AppleMikeyDriver          2.3.7fc4
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.1.3f3
    com.apple.driver.SMCMotionSensor          3.0.3d1
    com.apple.driver.AppleSMCLMU          2.0.3d0
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.AppleLPC          1.6.0
    com.apple.driver.ApplePolicyControl          3.3.0
    com.apple.driver.AppleSMCPDRC          1.0.0
    com.apple.driver.AppleUpstreamUserClient          3.5.10
    com.apple.driver.AppleMCCSControl          1.1.11
    com.apple.kext.AMDFramebuffer          8.1.0
    com.apple.AMDRadeonAccelerator          1.0.6
    com.apple.driver.AppleIntelHD3000Graphics          8.1.0
    com.apple.driver.AppleIntelSNBGraphicsFB          8.1.0
    com.apple.driver.AppleMuxControl          3.3.0
    com.apple.driver.AppleUSBTCButtons          237.1
    com.apple.driver.AppleUSBTCKeyboard          237.1
    com.apple.driver.AppleIRController          320.15
    com.apple.iokit.SCSITaskUserClient          3.5.5
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          34
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.3.1
    com.apple.driver.AppleUSBHub          5.5.5
    com.apple.driver.AirPort.Brcm4331          614.20.16
    com.apple.driver.AppleSDXC          1.4.0
    com.apple.driver.AppleFWOHCI          4.9.6
    com.apple.iokit.AppleBCM5701Ethernet          3.6.0b1
    com.apple.driver.AppleAHCIPort          2.5.1
    com.apple.driver.AppleUSBEHCI          5.5.0
    com.apple.driver.AppleEFINVRAM          1.7
    com.apple.driver.AppleSmartBatteryManager          161.0.0
    com.apple.driver.AppleACPIButtons          1.7
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleHPET          1.8
    com.apple.driver.AppleSMBIOS          1.9
    com.apple.driver.AppleACPIEC          1.7
    com.apple.driver.AppleAPIC          1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
    com.apple.nke.applicationfirewall          4.0.39
    com.apple.security.quarantine          2
    com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
    com.apple.iokit.IOSurface          86.0.4
    com.apple.kext.triggers          1.0
    com.apple.driver.DspFuncLib          2.3.7fc4
    com.apple.iokit.IOAudioFamily          1.8.9fc11
    com.apple.kext.OSvKernDSPLib          1.6
    com.apple.iokit.IOSerialFamily          10.0.6
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.1.3f3
    com.apple.iokit.IOBluetoothFamily          4.1.3f3
    com.apple.driver.AppleSMBusPCI          1.0.11d0
    com.apple.driver.AppleSMC          3.1.4d2
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.IOPlatformPluginFamily          5.3.0d51
    com.apple.driver.AppleSMBusController          1.0.11d0
    com.apple.iokit.IOAcceleratorFamily          30.14
    com.apple.kext.AMD6000Controller          8.1.0
    com.apple.kext.AMDSupport          8.1.0
    com.apple.driver.AppleHDAController          2.3.7fc4
    com.apple.iokit.IOHDAFamily          2.3.7fc4
    com.apple.driver.AppleGraphicsControl          3.3.0
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.iokit.IONDRVSupport          2.3.7
    com.apple.iokit.IOGraphicsFamily          2.3.7
    com.apple.driver.AppleUSBMultitouch          237.3
    com.apple.driver.AppleThunderboltDPInAdapter          1.8.9
    com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.9
    com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.6
    com.apple.iokit.IOUSBHIDDriver          5.2.5
    com.apple.driver.AppleUSBMergeNub          5.5.5
    com.apple.driver.AppleUSBComposite          5.2.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.5
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOAHCISerialATAPI          2.5.1
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.5
    com.apple.driver.AppleThunderboltNHI          1.6.3
    com.apple.iokit.IOThunderboltFamily          2.2.6
    com.apple.iokit.IOUSBUserClient          5.5.5
    com.apple.iokit.IO80211Family          522.4
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOEthernetAVBController          1.0.2b1
    com.apple.iokit.IONetworkingFamily          3.0
    com.apple.iokit.IOAHCIFamily          2.3.1
    com.apple.iokit.IOUSBFamily          5.5.5
    com.apple.iokit.IOHIDFamily          1.8.1
    com.apple.driver.AppleEFIRuntime          1.7
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          220.2
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.DiskImages          345
    com.apple.iokit.IOStorageFamily          1.8
    com.apple.driver.AppleKeyStore          28.21
    com.apple.driver.AppleACPIPlatform          1.7
    com.apple.iokit.IOPCIFamily          2.7.3
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0

  • Projector killed hard drive under newly installed yosemite??

    hey folks!
    i connected my macbook pro (mid 2012, non-retina) to a projector today and as i did that everything froze. i disconnected the projector, but no change. i forced a reboot and got a light grey screen with a blinking folder and question mark. it turns out my internal hard drive is dead.
    i updated to yosemite last week and have had smaller issus since then when connecting to a projector (black space where the keynote window was before which only vanished with a reboot).
    can anyone tell me, whether my hard drive dying has anything to do with the update to yosemite (my warranty ran out 2 weeks ago)? anyone with similar problems?
    thanks!

    minopilus wrote:
    can anyone tell me, whether my hard drive dying has anything to do with the update to yosemite (my warranty ran out 2 weeks ago)?
    I think it is very unlikely that the two are connected.
    It is more likely (though not certain) that something weird happened when plugged into the projector. Like a bad cable or a bad port that maybe allowed some kind of power surge back into the motherboard that might have affected the hard drive. But let me emphasize...this is a very unusual problem that should not have happened. Thousands of Mac laptops are plugged into projectors every single day in corporations and schools and universities. It is not a problem that should be expected to happen.
    Also, dying hard drives have not been reported by the thousands of Mac users who have also done the Yosemite upgrades. I have two Macs that upgraded to Yosemite without a problem.
    I don't know what the real cause was, but chances are it was a fluke. One possibility: The hard drive was already having undiagnosed problems, and this just pushed it over the edge.

  • HT3974 Keeping failed Hard Drives

    Can I keep a HDD that apple are replacing under AppleCare.  Local store says No? Is this correct?  The apple site talks about apple not doing data recovery, but it does not say I cannot keep the failed HDD and attempt recovery myself. Is the store correct?

    I don't know if it's full price or not -- I was quoted $132 for a ~150GB drive -- but the technician said the same as you, that I could get a much higher capacity drive for less, so if it's a discounted rate, then it would seem quite overpriced.
    I understand what you're getting at, though: if if's a discounted rate, then that would be the consideration I'm receiving in exchange for "letting" them keep the drive. Problem is, I'm not given an option to pay full price in exchange for keeping the drive.
    I want to keep the drive to try to recover data from it (which may prove futile). As for why buy from Apple, I wanted to minimize the time and effort I am spending on this issue (have spent a lot already) by getting it taken care of then, while at the Genius Bar, instead of having to make additional trips to other stores to get the repair done.
    In the end, because of Apple's dumb policy, I will achieve my original objective -- replace and keep the failed HD -- but at considerably more effort and time on my part. Would have been easier for me to take care of it at the Genius Bar, and I would have been willing to pay a big markup on the price of the new drive to save me the additional headache. So it seems like it would have been a win-win, if not for the policy.

  • What do i do if my mac keeps saying hard drive full??

    i have emptied my trash constantly and deleted a large amount of movies photos music etc
    from my computer completely and it still says its full and will not let me install updates because of this
    please help.
    Thankyou

    are you sure you are using Lion?
    see where it is?  If you are using Lion, this is there.

  • Is there apple approved software to keep your Hard drive organized

    Hello,
    I seem to be having issues with excessive amounts of information being left on my harddrive from downloading new apps or information being left behind from programs I have deleted.  Is there any approved apple software to help you manage your harddrive?  Or something similar to what you do for a PC like defrag?
    thanks

    Several people like OmniDiscSweeper: http://www.omnigroup.com/products/omnidisksweeper/.  This is not endorsed by Apple to my knowledge, but several people in here recommend it.  You can find an app in the app store called DiscDoctor for  .99 cents.

  • Older MacPro as an External Hard Drive

    Greetings
    I recently moved from my 2010 MacPro to an iMac. Since the MacPro has 4 hard drive bays I was thinking of using the MacPro as an "external" hard drive. I can access the drives thru my ethernet network but I was wondering if there is a more direct (and faster) route? Thank You in advance.
    David

    David Ramsey2 wrote:
    I am trying to figure out the fastest connection between the iMac and MacPro.
    David,
    That question has been answered, you already have it... continue using Ethernet.

Maybe you are looking for

  • Reading an RTF file in Java

    Hi, Can someone tell me how can we read the data from an .rtf files like we do with text files in Java. I have seen solutions using Swing rtfeditor etc.. But I just need to read the data, I do not want to open rtf page. Any help would be appreciated.

  • Room Template's icons are not displaying

    In Collaboration->collaboration content->Administration of Room part Templates, The Room Template's icons are not displaying. All icons are avilable in the folder \usr\sap\J2E\SYS\global\config\cm\etc\public\mimes\images i checked in both IE 6.0 and

  • Layer 3 to the Access Layer and MPLS Design Considerations

    Hi, We are about to install a new network consisting of Cat 4500s with Sup7E at the Access Layer, with Nexus 7000 at the Distribution and Core layers. We have 14 floors with at least three 4500s on each floor. Within the office block where the Access

  • Macbook pro screen flickering/tearing

    i m having the foll. problem with my mac , see the vids http://www.youtube.com/watch?v=jK_SJQ6UOlY http://www.youtube.com/watch?v=H4V6xoJtM8 can any1 tell me what's going on ? what part of my mac has gone bad ?

  • Style a tag in htmlText problem

    I want to show an anchor as a standard blue underlined text. I created a style sheet in the mxml with this line: a:link{color:blue} and this a {color:blue} Nothing. All day I've been trying to make a link blue in Flex 2. Other things in the style she