My computer locks up and won't boot. What do I do?

Home » Windows

Summary: There are a few things to take a look at with your system if your computer locks up and won't boot.

Your computer locks up, crashes, stalls or otherwise fails to completely boot up into Windows. That's particularly painful, since most all of our diagnostic tools require that Windows be running. Diagnosing the problem with a computer that won't boot can be difficult.

In this article we'll look at some of the resources that you do have available, and try to gather a little information about the type of problem you might be experiencing.

I'll start at a successfully booting Windows, and work backwards to a completely dead machine.

•

• Loading User Settings

One of the last steps that Windows takes before being ready for use is to load the personal settings for the user logging in. That includes settings within the Windows Registry, saved network connections, and the security settings for the account. This step exercises a lot of different areas on the machine, so if it hangs, or is exceptionally slow here, it could be for many reasons. Things to check include disk space and fragmentation, physical errors on the disk holding the swap file, and network connectivity that might impact restoring those saved connections. In particular, in a Domain based environment, network connectivity can be a particular problem as the system tries to contact the domain controller. (Domains are common in business settings as opposed to a Workgroup, more common in small business and home).

• Blue Screens and Other Hangs

A "Blue Screen" is the name given to the blue screen of strange numbers and information that can sometimes come up if your machine crashes. Essentially any blue screen, hang, crash or lock-up that happens after the Windows logo is displayed falls into this category. If that happens repeatedly during boot, it could be anything from a bad device driver to spyware to a virus.

The best first step to take is to attempt to boot in what's called "Safe Mode". Safe mode disables a number of operating system components, possibly avoiding the component that might be causing the problem. Once in safe mode you can try running the system file checker, your anti-virus software, anti-spyware software, and possibly get Windows updates. The Microsoft Knowledgebase has an article on A description of the Safe Mode Boot options in Windows XP that details how to start Safe Mode, and its options.

If Safe Mode itself won't work, the next step back is something called the Recover Console. You can install it on your machine before problems happen, as described in this Knowledgebase article How to Install and Use the Recovery Console in Windows XP.

• Hangs before the Windows Logo

If you can't actually get anything to come up - by that I mean that you never even see the initial Windows logo, you can run the Recovery Console from your Windows XP Installation CD. This article: Windows XP Crashed? Here's Help gives a step-by-step overview of the process. This also applies if you didn't install the recovery console beforehand.

Regardless of how you got there, the recovery console will allow you to copy files, undo a recent installation, or fix the master boot record should that have become corrupt.

• Operating System? What Operating System?

One of the scarier messages is "Operating System Not Found". It implies that the operating system on your hard disk isn't there any more.

First, remove any floppy from the machine. It's a common error - when you reboot, the computer will try to boot from it, not find an operating system and halt.

Assuming that wasn't the problem, get out and boot from your Windows XP Installation CD. You can try the Recovery Console I just discussed - sometimes fixing the MBR (Master Boot Record) is all that's needed. Other times the recovery is more involved, in which case this article by Microsoft MVP Michael Stevens - How to Perform a Windows XP Repair Install can guide you.

• Hard Disk? What Hard Disk?

Things start to get a little scarier when your computer doesn't appear to even have a hard disk. When software like the Recovery Console doesn't even see that you have a hard disk in your machine, things get interesting.

The most common cause of this in a previously working machine is that the CMOS memory, which keeps your hardware and BIOS configuration settings, has lost its contents. That can happen due to anything from a power spike to errant software - but the most common cause on older machines is that the little battery that keeps the CMOS alive has worn out. The type and location will vary from machine to machine.

CMOS settings on some machines are what tell the computer what kind of hard disk you have. You'll probably want to review the settings in your BIOS to make sure they are correct. Typically most brand name computers include a print-out of their CMOS settings when they come new, or their technical support resources may be able to help. A misconfiguration can "look like" a hard disk to the BIOS, but in fact be wrong.

And, of course, there is the possibility of hardware failure of the drive itself. If that's what you suspect, it's probably time to touch base with the manufacturer or a local repair technician.

• BIOS & POST

If your computer doesn't even get so far as to try the hard disk, or perhaps not even print anything on the screen, you probably do have some type of hardware problem. For example, if the computer simply beeps a few times and then does nothing, then that's the POST telling you something is wrong. For what ever reason it might not be able to display an error message, so it simply beeps in a pattern to tell you what it's found. They vary based on the brand of your computer or BIOS, but POST beep codes can often give a technician a quick idea of exactly what might be wrong.

And finally, when you turn on the power, if your computer does nothing at all, obviously something is seriously wrong. In my experience, it's typically the power supply that has failed, however it's also possible that critical components on the motherboard have failed, or that a peripheral card has been inserted improperly or has failed in such a way as to prevent the rest of the system from working at all.

•

Today's computers, and the operating systems that run them, are incredibly complex animals. Each problem will have it's own unique cause. Hopefully this overview, and some of the resources listed below, will help you at least understand the nature of problems you may be having, and perhaps even help you resolve them yourself.

Related:

• What is the System File Checker, and how do I run it? The System File Checker is a little known utility that validates that Windows own files are undamaged. It's a simple to run command line program.

• I don't have an installation CD for Windows XP - what if I need one? At some point you'll need your Windows installation CD. If you don't have one, you could be out of luck. Be sure to get one and keep it safe.

• 
  

• bootdisk.com

• Boot-time POST beep codes

• Digital Webcast - Windows XP Crashed? Here's Help

• Michael Stevens - How to Perform a Windows XP Repair Install

• Microsoft - A description of the Safe Mode Boot options in Windows XP

• Microsoft - How to Install and Use the Recovery Console in Windows XP

• Michael Stevens - How to Perform a Windows XP Repair Install

• Webopedia definitions: BIOS, boot, CMOS, MBR, motherboard, POST

Article C2073 - June 19, 2004