A Continually Restarting PC

The continuous reboot problem can have a variety of causes, including faulty or unseated memory modules; out-of-date, corrupt, or missing drivers; software conflicts; overheating components; virus or malware; bad software; or bad hardware.

Hardware

Your computer may immediately fail to boot if one of your memory modules is unseated. The memory modules are long, narrow sticks that attach to the motherboard located near the processor and have clips at either end. If one or both of the clips is not closed or laying flat against the edges of the module, press down on the edge of the nearest to the clip. You may have to remove the memory module and reseat it. Restart the computer. Your computer may also immediately reboot if another piece of hardware fails, has a loose connection, or becomes disconnected. Check that power plugs from your power supply are connected to the appropriate components and that those connections are secure. Listen for your hard drive to start spinning. If it is silent, then it may be faulty or disconnected from the motherboard. Also, be sure the fans on your motherboard or graphics card start spinning. If any component seems unresponsive, replace it.

BIOS

If the settings in the BIOS have changed or become unstable, you may need to reset the settings to get your system to boot again. Restart your computer and access the BIOS setup utility. When you have access to the BIOS setup utility, you should see options to Load Defaults, Load Optimized Defaults, Load Fail-Safe Defaults, or something similar. First, try loading the Optimized Defaults. If your computer still fails, re-enter the BIOS and load the Fail-Safe Defaults. If you don’t have a choice, simply load the default settings as described in your computer or motherboard manual. Confirm your choice and allow the system to reboot. You may have to select the Save And Exit option to restart your system. 

Sometimes, your computer won’t even let you access the BIOS. In these instances, you may have to reset the BIOS using a more hands-on approach. The CMOS (complementary metal-oxide semiconductor) memory retains your computer’s BIOS settings but can be reset by moving a jumper on a three-pin header on the motherboard and then moving it back to its original position after a short wait. You’ll have to consult your computer or motherboard manual for specific instructions on how to perform this operation. Restart the computer.

 Reseat your memory modules one side at a time.

Restarting sans error message

If your system is infected with a virus or malware or experiencing system-crippling errors, you may never see error messages that can provide clues as to why your computer continuously reboots. Windows is set to reboot when it encounters a critical error. Disabling this can let you view error messages and on-screen prompts. 

 If you can boot into Safe Mode, disable unnecessary

startup programs that may be breaking Windows’ bootup

To change the setting in WinXP, boot into Safe Mode and access the Control Panel. If you’re using Win2000/XP with the Control Panel displayed in Classic View, simply double-click the System icon. If you’re a WinXP user viewing the Control Panel in Category View, click Performance And Maintenance and click System from the bottom of the dialog box. Click the Advanced tab and then click the Settings button from the Startup And Recovery section of the System Properties dialog box. Next, deselect the checkbox in front of Automatically Restart in the System Failure portion of the dialog box. Click OK and click OK again. Close the Control Panel and restart the computer. Now, when your system encounters an error, it will remain on-screen.

Whatever the circumstances surrounding a particular boot failure, the important thing is to address the issue immediately. 

Follow the steps we’ve described here, refer to the product documentation that came with your computer, and contact the computer manufacturer’s support resources for step-by-step guidance in resolving the problem. And take heart: You will get your PC up and running again.

Error Messages After Windows Starts

When Windows launches but won’t go any further without locking up or spewing forth error messages, check out the following options.

Windows utilities

Repeatedly press F8 (check your PC’s documentation for another option if this key doesn’t work) during startup to launch the Windows Advanced Options menu. Select Enable Boot Logging. When Windows starts, go to C:\WINDOWS, open Ntbtlog.txt, and browse for error messages. Work from Safe Mode to repair any errors you find.

Safe Mode

