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

Similar Messages

  • 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!

  • 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 problems

    Hi 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)

  • 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?
    James

    You may want to look at this similar post:
    http://discussions.apple.com/thread.jspa?messageID=690609&#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 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.

  • 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: KrayzBlu

    Could 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.

  • Server freezes at login screen

    We had to reinstall and rebuild our Snow Leopard XServes from scratch over this past spring due to open directory problems. At this point, both servers are running okay, but one of them will not make it past the login screen unless it's in Safe Boot mode. We've run a pate of diagnostics on this server but they all give it a clean bill of health and, since it was recently rebuilt, I con't think of any third party extensions that might be tripping it up in such a way. I'm hesitant to do a lot of heavy user creation and configuration until we can get it to boot normally. What might be causing this?
    Chris

    I rebooted the server normally to catch the hang in the server logs and found this section, spanning from the appearance of the login window, to the spinning beachball and subsequent recognition of a reboot into Safe Mode (boldface added):
    Aug 26 16:30:29 kirk /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[76]: Login Window Application Started
    Aug 26 16:30:29 kirk blued[92]: Apple Bluetooth daemon started
    Aug 26 16:30:29 kirk com.apple.usbmuxd[63]: usbmuxd-268.5 on Apr  5 2012 at 15:33:48, running 64 bit
    Aug 26 16:30:29 kirk fseventsd[83]: log dir: /.fseventsd getting new uuid: EEB152ED-7952-4B67-847C-AE2869BAE364
    Aug 26 16:30:30 kirk com.apple.ppp.l2tp[72]: 2012-08-26 16:30:30 MDT          Listening for connections...
    Aug 26 16:30:30 kirk vpnd[72]: Listening for connections...
    Aug 26 16:30:30 kirk servermgrd[68]: -[AccountsRequestHandler(AccountsOpenDirectoryHelpers) openLocalLDAPNodeIfNeeded]: dsLocalLDAP = (null), error = Error Domain=com.apple.OpenDirectory Code=2000 UserInfo=0x10820fd10 "Unable to open Directory node with name /LDAPv3/127.0.0.1."
    Aug 26 16:30:31 kirk loginwindow[76]: Login Window Started Security Agent
    Aug 26 16:30:31 kirk WindowServer[133]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    Aug 26 16:30:31 kirk com.apple.WindowServer[133]: Sun Aug 26 16:30:31 kirk.da.org WindowServer[133] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    Aug 26 16:30:31 kirk servermgrd[68]: initializing servermgr_teams
    Aug 26 16:30:31 kirk servermgrd[68]: -[AccountsRequestHandler(AccountsOpenDirectoryHelpers) openLocalLDAPNodeIfNeeded]: dsLocalLDAP = (null), error = Error Domain=com.apple.OpenDirectory Code=2000 UserInfo=0x106cada60 "Unable to open Directory node with name /LDAPv3/127.0.0.1."
    Aug 26 16:30:31 kirk servermgrd[68]: -[AccountsRequestHandler(AccountsOpenDirectoryHelpers) openLocalLDAPNodeIfNeeded]: dsLocalLDAP = (null), error = Error Domain=com.apple.OpenDirectory Code=2000 UserInfo=0x108307a30 "Unable to open Directory node with name /LDAPv3/127.0.0.1."
    Aug 26 16:30:32 kirk servermgrd[68]: servermgr_ipfilter:ipfw config:Notice:Flushed IPv4 rules
    Aug 26 16:30:32 kirk servermgrd[68]: servermgr_ipfilter:ipfw config:Notice:Flushed IPv6 rules
    Aug 26 16:30:33 kirk configd[31]: network configuration changed.
    Aug 26 16:30:34 kirk com.apple.launchd[1] (com.apple.CoreRAID): Throttling respawn: Will start in 4 seconds
    Aug 26 16:30:36 kirk XProtectUpdater[59]: Ignoring new signature plist: Not an increase in version
    Aug 26 16:30:36 kirk com.apple.launchd[1] (com.apple.xprotectupdater[59]): Exited with exit code: 252
    Aug 26 16:30:37 kirk servermgrd[68]: servermgr_accounts: noteDirectorySearchPolicyChanged (reopening nodes)
    Aug 26 16:30:38 kirk servermgrd[68]: servermgr_mail: Network change request does not identify the old address.  No action taken.
    Aug 26 16:32:28 localhost com.apple.kextd[26]: Safe boot mode detected; invalidating system extensions caches.
    Aug 26 16:32:02 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***
    I'm not sure if this LDAP error is what's causing my problems, but its recurrence is suspicious to me. Following the advice I recieved from a different issue, pertaining to the OS continually trying to respawn failed launch agents and daemons (http://reviews.cnet.com/8301-13727_7-20068791-263.html), I'm downloading the 10.6.8 server Combo Update and will attempt to patch whatever issues can be patched with this. Once applied I'll check the logs again if the problem persists. Does it sound like I'm looking in the right place?
    Chris

  • Screen freezes at login screen

    My mac froze and so I rebooted it manually with the power button.
    It runs ok until the login screen pops up. The beach ball never stops spinning . I also notice that there were weird lines in the background.
    I repaired the disk under safe mode but it doesn't help ...
    I did get messages saying that my start up disk is almost full before but not sure if it's related...
    Does anyone know what the problem might be?
    Many thanks....

    Try booting from the Snow Leopard DVD or disk 1 that came with the computer and run Disk Utility/Repair Disk and Repair permissions.
    Do you have a backup?

  • 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

  • Keyboard and Mouse Freeze On Login Screen

    Hey there,
    after just turning on my macbook pro 10.5.6 i am not able to use the keyboard nor the mouse to login, they are like froze, however the system is not. the writing cursor blinks in the password field, and the only button that works is the power button which i can press but cant use the keyboard to navigate, so i have to force shutdown. i can use keyboard to get into safe mode, where the same issue is found. and when i boot into single user mode, i am not able to use the keyboard. i also have tried attaching external keyboard and mouse, also no luck. However when i boot from the mac recovery discs, i am able to use both keyboard and mouse. Please if anyone can help me, i dont want to lose my information due to a restore. Thank You So Much Merry Christmas And Happy New Year!

    lol sorry about that.
    ok here is what i tried:
    1) using the recovery disks to repair disk and permissions.
    2) remove battery, press power button for 5 seconds and returning battery (weird, i read it on google)
    3) long press power button
    4) resetting the pram
    5) tried attaching external keyboard and mouse
    6) tried to enter single user mode however keyboard does not work in it to try some commands, also tried external keyboard, same result

  • 13" Macbook Pro Freezes at Login Screen

    Hi there,
    I've had my Macbook Pro for about a month and a half. This is my first time using a Mac, so honestly I am fairly clueless as to troubleshooting problems on my own. For the past few weeks, after the macbook has been on or sleeping for several hours, when I open it to log in, the screen is frozen. My mouse won't move and I am unable to type my password into the bar, however, the text cursor still flashes in the log in bar. Sometimes I am able to wait for about five minutes and it becomes unstuck all on it's own, but the past couple of times it has taken so long that I have had to just reboot the computer. I don't leave the macbook on for extended periods of time, and I can't think of anything I have done in correlation to this problem. Any help is appreciated, thanks!

    A new MBP comes with 90 days of free telephone support.  It is in your interest to take advantage of this option.
    Ciao

  • I keep getting black outs on the screen, typing is extremly slow to show up and firefox is moving very slow

    moving extreamly slow screen blacking out never used to have this problem. when I click on something it blacks out like if I click file the drop box is black

    Try to disable hardware acceleration in Firefox.
    *Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
    *https://hacks.mozilla.org/2010/09/hardware-acceleration/
    You can check for problems caused by recent Flash updates and try these:
    *disable a possible RealPlayer Browser Record Plugin extension for Firefox and update the RealPlayer if installed
    *disable protected mode in Flash 11.3 and later
    *disable hardware acceleration in the Flash plugin
    *http://kb.mozillazine.org/Flash#Troubleshooting

  • My macbook pro won't start up at all, it shows a grey screen, before this it was extremely slow. What is the problem?

    My Mac won't start up at all now, it happened again 3 weeks ago and I reinstalled OS and lost everything on my computer
    Now it happened again after it was extremely slow.. what is the problem?

    and how can I fix it without losing everything again?

Maybe you are looking for