IMac Freezes at Login Screen
When I reboot my IMac, it gets to the login screen and freezes. The mouse will work, but I cannot enter anything into the password field; after a few minutes, I am able to start typing.
Any ideas?
Joe
jcabaleiro wrote:
When I reboot my IMac, it gets to the login screen and freezes. The mouse will work, but I cannot enter anything into the password field; after a few minutes, I am able to start typing.
If you launch the Console utility you might spot messages around the time of the freezes that could explain what's happening.
Similar Messages
-
IMac freezes at login screen for file server
The machine: iMac (lampshade), OS 10.3.9
The symptom: During the boot/login sequence, the machine locks up at the login screen to the file server.
If I disconnect the network cable during the boot sequence, it will error but not freeze; I can later reconnect the cable and login without a problem.
Any ideas?
JamesYou may want to look at this similar post:
http://discussions.apple.com/thread.jspa?messageID=690609򨦱
Heres what Mac Help said.
Open System Preferences and click Startup Disk.
If necessary, click the lock icon and type the name and password for an administrator user.
Click the icon of the system folder or system volume that you want to use, then click Restart.
IMPORTANT: When selecting a network startup volume, be sure you select a valid network startup volume and not a network install image. Choosing a network install image reinstalls your system software and may erase the contents of your hard disk. A standard network volume icon appears as a globe and Mac OS X system folder. When you select a network volume icon, a message appears in the Startup pane describing the volume. A network install icon appears as a globe with downward pointing green arrow.
Another way to select a startup disk is to hold down the Option key as you restart your computer. You'll see the available startup disks and can select one.
If your computer is on a network and a network startup volume is available, you can start up from the network startup volume by holding down the N key as you restart your computer. -
IMac Freezes Periodically During Screen Saver Only
I own a late-2006 Intel-based iMac. Over the last few months, I've noticed that the iMac freezes when the screen saver is running. This doesn't happen all the time, and it doesn't matter what screen saver I use. (None of the screen savers is a third-party.) The iMac doesn't freeze at any other time.
Any ideas?
- Keith
P.S. I'm running Snow Leopard right now, and it happens even with Snow Leopard, just as it did with plain ol' Leopard.Your iMac has a dedicated Graphic's chip (GPU), while some of the Late 2006 17" iMacs had a GMA 950 graphics processor with 64MB of DDR2 SDRAM that shared with the main memory. To check which Graphic's chip you have go to: Apple > About This Mac > More Info and in the Hardware section select Graphics/Display.
If you would like to monitor the temperature of your GPU, CPU, HD and Memory check out the iStat Pro widget > http://www.islayer.com/apps/istatpro/
The main reason I suspect the lack of RAM over an overheating GPU is because you only reported a problem with the Screen Saver and not with other intense graphic's like movies, videos or games.
Please let us know how you make out with the RAM upgrade.
Dennis -
Screen Sharing via iCloud on Lion Freezes at Login Screen
After updating to OSX Lion 10.7.3, screen sharing between two computers via the Internet allows me to connect to the remote computer and see the remote user's login screen, but as soon as I click on a user to login, the screen share image freezes before I can enter the user password.
Using iCloud Back to My Mac because all machines have the same Apple ID & password. Exact same setup worked before the 10.7.3 upgrade, but it could be coincidence.
Details:
Can see the remote computers in my finder,
Can click on them and connect successfully using either the Apple ID or the name and password a user that is allowed under Sharing -> Screen Sharing,
When clicking on "Screen Share," the computers connect and I'm prompted to either "Ask to Share the Display" or "Connect to Virtual Display"Since there really isn't anyone using the computer, I select "Connect to Virtual Display"
After clicking "Connect to Virtual Display" the Screen Sharing window shows the remote computer's login screen, whcih shows the user names, their icons and "Sleep" "Restart" or "Shut Down" on the bottom of the screen. One user has an orange circle with a white checkmark next to it.
Previously, I could click a user's name or icon, enter the password and control the remote Mac. Now, not amount of clicking works.
Have tried disconnecting and reconnecting as different users or using Apple ID without changes in the perofmance. Have restarted both machines.
Any help?I'm having the same problem screen sharing to a Lion 10.7.3 machine, I get this message.
However, it works just like it used to when I screen share from a 10.7.3 machine to another Mac running 10.6.8.
Any thoughts?
Thanks! -
Imac freezes with gray screen after mavericks update
I was updating my imac system and it is frozen in a gray screen, like it is restarting.
It's been twenty minutes and it didn't restarted.
What can i do if it don't restart anymore?
All my work data is on that imac.Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. -
OSX 10.7.4 freezes on login screen
I have a mid-2010 MacBook Pro and I've noticed several freezes on the login screen: it gets on the login screen and the multicolored spinning ball appears and you are not able to authenticate.. The only thing you can do is to force a shutdown with the power button. I always see this messages before the forced shutdown:
29/06/12 21:53:05,000 kernel NVDA(OpenGL): Channel exception! exception type = 0x6 = Fifo: Parse Error
29/06/12 21:53:05,000 kernel IOVendorGLContext::ReportGPURestart
29/06/12 21:53:05,000 kernel NVDA(OpenGL): Channel exception! exception type = 0x6 = Fifo: Parse Error
29/06/12 21:53:05,896 sandboxd ([226]) DumpGPURestart(226) deny network-outbound /private/var/run/mDNSResponder
29/06/12 21:53:21,624 UserEventAgent servermgr_certs[202] -[CertsRequestHandler(HelperAdditions) identitiesFromKeychain:]: SecItemCopyMatching (err = -25300)
29/06/12 21:53:21,630 com.apple.UserEventAgent-System SecItemCopyMatching: Impossibile trovare nel portachiavi l’elemento specificato.
29/06/12 21:53:21,633 UserEventAgent servermgr_certs[202] -[CertsRequestHandler(HelperAdditions) identitiesFromKeychain:]: SecItemCopyMatching (err = -25300)
29/06/12 21:53:21,633 com.apple.UserEventAgent-System SecItemCopyMatching: Impossibile trovare nel portachiavi l’elemento specificato.
29/06/12 21:53:21,634 UserEventAgent CertsKeychainMonitor: ready to process keychain & timer events
29/06/12 21:53:25,000 kernel NVDA(OpenGL): Channel timeout!
29/06/12 21:53:37,000 kernel AppleIntelFramebuffer VBL interrupts lost DEISR 00000010 DEIMR 7cdfff7f DEIER 83200080
Can it be a software issue related with the NVidia drivers?Follows the details of the DumpGPURestart log entry:
DumpGPURestart(226) deny network-outbound /private/var/run/mDNSResponder
Process: DumpGPURestart [226]
Path: /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/DumpGPURestart
Load Address: 0x104d15000
Identifier: DumpGPURestart
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Date/Time: 2012-06-29 21:53:05.465 +0200
OS Version: Mac OS X 10.7.4 (11E53)
Report Version: 7
Backtrace:
0 libsystem_kernel.dylib 0x00007fff92feb57e __connect_nocancel + 10
1 libsystem_dnssd.dylib 0x00007fff8d877448 ConnectToServer + 829
2 libsystem_dnssd.dylib 0x00007fff8d878e9d DNSServiceCreateConnection + 50
3 libsystem_info.dylib 0x00007fff93ac307d _mdns_search + 1689
4 libsystem_info.dylib 0x00007fff93ac38b7 mdns_addrinfo + 615
5 libsystem_info.dylib 0x00007fff93ac4151 search_addrinfo + 152
6 libsystem_info.dylib 0x00007fff93ac7a1c si_addrinfo + 1614
7 libsystem_info.dylib 0x00007fff93ac922a si_list_call + 294
8 libsystem_info.dylib 0x00007fff93ac9050 __si_async_call_block_invoke_1 + 96
9 libdispatch.dylib 0x00007fff88afaa86 _dispatch_call_block_and_release + 18
10 libdispatch.dylib 0x00007fff88afb965 _dispatch_worker_thread2 + 255
11 libsystem_c.dylib 0x00007fff894a33da _pthread_wqthread + 316
12 libsystem_c.dylib 0x00007fff894a4b85 start_wqthread + 13
Binary Images:
0x7fff88af9000 - 0x7fff88b07fff libdispatch.dylib (187.9.0 - compatibility 1.0.0) <1D5BE322-A9B9-3BCE-8FAC-076FB07CF54A> /usr/lib/system/libdispatch.dylib
0x7fff89453000 - 0x7fff89530fef libsystem_c.dylib (763.13.0 - compatibility 1.0.0) <41B43515-2806-3FBC-ACF1-A16F35B7E290> /usr/lib/system/libsystem_c.dylib
0x7fff8d875000 - 0x7fff8d87dfff libsystem_dnssd.dylib (??? - ???) <D9BB1F87-A42B-3CBC-9DC2-FC07FCEF0016> /usr/lib/system/libsystem_dnssd.dylib
0x7fff92fd5000 - 0x7fff92ff5fff libsystem_kernel.dylib (1699.26.8 - compatibility 1.0.0) <1DDC0B0F-DB2A-34D6-895D-E5B2B5618946> /usr/lib/system/libsystem_kernel.dylib
0x7fff93aad000 - 0x7fff93ae8fff libsystem_info.dylib (??? - ???) <35F90252-2AE1-32C5-8D34-782C614D9639> /usr/lib/system/libsystem_info.dylib -
Windows XP Machine Freeze before Login Screen 2015
Has there been any Windows updates applied recently that may be causing this? Has any new hardware been added to them? A virus seems unlikely but not impossible. How old are the machines and how many is this happening to?
When you get to System Restore, what is the last checkpoint showing as having a Restore point created for? It is quite likely that that event is causing this
You really need to look at getting off XP - it is out of support and is going to have more and more of these problemsHi All,
Suddenly all machines running Windows XP just freezes before the login screen comes.
Windows boots up. Showing the LOGO but just before the login screen comes it just freezes.
I have performed system restore some restore and boots up but some does not restore.
On Some of the computers that have been restored successfully, this problem has reoccured. The are instance where we have formatted a machine completely, but after a while this problem reoccurs.
I am suspecting a virus but not totally sure.
Can anyone help
This topic first appeared in the Spiceworks Community -
Mac Pro freezes at login screen
Mac Pro (2008, dual 2.8GHz quadcore, OS 10.6.8) is set up with
Energy Saver settings: computer sleep 1 hour, screen sleep 5 minutes
Security settings: require password immediately after sleep or screen saver begins
After the computer goes to sleep, upon hitting a key, the login screen appears. However after typing password, there was a message "checking password" and then the computer freezes. I've followed recommendations in Mac Pro Freezing: Checking Password
After the computer goes to sleep, the login screen is frozen. I cannot even enter password. After hard-rebooting it, it appears OK.
Here are the last entries in system.log:
Jan 8 15:21:59 oldmacpro com.apple.backupd[402]: Post-back up thinning complete: 4 expired backups removed
Jan 8 15:22:00 oldmacpro com.apple.backupd[402]: Backup completed successfully.
Jan 8 17:09:27 localhost DirectoryService[11]: Improper shutdown detected
Here are the last entries in kernel.log
Jan 8 15:50:55 oldmacpro kernel[0]: PM notification cancel (pid 47, cupsd)
Jan 8 15:50:55 oldmacpro kernel[0]: IOPMrootDomain: idle cancel
Jan 8 15:56:20 oldmacpro kernel[0]: PM notification cancel (pid 47, cupsd)
Jan 8 15:56:20 oldmacpro kernel[0]: IOPMrootDomain: idle cancel
Jan 8 17:09:27 localhost kernel[0]: npvhash=4095
Question: how can I find out what causes the computer to freeze and how can I fix it ?I would say yes to the verbose mode and go one further and make it permanent. Coming to OSX from running Tiger on an XPF install on a beige G3 system (totally unsupported by Apple), it was ALWAYS a smart move and even in new machines running hardware they're built to, you can't lose. For the times I do have to reboot, it's good to be able to watch the startup, as you catch immediately if there's a problem with anything. It is verbose after all...
To turn the mode on, you open the Terminal, and at the prompt, type in
*sudo nvram boot-args="-v"* and hit enter. It will nag you about using the terminal (if you haven't done so before) and you enter your password, hit enter again and you're good to go. (if you want to turn it off, type in *sudo nvram boot-args=* and hit enter and your password again) -
On the iMac user account login screen, what does the checkmark mean?
On my iMac, I have 3 user accounts. Sometimes I have noticed that next to 1 of the 3 account names that I will sometimes see a small white check mark in a red circle. What does this mean?
I just received the same login for the first time in a while. I had left my MacBook Pro asleep for several days and then turned it back on and the wakeup/login screen presented a similar red circle with a white check mark inside. Did you find an answer? I created a new post today to see if anyone has had anything similar, not sure if it's firevault or not confirming id...
-
Hey there.
My iMAC crashes quite often in the login scree. last time it happened , I got the log file from the console. This is the activity from the moment I turned on my iMAc and it crashed on login screen. i then rebooted and got the log file as soon as I was in the system.
here it is:
27/06/2009 21:17:27 com.apple.launchctl.System[2] fsck_hfs: Volume is journaled. No checking performed.
27/06/2009 21:17:27 com.apple.launchctl.System[2] fsck_hfs: Use the -f option to force checking.
27/06/2009 21:17:28 com.apple.launchctl.System[2] BootCacheControl: could not open /var/db/BootCache.playlist: No such file or directory
27/06/2009 21:17:28 com.apple.launchctl.System[2] BootCacheControl: could not unlink playlist /var/db/BootCache.playlist: Unknown error: -1
27/06/2009 21:17:29 com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
27/06/2009 21:17:29 com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
27/06/2009 21:17:29 com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
27/06/2009 21:17:29 com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
27/06/2009 21:17:29 com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
27/06/2009 21:17:29 com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
27/06/2009 21:17:36 com.apple.launchd[1] (com.openssh.sshd) Unknown key: SHAuthorizationRight
27/06/2009 21:17:41 com.apple.launchd[1] (com.paceap.pacesupport52) posix_spawnp("/System/Library/Extensions/PACESupportFamily.kext/Contents/Resour ces/paceload", ...): No such file or directory
27/06/2009 21:17:41 com.apple.launchd[1] (com.paceap.pacesupport52) Exited with exit code: 1
27/06/2009 21:17:44 com.vmware.launchd.vmware53 VMware Fusion 51348: Starting VMware Fusion:
27/06/2009 21:17:45 com.vmware.launchd.vmware53 kextload serialization lock busy; sleeping (89 retries left)
27/06/2009 21:17:46 org.ntp.ntpd26 Error : nodename nor servname provided, or not known
27/06/2009 21:17:46 com.vmware.launchd.vmware53 kextload serialization lock busy; sleeping (88 retries left)
27/06/2009 21:17:48 com.vmware.launchd.vmware53 kextload: /Library/Application Support/VMware Fusion/kexts/vmmon.kext loaded successfully
27/06/2009 21:17:49 com.vmware.launchd.vmware53 kextload: /Library/Application Support/VMware Fusion/kexts/vmci.kext loaded successfully
27/06/2009 21:17:52 com.vmware.launchd.vmware53 kextload: /Library/Application Support/VMware Fusion/kexts/vmioplug.kext loaded successfully
27/06/2009 21:17:52 com.vmware.launchd.vmware53 kextload: /Library/Application Support/VMware Fusion/kexts/vmnet.kext loaded successfully
27/06/2009 21:17:53 com.vmware.launchd.vmware53 Internet Software Consortium DHCP Server 2.0
27/06/2009 21:17:53 com.vmware.launchd.vmware53 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
27/06/2009 21:17:53 com.vmware.launchd.vmware53 All rights reserved.
27/06/2009 21:17:53 com.vmware.launchd.vmware53 Please contribute if you find this software useful.
27/06/2009 21:17:53 com.vmware.launchd.vmware53 For info, please visit http://www.isc.org/dhcp-contrib.html
27/06/2009 21:17:53 com.vmware.launchd.vmware53 Can't open lease database /var/db/vmware/vmnet-dhcpd-vmnet8.leases: No such file or directory -- check for failed database rewrite attempt!
27/06/2009 21:17:53 com.vmware.launchd.vmware53 Please read the dhcpd.leases manual page if you.
27/06/2009 21:17:53 com.vmware.launchd.vmware53 don't know what to do about this.
27/06/2009 21:17:53 com.vmware.launchd.vmware53 exiting.
27/06/2009 21:17:53 com.apple.launchd[1] (com.vmware.launchd.vmware53) Exited with exit code: 1
27/06/2009 21:18:00 com.apple.SystemStarter31 PACESupport - Couldn't find the paceload script
27/06/2009 21:18:01 com.apple.SystemStarter31 Starting Qmaster services
27/06/2009 21:23:08 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow97) Exited: Terminated
27/06/2009 21:23:08 com.apple.launchd112 (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
27/06/2009 21:23:08 com.apple.launchd112 (org.x.startx) Unknown key for boolean: EnableTransactions
27/06/2009 21:23:09 com.apple.FolderActions.enabled115 launchctl: Error unloading: com.apple.FolderActions.folders
27/06/2009 21:23:11 Dock125 _DESCRegisterDockExtraClient failed 268435459
27/06/2009 21:23:17 Dock125 QL ERROR Generator database update takes too long... we will use what we currently have
27/06/2009 21:23:25 0x0-0x10010.info.virtuedesktops.VirtueDesktops137 dyld: Library not loaded: @executable_path/../Frameworks/TAUserInterfaceElements.framework/Versions/A/TAU serInterfaceElements
27/06/2009 21:23:25 0x0-0x10010.info.virtuedesktops.VirtueDesktops137 Referenced from: /Applications/VirtueDesktops.app/Contents/MacOS/VirtueDesktops
27/06/2009 21:23:25 0x0-0x10010.info.virtuedesktops.VirtueDesktops137 Reason: unsafe use of @executable_path in /Applications/VirtueDesktops.app/Contents/MacOS/VirtueDesktops with setuid binary
27/06/2009 21:23:27 com.apple.launchd112 (0x0-0x10010.info.virtuedesktops.VirtueDesktops137) Exited abnormally: Trace/BPT trap
27/06/2009 21:23:36 0x0-0x12012.com.apple.systemevents139 com.apple.FolderActions.enabled: Already loaded
27/06/2009 21:26:49 0x0-0x18018.com.apple.Safari168 Debugger() was called!
27/06/2009 21:29:40 com.apple.launchd112 (0x0-0x1c01c.com.apple.Console177) Exited: Terminated
Thanx!HI,
If you can access these files, delete them and see if it helps.
com.apple.loginitems.plist
com.apple.loginitems.plist
/Users/YourName/Library/Preferences. Drag those files from the Preferences folder to the Trash, empty the Trash and restart your Mac.
*"27/06/2009 21:17:44 com.vmware.launchd.vmware53 VMware Fusion 51348: Starting VMware Fusion:"*
Are you running a Windows partition?
Are you using VirtueDesktops? If so, you may want to delete the app and see if that makes a difference.
Carolyn -
Leopard freezing on login screen
Hi everyone.
Yesterday I was using my iMac normally, but today when I booted it froze on the login screen.
I tried reconnecting the mouse, the keyboard, tried unplugging and turning off everything for 15 seconds and nothing. Tried reseting the PRAM, still nothing.
Tried repairing the disc in disc utility trought Leopard Disc and tried repairing the permissions and stills the same.
But when I booted Windows XP on my Boot Camp partition it worked like a charm.
After that I formatted the bootcamp partition into a HFS+ partition and tried installing, but I got a message saying that I couldn't install Mac OS X on this partition (the partition was already formatted as HFS+ and not NTFS)
Any suggestions?
Obs:
iMac 2.66ghz, 2Gb DDR2 RAM, HD2600 PRO, 20-Inch aluminum. Running Mac OS X Leopard 10.5.6 with stock mouse and keyboard.
Since now thanks for the help guys.Have you tried to Safe Boot the Mac?
"+To start up in safe mode:+
+Shut down your computer and wait 10 seconds.+
+Press the power button.+
+Immediately after you hear the startup tone, hold down the Shift key.+
+You should press the Shift key as soon as possible after your hear the startup tone, but not before.+
+Release the Shift key when you see the gray Apple logo and progress indicator (spinning gear)."+
Safe Boot fires up with the basic OS software necessary to run the machine. If it works, then something may have been added to your system at some point in time that might be causing a problem.
If so, open 'About this Mac' then look in 'Start Up Items'. See what you have got in there.
Others may have suggestions for you on what to out look for, myself not being a Bootcamp user.
Good luck (oh, and Merry Christmas to you too).
Message was edited by: El Deanio -
All of a sudden, my iMac started getting stuck on the login screen. Once I enter the account name, the spinner just spins but never logs me in, and I have to power off. Once I restart the machine and get to the login screen, it allows me back into my account every single time (but gives me the warning about the computer not shutting down properly the last time). I cleaned the caches and made sure the external drive was not connected. Not sure what else I can do to resolve this ongoing problem. It does not occur on the guest account.
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time after you had the problem. Select the messages logged before the boot, while the system was unresponsive or was failing to shut down. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V). Please include the BOOT_TIME message at the end of the log extract.
If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful. -
MacBook Pro Freezes in Login Screen
Hello,
I've encountered a strange error on my 08 MBP (Should not be hardware related). When my computer boots up and gets to the login screen, it simply stops. Mouse clicks and key hits (either onboard or USB devices) do not appear to register, as nothing happens when I do either of these, but I can however move the cursor around freely. Same result in safe boot.
I've checked hardware out via Hardware Test and such, and everything checks out fine. Verbose Boot just goes right on through without stopping. I've connected the computer as a FW drive and pulled the system logs, where I get the following:
Apr 8 16:11:22 localhost com.apple.kextd[10]: Cache file /System/Library/Caches/com.apple.kext.caches/Directories//System/Library/Extens ions/KextIdentifiers.plist.gz is out of date; not using.
Apr 8 16:11:18 localhost com.apple.launchd[1]: * launchd[1] has started up. *
Apr 8 16:11:27 localhost bootlog[34]: BOOT_TIME: 1270764678 0
Apr 8 16:11:34 localhost DirectoryService[30]: Improper shutdown detected
Apr 8 16:11:34 localhost blued[35]: Apple Bluetooth daemon started
Apr 8 16:11:39 localhost VMware Fusion 204229[48]: Starting VMware Fusion:
Apr 8 16:11:39 localhost com.vmware.launchd.vmware[39]: VMware Fusion 204229: Starting VMware Fusion:
Apr 8 16:11:39 localhost com.apple.kextd[10]: Cache file /System/Library/Caches/com.apple.kext.caches/Directories//System/Library/Extens ions/IOKitPersonalities_i386.ioplist.gz is out of date; not using.
Apr 8 16:11:39 localhost mDNSResponder[23]: mDNSResponder mDNSResponder-214.3 (Feb 11 2010 04:49:16) starting
Apr 8 16:11:39 localhost com.apple.usbmuxd[16]: usbmuxd-190 built for iTunesNineOne on Mar 8 2010 at 20:25:36, running 32 bit
Apr 8 16:11:40 localhost configd[32]: bootpsessiontransmit: bpf_write(en1) failed: Network is down (50)
Apr 8 16:11:40 localhost configd[32]: DHCP en1: INIT-REBOOT transmit failed
Apr 8 16:11:40 localhost configd[32]: network configuration changed.
Apr 8 16:11:40 administrators-macbook-pro configd[32]: setting hostname to "administrators-macbook-pro.local"
Apr 8 16:11:40 administrators-macbook-pro com.vmware.launchd.vmware[39]: Verifying files from package 'com.vmware.fusion.application' on '/'.
Apr 8 16:11:40 administrators-macbook-pro com.vmware.launchd.vmware[39]: Finished verifying files from package 'com.vmware.fusion.application' on '/'.
Apr 8 16:12:08 administrators-macbook-pro configd[32]: subnet_route: write routing socket failed, Network is unreachable
Apr 8 16:12:09 administrators-macbook-pro /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[24]: Login Window Application Started
Apr 8 16:12:09 administrators-macbook-pro configd[32]: network configuration changed.
Apr 8 16:12:09 administrators-macbook-pro vmnet-bridge[77]: UUID: Unable to open /dev/mem: No such file or directory
Apr 8 16:12:09 administrators-macbook-pro vmnet-bridge[77]: Dynamic store changed
Apr 8 16:12:09 administrators-macbook-pro vmnet-bridge[77]: Started bridge for 0, en1
Apr 8 16:12:10 administrators-macbook-pro com.vmware.launchd.vmware[39]: Started network services
Apr 8 16:12:10 administrators-macbook-pro configd[32]: network configuration changed.
Apr 8 16:12:10 administrators-macbook-pro vmnet-bridge[77]: Dynamic store changed
Apr 8 16:12:10 administrators-macbook-pro com.vmware.launchd.vmware[39]: Verifying and re-installing files from /Library/Application Support/VMware Fusion/thnuclnt
Apr 8 16:12:21 administrators-macbook-pro WindowServer[62]: bootstraplookip failed: Unknown service name
Apr 8 16:12:25: --- last message repeated 4 times ---
Apr 8 16:12:25 administrators-macbook-pro loginwindow[24]: Login Window Started Security Agent
Apr 8 16:12:25 administrators-macbook-pro WindowServer[62]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Apr 8 16:12:25 administrators-macbook-pro com.apple.WindowServer[62]: Thu Apr 8 16:12:25 administrators-macbook-pro.local WindowServer[62] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
After this, the log cycles the following until I powered off the computer:
Apr 8 16:12:26 administrators-macbook-pro WindowServer[62]: bootstraplookip failed: Unknown service name
Apr 8 16:12:27: --- last message repeated 1 time ---
Apr 8 16:12:27 administrators-macbook-pro SecurityAgent[121]: retry:2 common fonts return value[0,1,2]:10000003,10000003,0
Apr 8 16:12:27 administrators-macbook-pro SecurityAgent[121]: CoreText CopyFontForName received mig IPC error (10000003) from font server
Apr 8 16:12:27 administrators-macbook-pro SecurityAgent[121]: Invalid font server IPC destination! Namespace changed? Retrying (0)...
Apr 8 16:12:28 administrators-macbook-pro WindowServer[62]: bootstraplookip failed: Unknown service name
Apr 8 16:12:30: --- last message repeated 1 time ---
Apr 8 16:12:29 administrators-macbook-pro SecurityAgent[121]: retry:2 common fonts return value[0,1,2]:10000003,10000003,0
Apr 8 16:12:29 administrators-macbook-pro SecurityAgent[121]: CoreText CopyFontForName received mig IPC error (10000003) from font server
Apr 8 16:12:29 administrators-macbook-pro SecurityAgent[121]: Invalid font server IPC destination! Namespace changed? Retrying (1)...
Apr 8 16:12:30 administrators-macbook-pro WindowServer[62]: bootstraplookip failed: Unknown service name
Apr 8 16:12:31: --- last message repeated 1 time ---
Yesterday, I did install MathType. Could this be causing the problem, which I assume is being cause by a font error? If so, how does a font prevent me from using my computer? I would like to resolve this without needing to reinstall OS, as I just did that 7 days ago due to HD failure, which I am still working on recovering preferences, etc. from.
Help is appreciated.
Thanks.
Message was edited by: KrayzBluCould boot up holding down command+s so you get into single user mode. Run the fsck like it says on the screen.
Then I would mount the hard drive and delete caches in /Library/Caches and /System/Library/Caches and probably caches in /private/var/db/dyld
If your not sure use these commands, but be careful make sure your in the correct directory by running ls to list the contents or pwd to see what directory your in. Running rm -rf will force deletion of everything in that directory using * :
cd /Library/Caches
rm -rf *
cd /System/Library/Caches
rm -rf *
cd /private/var/db/dyld
rm -rf *
If all else fails you can always throw the Snow Leopard CD in and reinstall the OS. It shouldn't hurt your files any in your profile. Snow Leopard is pretty much dummy proof when reinstalling.
Of use a third party utility like Disk Warrior or something to maybe fix an error. Could try Tech Tool Pro you get with Applecare as well, but I haven't used that in years. Not sure what it does now. -
My iMac freezes at login and won't go any further
I started to get frozen grey screen and with rebooting I could get to the login screen where it would think about matters then move on and get stuck in a blue or grey screen. Now it goes no further than the login screen and won't move forward.
I've tried a safe reboot and power off etc but still not working.
Any suggestions?
Thanks,
Brian.Hi Brian, which OSX version?
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive & clear caches.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
If 10.7.0 or later...
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions. -
Satelltie L855-s5155 freeze at login screen or was extremely slow - now need windows 8or 8.1
I purchased this laptop about a year and half ago. I have used it a total of 5 times. It mainly remains in the laptop back int he closet.
Model L855-S5155
Serial Number: XXXXXXXXX
I turned it on last week and it booted up to the login screen. I typed my password in and nothing happened. The cursor was flashing in the password field but when I typed my password, the cursor moved two spaces and remained there for a couple of hours at which time I had to turn it off by holding the power button for 5 seconds. I repeated this process several times. At one time it took my password and the dots started going in circles to I guess load the live tiles. I left that go for about 4 hours at which time I turned it off again.
Upon turning it on I did get an error message on a bably blue screen that stated 'Windows was not shutdown properly' and it restarted. At the Toshiba splash screen the dots going in a circle showing that something was loading so I left that go for about 6 hours while it remained still at that screen.
At one point I had gotten the maintenance screen upon boot up so I tried a system restore. That didn't work. Same issues. Unfortunatley I hadn't made a restore / recovery disk which I guess being Toshiba that should have been my first task. As I reviewed the boards I found that the system never shuts down and at the current situation I was in not being able to login to Windows I had to resort to removing the battery for a minute and restarting the laptop to get to certain areas.
I attmepted to reset the PC from the maintenance screen in hopes that would fix the problem. I had upgraded from windows 8 to 8.1, but it was working after the upgrade so I didn't worry about it. Unfortunatley that didn't work. When it restarted it remained on the Toshiba slpash screen for 10 hours with the dots going around in a circle. Knowing some processes take a little time, I have been leaving the laptop on for a while to make sure certain processes have time to finish but 10 hours to me might have been too long after a recovery. Everytime I turn on the laptop the Toshibal splash screen would come up and the dots would go around in circles. I left it go over night one night to see if there was some process that needs longer to run, but no.
Being that I purchased my laptop with windows 8, I would like to have windows 8 on it. Unfortunately I need to laptop for a project so I decided maybe I should put windows 7 on the computer just to get t running so upon restarting the laptop and getting the BIOS screen there was screen that came up that would delete all partitions. I guess and HDD Recovery. Now that I have run that of course I have, what I think, may be a clean hard disk to start from.
Something I did notice when I began to install windows 7 is that my 750 gb hard drive only shows 698 gb of free space. Being that there aren't any disk maintenance tools to let me know if there are bad sectors due to a possibly bad hard disk or is the windows 8 image still hiding on there. Doubtful if the partitions were removed.
Can anyone tell me what happened? Is there anyway to get windows 8 back onto the laptop without buying it again? Any assistance would be greatfully accepted.
[Moderator edit to remove serial number.]Satellite L855-S5155
If no recovery media was created, you can obtain it from Toshiba. Scroll down to Get Recovery Media here.
For instructions, see the section Restoring from recovery media, which begins on p. 57 of the User's Guide.
Satellite/Satellite Pro C800/L800/S800 Series User’s Guide
When you upgrade to Windows 8.1, be sure to follow these instructions.
How to Update from Windows 8 to Windows 8.1
-Jerry
Maybe you are looking for
-
Trying to add a pause after Ken Burns effect to hold the photo
I am trying to set a pause to my still photos after using the Ken Burns effect. So it starts zoomed in on an area of the photo and pulls out and then I want it to hold for a few seconds so you can see the full photo. Any suggestions? I can't find
-
On iCloud pages how can you put a header on only the first page and not the second page?
I'm trying the do a visual report and every time I put a header on the first page it goes to the next page and if I try to delete it on the second page it deletes on the first page too.
-
How do I remove the display glass on an imac7.1 to replace the optical drive?
I have a 2007 iMac 24inch which has a bad optical drive. How do I remove the display glass to get to the optical drive?
-
Hi my name is Lior Sassi from Israel. I bought an iPhone 5 in Amsterdam. Now I have a problem with the button on the iPhone and I still have a guarantee. Where can I fix the problem?
-
Someone Using My email Address to Send Spam
Does anyone know how to stop and preventing someone from using my email address? It says it's coming from Verizon. net moblie. I thought verizon put measures in place to prevent this sort of thing from happening?