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

Level 1

4 points

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

72 replies

.ng

Level 1

0 points

Jan 30, 2011 9:12 PM in response to djenryte

I have Applecare. Brought it in last week and they ran some test and found out something with the graphics card. Had the entire logic board replaced. A few days ago it started freezing again... Don't know what the issue is, but I'm going to bring it back in tomorrow.

I have the Late 2007 MacBook Pro 2.2 Ghz.

K Goetz

Level 1

4 points

Feb 5, 2011 5:37 PM in response to Peter DeWolf

Ok. So maybe this thread is dead.
But I'm not - quite.

A month ago, I upgraded a new-ish PowerMac box from 10.5.something to 10.6.3 and then 10.6.5. The box in question was new-ish but the system disk was inherited and had lots of old junk lying around.

As soon as I got to 10.6.5 and let the system sit still for awhile, I'd have this auto log-out "feature" kick in. The first time it happened, all my open apps and windows and such would vanish as though I'd logged out. Boom! The loginwindow app crashed and automatically restarted with a login window. This always seemed to happen a few hours after I'd left work. So it'd happen at, for example, 2am. Then, after that every ~68 minutes, the loginwindow app would crash again - just sitting there waiting for me to log back in. I'd log in the next working day and the box would be fine all day until it'd start the same routine during the night.