Select Safe Mode from the Windows Advanced Options menu. Safe Mode loads Windows with a minimal set of drives and processes for more effective troubleshooting. Perform some basic system maintenance, such as an antivirus scan and Chkdsk. Reboot your computer. If this fails to solve the problem, go back to Safe Mode and use Add/Remove Programs to uninstall anything you recently added to your system. Also try a System Restore, which will roll the OS (operating system) back to its state at an earlier date. Go to Start, All Programs, and Accessories. Select System Restore from the System tools submenu and follow the prompts.

Last Known Good Configuration

If you can’t perform a System Restore from Safe Mode, select Last Known Good Configuration from the Advanced Options menu. Last Known Good Configuration rolls back your Registry and device drivers to the last setting under which your computer shut down successfully.

Windows CD

Use your Windows installation disc or system recovery CD. Insert the disc and boot up. You need to press any key in order to boot from the disc. If not, you’ll have to enter the BIOS and set your optical drive as the primary boot option. After setting the optical drive as the primary boot drive, restart your system and try booting into Windows. There’s a difference between a true Windows OS disc and the image restoration discs many manufacturers ship with PCs. If you only have the latter, the following tips may not work. Windows’ repair option attempts to re-create the Registry and restore settings without removing or altering user data. When a repair is available and works as planned, it’s a great way to get a troubled system running again without starting from scratch. Boot into your Windows installation disc or system recovery CD. When prompted to choose between setting up Windows, accessing the

Recovery Console, or quitting Setup, press ENTER to enter Windows Setup. Press F8 to accept Microsoft’s license agreements and then press R to Repair the selected

Windows installation when prompted.

Recovery console

If you have any way to back up your data, do so. Boot from your Windows installation CD (a manufacturer’s restoration CD won’t work). Press R from the Welcome screen. Select your Windows installation if prompted and enter your administrator password. At the command line, delete your existing Registry files by typing delete c:\windows\system32\config\system. Repeat four times, substituting software, sam, security, and default for system, each in turn. Now copy pristine versions of those files by entering copy c:\windows\repair\system c:\windows\system 32\config\system. Repeat four times replacing system in both portions of the command with the words software, sam, security, and default. Type exit, press ENTER, and reboot.

A Beeping Computer

Should something go wrong during the boot process that prevents the computer from even sending data to the monitor or starting the computer, you need some way to identify the problem. When something goes wrong that causes the BIOS to be unable to start the computer properly, it uses specific patterns of beeps to give you clues to what the underlying problem is.

New hardware. It’s easy to accidentally bump something while working inside a computer. Retrace your steps and ensure everything is firmly in place. Reboot your computer. If the beeping continues, remove the new hardware and see if the beeping goes away.

Beep codes. There aren’t any standard beep patterns. To make sense of the beeps, you first need to identify your BIOS. The documentation for your motherboard likely contains this information. With this data in hand, search online for the meanings behind the beeps. Many sites offer such information.

Defective components. If your problem persists, it’s time to look at replacing the troublesome component. If your beep codes indicate that the RAM is failing, you might need to first figure out which module in particular is the problem, because most computers have more than one memory module installed. Depending on how old the computer is, you should be able to take out the memory modules one at a time and reboot the computer to see if the problem goes away; doing so will identify the problematic stick of RAM. If your video card is the problem, swap it out with a new one and see if the problem continues. Make sure that the video card you choose to troubleshoot or replace yours with is compatible with your motherboard and your operating system— otherwise, you will only create new problems.

For troubleshooting purposes, it is helpful to have another computer you can borrow parts from. It is best to work through the troubleshooting and be fairly confident of your diagnosis before you run down to the local computer retailer and start buying replacements. If the new parts don’t fix the problem, you may be stuck with parts you can’t return.

Error Messages Prior To Windows

Dealing with a PC that seems to be starting up but stops and coughs up an error message before it can load Windows is one of the more frustrating situations a computer user can experience. Fortunately, these messages do have a rhyme and reason. Often (but not always), they indicate a minor problem.

