Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

After upgrade to 10.6.5, I get forcibly logged out

Twice, so far. Every application I'm in is immediately terminated - no save! - and I am presented with the Login window.

The first time, I went into Time Machine. I clicked at a spot on the screen and bam! Time to log in.
The second time I was in Itunes. I selected the Visualizer, selected full screen mode, and then typed command-F - hoping (since I'd never tried the visualizer) it would take me out of full screen. The image froze. I clicked my mouse and bam! the music stopped, my screen went blue (as if the system was rebooting) and then showed the default background and the Login window.

This is pretty scary. Is there a way to downgrade to 10.6.4 safely?

MacBook Pro 3,1, Mac OS X (10.6.5)

Posted on Nov 20, 2010 12:37 AM

Reply
72 replies

Dec 12, 2010 7:29 PM in response to Peter DeWolf

I have a late '08 MBP (4,1) with an 8600M GT but it has 512 mb of VRAM. I watch a lot of full screen video and have experienced no problems. Does anybody that's having problems have more than 256 on the VRAM? Maybe for some reason the task is requiring more VRAM than you have.

Has anybody tried logging into another user account to see if the problem persists? If not, I would strongly recommend that as it will tell whether the problem is systemwide or user specific. It's best if it's a clean account (Create one. you can get rid of it when you're done).

Let us know if this makes a difference or not.

Also, use disc utility to repair permissions and check your disc.

If you have any diagnostic software, run it. Apple offersTechTool Deluxe free to any to anyone with a Mac. Go here and try to download it. you just need your serial number ( Go to the Apple menu and choose about this Mac. Then choose more info. The serial numbers near the Bottom. You should be able to copy and paste.

http://support.apple.com/kb/DL1005

Also rebuild your PRAM. Start up the Mac while holding Command-Option-P-R. Hold them til you hear a third startup chime.

Let me know if any of this helps.

Good luck. 🙂

Dec 12, 2010 11:42 PM in response to Peter DeWolf

Just to add my voice to the mass, and some context:
MaxBook Pro 3.1 15", full screen youtube video, freeze, bluescreen, "kicked" out.

I don't think this issue is related to some hardware issue with the GT8600. I had my mainboard replaced about a year ago, precisely because of the nvidia problem. My system has been running smooth since then. Then, I upgraded to 10.6.5 2 days ago and noticed the issue once (well, I haven't tried again). Now I must say that I updated Safari at the same time. So it might be related to WebKit (found some clue in the console)

Dec 14, 2010 8:02 PM in response to Igor_G5

I am jumping to this thread to report me having the same problem.
Late 2007 3,1 macbook pro 15"
Almost always happen when stream video full screen as well. Seems like the similar symptoms across the board eh?
I hope this get resolved soon... My wife stream a lot of video online and it's annoying that it can't be full screen.

Thanks guys!

Dec 19, 2010 5:00 PM in response to Peter DeWolf

Happens to me as well.

NVDA: Fatal error, failed to make a texture resident. GPU heap size is 746 MB with 3262 textures and 8 surfaces.

But only since I got a 27" cinema display a couple of weeks ago (after upgrade to 10.6.5). It occurs maybe every day or two, but never while I'm working on the computer. I come back to it and find it's rebooted while I was wasn't watching. Perhaps its the screen saver kicking into full screen mode as others have reported.

I have a 15" MBP with Core Duo, week 3 2010 build.

I do have old VMware installed but it's never active when this happened (apart from all those background processes).

Do people suspect this is a logic board problem or a bug in 10.6.5?

Dec 26, 2010 9:48 AM in response to naskies

Same problem here yesterday : Aperture 3 was running and was on the foreground. I put the MBP to sleep (clamshell mode) then woke it up a few minutes later… And Boom ! First, the desktop appeared just as if I had logged out and was logging in again (with menubar items progressively charged). Then I tried to re-launch Aperture, and… Re-boom : blue screen, and nothing else. I forced the Mac to re-boot after a while.
Already experienced a similar problem (except the screen was black) around one month ago, some days after updating to 10.6.5. Never had this kind of crash before. It seems like it is a 10.6.5-related issue :
http://reviews.cnet.com/8301-13727_7-20024774-263.html
Let's hope it will get fixed with Mac OS 10.6.6 !

Dec 27, 2010 12:14 PM in response to Peter DeWolf

I have a MacBook Pro 2.4 Ghz Intel core i5, running OS X 10.6.5 and an external 27 inch Apple Cinema display. Every time I went fullscreen on VLC or quicktime, the system logged me out.

BAsed on the advice in this thread I reset the PRAM (shut down then press the power button whilst holding the Command, alt and P and R keys till it chimes twice) and everything works fine now.

Try it out, hope it works for you!

Dec 31, 2010 10:15 AM in response to Peter DeWolf

Just to add another log to the fire...

I have seen this twice in two days since moving to 10.6.5 of MacOS.
And it's very alarming.

Both times it happened in the night - while I wasn't watching.
I returned in the morning to find my established session replaced with a login window. Very sad.

One time it was:

12/31/10 7:37:51 AM com.apple.launchd[1] (com.apple.loginwindow[86]) Job appears to have crashed: Bus error

12/30/10 1:53:27 AM com.apple.launchd[1] (com.apple.loginwindow[85]) Job appears to have crashed: Segmentation fault

One time a bus error and one time a seg fault. Odd.

In both case, the loginwindow line was preceded by a log line had a thing like this at the exact same time (to the second):

12/30/10 1:53:27 AM mDNSResponder[18] Bad service type in . ceqkJTTBHE69H6UQ-3J3X.tcp.local. Application protocol name must be underscore plus 1-15 characters. See <http://www.dns-sd.org/ServiceTypes.html>

Some of you talk about MBPs but my problem is on a more or less recent MacPro (2009).

I have noticed my startup chime disappearing lately. I don't know why. Resetting the PRAM makes it come back but only for a little while it seems. Some have suggested a PRAM reset as a solution for this problem. I'll try that just now if only out of superstition.

After upgrade to 10.6.5, I get forcibly logged out

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.