Frozen Grey Screen, Verbose stuck at Wireless Controller/ 5.10.38.24

Here's a good one...
Have an imac that was consistently freezing, restarting, etc.
Now, every time we start, it freezes at the grey screen.
The last two lines of Verbose Mode (or single user for that matter) reveal:
wl0: Broadcom BCM4328 802.11 Wireless Controller
5.10.38.24
Then it stops dead.
This is even AFTER a system reinstall.
Would this indicate a bad wireless card causing the issue, or perhaps a bad firewire port (Since that seems to be the next item that WOULD show up in the list), or am I not even close?
We actually had another imac with similar symptoms that is unfortunately apart right now, so I cannot verify the same Verbose sticking points (although the symptoms were identical. Any thoughts?

HI Chris,
Check the hard disk with your install disk.
Insert Installer disk and Restart, holding down the "C" key until grey Apple appears.
Go to Installer menu (Panther and earlier) or Utilities menu (Tiger and later) and launch Disk Utility.
Select your HDD (manufacturer ID) in the left panel.
Select First Aid in the Main panel.
(Check S.M.A.R.T Status of HDD at the bottom of right panel. It should say: Verified)
Click Repair Disk on the bottom right.
If DU reports disk does not need repairs quit DU and restart.
If DU reports errors Repair again and again until DU reports disk is repaired.
If you can't boot from an install disk, try Safe Mode. http://support.apple.com/kb/HT1564
Resolve startup issues and perform disk maintenance with Disk Utility and fsck
Carolyn

Similar Messages

  • Hp Touchpad Grey Screen with stuck partial download?

    Can anyone assist? After a recent download I now get a grey screen when I turn the machine on in the centre of which appears to be part of a map icon that does not work?
    The touchpad seems to be working OK and I suspect its just a download thats gone wrong but I have no real idea.
    Can anyone suggest how I can restore to the blue screen? Thanks
    Post relates to: HP TouchPad (WiFi)
    This question was solved.
    View Solution.

    This is just a matter of resetting your Wallpaper. Perform the following steps to reset it:
    Open the Screen & Lock app from the Settings tab
    Tap the Set Wallpaper button
    Choose the Walllpaper Album
    Choose the blue image to restore the default.

  • Mac Pro 3,1 Stuck on Grey screen for 1 min during boot

    I have a Late 2008 Mac Pro 3,1 and have started experiencing a very slow boot up.   The computer gets stuck for over a minute on the initial gray screen after the first boot chime.  Once the apple logo finally appears the boot goes normally.  Once running it seems OK.  The shut down seems normal with a  grey screen for a few seconds with the "clock" logo.
    Symptom:
    After the chime I see a blank gray screen for in excess of 1 minute, it used to last only a couple of seconds.
    Once the dark grey Apple logo appears the boot goes at normal speed
    I have a number of different hard drives with older systems and booting from each of then gives the problem - so it does not seem to be system/disc related
    Two partitions (Mavericks and ML) are on SSD's installed on a Sonnet PCIe Card and showed the same problem as the spinning hard discs.
    I tried: (following a trawl of the bb's etc)
    I repaired permissions and repaired all discs for all my boot partitions (10.5, 10.6, 10.7, 10.8 and 10.9) using the appropriate Disc Utility
    Zapping the Pram - this was very strange as I had to keep the cmd alt P R held down for around a minute before the second chime occurred, the time of the grey screen stays stuck
    Resetting the SMC
    Booting in Verbose Safe Mode: Again I had to hold the Alt V down for a minute on the gray screen before the screen went black and the text appeared
    I looked on the console log but could see nothing obvious, additionally from the verbose safe mode boot the text log seems to start from when the grey screen disappears. The time stamps show the boot finishing in well under the minute I wait.
    Any suggestions you may have are very welcome.
    Regards
    Dave

    Thanks The Hatter for that information.  The blank gray screen is now lasting 3 mins before the Apple appears.  When I restarted the system log is as below.  As  you can see there is just over a three minute gap between the shut down and the boot, indicating to me that it is not something in the system software after the boot but a problem at the very start.  It does look like it could be something to do with the hardware as you suggest.  I have verified all the discs with the disc utility and they report as OK and their SMART status is also OK.  I have disconnected the external drives with no change so I will now have to do a thorough check and systematically remove the internal ones but that will have to wait for the weekend.
    I have Mavericks on the Samsung 840 Pro and ML on a Crucial SSD (Crucial_CT240M500SSD1 Media) on a PCIe card.  The Mavericks install I think was an upgrade, not a clean install done quite a while ago.  I only noticed the problem this week when I re-booted in an ML to run some software not compatible with Mavericks.  I have made a system back up as a precaution to an external disc just in case my main drive is dying!
    There are some firmware updates for both the SSD discs that I have not applied these yet but I will leave them out of the mix until I have tried simplifying my configuration with a single disc.
    Apr 21 22:09:26 Davids-Mac-Pro.local shutdown[952]: reboot by _spotlight:
    Apr 21 22:09:26 Davids-Mac-Pro kernel[0]: Kext loading now disabled.
    Apr 21 22:09:26 Davids-Mac-Pro kernel[0]: Kext unloading now disabled.
    Apr 21 22:09:26 Davids-Mac-Pro.local shutdown[952]: SHUTDOWN_TIME: 1429650566 934799
    Apr 21 22:09:26 Davids-Mac-Pro kernel[0]: Kext autounloading now disabled.
    Apr 21 22:09:26 Davids-Mac-Pro kernel[0]: Kernel requests now disabled.
    Apr 21 22:09:26 Davids-Mac-Pro.local Mediatap[297]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted
    Apr 21 22:09:26 Davids-Mac-Pro.local Mediatap[297]: XPC error messaging com.apple.IconServicesAgent: Connection invalid
    Apr 21 22:13:02 localhost bootlog[0]: BOOT_TIME 1429650782 0
    Apr 21 22:13:04 localhost syslogd[18]: Configuration Notice:
      ASL Module "com.apple.appstore" claims selected messages.
      Those messages may not appear in standard system log files or in the ASL database.
    Apr 21 22:13:04 localhost syslogd[18]: Configuration Notice:
      ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".
      Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".

  • Has anyone encounter a Grey Screen with spinning wheel stuck (frozen waited more than 5h) in after running Lion Installer from SL?

    Hi
    I've tried almost everything on my Macbook Pro 8,2 (i7 2.0Ghz).
    Wipe/Erase the SL partition.
    Burned the ESD dmg to a DVD.
    Reset SMC,PRAM and NVRAM many times.
    Run Repair Disk. Passed OK.
    Run Hardware Test. Passed OK.
    Download the Lion Installer 4 times. MD5 Passed.
    Everytime I've tried to install lion it give me this Grey screen... The mouse wheel start spinning and it then stops, and nothing happens from that point. (Also rebooted many, many times same result).
    SL Install disk runs fine, even installing it from Zero. I've setted up time machine. (The restore to definetly works also the SL installation too)
    I'm a little far away to send my Macbook to a customer service.
    What else should I try?
    :S
    VR

    Thank you very much William
    I ran the installer and saw the same screen stuck... After I used Shift to boot in safe mode, I got the 3 beeps with grey screen apple logo. So then I rebooted into Single User do the 'nvram boot-args="-x -v"' and voila the installer continued with no issues I've turned back de 'nvram boot-args=""' and everything seems to be working fine.
    Really weird beahviour of the installer with my Mac.
    Thanks.

  • MBP (2010) stuck in grey screen with Apple logo no matter what I do.

    Hi everybody,
    I know this issue has been posted many times in the past, and I have searched everywhere, but I am quickly running out of option but to repartition/reformat and do a clean install. I have important files on my computer (I know! Back up! Back up! Back up!) and need your help to preferably regain full access to my system or somehow find access to my files so I could transfer them to an external hdd.
    From two days ago my as I was browing the net through Google Chrome my computer all of a sudden started to show the sippinig beach ball and became completely unresponsive. I could not force shut down any program or restart the system. So, I held down the power button and forced the system to shut down. When I rebooted the MB it all began going haywire. The boot process gets stuck in a grey screen with the Apple logo and the spinning wheel (not the beach ball) for a long time. After that I get the mouse pointer, and if I move that it turns to the spinning beach ball and nothing happens except that the screen flashes between silver and grey colors.
    So here are the steps I have taken as to "attempt" to fix the issue  (I have followed these instructions: https://discussions.apple.com/docs/DOC-3353) :
    1. Went into startup manager and ran the disk utility to verify disk volume and permissions. Everything seems to be OK.
    2. Conducted a PRAM reset. No change.
    3. Conducted a SMC reset. No change.
    4. I did a fsck -fy run (in command mode) on startup. No change.
    5. Ran the system in verbose mode and got the following error: "BootCacheControl : Unable to open /var/db/BootCache.playlist"
    6. And lastly, I created 10.8 OSX image on a USB stick and reinstalled ML one more time only to get stuck at the same place yet again.
    Additionally, I can see my computer from my wife's MBP also running ML for a while. The folder that I have set the permission to be available, I can access! I have moved some files, but naturally the files that I want are in folders that have restricted network access. That just tells me the hard itself should be fine (perhaps).
    I am running out of ideas fast to save the system. If anyone can help me, I'd be immensely grateful. Thanks.
    Amir

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    Step 1
    The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
    a. Boot into Recovery by holding down the key combination command-R at the startup chime, or from a local Time Machine backup volume (option key at startup.) Release the keys when you see a gray screen with a spinning dial. When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
    How to back up and restore your files
    b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    How to use and troubleshoot FireWire target disk mode
    c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Before reconnecting an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
    Step 3
    Boot in safe mode.* The instructions provided by Apple are as follows:
    Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
    When you see the gray Apple logo, release the shift key.
    If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    *Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. Post for further instructions.
    When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is damaged and the drive is probably malfunctioning. In that case, go to step 5.
    If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
    If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 4
    Sometimes a boot failure can be resolved by resetting the NVRAM.
    Step 5
    Launch Disk Utility in Recovery mode (see above for instructions.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it produces. Look for the line "Permissions repaired successfully" at the end of the output. Then reboot as usual.
    Step 6
    Boot into Recovery again. When the OS X Utilities screen appears, follow the prompts to reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.
    Step 7
    Repeat step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a backup.
    Step 8
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested.

  • Hello my Mac Air is frozen on the grey screen (with the apple symbol, sleeping mode, restart-and off button), once you turn it on.

    hello my Mac Air is frozen on the grey screen (with the apple symbol, sleeping mode, restart-and off button), once you turn it on. I Can`t press any button.My Mouse still works. Battery is charged. Alt-cmd-escape doesn`t work It even after a forced shutting off, the problem is the same.   what should i do? Thank you for your help.

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    Step 1
    The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.   
    There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
         a. Boot into the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
    b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
    Step 3
    Boot in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 5.
    If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
    If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 4
    Sometimes a boot failure can be resolved by resetting the NVRAM.
    Step 5
    Launch Disk Utility in Recovery mode (see Step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
    Step 6
    Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 7
    Repeat step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.
    Step 8
    This step applies only to older Macs (not current models) that have a logic-board ("PRAM") battery. The battery is distinct from the main battery of a portable. A dead logic-board battery can cause a gray screen at boot. Typically the boot failure will be preceded by loss of the startup disk and system clock settings. See the user manual for replacement instructions.
    Step 9
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested.

  • Hi, I downloaded Yosemite this evening. I downloaded o.k., it installed o.k. and then it restarted the Macbook and now it seems frozen. There is nothing but a grey screen, the apple logo and a bar that is half black

    Hi, I downloaded Yosemite this evening. It downloaded fine, it installed fine and then it restarted the Macbook. Now it seems to be frozen. I have nothing but a grey screen with the apple logo and a bar that is half black and half grey. It's been like this for over an hour. Should I worry or is it still working at something? How do I fix this if it's not still working at installing something. Thank goodness for this poor old pc as backup.

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

  • Help !!! freeze and stuck on grey screen, difficult to reboot, here is my EtreCheck report

    Help !!! I experienced more and more issues since I upgraded to mavericks and i brought my MBP 15" (from 2011, out of warranty) to the Apple genius bar a couple of days after my computer started to freeze and crash on a grey screen with less and less possibility to reboot it (tried all advices i could find on the forums to reboot in other ways, etc. ). The overnight tests at Apple gave nothing, they just decided to reinitiate the software and concluded that the problem was solved.
    But the problem happened again: when i reloaded my backup from Time Machine, i could run the whole process till the end then when I was asked to restart, I couldn’t open the finder, my screen was stuck on a light grey.
    I could reboot it (always in maintaining the off button to stop the machine or in using the single mode) but it’s non stable, after too many manipulations, the screen freezes or divides in 2 parts with lines, etc. And I have to try again different ways to reboot…
    I took a new appointment to the Apple Genius bar, but in the mean time, I tried to repair the authorizations, and I have to say that the list is really long, even if I did the operation more 3 times…
    I think there is a software conflict somewhere and find the possibility to check the system with EtreCheck (thanks! I will also bring this paper to the Genius bar technician).
    Please, would there be someone who could read this information and gives me some advices and opinion on what could be problematic, what to do etc.
    In end, what is very weird to me:
    I could read on this forum that “startup items” are no more necessary since OS 10.4. I tried to delete the ones that appear here in library/startupitems, and found another one which is not mentioned in this EtreCheck list : startouc
    Also when I tried to delete those items, it was refused by the finder with the message saying that this items are in use…
    Another point: I uninstalled the application Chiavetta Internet 42 a week ago when I started to have the problems. I was in Italy and this is a usb key with pin for internet. At the moment thought about a possible conflict with the key and deleted every item concerning this installation. This is because I don’t understand that it appears now in the “User login Items”.
    Thank you so much in advance
    Here is the EtreCheck report:
    Hardware Information:
                MacBook Pro (15-inch, Early 2011)
                MacBook Pro - model: MacBookPro8,2
                1 2 GHz Intel Core i7 CPU: 4 cores
                8 GB RAM
    Video Information:
                Intel HD Graphics 3000 - VRAM: 512 MB
                AMD Radeon HD 6490M - VRAM: 256 MB
    System Software:
                OS X 10.9.2 (13C1021) - Uptime: 0 days 1:42:38
    Disk Information:
                Hitachi HTS545050B9A302 disk0 : (500,11 GB)
                            EFI (disk0s1) <not mounted>: 209,7 MB
                      Macintosh HD (disk0s2) / [Startup]: 499,25 GB (219,23 GB free)
                            Recovery HD (disk0s3) <not mounted>: 650 MB
                MATSHITADVD-R   UJ-8A8 
    USB Information:
                Apple Inc. FaceTime HD Camera (Built-in)
                Apple Inc. BRCM2070 Hub
                            Apple Inc. Bluetooth USB Host Controller
                Apple Inc. Apple Internal Keyboard / Trackpad
                Apple Computer, Inc. IR Receiver
    Thunderbolt Information:
                Apple Inc. thunderbolt_bus
    Gatekeeper:
                Mac App Store and identified developers
    Kernel Extensions:
                [not loaded]            com.MBB.driver.MBBACMData (5.00.02) Support
                [not loaded]            com.MBB.driver.MBBActivateDriver (1.0.14) Support
                [not loaded]            com.MBB.driver.MBBEthernetData (2.00.05) Support
                [not loaded]            com.palm.ClassicNotSeizeDriver (3.1) Support
                [not loaded]            com.wdc.driver.1394HP (1.0.9) Support
                [not loaded]            com.wdc.driver.USBHP (1.0.11) Support
    Launch Daemons:
                [failed]            com.google.GoogleML.plist Support
                [failed]            com.google.keystone.daemon.plist Support
    Launch Agents:
                [loaded]            com.hp.help.tocgenerator.plist Support
    User Launch Agents:
                [loaded]            com.iLike.Agent.plist Support
    User Login Items:
                Transport Monitor
                Firefox
                My Day
                Chiavetta Internet 42
                GoogleSoftwareUpdateAgent
    Internet Plug-ins:
                Unity Web Player: Version: UnityPlayer version 4.2.1f4 - SDK 10.6 Support
                QuickTime Plugin: Version: 7.7.3
                Default Browser: Version: 537 - SDK 10.9
                OfficeLiveBrowserPlugin: Version: 12.3.6 Support
                Google Earth Web Plug-in: Version: 7.1 Support
                Mozillaplug: Version: 1.0
                Silverlight: Version: 5.1.20913.0 - SDK 10.6 Support
                DirectorShockwave: Version: 12.0.5r146 - SDK 10.6 Support
                iPhotoPhotocast: Version: 7.0 - SDK 10.7
    Safari Extensions:
                Amazon Shopping Assistant: Version: 1.1
                Searchme: Version: 1.3
                Ebay Shopping Assistant: Version: 1.1
    Audio Plug-ins:
                BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
                AirPlay: Version: 2.0 - SDK 10.9
                AppleAVBAudio: Version: 203.2 - SDK 10.9
                iSightAudio: Version: 7.7.3 - SDK 10.9
    iTunes Plug-ins:
                Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
    User iTunes Plug-ins:
                iLike: Version: 1.0 Support
                PPC Bundle: Version: (null) Support
                iLike Bundle: Version: (null) Support
                Tiger Bundle: Version: (null) Support
                TuneUp Visualizer: Version: (null) Support
    3rd Party Preference Panes:
                None
    Time Machine:
                Skip System Files: NO
                Mobile backups: OFF
                Auto backup: NO - Auto backup turned off
                Volumes being backed up:
                            Macintosh HD: Disk size: 464.96 GB Disk used: 260.79 GB
                Destinations:
                            EVE TIME MACHINE & PHOTOS [Local] (Last used)
                            Total size: 2 
                            Total number of backups: 22
                            Oldest backup: 2013-11-19 10:49:38 +0000
                            Last backup: 2014-05-07 09:35:48 +0000
                            Size of backup disk: Excellent
                                        Backup size 2  > (Disk size 464.96 GB X 3)
                            copy Time Machine + photos (22 Nov 2013) [Local]
                            Total size: 931.36 GB
                            Total number of backups: 5
                            Oldest backup: 2013-11-23 04:29:31 +0000
                            Last backup: 2014-03-26 20:03:02 +0000
                            Size of backup disk: Adequate
                                        Backup size 931.36 GB > (Disk used 260.79 GB X 3)
                Time Machine details may not be accurate.
                All volumes being backed up may not be listed.
    Top Processes by CPU:
                     5%            firefox
                     3%            WindowServer
                     0%            Microsoft Word
                     0%            launchservicesd
                     0%            fontd
    Top Processes by Memory:
                606 MB            com.apple.IconServicesAgent
                401 MB            firefox
                238 MB            Finder
                221 MB            mds_stores
                123 MB            Microsoft Word
    Virtual Memory Information:
                3.68 GB            Free RAM
                2.57 GB            Active RAM
                492 MB            Inactive RAM
                1.26 GB            Wired RAM
                2.42 GB            Page-ins
                0 B            Page-outs

    Hey thank you! I tried to send you a first answer but Firefox blocked... Again thank you for your advice and the detailed process to follow, hope it can help! - Also sorry for my English which is not my primary language.
    Also don't know how to edit the Anonymous UUID... is it in the apple discussion account?
    Here is what i found in Console > Diagnostic and usage information > System diagnostic report:
    there were 4 lines as titles, and after Firefox crash there are 5 now.
    I will send you the content for each of them, but in a new message each time in case it freezes again.
    1st line starts with diskarbitrationd, ends with .shutdownStall
    content:
    Date/Time:  
    2014-05-12 18:05:15 -0700
    OS Version: 
    10.9.2 (Build 13C1021)
    Architecture:
    x86_64
    Report Version:  18
    Command:    
    No Target
    Path:       
    No Target
    Version:    
    Parent:     
    UNKNOWN PROCESS [0]
    PID:        
    0
    Event:      
    shutdown stall
    Duration:   
    12.05s (sampling started after 2 seconds)
    Steps:      
    101 (100ms sampling interval)
    Hardware model:  MacBookPro8,2
    Active cpus:
    8
    Fan speed:  
    4033 rpm (-334)
    Free pages: 
    1153467 pages (-455)
    Pageins:    
    5 pages
    Pageouts:   
    0 pages
    Swapins:    
    0 pages
    Swapouts:   
    0 pages
    Process:    
    diskarbitrationd [21]
    Path:       
    /usr/libexec/diskarbitrationd
    Architecture:
    x86_64
    Parent:     
    launchd [1]
    UID:        
    0
    Sudden Term:
    Dirty
    Task size:  
    577 pages (-6)
    Importance: 
    Adaptive, Donating
    Timers:     
    Coalesced
      Thread 0x13d 
    DispatchQueue 1     
    priority 31   
      101 start + 1 (libdyld.dylib) [0x7fff8c4db5fd]
    101 ??? (diskarbitrationd + 28877) [0x10e56a0cd]
    101 CFRunLoopRun + 97 (CoreFoundation) [0x7fff8c3da811]
    101 CFRunLoopRunSpecific + 309 (CoreFoundation) [0x7fff8c3250b5]
    101 __CFRunLoopRun + 1161 (CoreFoundation) [0x7fff8c325779]
    101 __CFRunLoopServiceMachPort + 181 (CoreFoundation) [0x7fff8c326155]
    101 mach_msg_trap + 10 (libsystem_kernel.dylib) [0x7fff8f270a1a]
    *101 ??? (mach_kernel + 92160) [0xffffff8000216800]
      Thread 0x146 
    DispatchQueue 2     
    priority 33   
      101 _dispatch_mgr_thread + 52 (libdispatch.dylib) [0x7fff8ab9c152]
    101 kevent64 + 10 (libsystem_kernel.dylib) [0x7fff8f275662]
    *101 ??? (mach_kernel + 3949760) [0xffffff80005c44c0]
      Thread 0x15ac
    priority 31   
    *101 wq_unsuspend_continue + 0 (pthread) [0xffffff7f80b747c4]
      Thread 0x14e2
    priority 29   
      80 start_wqthread + 13 (libsystem_pthread.dylib) [0x7fff93750fb9]
    80 __workq_kernreturn + 10 (libsystem_kernel.dylib) [0x7fff8f274e6a]
    *80 wq_unpark_continue + 0 (pthread) [0xffffff7f80b746ae]
      Thread 0x1569
    priority 0    
      79 start_wqthread + 13 (libsystem_pthread.dylib) [0x7fff93750fb9]
    79 __workq_kernreturn + 10 (libsystem_kernel.dylib) [0x7fff8f274e6a]
    *79 wq_unpark_continue + 0 (pthread) [0xffffff7f80b746ae]
      Thread 0x15a6
    priority 31   
      71 start_wqthread + 13 (libsystem_pthread.dylib) [0x7fff93750fb9]
    71 __workq_kernreturn + 10 (libsystem_kernel.dylib) [0x7fff8f274e6a]
    *71 wq_unpark_continue + 0 (pthread) [0xffffff7f80b746ae]
      Binary Images:
    0x10e563000 -   
    0x10e578fff  diskarbitrationd (266) <94F10D52-A866-34ED-B278-873B4B2E0C7E> /usr/libexec/diskarbitrationd
    0x7fff8ab99000 -
    0x7fff8abb3fff  libdispatch.dylib (339.90.1) <F3CBFE1B-FCE8-3F33-A53D-9092AB382DBB> /usr/lib/system/libdispatch.dylib
    0x7fff8c2b5000 -
    0x7fff8c49afff  com.apple.CoreFoundation 6.9 (855.16) <617B8A7B-FAB2-3271-A09B-C542E351C532> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff8c4d8000 -
    0x7fff8c4dbff7  libdyld.dylib (239.4) <CF03004F-58E4-3BB6-B3FD-BE4E05F128A0> /usr/lib/system/libdyld.dylib
    0x7fff8f25f000 -
    0x7fff8f27bff7  libsystem_kernel.dylib (2422.90.20) <20E00C54-9222-359F-BD98-CB79ABED769A> /usr/lib/system/libsystem_kernel.dylib
    0x7fff9374b000 -
    0x7fff93752ff7  libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib
    *0xffffff7f80b71000 - 0xffffff7f80b78fff  com.apple.kec.pthread 1.0 (1) <619F6A5D-FFA2-3B59-9993-958FD7154B83> /System/Library/Extensions/pthread.kext/Contents/MacOS/pthread
    *0xffffff8000200000 - 0xffffff8000200000  mach_kernel <9FEA8EDC-B629-3ED2-A1A3-6521A1885953> /mach_kernel
    Process:    
    fsck_hfs [267]
    Path:       
    /System/Library/Filesystems/hfs.fs/Contents/Resources/fsck_hfs
    Architecture:
    x86_64
    Parent:     
    diskarbitrationd [21]
    Responsible:
    diskarbitrationd [21]
    UID:        
    0
    Task size:  
    206770 pages
    CPU Time:   
    10.043s
    Importance: 
    Adaptive, Donating
      Thread 0x968 
    DispatchQueue 1     
    priority 31    
    cpu time  10.043s
      101 start + 1 (libdyld.dylib) [0x7fff8c4db5fd]
    101 ??? (fsck_hfs + 7233) [0x106fe7c41]
    101 ??? (fsck_hfs + 76504) [0x106ff8ad8]
    101 ??? (fsck_hfs + 79339) [0x106ff95eb]
    101 ??? (fsck_hfs + 119757) [0x1070033cd]
    42  ??? (fsck_hfs + 135082) [0x107006faa]
    42  ??? (fsck_hfs + 73083) [0x106ff7d7b]
    38  ??? (fsck_hfs + 33605) [0x106fee345]
    24  ??? (fsck_hfs + 43420) [0x106ff099c]
    23  ??? (fsck_hfs + 40781) [0x106feff4d]
    6   ??? (fsck_hfs + 28484) [0x106fecf44]
    *6   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *6   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *6   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *6   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *6   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    3   ??? (fsck_hfs + 29225) [0x106fed229]
    *3   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *3   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *3   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *3   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *3   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    2   ??? (fsck_hfs + 29241) [0x106fed239]
    *2   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *2   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *2   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *2   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *2   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    2   ??? (fsck_hfs + 28343) [0x106feceb7]
    *2   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *2   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *2   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *2   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *2   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28442) [0x106fecf1a]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28427) [0x106fecf0b]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28390) [0x106fecee6]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 29203) [0x106fed213]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28331) [0x106feceab]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28938) [0x106fed10a]
    1   ??? (fsck_hfs + 26336) [0x106fec6e0]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28490) [0x106fecf4a]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 30064) [0x106fed570]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28519) [0x106fecf67]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28406) [0x106fecef6]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 40680) [0x106fefee8]
    1   ??? (fsck_hfs + 32482) [0x106fedee2]
    1   ??? (fsck_hfs + 17431) [0x106fea417]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    14  ??? (fsck_hfs + 43610) [0x106ff0a5a]
    14  ??? (fsck_hfs + 41086) [0x106ff007e]
    2   ??? (fsck_hfs + 28484) [0x106fecf44]
    *2   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *2   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *2   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *2   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *2   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28373) [0x106feced5]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 29225) [0x106fed229]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28492) [0x106fecf4c]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 29199) [0x106fed20f]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28511) [0x106fecf5f]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28505) [0x106fecf59]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28401) [0x106fecef1]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28477) [0x106fecf3d]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28390) [0x106fecee6]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 30356) [0x106fed694]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28496) [0x106fecf50]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28343) [0x106feceb7]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    4   ??? (fsck_hfs + 33871) [0x106fee44f]
    4   ??? (fsck_hfs + 41086) [0x106ff007e]
    1   ??? (fsck_hfs + 28652) [0x106fecfec]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28673) [0x106fed001]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 29179) [0x106fed1fb]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28664) [0x106fecff8]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    39  ??? (fsck_hfs + 134138) [0x107006bfa]
    39  ??? (fsck_hfs + 73083) [0x106ff7d7b]
    36  ??? (fsck_hfs + 33605) [0x106fee345]
    22  ??? (fsck_hfs + 43420) [0x106ff099c]
    20  ??? (fsck_hfs + 40781) [0x106feff4d]
    8   ??? (fsck_hfs + 28484) [0x106fecf44]
    *8   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *8   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *8   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *8   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *8   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    2   ??? (fsck_hfs + 28492) [0x106fecf4c]
    *2   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *2   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *2   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *2   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *2   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 29194) [0x106fed20a]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 29225) [0x106fed229]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 26738) [0x106fec872]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28433) [0x106fecf11]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28442) [0x106fecf1a]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28427) [0x106fecf0b]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28490) [0x106fecf4a]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28660) [0x106fecff4]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28496) [0x106fecf50]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28477) [0x106fecf3d]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    2   ??? (fsck_hfs + 40680) [0x106fefee8]
    2   ??? (fsck_hfs + 32482) [0x106fedee2]
    1   ??? (fsck_hfs + 17850) [0x106fea5ba]
    1   _platform_memmove$VARIANT$Nehalem + 258 (libsystem_platform.dylib) [0x7fff8ae280e2]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 17595) [0x106fea4bb]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    13  ??? (fsck_hfs + 43610) [0x106ff0a5a]
    13  ??? (fsck_hfs + 41086) [0x106ff007e]
    2   ??? (fsck_hfs + 30447) [0x106fed6ef]
    *2   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *2   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *2   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *2   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *2   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    2   ??? (fsck_hfs + 28484) [0x106fecf44]
    *2   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *2   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *2   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *2   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *2   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    2   ??? (fsck_hfs + 28477) [0x106fecf3d]
    *2   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *2   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *2   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *2   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *2   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 29225) [0x106fed229]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28511) [0x106fecf5f]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28406) [0x106fecef6]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 30435) [0x106fed6e3]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28490) [0x106fecf4a]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 29255) [0x106fed247]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 29237) [0x106fed235]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 43408) [0x106ff0990]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    2   ??? (fsck_hfs + 33871) [0x106fee44f]
    2   ??? (fsck_hfs + 41086) [0x106ff007e]
    1   ??? (fsck_hfs + 28860) [0x106fed0bc]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
    *1   ??? (mach_kernel + 900976) [0xffffff80002dbf70]
    1   ??? (fsck_hfs + 28331) [0x106feceab]
    *1   ??? (mach_kernel + 996585) [0xffffff80002f34e9]
    *1   ??? (mach_kernel + 898031) [0xffffff80002db3ef]
    *1   ??? (mach_kernel + 925350) [0xffffff80002e1ea6]
    *1   ??? (mach_kernel + 928680) [0xffffff80002e2ba8]
                  

  • MBP stuck on grey screen

    This morning my MBP, mod 6,2 (8GB, 500GB), started acting strange (would not minimize Word, Safari would crash and re-crash on restart...)
    so I decided to reboot it. Never came back.
    The system sits on the grey screen forever. In many attempts, once or twice it went to the login screen, and after I entered the password, got stuck on that screen removing the cursor.
    So far I have:
    - booted ML in recovery mode, checked and rechecked the HD (verify disk, check permissions....) - all ok
    (recovery mode runs fine, I can browse the web, run disk utility....without any problem)
    - reset PRAM and SMC (even if the problem does not appear related)
    - booted the AHT disk and passed the brief test (am running the extended one now)
    - booted in verbose mode and learned that the system gets stuck in these steps
    Com.apple.launchd          1 com.apple.UserEventAgent-LoginWindow                       #          stopping job
    Com.apple.launchd          1 com.apple.UserEventAgent-LoginWindow                                #          Sent Job SIGKILL
    Com.apple.launchd           1 com.apple.universalaccessd                                           #          stopping job
    Com.apple.launchd            1 com.apple.universalaccessd                                                    #          Sent Job SIGKILL
    Com.apple.launchd            1 com.apple.helpd                                                               #          stopping job
    Com.apple.launchd            1 com.apple.helpd                                                                        #          Sent Job SIGKILL
    Com.apple.launchd            1 com.apple.coreservices.appleid.authentication   #          stopping job
    where # is the process ID, which keeps increasing. The first time it appears, reads 249, then works its way up constantly.
    Any clue on what could be wrong?? I'm mostly interested in backing up the last few days of work before doing anything
    drastic with the system, but need to get in the system to do that.
    Thanks in advance

    If you want to preserve the data on the boot drive, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data, you can skip this step.
    There are several ways to back up a Mac that is unable to fully boot. You need an external hard drive to hold the backup data.
    1. Boot into Recovery (command-R at startup) or from a local Time Machine backup volume (option key at startup.) Launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
    How to back up and restore your files
    2. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    How to use and troubleshoot FireWire target disk mode
    3. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

  • Powermac G5 stuck on grey screen start up and fans running wild

    Hi All
    I also have the recurring problem all of a sudden - yesterday all seems well, today am stuck on grey screen and fans getting stronger by the minute. NOTHING works - have been through all sorts of forums and the most I got was to try disk utility - which says all is well - replaced the battery - tried just about anything short of pouring some acid on the **** thing, won't boot from original install CD either - I really need this machine as I earn my living with it and cant afford a new one and why as it was working just perfect - now this mess. In a way don't know why the excellerating fans are not built to simply pick up speed and then eat into the PC board and CPU - at lest this way we know for sure there is nothing we can do.
    Does no one here know why the mac is doing this - not even the mac fundies? Unbelievable. I live in Namibia and Apple Mac support here is similar to that on this website - might as well write this on a wall - that is why I am really frustrated... **** Mac

    Follow these steps in order:
    http://support.apple.com/kb/TS2570
    The G5 is also subject to solder failure around the RAM slots and memory controller.
    It is a fatal condition, but one that can sometimes be temporarily sidestepped by heating the logic board between the RAM slots with a hair dryer.
    Heat the board until very warm (hot) then start.
    If your machine starts after heating, then you better just leave the machine on all the time.
    You never know when the trick won't work......

  • IMac stalled and now is stuck on grey screen

    So, I got on my iMac(2008 I believe; it's got the black border, pretty sure it's got a core2duo processor. Running mountain lion) and while the screen was on, nothing was working. The desktop was completely frozen, the mouse wasn't moving, and the keyboard provided no response. So, I reset the system, and it hung up at the grey screen, with the apple logo and spinning wheel.
    after a few minutes I reset it again, and had the same issue. I tried loading up a backup, and the one from when I installed ML showed up, but after selecting it, nothing happened.
    So I tried safe booting it. No effect, other than it takes longer before the wheel appears.
    Next step was resetting the PRAM. First couple of attempts didn't result in a reset, so I moved on to the SMC.
    After resetting the SMC, I still saw no improvement to my situation, so I tried resetting the PRAM. This time it did reset, but the computer still hangs up.
    Now, I'm not really experienced in all this stuff, but I tried taking a peek in verbose mode... things got interesting here... things seem to load up like normal until it gets to a line along the lines of "USBMSC non-unique identifier ############### device not responding"(Sorry, going by memory here, no computer at home). This line begins repeating to infinity, with the occasional "timed out" message thrown in for good measure.
    Now, there's nothing plugged into my computer, I haven't had any issues leadinig up to this, and I haven't recently installed new hardware or software. I tried holding down cmnd-option-o-f, but nothing happened. I had to get back to the office, so maybe I just didn't hit the buttons properly. If I get into openfirmware, is there anything I can do from there?
    I don't have regular access to another mac. And, seeing as I work, it's not that easy for me to get in to the genius bar.
    Thanks for whatever help you guys can provide!
    edit: upon further reading, I see that I may not have tried safe mode properly. the instructions I read said to hold shift from before pressing the power button, now I see some instructions that say to wait until you hear the tone. So I will try that when I get home.... but please, feel free to throw in any theories until then!
    edit2: if I ever got a restore disk, I don;t know where it is now.
    edit3: 2009 iMac, not 2008. It's 27 inches.

    Try booting with Command + R depress to enter the Recovery Partition.
    Then start Disk Urtility and repair the disk.
    Allan

  • HELP!! powerbook stuck on grey screen, not able to boot safe or single user

    hey, i need some help, ive searched the forums the best i could, im experianced at fixing pc's but this has been my first mac in awhile, a friend of mine brought his 12" powerbook g4 to me, he says whenever he turns is on its stays stuck on the first screen where you see a grey apple and it shows a spinning wheel loading, he said hes even left it on overnight and it still stays there, he said he might have gotten a virus, cause he said he was searching **** last time it worked =P (hey i dont judge, every man has to find someway to reveive the "pressure")
    so anyway, i dont have alot of his specs, not even the exact o/s # i just know he told me it osx 10.4, so i did some research and found some ways to TRY and fix it, i tried safe mode (shift) and single user mode (cmd+s) and even verbose mode(cmd+v) when booting up the powerbook, but alas, none have worked, safe mode doesnt do anything, just the same grey screen, and single and verbose mode both halts after the cmd screen goes through a few lines.
    he doesnt have any software for his powerbook, they are all at home, which is about 900 kms away (or 559.26 miles to the non-metric ppl out there) so im working with nothing but my brain and the net, which isnt much, does anybody have any suggestions, maybe some third party software that would help, just point me in the right direction, or better yet, explain it to me like i was an infant, im not used to macs, but they intrigue. at least for now, i dont want to be put off just from this one little incident.
    thanks to anyone who offers help, its my first time EVER asking for it in any forum.

    Welcome to Apple Discussions.
    There's a couple of things I can think of that may be the problem. Based upon what you have described, the first is a hard drive failure.
    A couple of ways to check for this is to use the PowerBook's original installer disc (which you don't currently have access to), or perhaps a Mac OS X Tiger installation disc, to restart from and then use Disk Utility to perform a Repair Disk. Restarting from CD or DVD is performed by pressing the 'C' key during startup with the disc in the PB.
    Another way to check is to see if the drive can be accessed via FireWire Target Disk Mode.
    A second possibility is that there may be a directory corruption on the drive. If so, then DiskWarrior is the best option.
    Another possibility is to take the PB in to an Apple Store or Apple Authorised Service Provider for them to diagnose.
    15" 1.25GHz/12" 1GHz PBs, 2xPPC Mac minis, 12" iBook G4,   Mac OS X (10.4.6)   Cube, 2xTAMs, iPods 2G/4G, iPs, AEBS, AX

  • Stuck at "grey screen of death", disk I/O errors, Facility com.apple.system

    Good morning everybody!
    Yesterday, my MacBook Air revB crashed upon trying to open an mp4 video. I had to press and hold the power button until switch-off. After this, the machine wouldn't start in either normal or safe mode, but was stuck on the grey screen with the Apple logo and the spinning wheel. A start attempt in verbose mode revealed the error "[Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 6] [IOType Read]", occurring twice. After this, some normal startup posts appeared, but each after a very long time, and preceded by the name of my harddisk and "IO error". Therefore, the system hung doe to not being able to read from the disk what it wanted to read for start-up. I booted into single user mode and used the find command to search "com.apple.system.fs" from root. It was not found. I verified the find command by searching something else, and that was found. Now I renamed my User folder in single user mode and rebooted in verbose mode. The Facility com.apple.system.fs persisted, but afterwards the system booted normally, no chain of disk IO errors. I deleted the User folder that had been newly created due to renaming the old one, and changed the old one's name back to its original value. Afterwards, the system booted normally without any errors, including the "com.apple.system.fs" one. The S.M.A.R.T. status of the disk was and is "SMARTOK". In order to find this out, I opened the console, whereupon the system crashed again. Only after 20 min of 1 s-long windows of opportunity (when the beachball disappeared) was I able to force-quit the console by invoking alt-cmd-esc, and the system continued to respond normally. There are obviously corrupt log files producing the very same read errors that had originally caused the system to hang during boot. Does anybody now what is going on?
    The best,

    Hey there,
    I reread your original post... The problem to me is that what you did to make it boot again doesn't make much sense. Nothing in your home directory prevents the system from booting.
    You said that the system hung when you had Console open. Most of the log files shown there are in /var/log, /Library/Logs some are also in your User directory in ~/Library/Logs, you could try deleting everything inside...
    Why renaming your home folder changed anything is a mystery to me. The only theory I have is general file system corruption that got repaired during one of those bootups due to an automated fsck. That or the system deleted and recreated invalid plist files.
    Mac OS has important files in /Library and /System/Library. The ones in System belong to the System and are not supposed to be touched. The ones in /Library are open for Applications to add their own System-wide Configuration settings etc. The same structure exists in your home directory ~/Libary. Usually the most interesting areas in your home directory are ~/Library/Application Support and ~/Library/Preferences. However as I previously said nothing in your home directory would keep the system from booting. It would always go to the blue screen before the login screen would appear (even when you have auto login on).
    Good luck!

  • I didn't close my mac air down properly and when i tried to use it, the screen was frozen.  I turned it off and restarted it, and the grey screen with the apple logo appear and the circle just keeps spinning.  Can you advise?

    i didn't close my mac air down properly and when i tried to use it, the screen was frozen.  I turned it off and restarted it, and the grey screen with the apple logo appear and the circle just keeps spinning.  Can you advise?

    Try resetting the SMC
    Intel-based Macs: Resetting the System Management Controller (SMC)

  • My 2014 MacBook Pro stuck on grey screen since trying to update software over an hour ago

    My 2012 MacBook Pro has been stuck on the grey screen for more than hour since I tried updating the software.

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Maybe you are looking for

  • In Max, click Test Panel - Get Executable version (7.1.1) doesn't match resource file (7.1)

    Hi, I haven't used LabVIEW for a while. I plugged in a USB-6251 and ran Measurment and Automation explorer and saw that the USB-6251 was in the NI-DAQmx Device and was green. I clicked on the Test Panels button and got a window with the message: Get

  • Shipping tab missing in intercompany sto

    Hello every one, I configured Intercompany STO and I could complete the whole process of sto till to the invoice, I again created a vendor with reference to above intercompany vendor and started to create a PO and in this case I am unable to find the

  • How do I prevent Photostream from creating empty projects?

    With photostream on, it creates a project labelled "Nov 2011 Photo Stream" that is empty.  I don't remember creating this project, but I can't swear that I didn't. I delete the project, but everytime I reopen Aperture, it is recreated.  If I turn pho

  • S10-3 wirless driver on xp is not working

    hi i just bought lenovo s10-3 idea pad with window 7 started already preinstalled on it , but i decided to install windows xp instead well i could install all the drivers  that need but i couldnt find the wirless driver i tryed hard via google and so

  • "connect by" problem with "select distinct"

    When I run the following SQL (using "Scott" DB): select * from emp where deptno = 30 or mgr is null start with mgr is null connect by prior empno = mgr order siblings by ename I get the results one would expect. The President is first and all those r