Easy fixes. If an error message offers Last Known Good Configuration or Safe Mode, the error has something to do with Windows’ startup. Selecting the former option can solve a world of unknown ills. The latter is a good choice if you’ve recently added new hardware. Make sure there isn’t any removable media, including floppy diskettes, CDs, and thumb drives, in any drive. If you see an error message regarding keyboards, it’s most likely the cable has come loose. Barring that, make sure none of the keys are stuck and that all of the pins in the connectors are straight. If it’s still malfunctioning, try a new keyboard—most models are quite inexpensive.

Memory and parity errors. These error messages indicate problems with your PC’s memory modules. Remove memory modules and carefully reseat them in another slot. If the computer restarts properly, the slot is likely to blame; if it doesn’t, it’s likely the memory itself is the problem.

Unexpected Interrupt In Protected

Mode. This is indicative of an incompatible change to your BIOS (Basic Input/Output System). Enter your BIOS setup menu and look for an option to reset the BIOS to its defaults.

NTLDR missing. NTLDR (think NT Loader) is the first file that executes during the boot process; it can get moved, accidentally deleted, or corrupted. Restore NTLDR from the Windows XP Setup CD via the Recovery Console. At the command prompt, type cd.. and press ENTER. Enter the letter of your CD-ROM drive (probably D:, unless you have multiple drives) and press ENTER.

Type cd i386 and press ENTER. Type

copy ntldr c: and press ENTER. Type

copy ntdetect.com c: and press ENTER. (Ntdetect.com is another boot file that, when missing, can generate the NTLDR error.)

After the copy process completes,

type Exit and press ENTER. Your computer will restart.

What to Do If Your Computer Won’t Start

  

What to Do

When we press the power button on a computer, we expect that the operating system will appear on-screen. And when the expected does not happen, we . . . well, some of us freeze, some of us panic, and some of us gather our wits and prepare to fix the problem. The first step in restoring an expectation is to figure out specifically what went wrong. It’s not enough to say the lights won’t work or the car won’t start or the computer is on the blink. We have to determine whether a light bulb has burned out or a fuse is blown, whether we’re out of gas or the battery is dead, whether a cord is unplugged or the hard drive has crashed. Fortunately, making this kind of determination is rather simple, even when it involves a PC.

Finding the specific cause of a failed boot involves some detective work. Take note of everything that happens during the failed boot from the moment you press the power button to the moment the boot routine grinds to a sudden halt. Write these details, including the full text of any error messages you see, on

a piece of paper so that you can refer to them later.

No Power at All

As grave as this may seem at first blush, a computer that refuses to start isn’t usually all that serious. Oftentimes, something outside the computer itself is to blame for a powerless computer.

Power cord. A loose power cord is usually the problem that prevents your computer from starting.

Check each end of the cord to make sure it’s firmly in place. Also be sure to check the cables that run to your monitor.

 

Some power supplies have switches that let you

cut power to your system. Make sure you haven’t

turned off your power supply.

 Power supply switch. See if your computer’s power supply has an on/off switch that lets you kill

power to the PC without removing the cable. This button, located on the back of your computer, can get accidentally bumped.

Surge protectors, outlets, and fuses. Make sure the surge protector is firmly plugged into the wall outlet and that the power button on the surge protector is in the on position. If that checks out, see if the devices plugged into other outlets on the power strip are functioning. If not, the surge protector might be to blame.

Another likely culprit is a faulty wall outlet. Plug your computer directly into the outlet, sans surge protector. Ensure that the GFCI (ground fault circuit interrupter) hasn’t been tripped. If your PC still won’t turn on, plug something else, such as a lamp, into the socket to see if it works. Finally, check your fuse box or circuit breaker to make sure there isn’t a blown fuse or tripped circuit.

There are also a number of factors inside the computer that could prevent it from starting.

Motherboards and power supplies.

Most motherboards have a tiny light on them that lights up when the power supply is connected, even if the PC is off. If this LED (light-emitting diode) is lit, your PC is getting power, and your problem lies elsewhere. Power supplies can sometimes go bad, and if you’ve followed our troubleshooting steps to this point, you may have a dead PSU (power supply unit). To figure out whether this is the case, use a power supply tester. Follow the manufacturer’s instructions to check the well-being of your PSU.

