Gray screen of death on boot-up

I have a 2.1 GHz MacBook with a 120GB hard-drive that I bought last November. I've been doing a lot with video and music and I keep running out of disk space. So, I keep deleting files that I thought I didn't need. Unfortunately, I must have deleted something important (for the OS) yesterday, and now, when I try to boot the machine, I get the "gray screen of death". And, to make matters worse, I cannot find the boot-CD that came with the MacBook. I don't have back-ups for many of my files and am hoping that I'll be able to recover my files. So, I've just bought an external hard-drive (which I should have done before). Any ideas how I can get the MacBook to boot and repair the problem without the original boot-CD? Will I have to erase the hard-drive to repair the problem, and if so, will I be able to save the files first? Thanks!

Hi MB-GSofD,
Without the disc(s) that came with your machine, I'm afraid your options are extremely limited. You can try to startup the machine in Safe Mode (Hold Shift immediately on startup, until you get to the login window) but based on what you deleted out of the /System or /Library folders, you might just be dead in the water.
Are you near an Apple Store? Do you have access to another Mac, say a family member, friend, roommate, co-worker, etc? There is Target Disk Mode if you can get access to another Mac and a Firewire cable.
http://support.apple.com/kb/HT1661

Similar Messages

  • Gray Screen of Death on boot

    Hello all,
    I was using my white Macbook earlier today. I put it to sleep, and then some hours later I woke it up and used it a little. I then restarted it, and now I get the error screen (seen here: http://4.bp.blogspot.com/UqUwVPikChs/SKLhZ624D6I/AAAAAAAAEyE/nz8pRrCE7dQ/s320/MacOSX_kernelpanic.png) that tells me I need to restart the computer. I've tried restarting but this happens every time. What can I do? thanks!

    That is a kernel panic. Disconnect all peripherals from your computer and try the suggestions mentioned in the User Tips: Kernel Panics

  • Gray screen of death ... macbook boot failure

    Three weeks old and getting the gray screen of death. Power up works but MacBook just keeps trying to read a video disk I left in the ROM drive. Gray screen with nothing else (no processing circle, no apple logo, just a plain gray screen). I could hear the rom drive cycling.
    I worked with support via telephone and their solutions failed also:
    1. power up, hold down the eject button (nada)
    2. power up, hold down the mouse button (nada)
    3. power up, hold down the apple key, the cntl key, the P and the R keys for two chimes (got the two chimes but nada)
    Now it chimes when i start up but still sits there cycling the cdrom which has a movie disk in it.
    The support rep asked me if there was a small extraction hole by the drive. HELLO: are you really Apple ??? On the new macbook?
    The MacBook was delivered with 10.4.8. Wanting the large 10.4.9 update on CD for any future need, I downloaded the 10.4.9 intel combined update (larger than the other choice) and went with that not knowing which to use. However this was three weeks ago and the computer has been perfect. my session yesterday was perfect but I did 'brag' on the new macbook when a friend saw me using it. why does bragging cause boot failures? Murphy?/??????// HELP.
    Black MacBook intel core 2 duo 120gb drive 2 gb memory   Mac OS X (10.4.9)  

    My apologies to everyone if I raised an alarm. The hardware (i.e. the MacBook) is fine and the problem was that I am a new user. I have to say that Apple Support was unprepared to address the issue but I did resolve it myself by accident. Here is the resolution:
    I looked up the SMC reset instructions on the Apple Support site as a next step and the instructions said to try 3 things before doing the SMC:
    1. Force Quit (Option - Command - Escape)
    2. Restart (Control - Command - Power)
    3. Force Shutdown (hold down pwr button for 10 seconds
    As a new user I could not know that the key with the Apple was the Command key, but I guessed since the words control and option were called out, it had to be the Apple key with the Squiggle.
    I did each step but nada. I did get a different alert tone (lower pitch) after doing step 3. Each time I turned the computer off.
    I then started over and tried again turning on the macbook from being off each time. I did step 1 and turned the machine off and then did step 2 and the computer came alive.
    The system is just like I left it and the rom drive works fine. Again, my apologies to all you macbook users for raising any alarms. We are new to using Apple and have much to learn. I did not have any cheat sheets to work from so it took time. Many thanks for the responses.
    Black MacBook purchased in March 2007   Mac OS X (10.4.9)   I love this MacBook

  • IMac won't boot! (gray screen of death?)

    Hello,
    I just had a kernel panic on my main iMac computer, so I had to restart it...
    When it logged in automatically, it restarted again (by itself)...
    Now, once it booted, I'm staring at the horrendous Gray Screen of Death/Doom...
    No apple logo, no loading wheel, nothing... just a blank gray screen.
    Please help! I have no idea how to fix this!
    Thank you. All help is greatly appreciated.

    Hi mik.e245
    Pop in the Install Disk 1 that came with your iMac and run disk repairs as described in the articles below:
    http://kb.wisc.edu/helpdesk/page.php?id=3810
    http://docs.info.apple.com/article.html?path=DiskUtility/10.5/en/duh1018.html
    Not always, but many times Kernal Panic's are associated with a ram issue's. If a ram module was recently added it may have become partially dislodged/unseated and needs to be reseated.
    If your still having trouble run the Hardware Test from the same install disk as per this article.
    http://docs.info.apple.com/article.html?artnum=303081-en
    Dennis

  • Kernel Panics, Gray screen of death, and hard drives, oh my!

    Last week, while performing multiple tasks on my G4, Safari froze up and completely locked up the entire computer. I rebooted by manually pushing the glowing power button the front of the tower. During reboot, I got the gray screen of death with the "you need to restart your macintosh... by holding down the power button for several seconds" message.
    After a couple tries and getting that exact same gray screen of death, I started to worry about all my data.
    I took both drives out of the G4 Quicksilver - one, a 500gb Barracuda Seagate (Master/bay 1), the other a 200gb Hitachi (slave/bay 2). I hooked them up to an older G4 and ran DiskWarrior and DiskUtility on both of them. The master drive had serious (>34%) fragmentation, which has since been cleaned up. The slave drive was relatively fine.
    here's my current problem:
    When I hook up:
    1. Just the Master with no jumper pins, the drive runs fine, no problems, all settings and prefs are there, etc.
    2. Just the Master with the correct pin settings, I get the kernel panic screen of death
    3. The Master with correct pin settings and Slave with correct pin settings, kernel panic screen of death
    4. If I swap the Master and Slave, and make the correct pin settings, the booting process starts and then I get a light gray screen with the "ghostbusters/do not enter" circle.
    I put the original Slave drive in an external HD firewire enclosure, and it will mount on the desktop after the original Master drive has booted up - BUT - if I have the external drive powered up before I boot the Master, I get a gray screen with nothing on it - no message, nothing but grayscreen.
    I've backed up my critical data, but would like to get these two drives back into their normal operating Master/Slave relationship that served them well for the last couple years.
    Any help greatly appreciated.

    New wrinkle:
    This morning trying at boot up, the Mac chime sounded, the gray screen w/the apple logo appeared, and then the machine sounded like either the main fan or one of the two drives spun down. Shortly thereafter, I got the prohibitory sign again.
    I rebooted and then got something completely different: a black screen with a small blinking vertical rectangle in the top left of the screen, with nothing else happening for a long time, so I manually rebooted and tried to boot into safe mode.
    Trying to boot into safe mode gave me the chime, the apple logo, and then the sound of either the fan or drive spinning down and leaving me at the prohibitory sign once again.
    Finally I option-booted to the slave drive and upon startup, received the following crash report, which might as well be in Swahili as far as my being able to make sense of it:
    Sat Apr 11 09:59:48 2009
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000003DFFF70 PC=0x000000000032F68C
    Latest crash info for cpu 0:
    Exception state (sv=0x2d409780)
    PC=0x0032F68C; MSR=0x00009030; DAR=0x03DFFF70; DSISR=0x40000000; LR=0x00287A40; R1=0x2D3BFDD0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x2D3BFE20 0x00287AA0 0x00288658 0x0030C5AC 0x000B34C8 0xFFFFDFFF
    Proceeding back via exception chain:
    Exception state (sv=0x2d409780)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x24459500)
    PC=0x93091180; MSR=0x0000D930; DAR=0x00100AE4; DSISR=0x40000000; LR=0x000067FC; R1=0xBFFFED50; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: launchd
    Mac OS version:
    9G55
    Kernel version:
    Darwin Kernel Version 9.6.0: Mon Nov 24 17:39:01 PST 2008; root:xnu-1228.9.59~1/RELEASE_PPC
    System model name: PowerMac3,5
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x0009BCF0 0x0009C694 0x00029EA0 0x000AFA90 0x000B32F8
    Proceeding back via exception chain:
    Exception state (sv=0x2d409780)
    PC=0x0032F68C; MSR=0x00009030; DAR=0x03DFFF70; DSISR=0x40000000; LR=0x00287A40; R1=0x2D3BFDD0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x2D3BFE20 0x00287AA0 0x00288658 0x0030C5AC 0x000B34C8 0xFFFFDFFF
    Exception state (sv=0x24459500)
    PC=0x93091180; MSR=0x0000D930; DAR=0x00100AE4; DSISR=0x40000000; LR=0x000067FC; R1=0xBFFFED50; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: launchd

  • Gray screen of death at start up

    Hello all,
    Today when i was downloading the latest updates for my mac and iTunes my system froze while trying to access my BAD hard drive. So i restart my mac and after the apple logo appeared the gray screen of death showed up. I tried every thing from PRAM reset to disk and permission repair. So please help me with this problem.
    Thank you

    If you are on Mountain Lion you can boot from the Recovery Disk that is installed hidden from your internal HD. You can Use the Disk Utility from there to repair disk and you can also use that on OS re-installation of your ML.
    "OS X Lion or OS X Mountain Lion includes a built in set of utilities in the Recovery System. Restart your Mac and hold down the Command key and the R key (Command-R), and keep holding them until the Apple icon appears, indicating that your Mac is starting up. After the Recovery System is finished starting up, you should see a desktop with a OS X menu bar and a "Mac OS X Utilities" application window."
    Check this link
    http://support.apple.com/kb/ht4718

  • Gray screen of death.... Please help.

    Wife's 27" iMac is giving us the gray screen of death. I tried everything I could:
    Command + Option +P + R
    Holding Option at boot to try Recovery
    Command + Option + R (Internet Recovery)
    Holding shift to get to Safe Mode
    Inserting install disc while holding "C"
    Installed Mountain Lion on my Flashdrive to try to boot from that….
    ALL FAILED. Any ideas, guys? Please help. This Mac is just a little over a year old. just out of the one year warranty.

    Thanks for telling us everything you did. However, you haven't given us any information on what the computer did. So there's not much to go on except a gray screen. Assuming the drive has not failed:
    Install or Reinstall Lion/Mountain Lion from Scratch
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    Boot to the Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Erase the hard drive:
      1. Select Disk Utility from the main menu and click on the Continue button.
      2. After DU loads select your startup volume (usually Macintosh HD) from the
          left side list. Click on the Erase tab in the DU main window.
      3. Set the format type to Mac OS Extended (Journaled.) Optionally, click on
            the Security button and set the Zero Data option to one-pass. Click on
          the Erase button and wait until the process has completed.
      4. Quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Install button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible
                because it is three times faster than wireless.
    If you are not able to perform the above then the drive has most likely failed and will have to be replaced. Take the computer in for service..

  • Gray screen of death....after 3 reinstalls!!!

    Ok so i have the infamous gray screen of death after installing snow leopard but i think mine is slightly different. I don't have the circle going round and round. I only have a gray screen. For some odd reason the first time it happened i held the mouse button, then the cd drive (empty) came out and then it booted up (odd). Then i reinstalled, still happened, and i held the mouse on restart and again it worked. But now this time i reinstalled again, obviously it isn't starting up but even if i hold the mouse button it still won't load. Any ideas?

    If you can get it to start, go into System Prefs and check your startup volume...

  • Blue Screen of Death on boot: ctaud2k.sys

    Blue screen of Death on boot: ctaud2k.sys
    MEMORY.DMP analysis:
    (minidump will follow shortly)
    Microsoft (R) Windows Debugger Version 6..000.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    Symbol search path is:
    SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
    x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp2_gdr.0026-30
    Machine Name:
    Kernel base = 0xfffff800`0000000 PsLoadedModuleList = 0xfffff800`0d440
    Debug session time: Wed Dec 29 03:8:25.609 200 (GMT+)
    System Uptime: 0 days 0:0:24.536
    Loading Kernel Symbols
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`7efdf08). Type ".hh dbgerr00" for
    details
    Loading unloaded module list
    *????? Bugcheck Analysis
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffffadf8ebb5398, fffffadf8c644c0, 0}
    Page ac7d4 not present in the dump file. Type ".hh dbgerr004" for details
    Page acb29 not present in the dump file. Type ".hh dbgerr004" for details
    *** ERROR: Module load completed but symbols could not be loaded for
    ctaud2k.sys
    *** ERROR: Module load completed but symbols could not be loaded for
    ctprxy2k.sys
    PEB is paged out (Peb.Ldr = 00000000`7efdf08). Type ".hh dbgerr00" for
    details
    PEB is paged out (Peb.Ldr = 00000000`7efdf08). Type ".hh dbgerr00" for
    details
    Probably caused by : ctaud2k.sys ( ctaud2k+e398 )
    Followup: MachineOwner
    : kd> !analyze -v
    *????? Bugcheck Analysis
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffffadf8ebb5398, Address of the exception record for the exception
    that caused the bugcheck
    Arg3: fffffadf8c644c0, Address of the context record for the exception that
    caused the bugcheck
    Arg4: 0000000000000000, zero.
    Debugging Details:
    Page ac7d4 not present in the dump file. Type ".hh dbgerr004" for details
    Page acb29 not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 00000000`7efdf08). Type ".hh dbgerr00" for
    details
    PEB is paged out (Peb.Ldr = 00000000`7efdf08). Type ".hh dbgerr00" for
    details
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
    referenced memory at "0x%08lx". The memory could not be "%s".
    FAULTING_IP:
    ctaud2k+e398
    fffffadf`8ebb5398 488b02?? mov? rax,qword ptr [rdx]
    CONTEXT:? fffffadf8c644c0 -- (.cxr 0xfffffadf8c644c0)
    rax=000000000000000 rbx=fffffadf9a6390 rcx=000000000000000
    rdx=0000008ffffffff rsi=fffffadf9a63260 rdi=0000000000000000
    rip=fffffadf8ebb5398 rsp=fffffadf8c64cd0 rbp=fffffadf99c04330
    ?r8=fffffadf99c04330? r9=fffffadf9c6ff570 r0=fffffadf99c04330
    r=fffffadf8c64d98 r2=0000000000000000 r3=fffffadf8c64d98
    r4=000000000000000 r5=fffffadf9a632a8
    iopl=0?? nv up ei pl nz na po nc
    cs=000? ss=008? ds=002b? es=002b? fs=0053. gs=002b
    efl=0000206
    ctaud2k+0xe398:
    fffffadf`8ebb5398 488b02?? mov? rax,qword ptr [rdx]
    ds:002b:0000008`ffffffff=???
    Resetting default scope
    DEFAULT_BUCKET_ID:? DRIVER_FAULT
    BUGCHECK_STR:? 0x3B
    PROCESS_NAME:? DLLML.exe
    CURRENT_IRQL:? 0
    LAST_CONTROL_TRANSFER:? from fffffadf90b88785 to fffffadf8ebb5398
    STACK_TEXT:
    fffffadf`8c64cd0 fffffadf`90b88785 : 00000000`20206f49 fffff800`005039a
    fffffadf`99c04330 fffffadf`9a6390 : ctaud2k+0xe398
    fffffadf`8c64d50 fffff800`027f3 : 00000000`0000000 fffffadf`00000000
    fffffadf`8c6500 00000000`00000000 : ctprxy2k+0x5785
    fffffadf`8c64d90 fffff800`027ec36 : 00000000`0000034 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xa79
    fffffadf`8c64eb0 fffff800`002e33d : fffffadf`99ee2c20 fffffadf`9c8bbb70
    fffffadf`8c64f00 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
    fffffadf`8c64f20 00000000`78b83e48 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    00000000`006dd98 fffff800`0026640 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : 0x78b83e48
    fffffadf`8c65320 00000000`00000000 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KiCallUserMode
    FOLLOWUP_IP:
    ctaud2k+e398
    fffffadf`8ebb5398 488b02?? mov? rax,qword ptr [rdx]
    SYMBOL_STACK_INDEX:? 0
    SYMBOL_NAME:? ctaud2k+e398
    FOLLOWUP_NAME:? MachineOwner
    MODULE_NAME: ctaud2k
    IMAGE_NAME:? ctaud2k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:? 4a26ba
    STACK_COMMAND:? .cxr 0xfffffadf8c644c0 ; kb
    FAILURE_BUCKET_ID:? X64_0x3B_ctaud2k+e398
    BUCKET_ID:? X64_0x3B_ctaud2k+e398
    Followup: MachineOwner
    Bye,
    ? Skybuck.

    Minidump:
    <a rel="nofollow" target="_blank" href="http://members.home.nl/hbthouppermans/MiniDump/Mini2290-0.dmp"]http://members.home.nl/hbthouppermans/MiniDump/Mini2290-0.dmp[/url]
    Microsoft (R) Windows Debugger Version 6..000.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\WINDOWS\Minidump\Mini2290-0.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is:
    SRV*c:\Tools\WinDbg\WebSymbols*<a rel="nofollow" target="_blank" href="http://msdl.microsoft.com/download/symbols"]http://msdl.microsoft.com/download/symbols[/url]
    Executable search path is:
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
    x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp2_gdr.0026-30
    Machine Name:
    Kernel base = 0xfffff800`0000000 PsLoadedModuleList = 0xfffff800`0d440
    Debug session time: Wed Dec 29 03:8:25.609 200 (GMT+)
    System Uptime: 0 days 0:0:24.536
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *????? Bugcheck Analysis
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffffadf8ebb5398, fffffadf8c644c0, 0}
    Unable to load image \SystemRoot\system32\drivers\ctaud2k.sys, Win32 error
    0n2
    *** WARNING: Unable to verify timestamp for ctaud2k.sys
    *** ERROR: Module load completed but symbols could not be loaded for
    ctaud2k.sys
    Probably caused by : ctaud2k.sys ( ctaud2k+e398 )
    Followup: MachineOwner
    : kd> !analyze -v
    *????? Bugcheck Analysis
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffffadf8ebb5398, Address of the exception record for the exception
    that caused the bugcheck
    Arg3: fffffadf8c644c0, Address of the context record for the exception that
    caused the bugcheck
    Arg4: 0000000000000000, zero.
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
    referenced memory at "0x%08lx". The memory could not be "%s".
    FAULTING_IP:
    ctaud2k+e398
    fffffadf`8ebb5398 ??
    CONTEXT:? fffffadf8c644c0 -- (.cxr 0xfffffadf8c644c0)
    rax=000000000000000 rbx=fffffadf9a6390 rcx=000000000000000
    rdx=0000008ffffffff rsi=fffffadf9a63260 rdi=0000000000000000
    rip=fffffadf8ebb5398 rsp=fffffadf8c64cd0 rbp=fffffadf99c04330
    ?r8=fffffadf99c04330? r9=fffffadf9c6ff570 r0=fffffadf99c04330
    r=fffffadf8c64d98 r2=0000000000000000 r3=fffffadf8c64d98
    r4=000000000000000 r5=fffffadf9a632a8
    iopl=0?? nv up ei pl nz na po nc
    cs=000? ss=008? ds=002b? es=002b? fs=0053. gs=002b
    efl=0000206
    ctaud2k+0xe398:
    fffffadf`8ebb5398 ??
    Resetting default scope
    CUSTOMER_CRASH_COUNT:?
    DEFAULT_BUCKET_ID:? DRIVER_FAULT
    BUGCHECK_STR:? 0x3B
    PROCESS_NAME:? DLLML.exe
    CURRENT_IRQL:? 0
    LAST_CONTROL_TRANSFER:? from 0000000000000000 to fffffadf8ebb5398
    STACK_TEXT:
    fffffadf`8c64cd0 00000000`00000000 : fffff800`00000000 00000000`00000000
    00000000`00000000 00000000`20206f49 : ctaud2k+0xe398
    FOLLOWUP_IP:
    ctaud2k+e398
    fffffadf`8ebb5398 ??
    SYMBOL_STACK_INDEX:? 0
    SYMBOL_NAME:? ctaud2k+e398
    FOLLOWUP_NAME:? MachineOwner
    MODULE_NAME: ctaud2k
    IMAGE_NAME:? ctaud2k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:? 4a26ba
    STACK_COMMAND:? .cxr 0xfffffadf8c644c0 ; kb
    FAILURE_BUCKET_ID:? X64_0x3B_ctaud2k+e398
    BUCKET_ID:? X64_0x3B_ctaud2k+e398
    Followup: MachineOwner
    Bye,
    ? Skybuck.

  • Gray Screen of DEATH?

    i just got a GRAY screen of DEATH for my iphone today. i was wondering what can i do to fix it other than restoring? have anybody got this before? tyvm for your help!

    i just got a GRAY screen of DEATH for my iphone today. i was wondering what can i do to fix it other than restoring? have anybody got this before? tyvm for your help!

  • Gray screen of death on third-gen iPad...

    I'm caught in a bit of a circle and am needing a little help re if/how to get out of it. Hoping the community here might be able to help - or confirm that I'm out of luck.
    My third-gen iPad gave me the gray screen of death this morning, while downloading an app from the app store. I'm unable to reboot from the iPad itself (more gray screen, before shutting off). Based on the advice provided in the archives, my next step was a restore. Unfortunately, iTunes wants the passcode - which, of course, I'm unable to enter.
    Is there a workaround for this that anyone has found to get past this particular challenge?
    Not that I'm looking for an excuse for an updgrade....

    NPMaven wrote:
    Unfortunately, iTunes wants the passcode - which, of course, I'm unable to enter.
    Why are you unable to provide the passcode?  You are using the computer's iTunes, aren't you?
    If you're unable to do the Restore, go into Recovery Mode per the instructions here.

  • Gray Screen of Death (moving from Java 1.1 to 1.4)

    I am in process of moving my applet from Java 1.1 to modern Java 1.4 with Swing. My concern is that users on MS IE with the ancient MS JVM will get the "gray screen of death" and no hint that something is wrong. The best option I've found so far seems to be this:
    http://www.chaingang.org/code/util/AppletLaunch.html
    where you have one applet start up, check the version, and then either report "you need a new version of java" or launch the next applet. I'm not sure whether this will work when the first applet is compiled for Java 1.1, and the second is for Java 1.4 (they use different class file formats).
    What are the recommendations for dealing with this situation? I've seen that Sun has some very complicated stuff about using OBJECT, EMBED, and APPLET tags:
    http://java.sun.com/j2se/1.5.0/docs/guide/plugin/developer_guide/contents.html
    Also stuff about "Java Web Start Applications":
    http://java.sun.com/developer/technicalArticles/JavaLP/javawebstart/AutoInstall.html
    I've also seen something about the "HTML Converter".
    This is all looks way complicated!! As long as I can tell users "go update your java" and direct them to the java install web page I'm happy... I don't want to try to get their install started automatically. And I'd rather keep my HTML code simple and clean if possible.
    Thanks in advance...

    1. Write an applet in 1.4 that simply displays a small image.
    2. Place the image on the webpage beside the applet.
    3. Put a line of html beside or under the image and the applet saying "If you cannot see this image here (as in applet loaction) then you must download the 1.4 jre here"
    Yahoo provide an applet as a means of editing ones geocitys website. This is how they ensure the user has the required jre. Crude but very effective and without complication.

  • My Mac can't get passed gray screen, and I cannot boot from cd. Help!

    My Mac can't get passed gray screen, and I cannot boot from cd. Help!

    Grey Screen
    https://support.apple.com/kb/TS2570
    https://discussions.apple.com/message/16276201#16276201

  • Can't boot on hard drive or CD/DVD - grey/gray screen of death

    A few weeks ago my PowerPC G5 Dual Processor running Leopard OS X froze while the screen saver was running. I hard-powered-off the computer --> held down power button for ~10 seconds. When I tried to start up again, I got the "gray/grey screen of death" with the Apple logo. The screen hung there and then fans starting ramping up to full speed with no sign off boot up. I know others have posted similar issues, but I wanted to start a new thread.
    Basic Specs:
    PowerPC G5 Dual 2.5 Hz Processors
    4 Gb memory (recently upgraded form 2 to 4) ***
    Bought in early 2005 (I think)
    Here's a summary of what I've tried:
    DOES NOT WORK
    - booting up holding down C (for drive) --> straight to kill screen
    - booting up from original discs for G5 (from both C mode and Option mode)
    - booting up from 10.5 Leopard disc (from both C mode and Option mode)
    - booting up holding down Option-Comman-P-R --> straight to kill screen
    DOES WORK
    - connecting to secondary computer using target mode (holding down T) - I can see both of my hard drives
    - booting up holding down Option - I can select either my main drive (secondary is not present there but there is no OS on it) or CD/DVD in slot
    - booting from Apple Hardware Test (AHT) disk from Option menu
    -- I ran disk checks, had errors. I ran Disk Warrior from secondary computer in target mode and repaired the drive, running the AHT test again shows no errors
    - ran disk repair from secondary computer to fix errors (using disk utility and disc warrior)
    OTHER THINGS I'VE DONE
    - replaced backup battery on motherboard that was weak at only ~70 mV with fresher battery at ~3.6V
    - held down PMU (not SMU) reset button for 30 seconds
    - (main fans were cleaned a few weeks before issue)
    - two weeks before issue I installed more memory (from 2 Gb to 4 Gb with two new 1 Gb cards)
    - backed up data - so I can delete drives if needed
    THOUGHTS
    - I'm concerned that under CPU it shows 158950.77 GHz - shouldn't it be showing two CPU?
    - the drives look healthy when looking at them in target mode
    - issue is occurring between power up and drive selection (since CD/DVD is also not viewable)
    - maybe the new memory caused local over heating to the motherboard?
    - I may be able to replace the heat sink, but the spare computer I have access to has different looking hardware. It's probably a different model of the G5. My computer has one metal case cover and the extra one has a split case cover.
    NEXT STEP
    - I need to back up secondary drive fully first
    - pull out new memory sticks
    - pull out all memory except originals
    - pull out secondary drive
    LAST RESORT
    - buy external case for drives and cry about how no one will buy my dead desktop
    Because this is a long description, I will post updates in the comments and a final comment here:
    (Coming Soon)

    The final lines in the log were all iTunes, but I think it's a hardware issue that's preventing me from booting.
    Here is the line that includes the world "fatal" and a few lines before and after (it was the day before the crash):
    Oct  9 02:05:50 Rys-Big-One com.apple.SystemStarter[28]: kextunload: unload kext /System/Library/Extensions/CiscoVPN.kext succeeded
    Oct  9 02:05:51 Rys-Big-One kernel[0]: CiscoVPN : unloading cisco ipsec kernel module.
    Oct  9 02:05:50 Rys-Big-One com.apple.SystemStarter[28]: Stopping Adobe Version Cue ...
    Oct  9 02:05:50 Rys-Big-One vpnagent[88]: Termination reason code 7: The agent has been stopped.
    Oct  9 02:05:51 Rys-Big-One kernel[0]: CiscoVPN : detaching from interface: en0.
    Oct  9 02:05:50 Rys-Big-One vpnagent[88]: Function: getDownloaderMessage File: MainThread.cpp Line: 964 Invoked Function: CVpnMgr::processEvents Return Code: 0 (0x00000000) Description: fatal error, stopping service
    Oct  9 02:05:51 Rys-Big-One kernel[0]: CiscoVPN : interface en0, filter has been safely detached.
    Oct  9 02:05:51 Rys-Big-One vpnagent[88]: Cisco AnyConnect VPN Client Agent stopped, version 2, 4, 0
    Oct  9 02:05:51 Rys-Big-One com.apple.SystemStarter[28]: Using CATALINA_BASE:   /Applications/Adobe Version Cue/tomcat
    Here is the last lines in the log:
    Oct 10 15:59:53 Rys-Big-One com.apple.usbmuxd[26]: MuxSendToClient send failed for 0x1-ef497a0f0338225857a1061ea364e83ba6c46aa7@0x4b400000:64988->0x20da60-iTunes/ com.apple.iTunes:336: 32 - Broken pipe
    Oct 10 15:59:53 Rys-Big-One com.apple.usbmuxd[26]: HandleUSBMuxDictionary client 0x20da60-iTunes/com.apple.iTunes using library usbmuxd-211 built on May 16 2011 at 00:10:00, running usbmuxd-211 built on May 16 2011 at 00:14:52
    Oct 10 16:00:08 Rys-Big-One com.apple.usbmuxd[26]: HandleUSBMuxDictionary client 0x20e4d0-iTunes/com.apple.iTunes using library usbmuxd-211 built on May 16 2011 at 00:10:00, running usbmuxd-211 built on May 16 2011 at 00:14:52
    Oct 10 16:00:09 Rys-Big-One com.apple.usbmuxd[26]: HandleUSBMuxDictionary client 0x20da60-iTunes/com.apple.iTunes using library usbmuxd-211 built on May 16 2011 at 00:10:00, running usbmuxd-211 built on May 16 2011 at 00:14:52
    Oct 10 16:00:09 Rys-Big-One com.apple.usbmuxd[26]: HandleUSBMuxDictionary client 0x20da60-AppleMobileDeviceHelper/com.apple.SyncServices.AppleMobileDeviceHelper using library usbmuxd-211 built on May 16 2011 at 00:10:00, running usbmuxd-211 built on May 16 2011 at 00:14:52
    Oct 10 16:00:09 Rys-Big-One com.apple.usbmuxd[26]: HandleUSBMuxDictionary client 0x20d740-iTunes/com.apple.iTunes using library usbmuxd-211 built on May 16 2011 at 00:10:00, running usbmuxd-211 built on May 16 2011 at 00:14:52
    Oct 10 16:00:20 Rys-Big-One com.apple.usbmuxd[26]: HandleUSBMuxDictionary client 0x20e4d0-iTunes/com.apple.iTunes using library usbmuxd-211 built on May 16 2011 at 00:10:00, running usbmuxd-211 built on May 16 2011 at 00:14:52
    Oct 10 16:00:50: --- last message repeated 1 time ---
    Oct 10 16:01:20 Rys-Big-One com.apple.usbmuxd[26]: HandleUSBMuxDictionary client 0x20e4d0-iTunes/com.apple.iTunes using library usbmuxd-211 built on May 16 2011 at 00:10:00, running usbmuxd-211 built on May 16 2011 at 00:14:52
    Oct 10 16:02:20 Rys-Big-One com.apple.usbmuxd[26]: HandleUSBMuxDictionary client 0x20e4d0-iTunes/com.apple.iTunes using library usbmuxd-211 built on May 16 2011 at 00:10:00, running usbmuxd-211 built on May 16 2011 at 00:14:52
    Oct 10 16:03:20 Rys-Big-One com.apple.usbmuxd[26]: HandleUSBMuxDictionary client 0x20e4d0-iTunes/com.apple.iTunes using library usbmuxd-211 built on May 16 2011 at 00:10:00, running usbmuxd-211 built on May 16 2011 at 00:14:52
    Oct 10 16:04:21 Rys-Big-One com.apple.usbmuxd[26]: HandleUSBMuxDictionary client 0x20e4d0-iTunes/com.apple.iTunes using library usbmuxd-211 built on May 16 2011 at 00:10:00, running usbmuxd-211 built on May 16 2011 at 00:14:52
    Oct 10 16:04:23 Rys-Big-One iTunes[146]: _NotificationSocketReadCallback (thread 0xa03d1820): Unexpected connection closure...
    Oct 10 16:04:23 Rys-Big-One iTunes[146]: AMDServiceConnectionSendMessage (thread 0xa03d1820): Could not send message size: Broken pipe

  • Gray Screen - Mac Won't boot from DVD, Please Help!

    Hello all
    I have an issue. A big issue in fact. I made a fatal mistake of not reading whether my Mac Pro (1,1 1st Gen, 2006) supported Windows 7 64-bit. So I installed via the Bootcamp installer on a separate internal HD and ever since my Mac Pro will not boot up, it just boots into a gray screen and I get the spinning wheel of death. I can however, boot into Safe Mode.
    Throughout the years and many moving of houses has meant I have lost my original install disks, so I purchased a retail copy of Snow Leopard (10.6.3 / MC573Z/A). My thinking here was that something is obviously screwed and perhaps a good ol' fresh installation of OSX would do the trick. My Mac originally came with a version of OSX older than Snow Leopard so I'm not violating the can't-install-using-an-older-version-that-what-your-Mac-came-with rule.
    Cutting a long story short nothing I do can get the Mac to boot from the install DVD. I've tried the following:
    1. Holding down 'c' at start up
    2. Selecting the startup disk to be the DVD from Settings within Safe Mode
    3. Holding down alt + option key then selecting the DVD
    4. Holding down apple + option + shift + delete (read somewhere this forces the Mac to ignore it's desire to boot from the main partition and boot from next available device)
    5. Tried resetting the NVRAM
    6. Repaired disk permissions from within Safe Mode
    All unnecessary periphals have been removed. I have yet to remove 3rd party RAM admittedly.
    Really struggling for ideas now.
    Is there any hope for me and my beloved Mac Pro?
    Many thanks for your suggestions.

    Right, another update. This coffee stuff really works!
    Did a bit more digging around and found the following forum threads:
    http://forums.macrumors.com/archive/index.php/t-1241149.html
    http://osx86.wikidot.com/known-issues
    Anyway, turns out the chap in the first forum link had the exact same problem as me. He temporarily got around this by removing the following files from the following location whilst in Safe Mode:
    Location: /System/Library/Extensions
    Files:
    NVDANV40Hal.kext
    NVDANV50Hal.kext
    NVDAResman.kext
    NVSMU.kext
    GeForce.kext
    GeForce7xxxGLDriver.bundle
    GeForceGA.plugin
    GeForceGLDriver.bundle
    GeForceVADriver.bundle
    I decided what the heck and moved these files into a new folder on my desktop and deleted the originals.
    Sure enough my mac now boots up normally!
    So it seems that the graphics card was the issue. I have read about the NVIDA 7300 GT only supporting 32-bit, but my tekkie understanding is not enough to know 32-bit what? I thought OSX was a 64-bit OS? If so, then why had it worked all this time? Only when I mistakenly installed Windons 7 64-bit did all my problems start.
    Anyway, looks like I'll need to find a suitable replacement.

Maybe you are looking for