Grey screen persists
Hi. For several hours now I have been trying to get my mac to restart properly. The problem began this morning while working in adobe photoshop where the spinning wheel kept causing stalls. Frustrated, quit APS I did a computer shut down. But when I wanted to restart the grey screen with grey spinning wheel kept appearing. Nothing happened. So shut down again using the command-option-shift-power keys. Then upluggied the computer, then power strip, and disconnected all external peripherals. Next, decided to start up in safe mode by hitting the shift key and power button, but again nothing but the persistent grey screen. Next, I tried to reset the pram, but grey screen then a black screen, then the grey screen.
I think maybe I should try to install my install disc and try. But is it ok to insert the disc while the grey screen and wheel is spinning? Don't want to install the disc and have something weird happen to it too.
Help most appreciative.
"Invalid sibling link", not a good sign.
You can shutdown from using your install dvd just like you always do. You can do a google search for "Invalid sibling link" and you will get lots of hits and possible solutions, most involving using terminal, which I don't think you will feel comfortable using.
One high level possibility (no guarantee) mentioned in some of those search hits is to use Disk Warrior, but is is not free.
Of course it's a little late now, but your situation is why you should always have backups of your system.
I'm not sure what else to suggest at this point other than what I mention in this post.
Similar Messages
-
Persistent grey screen on startup.
I own a late 2011 MacBook Pro running osx mavericks. Had it for two years with no problems. In early January of this year the macbook would crash whenever I opened photoshop or other programs like iMovie or photobooth. The only way to get it to function again was to hard restart the laptop. And Even then sometimes I would get the grey screen on start up and hear three beeps. I Went to the Genius Bar and the employee reseated the RAM and the laptop functioned well for a week. When the persistent grey screen appeared again, the genius employee erased all my storage, with my permission, reset my operation system completely. Even still I get the grey screen and the laptop doesn't make it to the login. What should I do to fix it? Would buy info new ram solve the problem? If tried pessimg shift and running in safe mode but I just get a blue screen and am forced to hard reset.
Hi there friends
I don't have apple help in my city
I'm using MBP as desktop removed battery due to batter sensors issue.
It is late 2011.
It started with no startup tone chime than I set nvram so startup tone came but the persisting issue is grey bar at the startup blow apple logo that takes 20 min almost and after completion MBP turns off and requires manual turn on and upon re turning on again that grey bat appears same fasion.
Some one told me to go to safe mode and apply some changes but I can't go to safe mode with shift key startup login Id password bar appears and constant shift key press interrupts and again grey bat appears.
I don't know how to disable startup password and how to disable vault.
Please help me in
How to get into safe mode
How to get rid of grey bar on startup
My discs are working well I checked in recovery.
Please help me even I don't have disc
And if you could help me in how to open a USB net modem.with the MBP having same issues as with mine
Thanks -
TS3148 my mackbook air starts up with a persistent grey screen, apple logo and spinning gear
my mackbook air starts up with a persistent grey screen, apple logo and a spinning gear. It will not show the login window
Press and hold the power button down to force a hardware shutdown (emergency use only!)
Next find the Shift key and hold it and press the power button, the machine will boot into Safe Mode.
Next backup your files to a external drive just in case.
Emergency backup procedure
Drag and drop copy your users file folders (music, pictures, documents etc) to a regular external powered drive as soon as possible.
Do not use, setup or trust only TimeMachine at this troubled time as it will copy corrupted data and we need just your users files safe just in case. TimeMachine cannot be used with a Windows PC.
Unmount and Disconnect all external drives once the backup process is completed.
Note:
If you have any over 4GB sized files, those won't copy to a standard formatted FAT32/MSDOS drive from the factory, if you need to save these 4GB+ files use another blank/empty drive and use Disk Utility to format it 1 Partition, Option: GUID, Format: OS X Extended Journaled (or the standard default one for older Mac's).
Mac's cannot copy to nor format a NTFS drive. ExFAT format to be used with a Windows machine must be right click formatted by Windows, not OS X (does it wrong) XP macines can install a free exFAT update from Microsoft. Vista-Win 8 can format exFAT.
Formatting a drive will erase all data on it.
Most commonly used backup methods
Your problem is likely due to a incompatible third part at boot kernel extension file that some program installed into OS X at some time.
If you can recall which programs you installed using your Admin password then that's a good place to start and update or uninstall those programs.
The next solution is a #8 Reinstall Just OS X + Software Update fully, this will replace OS X with a new copy, fix OS X if it's the cause and kick out ALL third party kext files out of OS X.
You also can manually drag and drop the third party kext files (if you know what they are) out of of the System/Library/Extensions folder and reboot.
..Step by Step to fix your Mac
Solving at boot kext issues in Snow Leopard -
Disk repair and Apple Hardware Test says HD has no problem but grey screen still persists on MBP
5 days ago while on vacation, my MBP just froze with the grey screen, apple logo and spinning gear.
I performed all that was instructed on the following discussions:
http://support.apple.com/kb/TS2570
except Archive and Install installation of MAC OS X and Erase and Install MAC OS X since I was able to save my files in my husband's MBP via Firewire Target Disk Mode. At this point, I am still apprehensive in erasing my files and installing again the MAC OS X.
When I did the Disk Repair under the Disk utilities, it says that my Mac Os X is ok. (It also said ok when I did the fsck -fy when I till did not have my CD when I was on vacation)
I also tried the Apple Hardware Test (AHT) to further l test the hardware of my MBP and performed an extended checking and after an hour, its says that my HD has no problem.
Yet, after all these, when I restart my computer, it still has the grey screen with apple logo and spinning wheel!
Can anyone tell me what else can I do??? Appreciate any help!I like the free demo of SuperDuper to make clones. It's free, Leopard and Snow ready and is easy to use. If you buy the full version you can do incremental backups.
You should use Disk Utility to do a Disk Repair, as shown in this link, booted up on your install disk, before you make a clone of it. I use DiskWarrior for that instead.
I then partition my external disk, in Disk Utility, with a partition that is the same size , actually a tad bigger, as my system disk. I then use SuperDuper to clone my system disk over to that partition.
With a clone on an external FireWire drive (USB drives are not bootable on PPC Macs but are on some Intel Macs) you can bootup on it to do your repairs, on the main drive, or just run your Mac anytime you have trouble with your main drive.
That's why I like clones better then Time Machine. You can just bootup on them and use your Mac.
On the DiskWarrior thing, I use DW once a month to try and catch errors in my system from getting too far out of hand. It has repaired every little and big issue I have ever had with my three Macs.
And I have had times when Disk Utility's Disk Repair says everything's fine but my system was still having issues. Disk Utility, in my experience, cannot be totally relied on to find and report all issues. It just isn't robust enough.
I run DiskWarrior, it does find errors, repairs them and I'm back in business. I swear by it!
DALE -
Your computer shut down because of a problem. Mac grey screen
Recently I have been having issues with my Mac.
The computer will freeze for no apparent reason and the screen goes ever so slightly blue, then crashes to grey screen - 'Your computer has shut down... blah blah blah' and then it restarts itself and i get a kernel panic (Below is the msot recent one).
At christmastime I installed extra RAM which could be a problem but I think the problem occurs when using Google Chrome. I have tried to switch to Safari for the time being to see if that eliminates the problem but I did use Chrome at some point today.
I believe that I lasted longer without the problem while I was using Safari.
Any help reading the panic log would be appreciated!
Cheers
As I was writing this (on Safari) the screen went completely black and restarted to the grey screen
Report:
Anonymous UUID: 54E61FB9-8E93-6428-45F2-05526730A5C1
Wed Jan 15 19:34:06 2014
panic(cpu 0 caller 0xffffff800e8dc19e): Kernel trap at 0xffffff800ecb937d, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff807e9633d4, CR3: 0x000000002250d000, CR4: 0x0000000000000660
RAX: 0xffffff802f88fb78, RBX: 0x0000000000000000, RCX: 0x0000000000001400, RDX: 0x0000000000000008
RSP: 0xffffff80be9633c0, RBP: 0xffffff80be9634b0, RSI: 0x0000000000000000, RDI: 0xffffff801f13c0c0
R8: 0x0000000000000096, R9: 0xffffff802f88fb00, R10: 0x0000000000000001, R11: 0xffffff801e0a0900
R12: 0xffffff802f88fb00, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0x0000000000001400
RFL: 0x0000000000010246, RIP: 0xffffff800ecb937d, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff807e9633d4, Error code: 0x0000000000000000, Fault CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff80be963050 : 0xffffff800e822f69
0xffffff80be9630d0 : 0xffffff800e8dc19e
0xffffff80be9632a0 : 0xffffff800e8f3606
0xffffff80be9632c0 : 0xffffff800ecb937d
0xffffff80be9634b0 : 0xffffff800ecb982e
0xffffff80be9634e0 : 0xffffff7f90342cea
0xffffff80be963660 : 0xffffff7f90342a03
0xffffff80be963670 : 0xffffff7f90307cd0
0xffffff80be963680 : 0xffffff7f90307d45
0xffffff80be963690 : 0xffffff7f902e9b11
0xffffff80be9636d0 : 0xffffff7f902ec085
0xffffff80be963700 : 0xffffff7f9033cb50
0xffffff80be963780 : 0xffffff7f90324cc0
0xffffff80be9637e0 : 0xffffff7f903255ba
0xffffff80be963830 : 0xffffff7f90325aa0
0xffffff80be9638a0 : 0xffffff7f903261a8
0xffffff80be9638e0 : 0xffffff7f902f31ca
0xffffff80be963a60 : 0xffffff7f90322b20
0xffffff80be963b20 : 0xffffff7f902f1cb9
0xffffff80be963b70 : 0xffffff800eccc226
0xffffff80be963b90 : 0xffffff800eccd821
0xffffff80be963bf0 : 0xffffff800eccb28f
0xffffff80be963d40 : 0xffffff800e8b6008
0xffffff80be963e50 : 0xffffff800e826bb1
0xffffff80be963e80 : 0xffffff800e8139b5
0xffffff80be963ef0 : 0xffffff800e81e003
0xffffff80be963f70 : 0xffffff800e8c921d
0xffffff80be963fb0 : 0xffffff800e8f3e26
Kernel Extensions in backtrace:
com.apple.GeForceTesla(8.1.8)[67BAF872-A238-3787-AB74-22297A51FE8F]@0xffffff7f9 02e0000->0xffffff7f903aafff
dependency: com.apple.iokit.IOPCIFamily(2.8)[447B4896-16FF-3616-95A2-1C516B2A1498]@0xffffff 7f8eed2000
dependency: com.apple.iokit.IONDRVSupport(2.3.6)[86BA68C6-18DD-30A1-ABF6-54597AD6C277]@0xff ffff7f8f334000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.6)[38E388A5-92D6-3388-B799-F2498E582287]@0 xffffff7f8f17e000
dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.1.8)[0A1B6F41-168D-307A-BABD-162F3B3 C2786]@0xffffff7f8f344000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
13A603
Kernel version:
Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
Kernel slide: 0x000000000e600000
Kernel text base: 0xffffff800e800000
System model name: MacBookPro7,1 (Mac-F222BEC8)
System uptime in nanoseconds: 5774181339652
last loaded kext at 789315214894: com.apple.filesystems.smbfs 2.0.0 (addr 0xffffff7f90cb2000, size 335872)
last unloaded kext at 352614516015: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f90cb0000, size 57344)
loaded kexts:
com.regularrateandrhythm.driver.RowmoteIREmu 1.0
com.sophos.kext.sav 9.0.53
com.splashtop.driver.SRXFrameBufferConnector 1.6
com.splashtop.driver.SRXDisplayCard 1.6
com.Cycling74.driver.Soundflower 1.6.6
com.sophos.nke.swi 9.0.53
com.logmein.driver.LogMeInSoundDriver 1.0.2
com.globaldelight.driver.BoomDevice 1.1
com.apple.filesystems.smbfs 2.0.0
com.apple.filesystems.ntfs 3.11
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AGPM 100.14.11
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.2.0f6
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleHDA 2.5.2fc2
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleMikeyDriver 2.5.2fc2
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.GeForceTesla 8.1.8
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.0f6
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleBacklight 170.3.5
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.driver.AppleMCCSControl 1.1.12
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleIRController 325.7
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleUSBCardReader 3.3.5
com.apple.iokit.SCSITaskUserClient 3.6.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.4.0
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.iokit.AppleBCM5701Ethernet 3.6.9b9
com.apple.driver.AppleUSBHub 650.4.4
com.apple.driver.AppleFWOHCI 4.9.9
com.apple.driver.AppleAHCIPort 2.9.5
com.apple.driver.AppleUSBOHCI 650.4.1
com.apple.driver.AppleUSBEHCI 650.4.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleSMBIOS 2.0
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 216.0.0
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 216.0.0
com.apple.AppleGraphicsDeviceControl 3.4.12
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.driver.DspFuncLib 2.5.2fc2
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOSurface 91
com.apple.iokit.IOBluetoothFamily 4.2.0f6
com.apple.iokit.IOAudioFamily 1.9.4fc11
com.apple.kext.OSvKernDSPLib 1.14
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.nvidia.classic.NVDANV50HalTesla 8.1.8
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.0f6
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.driver.AppleHDAController 2.5.2fc2
com.apple.iokit.IOHDAFamily 2.5.2fc2
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.driver.IOPlatformPluginFamily 5.5.1d27
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.driver.AppleSMBusController 1.0.11d1
com.apple.nvidia.classic.NVDAResmanTesla 8.1.8
com.apple.iokit.IONDRVSupport 2.3.6
com.apple.iokit.IOGraphicsFamily 2.3.6
com.apple.driver.AppleSMC 3.1.6d1
com.apple.driver.AppleUSBMultitouch 240.6
com.apple.iokit.IOUSBHIDDriver 650.4.4
com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.0
com.apple.iokit.IOUSBMassStorageClass 3.6.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 650.4.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.0
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.6.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.0
com.apple.iokit.IO80211Family 600.34
com.apple.iokit.IOEthernetAVBController 1.0.3b3
com.apple.driver.mDNSOffloadUserClient 1.0.1b4
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOUSBUserClient 650.4.4
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOAHCIFamily 2.6.0
com.apple.iokit.IOUSBFamily 650.4.4
com.apple.driver.NVSMU 2.2.9
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.10
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 21
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.8
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
Anonymous UUID: 54E61FB9-8E93-6428-45F2-05526730A5C1
Wed Jan 15 17:03:55 2014
panic(cpu 1 caller 0xffffff800adda9b0): "vnode_rele_ext: vp 0xffffff8026f282d0 usecount -ve : -1. v_tag = 0, v_type = 1, v_flag = 84800."@/SourceCache/xnu/xnu-2422.1.72/bsd/vfs/vfs_subr.c:1788
Backtrace (CPU 1), Frame : Return Address
0xffffff80158f35e0 : 0xffffff800ac22f69
0xffffff80158f3660 : 0xffffff800adda9b0
0xffffff80158f36a0 : 0xffffff7f8b1be77e
0xffffff80158f36c0 : 0xffffff7f8b1bdf70
0xffffff80158f39f0 : 0xffffff7f8b1bfeb3
0xffffff80158f3a30 : 0xffffff800afb3671
0xffffff80158f3a90 : 0xffffff800addf80d
0xffffff80158f3ae0 : 0xffffff800adf4360
0xffffff80158f3b80 : 0xffffff800ade5f15
0xffffff80158f3c30 : 0xffffff800ade67d2
0xffffff80158f3f50 : 0xffffff800b03de23
0xffffff80158f3fb0 : 0xffffff800acf3e06
Kernel Extensions in backtrace:
com.sophos.kext.sav(9.0.53)[00000000-0000-0000-0000-000000000000]@0xffffff7f8b1 bd000->0xffffff7f8b1c1fff
BSD process name corresponding to current thread: mds_stores
Mac OS version:
13A603
Kernel version:
Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
Kernel slide: 0x000000000aa00000
Kernel text base: 0xffffff800ac00000
System model name: MacBookPro7,1 (Mac-F222BEC8)
System uptime in nanoseconds: 78786791674337
last loaded kext at 78774646540958: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f8d102000, size 65536)
last unloaded kext at 78756353100860: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f8d102000, size 57344)
loaded kexts:
com.regularrateandrhythm.driver.RowmoteIREmu 1.0
com.sophos.kext.sav 9.0.53
com.splashtop.driver.SRXFrameBufferConnector 1.6
com.splashtop.driver.SRXDisplayCard 1.6
com.Cycling74.driver.Soundflower 1.6.6
com.sophos.nke.swi 9.0.53
com.logmein.driver.LogMeInSoundDriver 1.0.2
com.globaldelight.driver.BoomDevice 1.1
com.apple.filesystems.msdosfs 1.9
com.apple.driver.AppleUSBCDC 4.2.1b2
com.apple.filesystems.smbfs 2.0.0
com.apple.filesystems.ntfs 3.11
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AGPM 100.14.11
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.2.0f6
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleHDA 2.5.2fc2
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.0f6
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleMikeyDriver 2.5.2fc2
com.apple.GeForceTesla 8.1.8
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.driver.AppleBacklight 170.3.5
com.apple.driver.AppleMCCSControl 1.1.12
com.apple.driver.AudioAUUC 1.60
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleIRController 325.7
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.AppleUSBCardReader 3.3.5
com.apple.iokit.SCSITaskUserClient 3.6.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.4.0
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.iokit.AppleBCM5701Ethernet 3.6.9b9
com.apple.driver.AppleUSBHub 650.4.4
com.apple.driver.AppleFWOHCI 4.9.9
com.apple.driver.AppleAHCIPort 2.9.5
com.apple.driver.AppleUSBOHCI 650.4.1
com.apple.driver.AppleUSBEHCI 650.4.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleSMBIOS 2.0
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 216.0.0
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 216.0.0
com.apple.AppleGraphicsDeviceControl 3.4.12
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.driver.DspFuncLib 2.5.2fc2
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.0f6
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.driver.AppleHDAController 2.5.2fc2
com.apple.iokit.IOHDAFamily 2.5.2fc2
com.apple.nvidia.classic.NVDANV50HalTesla 8.1.8
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.nvidia.classic.NVDAResmanTesla 8.1.8
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IOSurface 91
com.apple.iokit.IOBluetoothFamily 4.2.0f6
com.apple.iokit.IOAudioFamily 1.9.4fc11
com.apple.kext.OSvKernDSPLib 1.14
com.apple.driver.AppleSMBusController 1.0.11d1
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.driver.IOPlatformPluginFamily 5.5.1d27
com.apple.iokit.IONDRVSupport 2.3.6
com.apple.iokit.IOGraphicsFamily 2.3.6
com.apple.driver.AppleSMC 3.1.6d1
com.apple.driver.AppleUSBMultitouch 240.6
com.apple.iokit.IOUSBHIDDriver 650.4.4
com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.0
com.apple.iokit.IOUSBMassStorageClass 3.6.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 650.4.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.0
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.6.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.0
com.apple.iokit.IO80211Family 600.34
com.apple.iokit.IOEthernetAVBController 1.0.3b3
com.apple.driver.mDNSOffloadUserClient 1.0.1b4
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOUSBUserClient 650.4.4
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOAHCIFamily 2.6.0
com.apple.iokit.IOUSBFamily 650.4.4
com.apple.driver.NVSMU 2.2.9
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.10
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 21
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.8
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
Model: MacBookPro7,1, BootROM MBP71.0039.B0E, 2 processors, Intel Core 2 Duo, 2.4 GHz, 6 GB, SMC 1.62f7
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x029E, 0x434D33583447534431303636202020202020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334648302D4346382020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.0f6 12982, 3 services, 23 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST9500325ASG, 500.11 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: Built-in iSight
USB Device: Internal Memory Card Reader
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: IR Receiver
USB Device: Apple Internal Keyboard / Trackpad
Thunderbolt Bus:Hi kiplin1995,
Thanks for visiting Apple Support Communities.
If you have not already, I would recommend removing the additional RAM and seeing if the issue persists. See this article for more information:
OS X: When your computer spontaneously restarts or displays "Your computer restarted because of a problem."
http://support.apple.com/kb/TS4636
Check internal RAM and third-party hardware
Turn off your Mac.
Reseat the Apple RAM, and remove third-party RAM and third-party internal hardware. If you do not have the Apple RAM that came with the system, reseat the third-party RAM.
Turn on your Mac.
Use your Mac for the amount of time it would usually take for a kernel panic to occur.
If the kernel panic does not occur: The third-party RAM or internal third-party hardware may need to be replaced.
If a kernel panic does occur: Bring your Mac to an Apple Store, or an Apple Authorized Service Provider for service and support. Be sure to ask that, if the drive needs reformatting or replacing, they contact you about escalating your case to a special data recovery service. If you plan to visit an Apple Retail store, you can make a reservation (available in some countries only).
Best,
Jeremy -
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! -
MBP Screen Distortion/Flicker Goes into Grey Screen Loop
Hello All!
Model: MBP 3.1,
SMC Version: 1.16f11
Device ID for 8600M GT: 0x0407
Revision ID for 8600M GT: 0x00a1
Basically, started seeing this problem when I upgraded into 10.5.8. At first, it would freeze on my screen saver so I would just restart it. Then one day, it froze on the screen saver again so I restarted and I got the grey screen in which it tells you to restarts. Thus, I logically thought it was the hard drive so I inserted the install disk and verified and repaired the hard-disk and it was found to contain no errors. So then I used it for another day and then my screen started to flicker and like display distortions of pixels with some pinkish hue. At this point I couldn't really do much, I could move the mouse around but not really do anything else, my only option from there was to restart into which I was greeted by the grey screen again that tells you to restart. Thus, I decided to reformat to correct the problem. I have reformatted a fresh copy of leopard and am running 10.5.8. I have also ran the hardware diagnostics test by inserting my original Tiger disks and the results came out clean, in which no hardware errors were found.
Basically, at this point I am confused I have read the Article: TS2377 in which it explains that the 8600M GT might be a cause of this problem, but the hardware diagnostics that I ran from the disks displayed no error. So I am afraid that once I take it to the "genius" they will feed me some sort of "crap" and try to trick me into paying for something that seems clearly is caused from the nvidia graphics card. I really do not know what else can be causing the problem.
I have also added some pictures of the distortions and pixels that I seen and the error report that I have received.
Thanks, any help would be much appreciated it.
*ERROR REPORT:*
Interval Since Last Panic Report: 0 sec
Panics Since Last Report: 1
Anonymous UUID: F8D96EA8-C3D9-4F06-8272-4C1419E26365
Wed Aug 19 22:31:11 2009
panic(cpu 0 caller 0x001AB0FE): Kernel trap at 0x00b44c1e, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x014a0000, CR4: 0x00000660
EAX: 0x2eb59630, EBX: 0x04f4f404, ECX: 0x04d3e000, EDX: 0x00000000
CR2: 0x000000bc, EBP: 0x2eb59668, ESI: 0x00000000, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00b44c1e, CS: 0x00000008, DS: 0x04d30010
Error code: 0x00000000
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x2eb59408 : 0x12b4c6 (0x45f91c 0x2eb5943c 0x13355c 0x0)
0x2eb59458 : 0x1ab0fe (0x469a98 0xb44c1e 0xe 0x469248)
0x2eb59538 : 0x1a1713 (0x2eb59550 0x9 0x2eb59668 0xb44c1e)
0x2eb59548 : 0xb44c1e (0xe 0x48 0x2eb50010 0xb70010)
0x2eb59668 : 0xb4cbaa (0xc1d00005 0x1000000 0x1000003 0x40)
0x2eb596c8 : 0xb3f28f (0x2eb59858 0x6 0x0 0x0)
0x2eb59828 : 0xb30402 (0x0 0x600d600d 0x7027 0x2eb59858)
0x2eb598e8 : 0xd1e01b (0xc1d00005 0x1000000 0x1000003 0x40)
0x2eb59918 : 0xd297ac (0x242a8000 0x1000000 0x88100090 0x3e)
0x2eb5b8a8 : 0xd05189 (0x242a8000 0x1000000 0x15 0x242a801c)
0x2eb5b9a8 : 0xb2bb29 (0x242a8000 0x0 0x2eb5bab2 0x80)
0x2eb5ba08 : 0xb2069d (0x4715400 0x0 0x2eb5bab2 0x80)
0x2eb5bb38 : 0xb21f44 (0x4715400 0xb2562c 0x2eb5bbec 0x4)
0x2eb5bc08 : 0x7e1c18 (0x4715400 0x1 0x0 0x13)
0x2eb5bc68 : 0x7dabe6 (0x4715400 0x2eb5bd2c 0x421d0bc 0x4715400)
0x2eb5bc98 : 0x415e83 (0x4715400 0x421d0bc 0x421d0bc 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.4.8)@0xb28000->0xd86fff
dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0xb1a000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x5ce000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x7d2000
com.apple.iokit.IONDRVSupport(1.7.3)@0xb1a000->0xb27fff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x5ce000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x7d2000
com.apple.iokit.IOGraphicsFamily(1.7.3)@0x7d2000->0x7eefff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x5ce000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
9L31a
Kernel version:
Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)
System uptime in nanoseconds: 34142102374
unloaded kexts:
(none)
loaded kexts:
com.apple.driver.InternalModemSupport 2.4.0 - last loaded 31982254262
com.apple.driver.AppleHDAPlatformDriver 1.7.1a2
com.apple.driver.AppleUpstreamUserClient 2.7.5
com.apple.driver.AppleHDAHardwareConfigDriver 1.7.1a2
com.apple.driver.AppleHDA 1.7.1a2
com.apple.GeForce 5.4.8
com.apple.iokit.IOBluetoothSerialManager 2.1.8f2
com.apple.filesystems.autofs 2.0.2
com.apple.driver.AppleIRController 113
com.apple.DontSteal_Mac_OSX 6.0.3
com.apple.nvidia.nv50hal 5.4.8
com.apple.driver.ACPISMCPlatformPlugin 3.4.0a17
com.apple.driver.AirPort.Atheros 320.16.2
com.apple.driver.AppleHDAController 1.7.1a2
com.apple.iokit.IOFireWireIP 1.7.7
com.apple.driver.SMCMotionSensor 2.1.1d2
com.apple.driver.AudioIPCDriver 1.0.6
com.apple.kext.AppleSMCLMU 1.4.5d1
com.apple.driver.AppleLPC 1.3.1
com.apple.driver.AppleGraphicsControl 2.8.15
com.apple.driver.AppleBacklight 1.6.0
com.apple.driver.AppleTyMCEDriver 1.0.0d28
com.apple.driver.AppleUSBTrackpad 1.7.4f1
com.apple.driver.AppleUSBTCKeyEventDriver 1.7.4f1
com.apple.driver.AppleUSBTCKeyboard 1.7.4f1
com.apple.driver.CSRUSBBluetoothHCIController 2.1.8f2
com.apple.driver.CSRHIDTransitionDriver 2.1.8f2
com.apple.driver.AppleUSBMergeNub 3.4.6
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.1.1
com.apple.iokit.SCSITaskUserClient 2.1.1
com.apple.driver.XsanFilter 2.7.91
com.apple.iokit.IOAHCIBlockStorage 1.2.2
com.apple.iokit.AppleYukon2 3.1.13b2
com.apple.driver.AppleFileSystemDriver 1.1.0
com.apple.driver.AppleAHCIPort 1.7.0
com.apple.iokit.IOATAPIProtocolTransport 1.5.3
com.apple.driver.AppleUSBHub 3.4.9
com.apple.iokit.IOUSBUserClient 3.4.9
com.apple.driver.AppleFWOHCI 3.9.7
com.apple.driver.AppleUSBEHCI 3.4.6
com.apple.driver.AppleIntelPIIXATA 2.0.1
com.apple.driver.AppleUSBUHCI 3.3.5
com.apple.driver.AppleEFINVRAM 1.2.0
com.apple.driver.AppleSmartBatteryManager 158.10.5
com.apple.driver.AppleRTC 1.2.3
com.apple.driver.AppleHPET 1.4
com.apple.driver.AppleACPIPCI 1.2.5
com.apple.driver.AppleACPIButtons 1.2.5
com.apple.driver.AppleSMBIOS 1.4
com.apple.driver.AppleACPIEC 1.2.5
com.apple.driver.AppleAPIC 1.4
com.apple.security.seatbelt 107.12
com.apple.nke.applicationfirewall 1.6.77
com.apple.security.TMSafetyNet 3
com.apple.driver.AppleIntelCPUPowerManagement 76.2.0
com.apple.driver.DiskImages 199
com.apple.BootCache 30.4
com.apple.driver.DspFuncLib 1.7.1a2
com.apple.iokit.IOSerialFamily 9.4
com.apple.NVDAResman 5.4.8
com.apple.driver.IOPlatformPluginFamily 3.4.0a17
com.apple.iokit.IO80211Family 216.1
com.apple.iokit.IOHDAFamily 1.7.1a2
com.apple.iokit.IOAudioFamily 1.6.9fc5
com.apple.kext.OSvKernDSPLib 1.1
com.apple.driver.AppleSMC 2.3.1d1
com.apple.iokit.IONDRVSupport 1.7.3
com.apple.iokit.IOGraphicsFamily 1.7.3
com.apple.iokit.IOUSBHIDDriver 3.4.6
com.apple.driver.AppleUSBBluetoothHCIController 2.1.8f2
com.apple.iokit.IOBluetoothFamily 2.1.8f2
com.apple.driver.AppleUSBComposite 3.2.0
com.apple.iokit.IOSCSIBlockCommandsDevice 2.1.1
com.apple.iokit.IOBDStorageFamily 1.5
com.apple.iokit.IODVDStorageFamily 1.5
com.apple.iokit.IOCDStorageFamily 1.5
com.apple.iokit.IONetworkingFamily 1.6.1
com.apple.iokit.IOAHCIFamily 1.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily 2.1.1
com.apple.iokit.IOFireWireFamily 3.4.9
com.apple.iokit.IOATAFamily 2.0.1
com.apple.iokit.IOUSBFamily 3.4.9
com.apple.driver.AppleEFIRuntime 1.2.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.iokit.IOStorageFamily 1.5.6
com.apple.iokit.IOHIDFamily 1.5.5
com.apple.driver.AppleACPIPlatform 1.2.5
com.apple.iokit.IOACPIFamily 1.2.0
com.apple.iokit.IOPCIFamily 2.6
PICTURES:
http://img170.imageshack.us/img170/3705/dsc02407a.jpg
http://img200.imageshack.us/img200/6653/dsc02408q.jpgI can't really read your panic log, but my guess would be the NVIDIA graphics chip. Do you get the same thing on an external display? If so, that would indicate a graphics chip problem and not an internal display problem.
Apple has a specific hardware test for the NVIDIA chip problem, and to get the problem fixed, you will have to go to them and have them run it. It is a different test than the Apple Hardware Test that we have, which may or may not indicate a problem. From what I have read in other threads, the NVIDIA problem may or may not be detected by the AHT. I've even heard of the AHT giving an error code and not the official test, which makes me wonder just what these test are designed to detect.
Take along your photos and have them read the panic log. If a genius can't get the error on the official test, ask to speak to the store manager. Be polite, but persistent. There could be something else going on as well as the graphics problem, but Apple likes to have happy customers, so I think in view of the fact that graphics problems with this chip is a well-known issue, they should in the end be willing to fix the problem at no cost to you.
Good luck! -
Macbook Pro will not boot beyond grey screen. System freezes.
My Macbook Pro will not boot-up or get beyond the grey screen (with spinning gear wheel.) I've tried all the recommended actions: resetting PRAM, disk repair, permissions repair, re-boot in safe mode etc but still the problem persists. When viewing the safe-boot in verbose mode, the system seems to hang at the stage when it's checking the Airport & Ethernet - the last line on the page reads: "AppleBCOM5701Ethernet: 0 0 setFixedSpeed - logic error, speed any?"
Any ideas how to fix this without doing an Archive & Install?
I'm assuming that if I do an "Archive & Install" then I will lose all my Applications (VLC, Handbrake, MS Office for Mac etc.) Will this actually be the case? Will I lose them.
Any help gratefully received. Many thanks.jfromplymouth wrote: ...I'm assuming that if I do an "Archive & Install" then I will lose all my Applications (VLC, Handbrake, MS Office for Mac etc.) Will this actually be the case? Will I lose them...
Archive and Install just affects the System files, so any apps you have should still be available afterwards. The Installer on the disk that came with your Mac, when you bought it, will tell you this before you proceed. Of course, you can always back out of the Installer if you feel chicken.
Notwithstanding it is still necessary to backup everything. You need to check that Time Machine is set to also backup your Applications folder. It might be set not to do this.
It may not be necessary to worry about this if you have the original installer disc(s). I think any stuff downloaded from iTunes etc can be re-downloaded. However, it's probably quicker to get Time Machine to backup your apps if you can afford the HDD space. It's bound to be quicker than re-downloading the stuff plus any updates. And of course there's those Apps that you have but forgotten about. What about them? -
When I turn on my iMac (27" intel) all I get is connect my wireless keyboard and mouse on a grey screen. The mouse will connect (sometimes) after I wiggle it a bit, but nothing from the keyboard. After a few minutes the disk utilities box comes up. I ran permissions and repair permissions, verify and repair on my computer and it tells me everything is ok. But it won't let me past this screen. Any suggesions? Help!?!
Hi Grace Be,
Welcome to the Support Communities!
The articles below may be able to help you with this. I've summarized some of the key points below for you. Click on the links to see more details and screenshots.
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/TS2570
Disconnect, test peripheral devices and network cables
Note: "Peripheral devices" refers to external devices other than what came with your Mac, such as hard drives, printers, or hubs that you connect via a USB or FireWire cable.
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Disconnect all peripheral devices such as external hard drives or printers (leave only the display, a keyboard, and mouse connected).
Disconnect any Ethernet cables.
Start up your Mac.
If you can start up this way, one or more of your peripheral devices (or installed software related to the device) is probably causing the gray screen issue. Connect one device, then restart your Mac to test for the issue. Repeat the process until you locate the device at issue. Check with the manufacturer of the device for support or possible software driver or firmware updates that may be available for the device. Try a different cable with the device if possible (such as a different USB or FireWire cable).
If you are using a desktop Mac with a third-party keyboard and/or mouse device, and the issue still occurs, try starting up with an Apple keyboard and mouse connected instead. Try starting with no keyboard and mouse connected, then connect them after start up. Also, try a different USB port on your Mac.
If the gray screen issue persists with no devices connected, go to the next section (with the peripherals still disconnected).
Perform a Safe Boot
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Start your Mac, then immediately hold the Shift key. This performs a Safe Boot. Advanced tip: If you want to see the status of a Safe Boot as it progresses, you can hold Shift-Command-V during start up (instead of just Shift).
Note: A Safe Boot takes longer than a typical start up because it includes a disk check and other operations.
If your Mac starts up as expected, immediately try restarting.
If the Safe Boot does not work, or the restart after a successful Safe Boot does not work, go to the next section.
Reset the NVRAM / PRAM
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Reset the NVRAM / PRAM.
I hope this information helps ....
Have a great day!
- Judy -
Mac freezes, shows grey screen then starts back up
For the past two weeks I have had the issue of my iMac suddenly freezing for a few seconds and then it turns to a grey screen for a few more seconds before it starts back up on my user area.
All programs get shut down (which is annoying as I do graphic design so I'm usually on PS or AI and lose work I've done since last save). Programs which are set to start up automatically upon login do not start up. Thankfully firefox will start back up when I click it and continue from all the tabs I had open.
I cannot seem to find a source for this to be happening... The programs which are always running when this has happened previously are: Mac Mail, finder, Messages, Spotify, Wacom Desktop Center. This morning it happened when none of my adobe programs were running.
Has anyone had the same issue or knows what's up?
I tried to go to apple support but it said I need to pay £35 for someone to answer my question.
27" iMac
Late 2012
16GB
1TB storage with 431gb free
running OSX10.8.5Hi,
Try ; Intel-based Macs: Resetting the System Management Controller (SMC)
and : About NVRAM and PRAM
to ensure the proper operation of the SMC.
and if still issues persist, try: OS X: What is Safe Boot, Safe Mode?
Cheers -
10.8.1 won't shut down, grey screen
Fresh clean install on 2009 Nehalem Mac Pro with upgraded Kingston SSD drive. Everything was working flawlessly for 3 weeks.
1) Shut Down Dialogue
2) Desktop disappears
3) Computer hangs in a light grey screen, remain powered on. Mouse movements accepted.
I ran Cache Cleaner, repaired permissions... problem persists. Any help much appreciated.Try downloading the Trim enabler app - (google OSX trim Enabler) and enable TRIM - by default and for some ridiculous reason that I cant figure, Apple dont support Trim on any after-market SSD - however if your drive is Trim capable having trim switched off can indeed result in some strange delays and hangs. It will also shorten the life of your SSD.
When ever you update OSX - you need to re-enable trim as the enabler works by patching a file. This is also how I know that the symptom you decribe is probably trim related - because I had this exact symptom when I upgraded to 10.8.1 and lost the trim patch that I had orginally loaded in 10.8.0 -
Mac won't boot, stuck on grey screen if the external hdd plugged in
as the title.
if i plug my external drive, via usb port, the mac won't boot and stuck at grey screen.
unplugging it, the boot process will continue.
the hdd is a LaCie mobile hdd
any help?Hello jason(?)
It's a LaCie external mobiel hdd, formatted as exFAT. without adapter. take power directly from usb port.
i tested it on my iMac and it works fine. boot up as normal. the only difference is my iMac is on 10.6.8 and my Air is on 10.7.2
I tested on both USB port on my Air and the problem still persist.
the read/write speed is normal (bought it like a day ago).
another thing is I don't have this problem with my external WD drive.
One thing to notice is that, I accidentally left like for like 2-3 mins and it boots. So why the question now is why it's taking so long to boot? normally it just takes <20 seconds. Seems like it tried to boot from the external hdd, doesn't it? -
Stuck on grey screen with apple logo after failed iTunes update
I tried to install an update for iTunes 9.2 on my MacBook. During installation a box appeared telling me the update had failed. I clicked the 'Restart' button. Now it won't go past the grey screen with the apple logo and the rotating wheel; it just loads indefinitely. I have a very important document saved on the Mac which I've added to without backing it up. I'm worried that I will lose (or have already lost) a great deal of writing. Is there a way to get my computer running again without damaging my files? Because this computer was a gift, I don't have the software installation CDs that came with it (or Disk Utility). I'm also not very familiar with computers in general, so if you explain your solutions in a really basic way, I'd appreciate it. Any kind of advice would be extremely welcomed...
This one?
http://docs.info.apple.com/article.html?artnum=106214
Resolve startup issues and perform disk maintenance with Disk Utility and fsck
* Last Modified: June 25, 2009
* Article: TS1417
* Old Article: 106214
[Email this article]
[Print this page]
Symptoms
If your computer won't start up normally, you may need to use a disk repair utility to fix the issue. Mac OS X includes two utilities for this—Disk Utility and fsck (a command-line utility). You can also use these even when your computer starts just fine but you want to check the disk for possible file system issues. For Mac OS X 10.4.3 or later, check out "About live verification in Mac OS X 10.4.3 or later," below.
Important: If you're using Mac OS X 10.4 or later, you should use Disk Utility instead of fsck, whenever possible.
In some situations, file system errors may prevent your computer from starting up. This can occur after an improper shutdown, forced restart, or power interruption. If your computer shows any of the following symptoms on startup, use a disk repair utility:
* Your computer partially starts but then displays a command line in a text-only environment. You may see the message, "file system dirty, run fsck." Below it, you'll see what's called a command-line prompt, indicated by a number sign (#), that allows you to type a command. If you see this, you'll need to run fsck from the command line (see "Use fsck if necessary," below).
* Your computer starts but either it won't reach the login screen, or it may reach the login screen but not load the Desktop after you log in. However, you can start up in single-user mode.
If your computer exhibits either of the above issues, here are some things to try to get your computer back to starting up properly again. If you can't find the system discs that came with your computer, see "Use fsck," below.
Products Affected
Mac OS X 10.4, Mac OS X 10.3, Mac OS X 10.2, Mac OS X 10.1
Resolution
Try a Safe Boot
If you're using Mac OS X 10.2 or later, you can start up your computer in Safe Mode, which includes an automatic disk check and repair. If you're using Mac OS X 10.1.5 or earlier, skip to the next section. A Safe Boot, which starts up your computer into Safe Mode, may allow you to start up your computer successfully using a reduced version of the system software. To do this, follow these steps:
1. Start up in Safe Mode.
2. After the system has fully started up, restart your computer again normally.
If the computer successfully restarts, you do not need to do any more troubleshooting. If the issue persists, try Disk Utility.
Try Disk Utility
1. Start from your Mac OS X Install disc: Insert the installation disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk.
Tip: Always start up your computer from an Install or Restore disc when using Disk Utility to verify or repair your startup volume. Otherwise, you might see some disk error messages.
Use fsck if necessary
fsck is a command-line utility that may be able to verify and repair a disk. If you can successfully start up in Safe Mode or use Disk Utility while started up from a disc, you don't need to use fsck. Here are some situations in which fsck may be necessary.
* Your Mac OS X disc isn't available.
* Your optical drive isn't available.
* You can't start with a Safe Boot by holding the Shift key during start up.
Tip: If you use a Mac OS X Extended (Journaled) formatted volume, such as with Mac OS X 10.3 or later, you probably won't need to use fsck. If you do use it for any reason, please be aware that benign error messages can appear.
If you're not sure how your volume is formatted and you can't start up from your Mac OS X volume to find out, type the following command in a command-line interface and then press Return: diskutil info /
If you see "File System: Journaled HFS+" returned, you have a Journaled volume.
To use fsck, you must run it from the command line. Unlike using your mouse pointer to open an application to do something, you'll need to type a text command at the prompt (#) to tell fsck what to do. The Terminal application (/Applications/Utilities) and single-user mode are two examples of command-line interfaces in which you can type such commands. To use fsck:
1. Start up your computer in single-user mode to reach the command line.
Note: If necessary, perform a forced restart as described in the Emergency Troubleshooting Handbook that came with your computer. On desktop computers, you can do this by pressing the reset/interrupt button (if there is one) or holding down the power button for several seconds. On portable computers, simultaneously press the Command-Control-power keys. If your portable computer doesn't restart with this method, you may need to reset the Power Manager.
2. At the command-line prompt type:
/sbin/fsck -fy
3. Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found:
** The volume (nameofvolume) appears to be OK
If fsck found issues and has altered, repaired, or fixed anything, it will display this message:
*** FILE SYSTEM WAS MODIFIED ***
Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
4. When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
Your computer should start up normally and allow you to log in.
Additional Information
About live verification in Mac OS X 10.4.3 or later
In Mac OS X 10.4.3 or later, you can verify your Mac OS X volume while started from it. This is known as live verification, and can be used in three different ways.
Option 1: Verify your disk using Disk Utility while started from the startup disk. To find out how to do this, see this article. Please note that live verification does not involve any disk repair, so if verification finds something that should be repaired, start up from your Mac OS X Install disc and use Disk Utility as described above in "Try Disk Utility."
Option 2 (advanced): Use the command line and the command-line utility, diskutil.
1. Start up your computer and log in as an administrator.
2. Open Terminal (/Applications/Utilities).
3. At the prompt, type the following command and then press Return:
diskutil verify /
Note: Don't use this method to check non-startup volumes.
You should see messages such as the following during the disk check:
Could not unmount disk for verification, attempting live verify
Started verify/repair on volume disk0s3 Macintosh HD
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
The volume Macintosh HD appears to be OK.
Mounting Disk
Verify/repair finished on volume disk0s3 Macintosh HD
Option 3 (advanced): Use the command line and the fsck_hfs -l command.
1. Start up your computer and log in as an administrator.
2. Open Terminal (/Applications/Utilities).
3. At the prompt, type the following command and then press Return to determine your filesytem ID:
df -hl
4. Look for some lines of text that look like this:
Filesystem Size Used Avail Capacity Mounted on
/dev/disk0s3 37G 20G 17G 55% /
/dev/disk0s5 37G 37G 641M 98% /Volumes/Storage
5. Make a note of the first "disk" name that appears after /dev/, such as "disk0s3." This is your filesystem ID for your startup volume.
6. At the prompt, type the following command and then press Return:
df -hl
7. Then type the following command, where "disk0s3" is your filesystem ID you noted in step 4, then press Return:
sudo fsck_hfs -l /dev/disk0s3
8. When prompted, enter your admin password, then press Return to begin the verification.
9. You should see messages like these during the disk check:
** /dev/rdisk0s3 (NO WRITE)
** Root file system
** Checking HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking volume bitmap.
** Checking volume information.
** The volume Macintosh HD appears to be OK.
Advanced information
If you're interested in UNIX-style command-line syntax, here's a look at how a couple of flags used above can influence fsck:
* The -y flag: Tells fsck that you want to answer "yes" to all questions about fixing, repairing, or salvaging information. This is the optimal approach, as answering "no" to any question causes fsck to stop. You cannot determine that all necessary repairs have been made until fsck completes and gives its final report.
* The -f flag: Forces fsck to check "clean" filesystems when preening.
See also
* Handling "overlapped extent allocation" errors reported by Disk Utility or fsck
* Disk Utility reports "Underlying task reported failure" when repairing a volume -
MacBook Pro grey screen on startup, no apple logo.
Hello,
Today I've been working on my MBP(2009) and everything worked perfectly, then I had to shut my MBP down. It happened with no problem. Next time when I've tried to start it up, only grey screen appeared with no Apple logo and it persists no matter how long I wait. Anybody who encountered the same issue?
Thank you for your help.I have followed this text, however I have no peripheral devices connected (no charger, no ethernet, no usb filled). They tell me to access the modes with keyboard shortcuts, but I cannot do that, when I cannot get over the grey screen at the beginning.
-
Updated software recently - now my mac book displays a grey screen
Hi
I updated software on my mac book pro around a couple of hours back. I followed all the steps during the process. Now for the past two hours, my macbook pro shows a grey screen with two buttons for signing in as me or signing in as someone else- but these buttons are not clickable - in that, nothing happens when I click the buttons - How can I resolve this issue - I have been quite happy with the mac book otherwiseHi mk101!
I have an article for you that can help you troubleshoot the startup issues you seem to be experiencing. The article can be found right here:
Resolve startup issues and perform disk maintenance with Disk Utility and fsck
http://support.apple.com/kb/ts1417
Specifically, this section outlines the first step that you will want to try:
Resolution
Try a Safe Boot
If you're using Mac OS X 10.2 or later, you can start up your computer in Safe Mode, which includes an automatic disk check and repair. If you're using Mac OS X 10.1.5 or earlier, skip to the next section. A Safe Boot, which starts up your computer into Safe Mode, may allow you to start up your computer successfully using a reduced version of the system software. To do this, follow these steps:
Start up in Safe Mode.
After the system has fully started up, restart your computer again normally.
If the computer successfully restarts, you do not need to do any more troubleshooting. If the issue persists, try Disk Utility.
As it says, if the issues persist, you need to continue with the troubleshooting steps found in that article. Hope that helps, thanks for using the Apple Support Communities!
Regards,
Braden
Maybe you are looking for
-
Cannot print pdf file for school
I have acrobat adobe 9. Windows Vista Business Pro 6.0 OS. IE7. I go to school online at Kaplan University. Am taking a class on Nutrition and doing homework in Diet Analysis 9+. We have to enter foods eaten for 5 days time and create and print
-
I am using apex_item in a select, but when submit page the result is one error "ORA-01403:no data found". put in the select plus and presents data. My select: SELECT APEX_ITEM.HIDDEN(1,ID) ID, APEX_ITEM.TEXT(2,ID) ID_DISPLAY, APEX_ITEM.TEXT(3,SESSAO_
-
i can't get my videos/tv shows on my ipod. it says my software is too old and i must update to 1.2. it won't even let me do this. i just want my videos on my ipod because i bought them all to watch on a 9 hour flight i am taking WEDNESDAY. somebody p
-
I have a 17" Apple CRT hooked up to my 15" PB in extended desktop mode. Is there any way of using one monitor to preview the movie while using the other to work, like FCP or an Avid? PowerBook G4 1.25ghz Mac OS X (10.4.5)
-
Hello, I have began with KM from a few time ago. I know the standard approval workflow is sequential, so if I want that many people approve a document I may insert more approval steps. This is not a good solution for my client, because they want to a