Power button cables. If you’ve recently performed any repairs to your system, it’s quite possible that you accidentally pulled the power button cable free from the motherboard. If you spot an unplugged cable, check your motherboard for labels that indicate the prongs that support the power switch. In the event there are no such labels, check your motherboard’s users manual

How to Deal with Error Messages

 

When you were kid, you imagined that the future held flying cars and moon bases. Technology and humanity would be in perfect sync. Our machines would anticipate our needs, leaving us to pursue only the most relevant, important work. Well, it hasn’t happened yet; we’re still very much slaves to our machines instead of the other way around. It sometimes seems we can’t go an hour without intercepting some bad news from our computers: missing drivers, no paper in the printer, an exception at memory address 32xxff00. . . . Can’t we just get our work done? Don’t go back to pen and paper just yet. I’ve got some tips to help you deal with the different kinds of errors you run into while working with your PC.

An Error For Every Season

Error messages are communications from the PC to you. To create one, a programmer must anticipate an action you might take with which the system will disagree or by which the system will become confused.

Depending on how well the software is designed, these messages may either be informative or—so it sometimes seems—deliberately obtuse. There are hardware errors, software errors, and user errors.

Trying to answer these messages that associate the errors, one must have answers in a form like:

1. What is the problem?

2. Why is it a problem?

3. What can I do to solve the problem?

For a good example, consider a common type of user error: those related to printing. A good error message would inform you that your printer is out of paper that you won’t be able to print unless you load more paper into the tray, and that you should click

Print after you have loaded it. If you’re a user who often feels a victim of your computer, you can rest assured that if you see an error message that doesn’t meet these criteria, the programmer is almost certainly the one at fault, not you.

The Blue Screen of Death

 

Most hated error message, the Blue Screen Of Death 

providesinformation that can help developers 

track the cause of an error.

The most infamous error message is the Blue Screen Of Death. It’s so well-known that it has crept into the vernacular: “Aw, man! I was almost finished with my term paper when I got bluescreened!” The phenomenon is also known by its acronym, BSOD.

The conditions that cause a blue screen have changed since the days of Windows 95/98, as has what it means. In either case, chances are pretty

good that, if you get bluescreened, any unsaved work will be lost, as either Windows (in NT/2000/XP) or your application (in 95/98) has been shut down. The BSOD is perhaps the most despised error not only because it has wiped away countless hours of work over the years, but because of the obtuse way in which it does so. The messages delivered in the typical blue screen are meant for developers more than end users. For example, a blue screen delivered by Windows may deliver a message such as the following:“0x0000001E, KMODE_EXCEPTION_NOT_HANDLED.” And if you don’t find that sufficiently informative, you’ll see four variables in parentheses to help developers figure out what’s happening. Again, none of this will mean much to most of us, but a support rep or developer can often learn a great deal from such cryptic messages. Fortunately, blue screens are rare in recent versions of Windows and may disappear after a reboot. But if the problem recurs, you could have a real problem. Here are some troubleshooting steps to follow if you encounter a BSOD: While your system is booting, press F8 and select Safe Boot Mode, which loads a subset of Windows with minimal drivers. If things run smoothly in Safe Mode, you likely have a software problem with a recently installed application.

Try to decipher the error message to see if you can trace it to a specific program. If all else fails, uninstall your most recently-installed application. If you still see blue screen errors in Safe Mode, restart again and use F8 to get to the advanced options. This time, choose Restore Last Known Good Configuration, which is a snapshot of your system as it existed before you last installed any drivers or other software. You will lose any system changes you’ve made since that point, but your documents will normally remain untouched by this process. If you’re still having problems, you are likely suffering from a hardware problem or a corruption of vital system files. Again, any hints that you can glean from the error message could help you (or a tech support rep) trace the source of the problem. Remove any recently installed hardware and try booting again. In the worst case, it’s not uncommon to have to resort to reinstalling device drivers or even the whole operating system. Ultimately, the best cure for the BSOD is prevention: Save often, create frequent backups, and burn a little anger to curry favor with variable PC spirits.

