Sounds like it is time to either get another computer or a different graphics card. The 8600 has a ridiculous failure rate. Did Apple replace it with the same graphics card or what did Apple replace? If the problem was related to overheating, that could cause damage to multiple system components. Besides, if you already had the logic board replaced and the graphics card replaced, there is no point in continuing to sink money into that computer, especially now that it is over three years old.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac OS X "Blue Screen" Restart
- Thread starter muckluck
- Start date
- Sort by reaction score
Apple pays for the replacement of these graphics cards (and the attached motherboards) for free since it's been acknowledged that the card is faulty. The Apple Store line is that it's being replaced with an improved card that should not have the problem, but that's just to keep you happy, there is no improved card, it'll just keep failing. Apple is offering to cover these up to 4 years after the purchase date. I'm going to keep riding that for all it's worth, because I am not in a position to buy a new product from a company just because the last one they gave me failed prematurely.
Another update: I've had two of the major graphics glitch crashes, with console reporting a lot of stuff about kernel and NVDIA, so maybe this isn't a separate problem from the blue screen crashes. I thought it was separate because after having my graphics card replaced, the blue screen crashes persisted, while I thought the graphics crashes were resolved. It seems that whatever card they put in there is still faulty, so maybe both problems trace back to the graphics card. I'm going into the APple Store again today, I'll let you know what they say.
glad to find a support group on this
I've just started having the blue screen followed by what looks like I've just logged in (I also have auto-login set to on). Running 10.6.6, haven't had the graphics card looked at, but my console log also shows:
System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/libclh.dylib
I restored my system from a clone backup (after trying to run Tech Tool Deluxe and pretty much borking things up) but it happened again.
One thing triggered a thought in here - the three times I've had it happen my 2008 MacBook Pro, it's been plugged into a 24" cinema display. Someone else pointed that out for them too. Is that a common denominator?
There were reports of this in 2009 right after Snow Leopard came out, many coming to the conclusion that Rosetta was involved, but I'm not running anything with that.
So I guess all I have to add is "me too". Sure makes producing a live show on Ustream more of an adventure than it was already!
Allison Sheridan
NosillaCast Podcast at http://podfeet.com
A technology geek podcast with an EVER so slight Macintosh bias!
Follow me at http://twitter.com/podfeet
I've just started having the blue screen followed by what looks like I've just logged in (I also have auto-login set to on). Running 10.6.6, haven't had the graphics card looked at, but my console log also shows:
System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/libclh.dylib
I restored my system from a clone backup (after trying to run Tech Tool Deluxe and pretty much borking things up) but it happened again.
One thing triggered a thought in here - the three times I've had it happen my 2008 MacBook Pro, it's been plugged into a 24" cinema display. Someone else pointed that out for them too. Is that a common denominator?
There were reports of this in 2009 right after Snow Leopard came out, many coming to the conclusion that Rosetta was involved, but I'm not running anything with that.
So I guess all I have to add is "me too". Sure makes producing a live show on Ustream more of an adventure than it was already!
Allison Sheridan
NosillaCast Podcast at http://podfeet.com
A technology geek podcast with an EVER so slight Macintosh bias!
Follow me at http://twitter.com/podfeet
same problem
Hi, I've been having the same issue with blue screen 'log out' randomly, has happened about 5 times or so (so far). First time: after I accidentally dragged a file to trash. Another time: following iphoto freeze. This morning: after Chrome windows were left up overnight. When I awoke the computer from sleep and tried to close the window I got the blue screen again.
Seems to be triggered with separate applications that are running. Computer goes to blue screen, and then re-opens after 2 seconds, shows desktop background, then dock. All applications are closed. My computer is 6 months old, running on 10.6.6
Not sure if this is at all helpful, but here are some of the Console errors/warnings from this morning after trying to close the Chrome windows:
<Warning>: CGSShutdownServerConnections: Detaching application from window server
2/18/11 6:12:27 AM [0x0-0x29f29f].com.google.Chrome[3502] 2011-02-18 06:12:27.286 Google Chrome Helper[3738:107] HIToolbox: received notification of WindowServer event port death.
<Error>: kCGErrorInvalidConnection: CGSSetBackgroundEventMaskAndShape: Invalid connection
2/18/11 6:12:47 AM com.apple.launchd.peruser.501[87] ([0x0-0x29f29f].com.google.Chrome[3502]) Exit timeout elapsed (20 seconds). Killing
2/18/11 6:12:47 AM com.apple.launchd.peruser.501[87] ([0x0-0x29f29f].com.google.Chrome[3502]) Job has overstayed its welcome. Forcing removal.
2/18/11 6:12:47 AM com.apple.launchd.peruser.501[87] ([0x0-0x29f29f].com.google.Chrome) Bug: launchd_core_logic.c:1114 (24498):0
2/18/11 6:12:53 AM com.apple.launchd.peruser.501[87] (com.apple.AirPortBaseStationAgent[6167]) Exited: Killed
2/18/11 6:13:18 AM com.apple.launchd[1] *** launchd[1] has started up. ***
2/18/11 6:13:45 AM com.apple.launchd.peruser.501[87] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
2/18/11 6:13:45 AM com.apple.UserEventAgent-LoginWindow[80] ALF error: cannot find useragent 1102
2/18/11 6:13:45 AM com.apple.UserEventAgent-LoginWindow[80] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
2/18/11 6:13:45 AM com.apple.UserEventAgent-LoginWindow[80] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
2/18/11 6:13:47 AM com.apple.launchd.peruser.501[87] (com.apple.Kerberos.renew.plist[112]) Exited with exit code: 1
Hi, I've been having the same issue with blue screen 'log out' randomly, has happened about 5 times or so (so far). First time: after I accidentally dragged a file to trash. Another time: following iphoto freeze. This morning: after Chrome windows were left up overnight. When I awoke the computer from sleep and tried to close the window I got the blue screen again.
Seems to be triggered with separate applications that are running. Computer goes to blue screen, and then re-opens after 2 seconds, shows desktop background, then dock. All applications are closed. My computer is 6 months old, running on 10.6.6
Not sure if this is at all helpful, but here are some of the Console errors/warnings from this morning after trying to close the Chrome windows:
<Warning>: CGSShutdownServerConnections: Detaching application from window server
2/18/11 6:12:27 AM [0x0-0x29f29f].com.google.Chrome[3502] 2011-02-18 06:12:27.286 Google Chrome Helper[3738:107] HIToolbox: received notification of WindowServer event port death.
<Error>: kCGErrorInvalidConnection: CGSSetBackgroundEventMaskAndShape: Invalid connection
2/18/11 6:12:47 AM com.apple.launchd.peruser.501[87] ([0x0-0x29f29f].com.google.Chrome[3502]) Exit timeout elapsed (20 seconds). Killing
2/18/11 6:12:47 AM com.apple.launchd.peruser.501[87] ([0x0-0x29f29f].com.google.Chrome[3502]) Job has overstayed its welcome. Forcing removal.
2/18/11 6:12:47 AM com.apple.launchd.peruser.501[87] ([0x0-0x29f29f].com.google.Chrome) Bug: launchd_core_logic.c:1114 (24498):0
2/18/11 6:12:53 AM com.apple.launchd.peruser.501[87] (com.apple.AirPortBaseStationAgent[6167]) Exited: Killed
2/18/11 6:13:18 AM com.apple.launchd[1] *** launchd[1] has started up. ***
2/18/11 6:13:45 AM com.apple.launchd.peruser.501[87] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
2/18/11 6:13:45 AM com.apple.UserEventAgent-LoginWindow[80] ALF error: cannot find useragent 1102
2/18/11 6:13:45 AM com.apple.UserEventAgent-LoginWindow[80] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
2/18/11 6:13:45 AM com.apple.UserEventAgent-LoginWindow[80] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
2/18/11 6:13:47 AM com.apple.launchd.peruser.501[87] (com.apple.Kerberos.renew.plist[112]) Exited with exit code: 1
Update to blue screen flash/windows server crash
Update: I took my macbook to the Apple store today and spoke with a Mac Genius. I showed him the console from when my screen went blue this morning, and he suspected the blue screen flash was a problem with permissions, and that maybe a permissions error was causing the system to crash and reboot, looking like it was logging out and back in quickly. I guess permissions can be corrupted pretty easily.
Anyways, he repaired permissions and hopefully that will work. Here's the blog post I put up with more details on how to repair permissions:
http://firelitdesign.blogspot.com/2011/02/mac-crash-mac-blue-screen-flash-during.html
So far so good, hasn't happened again, so hopefully it is a good fix. I'll have to wait and see if I get that annoying blue screen again and loose all of my work.
Update: I took my macbook to the Apple store today and spoke with a Mac Genius. I showed him the console from when my screen went blue this morning, and he suspected the blue screen flash was a problem with permissions, and that maybe a permissions error was causing the system to crash and reboot, looking like it was logging out and back in quickly. I guess permissions can be corrupted pretty easily.
Anyways, he repaired permissions and hopefully that will work. Here's the blog post I put up with more details on how to repair permissions:
http://firelitdesign.blogspot.com/2011/02/mac-crash-mac-blue-screen-flash-during.html
So far so good, hasn't happened again, so hopefully it is a good fix. I'll have to wait and see if I get that annoying blue screen again and loose all of my work.
chasing a red herring
so I spent some time with a friend of mine who is much more clever in these things than me, and he suggested that we're chasing a red herring with the blue screen/logout/in issue, that it is merely a symptom, the root cause of which is extremely broad. He said that we're basically dealing with something as descriptive as a blue screen of death, albeit a much more elegant version.
He suspects that we could all be dealing with different root causes.
I had restored from a clone backup, but got another blue screen/relogin. I repaired disk permissions and t hasn't happened in a week, but I'm not at all confident I've solved the problem.
As much fun as it is to find kindred spirits suffering the same problem, I think in reality we're suffering the same symptoms but unlikely to find a single root cause here.
Allison Sheridan
NosillaCast Podcast at http://podfeet.com
A technology geek podcast with an EVER so slight Macintosh bias!
Follow me at http://twitter.com/podfeet
so I spent some time with a friend of mine who is much more clever in these things than me, and he suggested that we're chasing a red herring with the blue screen/logout/in issue, that it is merely a symptom, the root cause of which is extremely broad. He said that we're basically dealing with something as descriptive as a blue screen of death, albeit a much more elegant version.
He suspects that we could all be dealing with different root causes.
I had restored from a clone backup, but got another blue screen/relogin. I repaired disk permissions and t hasn't happened in a week, but I'm not at all confident I've solved the problem.
As much fun as it is to find kindred spirits suffering the same problem, I think in reality we're suffering the same symptoms but unlikely to find a single root cause here.
Allison Sheridan
NosillaCast Podcast at http://podfeet.com
A technology geek podcast with an EVER so slight Macintosh bias!
Follow me at http://twitter.com/podfeet
Blue Screen
Hello...
I'm new here, so excuse me if I'm in the wrong forum...if so, will someone let me know please?
I see people talking about the blue screen, which I had with my last computer and was never able to fix it, but this time my blue screen is different.
I have a MacBook Pro, it was purchased in Oct of 2008, and I am running 10.5.8 on it.
I was away from my computer for about an hour, when I came back to it; it had the blue screen, and I was forced to shut it down using the start button. When it came back on,it had a gray screen, hung there blank for a few seconds, then the apple screen came up and it took longer to load than normal.
I know I can try PRAM, but am against it because of what happened with my old computer, which I was told was a lost cause. I'm also hesitant because my warranty runs out this year, and with my luck, it will break right after it runs out.
Does anyone know what the blue screen mean when it comes up out of nowhere? Also, every tine I put safari on my menu bar below, it disappears.
I would really appreciate someone's take on this. Thank you in advance.
Hello...
I'm new here, so excuse me if I'm in the wrong forum...if so, will someone let me know please?
I see people talking about the blue screen, which I had with my last computer and was never able to fix it, but this time my blue screen is different.
I have a MacBook Pro, it was purchased in Oct of 2008, and I am running 10.5.8 on it.
I was away from my computer for about an hour, when I came back to it; it had the blue screen, and I was forced to shut it down using the start button. When it came back on,it had a gray screen, hung there blank for a few seconds, then the apple screen came up and it took longer to load than normal.
I know I can try PRAM, but am against it because of what happened with my old computer, which I was told was a lost cause. I'm also hesitant because my warranty runs out this year, and with my luck, it will break right after it runs out.
Does anyone know what the blue screen mean when it comes up out of nowhere? Also, every tine I put safari on my menu bar below, it disappears.
I would really appreciate someone's take on this. Thank you in advance.
I have this same problem for over months now (MBP 15'' late 2007 10.6.7 2,2Ghz)
My Logicboard is replaced twice (but still the same 8600M GT) and it occurs again.
HELP!
My Logicboard is replaced twice (but still the same 8600M GT) and it occurs again.
HELP!
It happens when playing a flash based movie on HD or fullscreen. Sometimes it happens with regular movies to.
Holy thread back from the grave Batman!
Seriously, you really need to try a different graphics card.
As mentioned earlier, I saw some pretty similar behavior when mine was dying...
Spidey!!!
Isnt the graphics card a part of the logic board, something you cant replace?
Besides that. If it is the graphics card, Apple should replace that one (wth a new LB if needed) under extended warranty or switch MBP's
Besides that. If it is the graphics card, Apple should replace that one (wth a new LB if needed) under extended warranty or switch MBP's
I'm having this exact same problem. Random blue screen restarts out of nowhere, all my programs are closed and I get booted back to the desktop. My graphics card has also been replaced on my 2007 15" MBP. I have no clue why this is happening, but it's really infuriating. I've lost unsaved work several times.
Have exactly the same problem with my MacBook Pro (also had a mainboard exchange, because of a dead nvidia chip (black display)).
I can not remember that I've had this problem with OS X 10.5.8. But with OS X 10.6.7 I now encounter it almost once or twice a day.
Would be more than glad to find out what the culprit is.
I can not remember that I've had this problem with OS X 10.5.8. But with OS X 10.6.7 I now encounter it almost once or twice a day.
Would be more than glad to find out what the culprit is.
Ah, right -- MacBook Pro (not Mac Pro).
Are you still getting stuff like this in the kernel.log?
Are you still getting stuff like this in the kernel.log?
Code:
10-11-30 7:53:06 PM kernel NVDA(OpenGL): Channel exception! exception type = 0xd = GR: SW Notify Error
10-11-30 7:53:07 PM kernel 0000006e
10-11-30 7:53:07 PM kernel 00200000 00008297 00000474 00000010
10-11-30 7:53:07 PM kernel 0000047e 000015e0 00000000 0000000a
10-11-30 7:53:07 PM kernel 00000000 00000000 00000002
10-11-30 7:53:07 PM kernel 00000010 00000000So I left my mac open this morning. I just came back and saw that the screen saver was active so I moved the trackpad and what happens...
Blue screen...
Blue screen...
OK - next questions:
- Do you have any unusual startup items, or menu-bar hacks / extensions installed?
- What about unusal QuickTime plugins (look in /Library/QuickTime)?
- Does the crash ever happen when nothing is running other than Finder?
- Are you using a non-standard screen saver?
Spidey!!!
1 Other then Dropbox, Google Calendar, Gmail and iGrowl no.
2 No
3 Didn't paid attention to that, will do now
4 No
For me it started about a week ago without me doing anything new nor installing any new software. It occurred on my MBP (10.6.7) independent on whether I had an external screen connected or I was on the laptop directly. Sometimes it occurred while I was not even present in the room...
How does one know if an application is using Rosetta as some rumors seem to link the problem with that? Looking in the various fora it seems this has been around for more than 3 years even with Leopard but for me it is the firstime it happened...
How does one know if an application is using Rosetta as some rumors seem to link the problem with that? Looking in the various fora it seems this has been around for more than 3 years even with Leopard but for me it is the firstime it happened...
I feel your pain, mine simply just went away. To find out whether any of your applications are Rosetta, open System Profiler like this: click on the Apple logo in the upper left, pull down to About this Mac, click on More Info, and then click on Applications in the left sidebar. You'll see several columns one of which is "Kind" and it will show Intel, Universal, and possibly Rosetta applications.
All that said, since this suddenly started happening, I doubt the eliminating Rosetta applications will help you. Good luck - hope yours stops like mine did.