So after trying some of the tricks suggested didn't help, I decided that maybe I had too much ancient junk hanging around on my system disk. I decided I'd have to start from scratch (something I hadn't done on this box in many many years).

In the meantime, I found that my box would be ok if I'd keep it from putting the display to sleep. So when I left work at night, I'd stick a little USB mouse jiggler in. The next morning, everything would be fine - just like I left it. So I could limp along for a month like that.

Some people here have suggested that there's a video aspect to this problem. Maybe. My box has two NVIDIA GeForce GT 120 video boards inside. Maybe my problem has something to do with the transition from screen saver to sleep. Dunno.

Anyhow, yesterday I decided to bite the bullet and start from scratch. So I installed 10.6.3 and then used software update to get all the way up to the latest thing - 10.6.6. And I went home for the night.

I was pretty sad to find that my box had logged me out. With my fresh install and everything.
Very sad!

So maybe there's something to this graphics thing.

My box is set to go to screen saver after 15 minutes.
It's set to sleep the displays at 1 hour.
It's set not to ever sleep the CPU.

So next I'll try the "russian" solution proposed earlier.

K Goetz

Level 1

4 points

Feb 7, 2011 4:37 PM in response to K Goetz

As a little loop closing...

I tried the "russian" solution described elsewhere. That means I manually (using pacifist) installed the update "SnowLeopardGraphicsUpdate1.0" into my 10.6.5 system.

Last night I was again logged out. As before. So that seems not to have done anything (or at least not what I was hoping it'd do). Alas.

Oddly, Apple lists 10.6.2 as resolving a "an issue that might cause your system to logout unexpectedly" which is what my system is doing every night with 10.6.5 and 10.6.6.

.ng

Level 1

0 points

Feb 10, 2011 12:14 AM in response to .ng

Could someone tell me how I can get a report of this crash? Normally when something crashes, there is a window that pops up telling me so. But in this situation, when I'm forced to log out or shut down, there isn't an opportunity to do so. I see others have posted theirs, I was wondering if someone could tell me how. Thanks.

Feb 12, 2011 8:08 AM in response to K Goetz

That's sick =(
Worked so well on my MacBook Pro 3,1 (late 2007) 2,2 GHz, Santa Roza.

I was getting logged out until I followed those steps carefully (read CAREFULLY) and have not hade a single log-out nor graphical bugs ever since.

My 3 year old MacBook Pro feels as good as ever again.

I hope you'll find a solution to your problem since the "Russian" one didn't work.

xgenius

Level 1

0 points

Apr 7, 2011 7:08 AM in response to Peter DeWolf

Hopefully this can help you and many others with this issue... I just had a customer with this problem and his was so severe that after he logged in, within 60 seconds it logged him back out. I tested this with a test account (which I had set up in a record breaking 16 seconds and the issue remained. Using an external OS to test I was able to verify that the unit's hardware was fine, thus I knew it to be software and started looking into the Log files.
What I found was a bunch of directory services, WindowServer, etc. issues so I attacked this thing with all I could think of.

*WARNING THIS IS NOT RECOMMENDED FOR PEOPLE UNCOMFORTABLE WITH BASH/UNIX *

I booted up to a install disc (10.6.3) and went into the menu and opened up Terminal and started renaming the following items:

/Library/LaunchAgents
/Library/LaunchDaemons
/Library/Preferences
/System/Library/Caches
/System/Library/FrameWorks
/System/Library/LaunchAgents
/System/Library/LaunchDaemons
/System/Library/Private\ Frameworks
/System/Library/StartupItems
/System/Library/CoreServices/Finder
/System/Library/CoreServices/SystemUIServer
/System/Library/CoreServices/SystemEvents

I renamed all of those with a ~OLD
and then did an install. I was able to preserve the user and all their settings (not 100% sure of the 3PP apps they had installed). But the good news is that it was able to boot up and I haven't seen the issue show up after several hours.
Had I had more time and more energy to pour into this I wouldn't pin pointed it down to fewer things but I checked the sizes of all the directories I had changed and saw that the new ones created by the installer were larger than the ~OLD versions I had created meaning that there was little loss there and it would be safe to delete the ~OLD after a couple more days of testing.
I hope this all helps, otherwise I'll keep thinking 🙂

koDiacc

Level 1

5 points

Jun 6, 2011 5:12 PM in response to xgenius

Same Problem Here.

Newest Mac OS X updates, Macbook Pro 15" Mid 2007 Santa Rosa, Replaced Mainboard because of the Graphic Issue.

It keeps crashing when i move to Fullscreen (2nd screen plugged in)

Trying the Solution from uplink13 now

koDiacc

Level 1

5 points

Jun 24, 2011 5:58 PM in response to koDiacc

for me, the trick from uplink13 obviously did it. since then, no more recurring problems! thanks a lot!

Jul 1, 2011 10:20 PM in response to Peter DeWolf

sudden blue screen flashes then I see the login screen. Lose all work. All apps shut down and logged out and the login screen appears.

This has happened twice while browsing on safari and once on firefox and once on Google Chrome and twice while using iTunes and Pathfinder. Extremely random and can not seem to be intentionally duplicated.

I recently bought my first Macbook Pro 3 months ago. I am severely disappointed. Now my 90 day phone coverage is over and I must pay $349 for the “apple protection plan” to get any service (but who will protect me from apple?).

It is true I have a lot of apps installed and there are lots of factors involved, but although there is a problem both the service center and the phone service refuse to help (unless, of course, I have the “protection plan” but how far does the “protection” go?).

Macbook Pro 15”

Mac OSX 10.6.8

Processor: 2 GHz intel core i7

Memory: 8 GB 1333 MHz DDR3

I think the sudden blue screen and logout is happening because of the peripherals. Lately I have had firewire and usb external hard drives plugged in because that is where I keep my iTunes libraries and lately I have been doing work with the external hard drives.

I did the “hold opt-CMD- P- R while restarting” to redo the memory.
I restarted in safe mode and that seemed to work for a day.
I did the onyx.app clean scenario
I am thinking about doing a clean install and start over again.

koDiacc

Level 1

5 points

Jul 2, 2011 7:03 AM in response to nimai_pandit

just look up in the Console.App and look for error descriptions before you get logged out and google this!

for me, the trick as mentioned aboved worked perfectly!

Jul 18, 2011 2:29 AM in response to koDiacc

Yes, but I don't feel comfortable doing the trick mentioned before and he warns the user not to do it if we feel uncomfortable with it.

Happened again: I did a complete erase and reinstall and I have slowly added the most essential apps. I installed Devonthink, pathfinder, launchbar… and when I installed “Blast” I went to enter the serial number and immediately it showed the blue screen and logged out! So, I immediately uninstalled “Blast” using appcleaner.

Jul 28, 2011 1:31 AM in response to nimai_pandit

Seems like Boom was the culprit as Bunnyslippers said in another thread!

https://discussions.apple.com/thread/2747999?answerId=15642312022#15642312022

Blast and Boom are from the same company so I had Blast and Boom uninstalled ~ but now testing Boom 1.2 Beta and the developers should visit these threads soon.

After upgrade to 10.6.5, I get forcibly logged out