How to Fix Your Own Computer

  PCs are wonderful tools that occasionally refuse to work the way they should. When something does go wrong, you can avoid frustrating and costly by learning to fix your own PC. Use the basic troubleshooting techniques and step-by step instructions in this website to solve hundreds of common hardware and software problems.

WHAT DO I DO?

When my PC won’t start

Trace the source of the problem

As the days goes by, PCs continue to increase in complication and our reliance with time.

People across the globe turn their PCs on each day to use them for research, leisure, entertainment learning, etc. Since we rely on the PCs to do our day to day activities, so there is equally needs for maintenance to avoid break down, cost, frustration especially when the PC just doesn’t work, and we don’t know why. The process of restoring the computer back to standard state is called troubleshooting, this process diagnosis the computer to get it back on the right truck

Although it’s tempting to start troubleshooting your computer as soon as it displays symptoms, you’ll save yourself a potential headache if you back up your files or document on a removable media like, pen drive, etc. so u can do away with the fear of losing your data.

It’s not always easy to determine whether your hardware or software is to blame, but it’s a good place to start troubleshooting: If you’re fairly confident that the problem is one or the other, you’ve eliminated several troubleshooting steps.

Look for common hardware symptoms.

Hardware problems, such as damaged components or loose cables, generally cause obvious, dramatic problems. For example, if your computer won’t power on at all, you’re looking at a hardware problem, rather than software. You should also suspect a hardware problem if your computer powers on, but no images appear on your monitor. If you can’t access any software (even the BIOS [Basic Input/Output System]), you’re not looking at a software issue. Of course, not all hardware issues display such obvious symptoms, and some hardware problems exhibit symptoms similar to those caused by software problems. For example, if your PC runs slowly, it may have too many unnecessary programs running at once or a virus or adware may be crippling your system; obviously, these are software problems. On the other hand, these same symptoms can be caused by an overheated processor, something that’s just as obviously a hardware issue.

Look for common software symptoms

A conflict between two programs, for example, may prevent you from accessing certain applications, but may not crash Windows itself. In many cases, the software that’s experiencing trouble will display an error message. Unfortunately, many error messages don’t offer much immediate help: The message will likely display a cryptic warning or a bunch of numbers and letters that don’t mean anything to anyone other than a programmer. Unless you receive an error message saying that hardware is to blame, the error message is a good indicator that you’re facing a software problem.

Find The Source Of The Problem

Once you know (or think you know) whether you’re dealing with a hardware or software problem, you can really dig into the next question: Which hardware component or program is the source of the trouble? If you can answer this question, you won’t have any trouble finding an article in this issue that addresses your problem. Here are some tips for narrowing the troubleshooting field.

Hardware problems. 

Once you suspect a hardware problem, list the components (internal or external) that might be the cause of the problem and then check each component, one at a time. In some cases, this may mean checking external and internal hardware. For example, if your print documents don’t reach the printer or you see error messages that say your printer isn’t connected to the computer, you’ll want to check the USB cable that runs from your computer to the printer to make sure neither of the connections is loose. You’ll also want to be sure that your computer’s USB port is functioning. (You can test this by plugging another USB device, such as a USB flash drive, mouse, or external hard drive into that port.).

In some cases, you may suspect that an internal component is damaged, but not be in a position to confirm the defect. If you think that your computer’s lost network connection is due to a damaged or incorrectly configured Ethernet NIC (Network Interface Card), you probably don’t have an extra Ethernet card that you can swap out. This is where the Device Manager, a built-in Windows tool, can help you identify problems without opening your PC or bumming spare parts from your friends.

To open the Device Manager, right-click the My Computer icon on the Desktop, and then click Properties. When the System Properties window appears, select the Hardware tab and then click the Device Manager Button. The Device Manager displays a list of your PC’s components by category, such as Disk Drives (hard drives),

