DazzaG

Q: 24" iMac Screen Freezes since 10.6.3 update - pls help!

I don't know if this is just coincidence or not, but since updating my iMac to 10.6.3 it keeps on crashing. On 3 separate occasions today, whilst using my Mac the screen has gone completely black with thin white lines down it.....see pic below:

http://picasaweb.google.com/lh/photo/6SYzhCgVYEU5TBKqRfOQ1Q?feat=directlink

The fans and hard disk are still running but it will not respond to any keyboard or mouse presses - I simply have to turn it off by holding the power button in.
It will then restart as usual.

Anyone got any ideas? Do you think that if I was to re-install Mac OS X from my original install disk it could solve the issue?

Thanks

Darren

24" intel imac 2.8Ghz, Mac OS X (10.6.3)

Posted on Mar 31, 2010 2:43 PM

Close

Q: 24" iMac Screen Freezes since 10.6.3 update - pls help!

  • All replies
  • Helpful answers

first Previous Page 114 of 120 last Next
  • by santitf,

    santitf santitf Nov 11, 2014 2:59 AM in response to DazzaG
    Level 1 (0 points)
    Nov 11, 2014 2:59 AM in response to DazzaG

    After a month without any freeze with the AMD kext from 10.9.5 I had two freeze yesterday, apply the 10.6.2 kext for my imac 7,1 and deleting the AMD and all works fine again.

  • by Tazthed,

    Tazthed Tazthed Nov 12, 2014 8:51 AM in response to DazzaG
    Level 1 (0 points)
    Nov 12, 2014 8:51 AM in response to DazzaG

    I also want to THANK the people who found the solution to this problem from OS X 10.6.3 to Yosemite and the people who shared their experiences in this thread. Without this thread I wouldn't be able to use the newest OS X om my iMac.

  • by Tazthed,

    Tazthed Tazthed Nov 20, 2014 10:42 AM in response to DazzaG
    Level 1 (0 points)
    Nov 20, 2014 10:42 AM in response to DazzaG

    iMac 8,1:

     

    When you update to Yosemite 10.10.1 you need to apply the "kext fix" again and the "kext-dev-mode=1" fix to prevent the imac to freeze.

  • by twedie,

    twedie twedie Nov 21, 2014 8:36 AM in response to mattwinters78
    Level 1 (0 points)
    Nov 21, 2014 8:36 AM in response to mattwinters78

    I have a 20-inch mid-2007 iMac with an ATI Radeon HD 2400 XT graphics card.

     

    It is currently running Mountain Lion.

     

    I speak very little English.


    What are they the "Keys" to be destroyed?
    What are they the arguments to put in the file with "com.apple.Boot.plist"


    Thanks,

  • by dmaude,

    dmaude dmaude Nov 21, 2014 9:22 AM in response to Tazthed
    Level 1 (0 points)
    Nov 21, 2014 9:22 AM in response to Tazthed

    I had a similar experience to Tazthed with the 10.1.1. The freezes came back almost immediately, but the update left the three previously installed ATI kexts in place -- they just didn't load. All I had to do was remove the three AMD ones and run "kext-dev-mode=1" in Terminal.

  • by Daniel Smith-Weiss,

    Daniel Smith-Weiss Daniel Smith-Weiss Nov 23, 2014 10:51 AM in response to dmaude
    Level 1 (4 points)
    Mac OS X
    Nov 23, 2014 10:51 AM in response to dmaude

    I'm getting really sick of applying this fix every update, so I finally posted a bug report to Apple on both their developer site and at the OS X feedback page here: http://www.apple.com/feedback/macosx.html

     

    I encourage everyone else to do this as well. It might not help, but it certainly won't hurt!

  • by mattwinters78,

    mattwinters78 mattwinters78 Nov 25, 2014 6:43 PM in response to twedie
    Level 1 (0 points)
    Nov 25, 2014 6:43 PM in response to twedie

    Twedie

    if you want to update to mavericks and need assistance with tutorial feel free to contact me. That said I have no experience with Mt. Lion I skipped over it completely.

  • by Nzlandrover,

    Nzlandrover Nzlandrover Nov 27, 2014 11:41 AM in response to swmaster
    Level 1 (0 points)
    Nov 27, 2014 11:41 AM in response to swmaster

    Thanks swmaster,

     

    I've been dutifully deleting and installing the kext fixes for a number of years (21+ updates?) on my early 2008 24" iMac.  It's always worked flawlessly until the latest 10.10.1 where the kext fix put it into something that felt like a weird safe mode.  I did your sudo nvram boot-args="kext-dev-mode=1" worked a treat so now I'm back in business.

     

    Here were the symptoms in case someone else with the same problem is searching...

     

    After 10.10.1 update via app store:

    Screen started its freezing tricks including beach ball cursor that doesn't do anything except move around.

     

    After kext fix:

    - Screen went very bright and brightness keys did nothing

    - In System Preferences/Displays, no brightness slider and I tried to calibrate colours but able to change anything and it thought I had a 31" screen.

    - Screen movement sluggish and slow to redraw windows, delays to scroll in windows, cursor went under bar at top of some windows. I could still close the window if I placed the cursor where the red dot "should" have been.

    - Names of dock programs wouldn't show up if I moved the cursor between them.

     

    After repair permissions:

    - No improvement

     

    After your kext-dev-mode=1

    - All good.

  • by Daniel Smith-Weiss,

    Daniel Smith-Weiss Daniel Smith-Weiss Dec 5, 2014 9:46 PM in response to Nzlandrover
    Level 1 (4 points)
    Mac OS X
    Dec 5, 2014 9:46 PM in response to Nzlandrover

    I actually got a response to the bug report I made on Apple's Developer Bug Reporter (I'm not a developer so I'm surprised I could make one at all)! Here's what they wrote:

    Please provide sysdiagnose output when you see this again. Please collect sysdiagnose while the problem is occurring or as soon as possible afterwards.

     

    You can use a key command to start sysdiagnose, or use a terminal command.

     

    Using a key command:

     

    1. Press Shift-Control-Option-Command-Period when the issue reproduces

    2. Wait for a few minutes (you can release the keys). 

    3. When sysdiagnose has completed (may take several minutes), a Finder window will open up showing the new sysdiagnose file in /var/tmp. Attach that file to the bug report. You can also manually locate the new sysdiagnose file in /var/tmp or /private/var/tmp, and upload that file.

     

    Using the terminal:

     

    1. Launch Terminal.app

    2. Enter this command: sudo sysdiagnose

    3. Enter your admin password

    4. When sysdiagnose has completed (may take several minutes), a Finder window will open up showing the new sysdiagnose file in /var/tmp. Attach that file to the bug report. You can also manually locate the new sysdiagnose file in /var/tmp or /private/var/tmp, and upload that file.

     

    I don't think that I can do this because when it freezes, I think the whole machine is non-responsive. Does anyone know if the OS is still functioning when the screen goes black or some other funky color? With the fix applied, this isn't likely to happen again until the next update for me. I don't know how I could do anything with the sysdiagnose file anyway since I can't see the Finder window pop up. If I could get some useful info though, I'd love to! Any thoughts?

  • by eBomber,

    eBomber eBomber Dec 6, 2014 3:16 AM in response to Daniel Smith-Weiss
    Level 1 (0 points)
    Dec 6, 2014 3:16 AM in response to Daniel Smith-Weiss

    In my case the machine still works, just misses the screen (graphics card). With the failure I've been able to connect to the iMac and access via SSH to turn it off correctly, not taking away the tension.

    The keyboard may work and can launch the sysdiagnose, but nothing will appear on the screen. The second option may be more feasible.

    I do not think that after so many years doing nothing Apple, now does, but you can try.

  • by jnik,

    jnik jnik Dec 15, 2014 11:35 AM in response to Tazthed
    Level 1 (0 points)
    Dec 15, 2014 11:35 AM in response to Tazthed

    Tazthed and swmaster,

     

      thanks for the tip on the "kext-dev-mode=1" in the "com.apple.Boot.plist" file.

    As I am not very familiar with Terminal do you mind posting detailed instructions on how to edit?

    Thanks a lot!

  • by aieronimo,

    aieronimo aieronimo Dec 30, 2014 11:29 AM in response to jnik
    Level 1 (0 points)
    Dec 30, 2014 11:29 AM in response to jnik

    Hey, folks.  Does the report below make anyone think that Apple still does not know how to write drivers for its graphics cards?

     

    http://appleinsider.com/articles/14/12/30/apples-latest-mac-pro-continues-to-cau se-problems-for-professional-users

     

    Note that the Windows drivers for these Mac Pro computers work fine, as indicated by the stability of the machines under Boot Camp.  Way, way back in this email thread on iMacs, someone indicated that the same was true regarding our machines.  So Windows has a driver that addresses the problem, whereas OS X users do not.

     

    Is anyone concerned about buying, say, an expensive Retina iMac and finding out a year or so down the road - after an OS upgrade - that the drivers make the computer freeze up?  Anyone want the solution to be booting into Windows?

  • by simen,

    simen simen Jan 14, 2015 2:37 AM in response to aieronimo
    Level 1 (4 points)
    Mac OS X
    Jan 14, 2015 2:37 AM in response to aieronimo

    Guys, this can be fixed with a firmware update.

     

    https://discussions.apple.com/thread...t=660&tstart=0

     

    Read that, and force the firmware update onto your GPU with either FreeDOS or Linux.

     

    No need to hack with old drivers.

  • by aieronimo,

    aieronimo aieronimo Jan 14, 2015 3:02 AM in response to simen
    Level 1 (0 points)
    Jan 14, 2015 3:02 AM in response to simen

    Simen - thanks but that link did not take me to anything except two postings that I made several years ago.  I think the link you posted is tied to your own login.  Can you try logging out of Apple Discussions, find the link and then re-send it?  Thanks.

  • by Daniel Smith-Weiss,

    Daniel Smith-Weiss Daniel Smith-Weiss Jan 14, 2015 6:46 AM in response to simen
    Level 1 (4 points)
    Mac OS X
    Jan 14, 2015 6:46 AM in response to simen

    With a little searching I found this. It should have been detected and automatically updated via software update like any other firmware updates. I think this issue affects others with different models too, so I'm not sure this will do anything. When I'm at my Mac at home I'll have to check to see if this was ever installed on my machine.

first Previous Page 114 of 120 last Next