The Device Manager lets you quickly determine whether your PC’s components are working properly. A red X indicates a problem.

Processors, DVD/CD-ROM Drive, and Display Adapters. By default, the list shows only the component categories, rather than the components themselves. If you want to see the names of your specific CD-RW and DVD-RW drives, for example, you’ll need to click the plus (+) sign next to DVD/CD-ROM Drives. The list will then expand to reveal all of the components in that category

Things to Check First

Although a list of things to check won’t catch every PC problem you encounter, you’ll be surprised at how often the simple steps below can lead to troubleshooting success. Whether you’re kicking off a troubleshooting session or at your wits’ end after hours of fruitless research, here are some good tips to try. Is the PC’s power supply switch turned on? Some PCs have a power switch at

the back. Make sure it hasn’t been switched off.

Are all cables connected? Loose connections regularly cause headaches. Remove and reconnect each plug firmly, even if you’re sure it’s connected.

Are all peripherals turned on? Make sure a powered-off print server isn’t preventing your printer from working.

Does the Device Manager display any problems? Check this tool for red Xs,

Which indicate a malfunctioning or disabled device?

Is there a new driver? Updated drivers often fix hardware problems. If you can’t find new drivers (check the manufacturer’s Web site), try reinstalling your existing driver.

Have you installed software updates? Software publishers sometimes release

patches via their Web sites. Also, check to see if your software recently installed

updates automatically. In rare cases, a software update may introduce problems.

Software problems.

If you’re fairly certain you’re facing a software problem, but you haven’t been able to identify the offending program, your best bet may be to use Windows XP’s System Restore. This feature is especially useful if you’ve installed multiple programs recently. System Restore reverts your computer to the condition it was in few days or even a few weeks ago, without destroying any of the documents, emails, music, or video files you’ve created. Thanks to System Restore, any programs you installed after the Restore Point (the date in the past to which you restore Windows) won’t appear on your PC. Once you complete the restore, you can reinstall the applications

one at a time and check your PC for problems after each installation.

System Restore is enabled by default in Windows XP, which means

that System Restore has already created Restore Points automatically, even if you’ve never used the System Restore feature before. To access System Restore, click Start, All Programs, Accessories, System Tools, and System Restore. Once you click the Restore My Computer to an Earlier Time radio button and click Next, System Restore will display a small calendar with several of the dates in bold. All bold dates have at least one Restore Point. (Note that Windows refers to automatically created Restore Points as System Checkpoints; you can create your own labels for Restore Points that you create yourself.) Select the Restore Point and then follow System Restore’s instructions to restore your system to this earlier date. Finally, make sure your PC is operating without trouble. If it is, you’ve narrowed the problem to one of the programs that System Restore just uninstalled (or to another program on your PC that conflicted with one of these programs). Now you’re ready to hunt for the problem program.

Troubleshooting

As we mentioned earlier, troubleshooting is largely a matter of eliminating parts or programs that are working until you find the part that causes the problem. Consider this scenario: You pressed your PC’s power button this morning only to find that it didn’t start. The PC worked just fine last night, and you haven’t recently performed any maintenance on the system’s interior. If you start by making sure your PC truly isn’t powered on, you’ll save yourself several troubleshooting steps. Check the monitor’s light: Is the monitor on? If not, you’ll want to check its power cords. Once the monitor is on, take a second look at your PC. Do any lights appear when you try to power on the system? If you see lights, or if you can see or hear running fans at the back of the computer, the system doesn’t have a power problem. Instead, the PC may be having trouble sending an image to your monitor, which could indicate a problem with your motherboard, video card, or memory. If the PC doesn’t power on at all, check the power cord and the surge protector. Many surge protectors have switches that let you kill power to any of the devices that plug into them: Check to make sure your pet didn’t accidentally trip that switch. Next, check the wall outlet by plugging a different device into the socket your PC’s power cord occupied.,