Hard Drive Problems (Optical Drives)

Hard Drive Problems (Optical Drives)

Problem: Your drive reads data very slowly.
Cause: This could occur if the drive is old, and the laser pick up assembly weakens. It might also happen when the pickup lensgathers dust.
Solution: Get a lens cleaning kit and clean the lens. If that doesn’t work, it’s time to get a new drive!

Problem: Your CD-RW drive ejects and reloads the disc during operation
Cause: This isn’t a problem; it’s a mechanism to clear the drive’s buffer. All CD-RW drives are provided with some buffer memory to smooth out the writing process. While some drives have a way to clear it out, some aren’t provided with any, in which case the drive might pop out the disc to clear the buffer memory.
Solution: Before buying a drive, make sure it has a way to clear out buffer memory. To find out what drives have this feature and which ones don’t, ask someone who already has the drive model you’re contemplating buying.

Problem: Your CD-ROM drive immediately ejects an empty disc.
Cause: This can be either a software or a hardware problem.
Solution: Certain hardware faults can cause the drive to immediately reject certain CDs. To make sure that it’s the drive and not the OS that is rejecting the CD, pull out the data cable from the drive and then insert a CD. If it is rejected, then the drive has a hardware fault. If the problem is with the OS, try disabling features such as auto-insertion notification.If the machine is powered on for some time and the CD-R was in use, then the resultant heat can at times lead to such rejection problems. The drive might needs realignment, and should be given to a service centre.

Problem: A multi-session disc has only the last-burnt data; you can’t see data from older sessions
Cause: This happens when you forget to link the data from previous sessions to the data in the latest sessions. Most CD-ROMs can’t view the data from older sessions unless they use an application that allows a selection of sessions to view.
Solution: This used to be a problem with older burning applications that simply over looked this problem. Newer applications default to saving the older sessions,or prompt for user input in this regard. If you are stuck with older software, update to a newer one that supports the session saving feature. Else in the older software, make sure you manually specify that the disc is a multi-session disc and that you want the older session to be saved.Also, applications such as IsoBuster and CD-R diagnostics allow accessing of older data sessions. However, some older CD-ROMs might not be able to work with this software, especially for retrieving older data.

Problem: A disc fails repeatedly.
Cause: The problem probably lies with the media and not the writer.
Solution: Media compatibility is critical for proper CD writing.Cheap blank CDs are the culprit—their reliability is questionable.Always use reliable CDs, even if they are more expensive. Try out different media and see which one offers better compatibility with your drive.

Problem: You’re unable to copy game CDs
Cause: It’s illegal to try to copy game CDs! Today, most game CDs come with some form of copy protection to avoid piracy. The game publisher places blank or unreadable sectors on the disc, which confuses the copying applications.
Solution: There’s no “solution” we can provide! We only suggest you use your game CD carefully so you won’t ever need a copy.

Problem: You get a buffer under run error.
Cause: Almost all CD/DVD recorders come with a small amount of buffer memory to smooth out the burning process. The buffer reads ahead and provides the data required for burning in a linear manner. A buffer under run error happens when the data source slows down for some reason. Since the CD is spinning and there is no data to be burnt, it causes the burning process to be aborted, resulting in a coaster.
Solution: Unless you have a really old drive, you shouldn’t see this error. In fact, almost all recorders today have hardware support to ensure buffer under runs don’t occur. Moreover, burning software also have support for this feature - make sure you activate it; it’s just a matter of checking a box. If you have a drive that does not support this feature, make sure you use your hard drive as the data source, since a CD to CD copy will definitely result in a coaster. Also,defragment your hard disk regularly to avoid a slow-down during the burning process.

Problem: Despite the write process completing, a CD turns upblank.
Cause: It’s not clear why this happens.
Solution: Try using different media. Go to the burning software’sWeb site and check whether any patches to fix the problem have been released. Sometimes, these patches will fix such an issue, if they don’t, try an alternative application.

Problem: A recorder won’t work with blank CD-RWs.
Cause: This is a common problem. CD-RWs are rated as Slow (1x to4x), High Speed (4x to 10x), Ultra Speed (12x to 24x), and Ultra Speed+ (for drives supporting even higher burning speeds).
Solution: Choose the correct CD-RW media depending on the burning speed supported by your drive. Also, if you’re trying to use an Ultra Speed + media, it might not get detected, whereas a lower speed media will get burnt at its maximum speed.

Problem: Video DVDs stutter.
Cause: This is a common problem with most DVD players. During video playback, most drives drop down to a lower speed to cut down on the excessive noise they make when spinning at high speeds. In technical terms, this lowering of the speed is called rip lock. In poor-quality DVD drives, rip lock is responsible for videos Cutter.
Solution: When choosing a DVD drive, make sure it won’t suffer from video stutter - ask people who have bought the same model you’re contemplating. Essentially, opt for drives from known manufacturers.

Problem: Some DVDs aren’t recognized in your DVD drive.
Cause: The problem lies with the media type. There are two main DVD formats - +R and -R. -R format is more commonly available and hence is usually supported by lot many older drives than +R format.If you have an older DVD drive, then it is possible that it has been manufactured to recognize only one format.
Solution: Check the formats supported by your drive and use mediaof only that format.

Problem: Your DVD-Writer doesn’t play DVD-RAMs.
Cause: Not all DVD-Writers are equipped to handle DVD-RAM. Unlike DVD±RW, DVD-RAM uses phase-change dual technology peppered with magneto-optic features. The main advantage of DVD-RAM is its defect management and faster access speeds. However, as we’ve mentioned,this format incompatible with most drives.
Solution: Select a drive that features support for DVD-RAM. Drives manufactured by LG, Hitachi, and Matsushita (Panasonic) have support for DVD-RAM.

Problem: You can’t burn DVDs faster than the rated speed as youused to do with your CD-Writer.
Cause: Over speeding is a feature supported only by a handful of drives, and only on selected media types. DVD drives from BenQ andPhilips officially support over speeding; however, you need to use good-quality media or media specially developed for over speeding.
Solution: Buy a DVD drive that officially supports the over speeding feature. Also, make sure you use officially certified over speeding media, for example, Taiyo Yuden. It might be possible to get such media, but it is not commonly available.

Problem: Some movie DVDs don’t play on your DVD drive
Cause: The movie is region locked, and will only play on a DVD drive that has the same region code. To control the release of their movies, the motion picture group divided the world into seven regions or zones. Each zone has its own region or zone number.When a specific movie is released in a particular zone, it is encoded with the zone number. DVD players, too, have a zone number.Hence, a movie released in America plays on all DVD players manufactured in the US, but not on DVD players manufactured in India such as those from Onida, Mitashi, Sony, etc.
Solution: Many DVD players can be hacked using software to doaway with the region locking encryption. This voids the warranty,but it isn’t illegal to do so. On some drives, however, you need to modify the chip to make it all-region playable.

Troubleshooting the Monitor

Troubleshooting the Monitor

Modern monitors are especially robust and in most cases, you would upgrade the PC before thinking of changing the monitor. Troubleshooting is relatively easier than the rest of the PC for the simple reason that it is an independent ‘box’ with no user-service­able parts.

Warning
Do not try to open the monitor yourself. There are high voltages inside, and it is best left to a monitor professional who knows what he is doing.

There’s no power to the monitor
Cause 1: There actually is no power being supplied to the monitor.
Solution 1: By far the most common mistake people make is to for­get to check the power cables! Sometimes, when monitors are moved around, the power connectors come off or become loose. Plug all cables in tight and check if the power returns. If it is con­nected to a UPS or stabiliser, check if there is power supply from that unit. Also check the power cable; try using another cable which you know works, to see if power is restored.

Cause 2: If the power cables are plugged in and there is still no power, the problem is more serious. It could mean that a fuse has blown, or there is a more serious problem with the CRT (Cathode Ray Tube).
Solution 2: If the fuse is accessible from the casing of the monitor, replace it and check. If the fuse blows again, or if it still doesn’t power up, you have a problem with the electrical circuitry inside the monitor. Your only option is to take it in for repairs.

The LED on the monitor glows but the screen is blank
Cause 1: A black screen is dis­played.
Solution 1: Another common mistake. Check the brightness and contrast settings. Some­times the settings are turned way down, giving you a blank screen. Also try the other display controls if changing the brightness and contrast don’t seem to work.

Cause 2: The monitor is incompatible with the PC or the CRT is dead.
Solution 2: If the monitor is being connected to the PC for the first time, it could be that you have a monitor that is incompati­ble with your PC. Check if the monitor works on another PC. If the monitor doesn’t work on that PC either, then it is most like­ly some sort of internal failure in the monitor and you will have to get it repaired, if possible. Otherwise, you’ll have to go in for a new monitor.

Cause 3: There might be a problem with the signal between the PC and the monitor.
Solution 3: In most modern monitors, if there is no signal from the video card, there should be a message on the screen saying some­thing like “No Signal.” Absence of any message, however, does not rule out the possibility of a problem with the cable between the monitor and PC. If the monitor works with another PC and the sig­nal cable is detachable (most monitors have the signal cable inte­grated with the monitor), use a different signal cable.If the signal cable is not detachable you might have to take it in for repairs. Check the other possible problems before you do so. If there is still no picture then this would point to some problem with the video card.

The monitor is producing a high-pitched whine
Cause: This is often noticed in cheaper monitors, and it will become more pronounced with age.
Solution: Try adjusting the brightness and contrast controls, this may reduce the noise somewhat. You can also try ignoring the noise and let it merge with the background, like the hum from your TV. If it is bothersome, take it to repair shop; there might be some components that can be changed to reduce the noise.

The screen is totally white or grey in colour
Cause: There is no signal from the video card.
Solution: Check the signal cable as explained above.

The display is too bright or dim; the contrast is too high or low
Cause: The brightness and contrast settings may not be set correctly. The CRT may be wearing out.
Solution: Check the brightness and contrast settings. As the CRT ages, the screen will start to dim. In some cases, your repair shop may be able to tweak the monitor to improve the brightness. Change the lighting in the room so that there is no direct light falling on the monitor. Turn off the monitor when not in use. In any case, this might well be an indication of age catching up with the monitor—time to go shopping!

The screen has a bluish, greenish or purplish tint
Cause: This is usually caused by a break in one of the three colour sig­nals between the video card and the monitor. The problem is espe­cially common in older monitors, and is caused by heat stresses that break the connections between the cable and the circuit board inside the monitor.
Solution: Check the signal cable for kinks, frays and other signs of wear and tear. If the cable is not integrated, have it replaced, else take the monitor to the repair shop and they should replace it for you at very little cost.

The screen twists with wavy lines and the picture bends
Cause: This is caused by electromagnetic interference (EMI) from some other appliance such as a fan, motor, or even other monitors, either very close to the monitor or on the same power circuit.
Solution: Move the other appliance out of range of the monitor or off the same power circuit. If the symptom continues, there could be an EMI problem with the monitor itself. Have it checked at the repair shop.

Images are blurred
Cause: This may be a problem with the display settings of the mon­itor, or with the signal cable
Solution: Adjust the display. There might be an option called ‘Focus’ or ‘Sharpness’. Adjust that setting. If that doesn’t work, check the cable and its connection to the PC.

There is some irregular discoloration along the edges of the screen
Cause: This is caused by the magnetisation of the metallic elements on the surface of the CRT. The magnetisation happens because of EMI or due to sudden knocks to the body.
Solution: Cycle through the display controls and select the Degauss option. Degaussing is the process of demag­netising the CRT.

The image disappears and reappears randomly
Cause: This most probably points to an electrical fault.
Solution: Check all the cable connections as well as the video card. The electrical fault may be internal to the monitor; get it checked at a repair shop.

MS-DOS-OPERATING SYSTEM

MS-DOS v6.22

IO.SYS - Interface between main operating system code and the hardware
MSDOS.SYS - Main operating system code
COMMAND.COM - Interface between main operating system code and the user

NB. If any of the core files are missing or corrupt the MS-DOSboot sequence will fail.

Boot Sequence

PC is switched ON
Signal is sent to the motherboard via the POWER GOOD wire (orange)
ROM BIOS performs POST (Power On Self-Test)
ROM BIOS references CMOS RAM (comparison)
ROM BIOS searches for the boot sector/MBR on the FD/HDD
The Boot Code searches for and loads IO.SYS
IO.SYS loads MSDOS.SYS
The Boot Code searches for and loads CONFIG.SYS
The Boot Code searches for and loads COMMAND.COM
The Boot Code searches for and loads AUTOEXEC.BAT

Internal Commands

These commands are less complex and are imbedded within COMMAND.COM

CD or CHDIR

Displays the name of or changes the current directory.

CHDIR [drive:][path]
CHDIR[..]
CD [drive:][path]
CD[..]

Type CD drive: to display the current directory in the specified drive.
Type CD without parameters to display the current drive and directory

MD or MKDIR

Creates a directory.

MKDIR [drive:]path
MD [drive:]path

RD or RMDIR

Removes (deletes) a directory.

RMDIR [drive:]path
RD [drive:]path

TYPE

Displays the contents of text files.

TYPE [drive:][path]filename

CLS

Clears the screen.

CLS

DATE

Displays or sets the date.

DATE [date]

Type DATE without parameters to display the current date setting and a prompt for a new one. Press ENTER to keep the same date.

TIME

Displays or sets the system time.

TIME [time]

Type TIME with no parameters to display the current time setting and a prompt for a new one. Press ENTER to keep the same time.

DIR

Displays a list of files and subdirectories in a directory.

DIR [drive:][path][filename] [/P] [/W] [/A[[:]attributes]]
[/O[[:]sortorder]] [/S] [/B] [/L] [/V] [/4]

[drive:][path][filename]
Specifies drive, directory, and/or files to list.
(Could be enhanced file specification or multiple filespecs.)
/P Pauses after each screenful of information.
/W Uses wide list format.
/A Displays files with specified attributes.
attributes D Directories R Read-only files
H Hidden files A Files ready for archiving
S System files - Prefix meaning not
/O List by files in sorted order.
sortorder N By name (alphabetic) S By size (smallest first)
E By extension (alphabetic) D By date & time (earliest first)
G Group directories first - Prefix to reverse order
A By Last Access Date (earliest first)
/S Displays files in specified directory and all subdirectories.
/B Uses bare format (no heading information or summary).
/L Uses lowercase.
/V Verbose mode.
/4 Displays year with 4 digits (ignored if /V also given).

Switches may be preset in the DIRCMD environment variable. Override preset switches by prefixing any switch with - (hyphen)--for example, /-W.

COPY

Copies one or more files to another location.

COPY [/A /B] source [/A /B] [+ source [/A /B] [+ ...]] [destination
[/A /B]] [/V] [/Y /-Y]

source Specifies the file or files to be copied.
/A Indicates an ASCII text file.
/B Indicates a binary file.
destination Specifies the directory and/or filename for the new file(s).
/V Verifies that new files are written correctly.
/Y Suppresses prompting to confirm you want to overwrite an
existing destination file.
/-Y Causes prompting to confirm you want to overwrite an
existing destination file.

The switch /Y may be preset in the COPYCMD environment variable.
This may be overridden with /-Y on the command line

To append files, specify a single file for destination, but multiple files
for source (using wildcards or file1+file2+file3 format).

DEL
Deletes one or more files.

DEL [drive:][path]filename [/P]
ERASE [drive:][path]filename [/P]

[drive:][path]filename Specifies the file(s) to delete. Specify multiple
files by using wildcards.
/P Prompts for confirmation before deleting each file.

REN or RENAME

Renames a file/directory or files/directories.

RENAME [drive:][path][directoryname1 filename1] [directoryname2 filename2]
REN [drive:][path][directoryname1 filename1] [directoryname2 filename2]

Note that you cannot specify a new drive or path for your destination.

PROMPT
Changes the Windows command prompt.

PROMPT [text]

text Specifies a new command prompt.

Prompt can be made up of normal characters and the following special codes:

$Q = (equal sign)
$$ $ (dollar sign)
$T Current time
$D Current date
$P Current drive and path
$V Windows version number
$N Current drive
$G > (greater-than sign)
$L < (less-than sign)
$B (pipe)
$H Backspace (erases previous character)
$E Escape code (ASCII code 27)
$_ Carriage return and linefeed

Type PROMPT without parameters to reset the prompt to the default setting.

VER

Displays the DOS version.

External Commands

These files are larger and are stored either as .COM or .EXE files, normally in the DOS directory.

Power Supply

Power Supplies

The computer needs electrical power to operate. It is plugged into a 110-volt socket, which uses Alternating Current (AC). Computers use 5- and 12-volt direct current (DC) electricity. Therefore, a device is required to convert the power from the wall socket to the power required by the computer. This is the function of a power supply. Power supply connectors are either the Molex type (square shape) or the Bundy type (rectangular shape).
Although power supplies are rated in different ways, the most common rating is in watts. A watt is a unit of measurement of an electrically powered device and is affected by the electricity that is passed through it. Because computer components are becoming increasingly more efficient with large-scale integration and low-power designs, a 200 or 250 watt power supply is typically large enough for most systems. Do not be surprised, however, to see a 300-or-more-watt power supply in some of the larger network servers with large hard drives and other peripherals.

Power supplies are most often found in a rear corner of the inside of the computer, and have several colored wires running out of them. These are called power connectors and are used to connect peripherals such as floppies, tape backups, or hard drives. The power supply will most likely have a fan attached. Although some newer designs do not, most still use the fan in order to maintain an internal temperature acceptable to the design of the circuitry. The fan moves warm air outside the computer and brings cool air in.

The power supply will have an AC line that will connect into the wall. It will also have connectors for external peripheral devices. Usually there are three or more disk drive connectors and two system board connectors. Hard drives and 5-1/4" floppy drives use the same connector; 31/2" drives use a smaller one. Older models of computers typically connected the monitor to the power supply. Newer models of monitors plug directly into the wall, because they require more power than the power supply connector can provide.

Getting a bit more technical, the AC current is converted to DC in the power supply. There are four voltages present in a power supply: +12 volts, -12 volts, +5 volts, and -5 volts. The +12 voltage is for the motor, and the +5 voltage is for the processor. These are the four levels of electricity the computer needs to operate. Different devices use different voltage levels. The power supply not only converts these, but also ensures that the flow of electricity into the computer is received evenly, without bursts or sags.

Because of the voltages used and because not all technicians are certified electricians, repairing power supplies is not recommended. Replacement is the safest option. However, the wiring for the connectors can be tested for proper voltage levels.
The following table shows specifications for the output wiring of the power supply.

Wire Voltage Proper Range Current Range (Amps)
Yellow +12 +8.5 - +12.6 0.0 - 2.00
Blue -12 -8.5 - -12.6 0.0 - 0.25
Red +5 +2.4 - +5.2 2.3 - 7.00
White -5 -4.5 - -5.4 0.0 - 0.30
The specifications may be tested with a multimeter, which has a dial so you can specify what you want tested. You can select DC Volts, AC Volts, or Amps. Later in the course, we will demonstrate the use of multimeters.

Selecting Power Supplies

When selecting power supplies to be used as on-hand spares, when building PCs from component subsystems, or when given the option on vendor-built systems, you need to give some thought to what you are selecting. While all power supplies use the same input voltages and provide the same DC output voltages, there are some differences, which may influence your decision.

Peak Power

This determines the amount of power available for short term, high current situations, as it occurs when you first turn on the system. Large hard disks can increase your peak power requirements.

Number and type of connectors

You will need a connector for each hard disk and floppy disk you install in your system. Both hard disks and 5-1/4" floppy disk drives use the same power connector.
Many 3-1/2" disk drives use a different type of connector. There are jumper plugs available that convert one type of connector to the other.

For today's PCs, the minimum rating for a power supply is 200 to 250 Watts.

Power Requirements

Listed below are the average power requirements that you can expect from many common devices. Several factors can affect these requirements. Always check vendor documentation for information on specific devices.

Device AC Current Requirements at 120 Volts Power Requirements
System Board &expansion cards 0.80 Amps 96.0 VA
Diskette drive and adapter 0.16 Amps 19.2 VA
Additional diskette drive 0.05 Amps 6.0 VA
Hard Disk* 0.13 Amps 15.6 VA
* Average value for 3 1/2" hard disk. Increase to 40 VA for a 5 1/4" hard disk. VA (Volt Amps) is a measure of power and is equal to WATTS.

Scanner Installation

Scanner Installation

You will want to consider the following before purchasing a scanner to attach to a PC.
The scanner will need to be attached to the PC via an expansion card. Some scanners offer a serial interface in addition to another interface; however, scanners generate large amounts of data, up to 7 MB or more. You will not want to send all of the data through a serial port because it takes too long. Faster interfaces, such as SCSI or Hewlett-Packard's General Purpose Interface Bus (GPIB), or one that is proprietary, will offer better scanner performance.

Does the machine to which you are planning to add the scanner have adequate expansion slots? Is an IRQ available? If you are adding a scanner to an 8-bit machine, IRQ 2 is a good starting point, because some network and video adapters use this IRQ. When adding a scanner to a 16-bit machine, try using the interrupts above IRQ 8.
In addition to finding an available IRQ, you will have to find an available I/O port. First, try using the address suggested by the manufacturer of the scanner. If you find you have a conflict in the I/O ports, you will have to find another address that works.

When installing a scanner, you may want to test it before reassembling the case of the PC. If you have problems and need access to the inside of the PC, the case will already be removed.
As always, exercise EXTREME care when working with a computer with the case removed. Make sure that you follow all safety guidelines discussed in Chapter Two.
After you install the expansion card and make the hardware settings, you will need to install the software to operate the scanner.

Before loading the scanner's software, make a backup copy of both the autoexec.bat and config.sys files so you will have a record of them before the scanner software is installed. You will need to make changes to the config.sys file to add a device driver. This change may be made automatically by the scanner's installation software. You will need to reboot the computer for the changes to take effect.

Troubleshooting TCP/IP

Troubleshooting TCP/IP

Troubleshooting TCP/IP - Detailed Steps

This article shows how to troubleshoot TCP/IP connectivity between computers on a Windows network. If you haven’t already done so, disable XP’s Internet Connection Firewall on all local area network connections, and remove all firewall programs on the network. Improperly configured firewalls are the most common cause of TCP/IP problems.

Open a Command Prompt Window

For many of these steps, you’ll be typing at the command prompt. To open a command prompt window in Windows 2000 or XP, click Start Run, type cmd in the box, and click OK. To open a command prompt window in Windows 95, 98, or Me, click Start Run, type command in the box, and click OK. Type one command per line, and press Enter after each one to execute it. To close the command prompt window, use the exit command.

Determine the TCP/IP Settings

Determine the TCP/IP settings of each computer on the local area network. In XP, open the Network Connections folder, right click the LAN connection, and click Status Support Details. For example, here are the Status and Details views for the LAN connection on an Internet Connection Sharing host.

In Windows 95/98/Me, click Start Run, type winipcfg in the box, and click OK. Select the LAN adapter from the menu, and click More Info.

You can also see the TCP/IP settings from the command prompt. This is especially convenient if a computer has more than one network adapter. Use the ipconfig /all command, which is available in all versions except Windows 95. The output from this command can be long, so it’s best to write it to a file. Specify the file name in the command this way:

ipconfig /all >ipconfig.txt

Description of TCP/IP Settings

Here are the TCP/IP settings that are used in network troubleshooting:

IP Address – Unique address assigned to a network adapter. A computer with multiple network adapters has an IP address for each one, and each one must be in a different subnet.

Subnet Mask – Used in conjunction with the IP address to determine which subnet an adapter belongs to. At the simplest level, communication is only possible between two network adapters when they’re in the same subnet.

Default Gateway - IP address of a computer or router, on one of this computer’s local area networks, that knows how to communicate with subnets not present on this computer. For an Internet connection, the default gateway is a router belonging to your Internet service provider, and all access to sites on the Internet goes through it. For an ICS client, the default gateway is the ICS host. If you use a hardware router, it serves as the default gateway.

DHCP Server – If an adapter is configured to obtain an IP address automatically, this is the address of the server that provides it. It could be your ISP, an ICS host, or a hardware router.

DNS Servers – IP address of one or more Domain Name Server computers. DNS servers translate Internet names (like http://www.practicallynetworked.com/) to their IP addresses (like 63.146.109.227).

Subnets

See our article on subnets for a brief description of how they work. For more details, see this Microsoft Knowledge Base article.

If two computers are supposed to be on the same subnet, but aren’t, something is wrong with the network hardware or software configuration. This is most likely to happen when one of them receives an IP address of 169.254.x.x, which indicates that:

It’s configured to obtain an IP address automatically.

It couldn’t find a DHPC server on the network to make the assignment.

Windows assigned it an Automatic Private IP Address.

See our article on Specific Networking Problems and Their Solutions for more information.

Pinging

The ping command is the basic tool for testing TCP/IP connectivity. It sends a special packet (called ICMP Echo) to a particular IP address and looks for a reply. If everything is working right, the reply comes back. If not, the ping times out in a few seconds. By default, the ping command repeats the process four times. Here’s an example of an ICS client computer pinging a Windows XP Home Edition ICS host, using the host’s IP address and its computer name.

When ping fails, you’ll see one of these error messages:

Request timed out - The IP address is valid, but there’s no reply from it. If the IP address is on a local area network, the most likely cause is a firewall program blocking the ping.

Unknown host or Ping request could not find host - The computer name doesn’t exist on the local area network. Make sure that NetBIOS over TCP/IP is enabled.

Destination host unreachable – The IP address isn’t on a local area network, and the default gateway can’t access it. Either there’s no default gateway, its address is wrong, or it isn’t functioning.

Pinging the Local Area Network

Here is a series of ping commands to use in finding where a problem occurs on a local area network. Run them in the order shown, and don’t go on to the next command until all of the previous commands work properly. In this example:

The computer being tested is named Winxp, with IP address 192.168.1.101.

There’s another computer on the network, named Win98, with IP address 192.168.1.123

Substitute the appropriate IP addresses and computer names for your network.

Command Target What Ping Failure Indicates

ping 127.0.0.1 Loopback address Corrupted TCP/IP installation

ping localhost Loopback name Corrupted TCP/IP installation

ping 192.168.1.101 This computer’s IP address Corrupted TCP/IP installation

ping winxp This computer’s name Corrupted TCP/IP installation

ping 192.168.1.123 Another computer’s IP address Bad hardware or NIC driver

ping win98 Another computer’s name NetBIOS name resolution failure

To fix a corrupted TCP/IP Installation on Windows XP, follow the steps in this Microsoft Knowledge Base article. For Windows 95/98/Me, un-install the TCP/IP protocol in Control Panel Network, reboot, and re-install it. If that doesn’t fix it, use this procedure on Windows 95 or 98.

Pinging the Internet

You can also use ping to find a problem with Internet access. Run these commands in the order shown, and don’t go on to the next command until all of the previous commands work properly. Use the Default Gateway and DNS Server addresses that you got from the winipcfg or ipconfig /all command.

Command Target What Ping Failure Indicates

ping w.x.y.z Default Gateway Default Gateway down

ping w.x.y.z DNS Server DNS Server down

ping w.x.y.z Web site IP address Internet service provider or web site down

ping www.something.com Web site name DNS Server down or web site down

Installation of Plug and Play Devices

Installation of Plug and Play Devices

If the device is a new installation, Windows should detect the
device at startup. One of three things can happen:
1. Windows will already have the required software device drivers and configure the system with or without user prompts
2. Windows will prompt the user for the OS installation CDs to retrieve the required drivers
3. Windows will prompt the user to provide the location for the required drivers supplied by the device manufacturer.
This would be your cue to insert the manufacturer’s CD that came with the device and point Windows to the correct driver installation file for the OS. Alternately, the manufacturer’s instal­lation guide may provide a different method for installation. Example: most USB devices require that you install the software first before connecting the device.
If Windows recognizes the device but you don’t have the man­ufacturer’s CD, there is a good chance that you can enable basic functionality by using the default Windows drivers. See the section Installation of non-Plug and Play Devices on how to tell Windows to use the default Windows drivers.

Installation of non-Plug and Play devices
If the device is not getting detected by Plug and Play during system startup, this usually means that you have a non-Plug and Play device. If you have the manufacturer’s CD and/or manual, look for installation instructions. Non-Plug and Play devices are usually older, and require manual allocation of resources, usually through setting jumpers or switchers on the device itself. Once you have ensured that the device has been configured as per the manufac­turer’s guidelines, boot up and install any software provided by the manufacturer as per the installation guidelines.
If there are no installation guidelines or the device is a second hand component with no documentation or you don’t have the required software drivers, then you can try to force Windows to recognise the device. First try to verify if the phys­ical installation and the jumper/switch settings on the device are correct. Search the Internet for information on how to do this. If you are able to do this, good; if not, don’t worry too much about it and go on to forcing Windows to recognise the device:
1. Click on the Add New Hardware (Windows 9x/ME) / Add Hardware (Windows 2000/XP) in the Control Panel. The Add Hardware Wizard will start up. Click Next.
2. If you have Windows 9x/ME go to Step 3, else go to Step 5.
3. In Windows 9x/ME, the Wizard will inform you that it is going to search for new hardware. Allow it to do so by clicking Next twice. After Windows finishes searching for Plug and Play Devices it will report that no Plug and Play devices are found.
4. Click Next. The first option tells Windows to search for non-Plug and Play devices. If it successfully detects the device, follow the on-screen instructions to complete the installation. Otherwise, select “No, I want to select the hardware from a list” and click Next. Go to Step 6.
5. In Windows 2000/XP, select “Add a new hardware device” and click Next. In the next dialog box, you can either ask Windows to search for a driver, or you can install the device manually. For manual device installation, select “Install the hardware that I manually select from a list (Advanced)”.
6. Select the hardware type from the list and click Next.
7. If you know the name of the device manufacturer, select the name of the manufacturer and browse through the list on the right side to see if your device model number is listed or a gener­ic name for your model series e.g. HP DeskJet for DeskJet printers. If you do not know the name of the manufacturer or the device model number, check if there are standard device types that you can install. If there are no standard types that can be installed, you will need to find a suitable driver by searching the Internet or getting it from other sources.
8. If the device has a standard type, choose the specification closest matching to your device. If the device does not have a standard type, click the “Have Disk…” button and provide the location for the appropriate driver installation file. Follow the on-screen instructions to complete the installation.

The above steps (for both Plug and Play and non-Plug and Play devices) should normally solve the device conflict and get your hard­ware operational.

BIOS Problems

General BIOS Problems

Problem: The BIOS fails to detect the hard disk(s), CD-ROM, floppy drive, etc.

Cause: All of a sudden, hard drives and floppies disappear from the list of devices, or you cannot boot because the BIOS declares that you have no hard drive!

Solution: The most common reason for this error is a bad or loose­ly connected cable or incorrect jumper settings on the device. Check all the cable connections to the device. Ensure that the data cable and the power cable are properly plugged in both to the device and to the motherboard. Next, check the jumper settings. If two disks are connected to a single port, make sure one is set to Master and the other to Slave. Also check the BIOS setup program and ensure that IDE controllers are enabled. Go to the Integrated Peripherals menu and confirm that the Primary and Secondary Channels are enabled. If you are not comfortable changing indi­vidual values, reset the settings using the “Load Fail-safe (or Factory) Defaults” option.

Problem: After powering off the PC and switching it back on after a few hours, the time has changed

Cause: The CMOS battery powers the real-time clock. This symp­tom indicates that the battery is dying. In rare cases, it could also mean there’s a problem with the battery port of the CMOS. Solution: Replace the battery. If the symptom persists, there’s a good chance that the battery port is damaged. In this latter case, you may need to replace the motherboard! Get it checked by a computer technician first.

Problem: An error message says there is a problem with IRQ, I/Oport, DMA configuration or resource allocation, and refers totroubleshooting the BIOS

Cause: The BIOS configures and allocates resources to the IRQ,and I/O ports. In most BIOSes, this allocation cannot be changed or modified by the user. Some BIOSes may provide a “soft menu” to change these allocations.

Solution: It’s preferable to get the BIOS checked by a computer engineer. Use the “Load Fail-safe (Factory) Defaults” options in the setup menu. If a soft menu is available, ensure you read up the associated documentation before changing any settings.

Problem: An error message asks to update the BIOS

Cause: The BIOS firmware does not support the device without an update.

Solution: See the Updating the BIOS section

Device Manager Error Codes

Device Manager Error Codes

Additionally, a problem code explaining the problem is displayed for the device. The next step is to understand what each of these error codes mean and apply the recommended resolution. The list of problem codes and the recommended resolution are as follows:

Code 1

Code Meaning: The device is not configured correctly.

Recommended Resolution: The software drivers for the device have been incorrectly installed or incorrectly configured. Select the Driver tab and click the Update Driver button. This will launch an update Wizard. Follow the instructions and locate the correct driver for the device to install it.

Additionally, you could try removing the device from Device Manager and reinstalling it using the Add Hardware Wizard.

Verify from the hardware documentation/manufacturer’s Web site that the device will work with your OS.

Code 2

Code Meaning: (Not applicable to Windows XP) Depending on the

type of device, this could indicate either a problem with the BIOS

or a problem with loading the device driver.

Recommended Resolution: Check with the BIOS manufacturer for

an updated BIOS. See the BIOS section of this guide on how to

update the BIOS.

OR

Get an updated driver for the device from the manufacturer and

update the device software by clicking Update Driver on the Driver

tab.

Remove the device from Device Manager and reinstall it using the

Add Hardware Wizard.

Code 3,REGISTRY PROBLEMS

Code Meaning: The driver is corrupt or your system is running low on memory and other resources.

Recommended Resolution: Run the Update Driver Wizard and rein­stall the driver or get an updated driver from the manufacturer. AND/OR

Close any applications using memory. AND/OR

Add more RAM. See the chapter on Memory on how to do that. AND/OR

Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.

Code 4

Code Meaning: (Not applicable to Windows XP) One of the drivers

for the device may have been corrupted, or its Windows Registry

entry may be damaged.

Recommended Resolution: Check the registry by running scan-

regw.exe. Click Start > Run. Type scanregw.exe and hit [Enter]. This

program will check the Registry for corruption and prompt you to

restore a previous good version of the Registry if it encounters any

damaged entries.

AND

Remove the device from Device Manager and reinstall it using Add

Hardware Wizard.

Code 5

Code Meaning: (Not applicable to Windows XP) The device has requested a resource that Windows doesn’t know how to handle. Recommended Resolution: Run the Update Driver Wizard and rein-stall the driver or get an updated driver from the manufacturer.

OR

Remove the device from Device Manager and reinstall it using the

Add Hardware Wizard.

Code 6

Code Meaning: (Not applicable to Windows XP) Another device is using a resource that this device needs.

Recommended Resolution: Run msinfo32.exe to get more infor­mation on the conflict. Check the Resources tab to get details of the conflict. Refer to the hardware documentation and/or the man­ufacturer’s Web site for instructions on the correct values that need to be set manually. Clear the Automatic Settings checkbox, click the Change Setting button and input the values.

OR

Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer. AND/OR

Remove the device from Device Manager and reinstall it using Add Hardware Wizard.

Code 7

Code Meaning: (Not applicable to Windows XP) The drivers need to be reinstalled.

Recommended Resolution: Run the Update Driver Wizard and rein­stall the driver or get an updated driver from the manufacturer. AND/OR

Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.

Code 8

Code Meaning: (Not applicable to Windows XP) Windows cannot load the basic device loader file that loads the device driver, or it is missing or corrupt, or a software value for the device is missing or corrupt.

Recommended Resolution: Run the Update Driver Wizard and rein­stall the driver or get an updated driver from the manufacturer.

OR

Remove the device from Device Manager and reinstall it using the

Add Hardware Wizard.

Code 9

Code Meaning: (Not applicable to Windows XP) The BIOS is report­ing the resources for this device incorrectly and the Windows Registry is invalid.

Recommended Resolution: Run the Update Driver Wizard and reinstall the driver or get an updated driver and the correct Registry entries from the manufacturer. AND/OR

Remove the device from Device Manager and reinstall it using the Add Hardware Wizard. OR (as a last resort) Reinstall Windows.

Code 10

Code Meaning: The hardware will report the reason for failure that Windows should display. If the hardware doesn’t report the reason for failure, Windows will say that the device is not present, not working correctly or does not have all the required drivers installed.

Recommended Resolution: If the failure message is present, use that to troubleshoot the problem by referring to the documenta­tion or manufacturer’s Web site. AND/OR

Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer.

OR

Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.

Code 11

Code Meaning: (Not applicable to Windows XP) Windows stopped responding when it tried to start the device, and hence will never try to start this device again.

Recommended Resolution: Run the Update Driver Wizard and reinstall with an updated driver from the manufacturer.

Code 12

Code Meaning: Two devices have been assigned the same I/O port, interrupt or DMA channel. This could be by the BIOS, by Windows, or both. Also, it could be that the BIOS has not allocated enough resources for the device.

Recommended Resolution: Disable one of the devices. (Windows 9x/ME: Double-click, select “Disable in this hardware profile” on the General tab of the property sheet; Windows 2000/XP: Right-click and select Disable)

OR

Check the Resources tab to get details of the conflict. Refer to the hardware documentation and/or the manufacturer’s Web site for instructions on the correct values that need to be set manually. Clear the “Automatic Settings” checkbox, click the “Change Setting” button, and input the values.

OR

Reconfigure the BIOS resource allocation if possible. Refer to the motherboard documentation along with the device documentation.

Code 13

Code Meaning: (Not applicable to Windows XP) Windows did not detect the hardware.

Recommended Resolution: Verify that the hardware is working and that the physical installation is correct. Refer to the manufac­turer’s documentation for specific installation instructions. AND

Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.

Code 14

Code Meaning: The device cannot work properly until the system is

restarted.

Recommended Resolution: Restart the computer.

Code 15

Code Meaning: (Not applicable to Windows XP) The device is caus­ing a resource conflict.

Recommended Resolution: Run msinfo32.exe to get more infor­mation on the conflict. Check the Resources tab to get details of the conflict. Refer to the hardware documentation and/or the manufacturer’s Web site for instructions on the correct values that need to be set manually. Clear the “Automatic Settings” checkbox, click the “Change Settings” button, and input the values.

Code 16

Code Meaning: The device is only partially configured and Windows could not find all the resources required by this device.

Recommended Resolution: Run msinfo32.exe to get more infor­mation on the conflict. Check the Resources tab to get details of the conflict. Refer to the hardware documentation and/or the man­ufacturer’s Web site for instructions on the correct values that need to be set manually. Clear the “Automatic Settings” checkbox, click the “Change Settings” button, and input the values.

Code 17

Code Meaning: (Not applicable to Windows XP) The hardware is a multi-function device whose driver file is reporting invalid infor­mation on how to split the resources.

Recommended Resolution: Remove the device from Device Manager and reinstall it using the Add Hardware Wizard. Use an updated device driver if required.

Code 18

Code Meaning: The drivers for this device should be reinstalled.

Recommended Resolution: Select the driver tab and click the “Update Driver” button. Use an updated device driver if required.

Code 19

Code Meaning: A problem with the Windows Registry entry for

this device was detected.

Recommended Resolution: In Windows 9x/ME/2000, run the Registry scanner (scanreg.exe). If this does not solve the problem, run “scanreg.exe /restore”. If this still does not solve the problem, remove the device and reinstall it using the Add New Hardware Wizard.

In Windows XP, run the Troubleshooting Wizard from the General tab of the Device Properties sheet. Click Uninstall and then click “Scan for hardware changes” to reinstall the device. If that doesn’t solve the problem, restart the computer in Safe Mode and select “Last Known Good Configuration”.

Code 20

Code Meaning: (Not applicable to Windows XP) One of the drivers

for this device could not be loaded, and Windows is not able to

interpret the result.

Recommended Resolution: Remove the device from Device

Manager and reinstall it using the Add Hardware Wizard.

Code 21

Code Meaning: The device is being removed as it has a problem,

and Windows needs to be restarted.

Recommended Resolution: Wait a few seconds and refresh the

Device Manager. If the device still shows, then restart the computer.

Code 22

Code Meaning: The device has either been disabled by a user or has

not started.

Recommended Resolution: Wait a few seconds and refresh the

Device Manager. If the device still shows, then restart the computer.

Trying enabling the device. If that is not possible, remove the

device, reboot the computer and reinstall it using the Add

Hardware Wizard.

Code 23

Code Meaning: (Not applicable to Windows XP) This indicates a problem with the drivers of either the primary or secondary dis­play adaptor. The device loader program delayed loading the device and then did not inform Windows.

Recommended Resolution: Verify that the drivers for all the dis­play adaptors on the computer are correct and updated. Remove the display adaptors and reboot. Windows will automatically detect the adaptors and configure them.

If the device is not a display adaptor, then remove the device and reinstall it using the Add Hardware Wizard.

Code 24

Code Meaning: Windows couldn’t detect the device. This error may

happen if the device has been set for removal.

Recommended Resolution: Verify that the hardware is working

and that the physical installation is correct. Remove the device

from Device Manager. Reinstall it using the Add Hardware Wizard.

Update the device driver to the latest.

Code 25

Code Meaning: (Not applicable to Windows XP) The device installa­tion has not yet been completed.

Recommended Resolution: Restart the computer. Windows may require to be reinstalled depending on whether the reboot solves the problem or not.

Code 26

Code Meaning: (Not applicable to Windows XP)

The device did not load or not all the drivers were installed.

Recommended Resolution: Remove the device from Device

Manager. Reinstall using the Add Hardware Wizard.

Code 27:

Code Meaning: (Not applicable to Windows XP)

The Windows Registry entry describing the resources for this

device is not valid.

Recommended Resolution: Remove the device from Device

Manager. Reinstall it using the Add Hardware Wizard.

Code 28

Code Meaning: (Not applicable to Windows XP) The driver for the device was not installed correctly.

Recommended Resolution: Use the Update Driver Wizard to rein­stall the driver. AND/OR

Remove the device from Device Manager. Reinstall it using the Add Hardware Wizard.

Code 29

Code Meaning: The device has been disabled in the BIOS, or the device will not work with the version of Windows you are using. Recommended Resolution: Enable the device in the BIOS. Refer to the motherboard documentation for details and see the BIOS sec­tion of this guide for further information.

Code 30

Code Meaning: (Not applicable to Windows XP) An IRQ that cannot be shared is being used by this device and another device driver. Recommended Resolution: View the resource conflict in the resources tab, if available. Refer to the manufacturer’s documenta­tion for either device and change the IRQ allocation manually. You can do this by clearing the “Automatic Settings” checkbox and clicking the “Change Settings” button.

Code 31

Code Meaning: To function properly, the device depends on anoth­er device which is not functioning properly. Most likely the other device will also have a error code.

Recommended Resolution: Troubleshoot the dependant device to enable this device. If they still don’t work, remove them from Device Manager and reinstall them using the Add Hardware Wizard.

Code 32

Code Meaning: (a) The installation disk/CD-ROM or network loca­tion was not accessible to install the device drivers. (b) A driver or service for the device has been disabled.

Recommended Resolution: (a) Restart the computer. If that doesn’t solve the problem, copy the installation files to the hard disk and run the setup program for the device.

(b) Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.

Code 33

Code Meaning: (a) The hardware is not responding to the driver software for the device.

(b) The software that determines the resources required by the device has failed.

Recommended Resolution: (a) Obtain an updated driver from the manufacturer. Remove the device from Device Manager and rein­stall it using the Add Hardware Wizard. (b) The hardware might have failed and needs to be replaced.

Code 34

Code Meaning: The device has to be configured manually.

Recommended Resolution: Refer to the manufacturer’s documen­tation for instructions.

Code 35

Code Meaning: The BIOS is missing a resource assignment entry

for the device and needs to be updated.

Recommended Resolution: Obtain and install a new or updated

BIOS from the computer manufacturer or motherboard

manufacturer.

Code 36

Code Meaning: The IRQ configuration has failed.

Recommended Resolution: Refer to the motherboard documenta­tion to see if you can change the IRQ settings in the BIOS. See the BIOS section of this guide for further information.

Code 37

Code Meaning: The driver software failed to load.

Recommended Resolution: Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.

Code 38

Code Meaning: The driver software is already loaded into RAM and

cannot be loaded again.

Recommended Resolution: Restart the computer.

Code 39

Code Meaning: Some or all the drivers could not be loaded as they

may be corrupted or missing.

Recommended Resolution: Remove the device from Device

Manager and reinstall it using the Add Hardware Wizard. Update

the driver if possible.

Code 40

Code Meaning: The driver’s Registry entry is either corrupted or

missing.

Recommended Resolution: Remove the device from Device

Manager and reinstall it using the Add Hardware Wizard. Update

the driver if possible.

Code 41

Code Meaning: This usually happens when Windows cannot

detect non-Plug and Play devices.

Recommended Resolution: Obtain an updated driver for the

device from the manufacturer. Remove the device from Device

Manager and reinstall it using the Add Hardware Wizard. Update

the driver if possible.

Code 42

Code Meaning: A (system bus) driver has created duplicate entries,

or a serial number is discovered in a new location before it is

removed from the old location.

Recommended Resolution: Restart the computer.

Code 43

Code Meaning: One of the drivers controlling the device notified

Windows that the hardware has failed in some manner, and

Windows stopped the device.

Recommended Resolution: Refer to the hardware documentation

or the manufacturer’s Web site to resolve this error.

Code 44

Code Meaning: A software program or system service has shut

down the hardware.

Recommended Resolution: Restart the computer.

Code 45

Code Meaning: The hardware is not connected to the computer.

This error is reported when the computer is set to show all devices

previously connected to the computer.

Recommended Resolution: Reconnect the hardware or ignore the

error. No resolution is necessary.

Code 46

Code Meaning: Windows is not able to access the device as the sys­tem is shutting down.

Recommended Resolution: The device should work correctly when the computer restarts.

Code 47

Code Meaning: The device has been prepared for safe removal either by unplugging or pressing an eject button.

Recommended Resolution: Unplug or eject the device and then plug it or insert it back in to bring the device back online. Note: Restarting the computer also brings the device back online.

Code 48

Code Meaning: The driver for the device is known to have problems

with Windows.

Recommended Resolution: Obtain an updated driver from the

device manufacturer and update the driver.

Code 49

Code Meaning: The system hive of the Windows registry has reached its maximum limit and new devices cannot work until the size is reduced.

Recommended Resolution: The system hive contains configura­tion for the entire computer. Uninstall all device drivers that are no longer in use to reduce the size of the system hive.

BIOS Beep Codes

BIOS Beep Codes

When your system has a problem that won’t let it start up proper­ly, the first thing you will hear is warning beeps. These could be because of hardware or even because of the BIOS itself.

Unfortunately, beep codes are not standardized across BIOS vendors and motherboard manufacturers. Below are mentioned the beep codes, along with the possible problem that could be causing the beep, and some suggestions towards resolution. These are for two popular BIOS vendors—AMI and Award. If your BIOS is from any other vendor, you will need to refer to the motherboard manufacturer’s or the BIOS vendor’s manual for details.

Also, motherboard manufacturers may modify the beep codes to their convenience and not maintain consistency. Keep an open mind when you decipher the beep, and don’t get into a tizzy if the codes don’t match what is in here or in the BIOS vendor’s manual! You should always try and contact the manufacturer to get the correct beep codes.

AMIBIOS (American Megatrends Inc.)

One beep: RAM failure

Problem: Motherboard problem or failed RAM.

Solution: Troubleshoot the motherboard and/or the RAM.

Two beeps: Parity Circuit Failure

Problem: Motherboard problem or failed RAM.

Solution: Troubleshoot the motherboard and/or the RAM.

Three beeps: Base 64K RAM failure

Problem: There is a failure within the first 64K of memory.

Solution: Troubleshoot the motherboard and/or the RAM.

Four beeps: System Timer Failure

Problem: One or more of the system timers on the motherboard has failed; usually indicates motherboard failure.

Solution: Troubleshoot the motherboard. You may need to replace it.

Five beeps: Processor Failure

Problem: The processor is generating an error condition. This does not mean that the processor is not working—with a dead proces­sor, the computer won’t boot at all.

Solution: Check if the processor is overheating, and whether it is set correctly on the motherboard. Troubleshoot the motherboard.

Six beeps: Keyboard controller or gate A20 failure

Problem: Keyboard, keyboard controller or motherboard error.

Solution: Check if the keyboard is connected properly. Use anoth­er keyboard to see if the problem persists. If it does, look for the keyboard controller chip on the motherboard and see if it is seat­ed properly and that it is not damaged. If the problem continues, troubleshoot the motherboard.

Seven beeps: Virtual mode exception error

Problem: This error is reported when testing the processor’s virtu­al mode. Solution: Troubleshoot the motherboard/processor. Verify that all jumpers are properly configured.

Eight beeps: Display memory read/write failure

Problem: The BIOS is not able to read/write the display card’s memory.

Solution: Troubleshoot the motherboard and/or display card.

Nine beeps: BIOS’ ROM checksum failure

Problem: The BIOS CMOS chip is most likely defective. May also be a problem with the motherboard.

Solution: The CMOS chip can be replaced, but replacing the moth­erboard is simpler and more cost-effective.

10 beeps: CMOS shutdown register read/write error

Problem: A motherboard component is creating an error when interacting with the CMOS.

Solution: Troubleshoot the motherboard and verify that all com­ponents are properly set up and configured.

11 beeps: Cache memory error

Problem: There is an problem with the processor’s L2 cache.

Solution: Verify that the L2 cache chip is inserted correctly. Verify that all connections inside the PC are correct. Replace the cache module if the problem persists.

Continuous beeps: Video / Memory problem

Problem: A problem with the RAM, display card or motherboard.

Solution: Troubleshoot the RAM first, followed by the display card and then the motherboard.

Other beeps: Check motherboard manual

Problem: Check the motherboard manual or the vendor’s Web site for more information. Treat it as a motherboard problem.

Solution: Troubleshoot the motherboard.

Award BIOS Award has the least number of documented beep codes. They prefer to display an error message on the screen. Beep codes are used only if the BIOS can’t access the display subsystem.

One long beep: Memory problem

Problem: A problem with the memory or motherboard

Solution: Troubleshoot the memory and the motherboard

One long and two short beeps: Video error

Problem: The BIOS is not able to access the video sub-system

Solution: Troubleshoot the video card, and if the problem persists, go on to the motherboard.

One long and three short beeps: Video error

Problem: The BIOS is not able to access the video sub-system

Solution: Troubleshoot the video card, and the if problem persists, go on to the motherboard.

Continuous beeps: Video / memory problem

Problem: There is a problem with the RAM, display card or motherboard.

Solution: Troubleshoot the RAM first, followed by the display card and then the motherboard.

Other beeps: Check the motherboard manual

Problem: Check the motherboard manual or the vendor’s Web site for more information. Treat it as a motherboard problem.

Solution: Check the motherboard manual. Troubleshoot the motherboard.

Troubleshooting the Blue Screen

Troubleshooting the Blue Screen Of Death
One of the most dreaded error messages for a Windows user is the blue screen, or the Blue Screen of Death (BSOD) as it is pop­ularly known, which suddenly pops up informing you that something is seriously wrong with Windows. What this screen essentially means is that Windows has crashed and needs to reboot to recover. Usually, you will be able to recover and con­tinue without any problems, but it can sometimes be a hair-rais­ing experience—like when you’re pressed for time and have to get that PowerPoint presentation ready for your boss!

Windows 9x/ME
In Windows 9x/ME this error is less serious but more common. You can usually recover from the error by simply pressing [Ctrl] + [Alt] + [Del] and restarting the computer, or by switching off the PC and switching it back on. However, the error message will contain very little information that you can use in troubleshooting.

Problems causing the BSOD
The BSOD is the main way for virtual device drivers to report a problem. The error description will state that Windows faced a problem (exception) at a particular memory address (a portion of the RAM) in a certain file, usually with the prefix VxD (virtual device driver), or the file name may have the DLL extension. At the minimum, it indicates that there was a problem with that particu­lar file. Typically, this may have been caused by some action of the user that Windows does not allow—like accessing a document from a floppy and then removing the floppy before closing document. In other cases it may indicate that there is a problem with a particular software or hardware. If the BSOD repeats with the same message, then there is potentially something seriously wrong, and you should investigate further.

The basic approach
Use the file name in the error message to give you a clue as to what is causing the problem. Search the hard disk for the filename and look at the folder in which the file is located to give you an idea of which software program or hardware uses this file. Also search the Internet for any information on this file. Once you have identified the soft­ware or hardware associated with the filename, uninstall or remove the software or hardware. Verify that the software or hardware, as the case may be, is compatible with your version of Windows. Get updates if applicable and reinstall it. Also, see the Troubleshooting Startup, Shutdown and Power Management sections in this guide.

System Restore in Windows ME and Windows XP
In addition to the above, Windows ME/XP provides the extremely useful System Restore tool. System Restore takes daily snapshots of the system state—every 10 hours the system is on and every 24 hours of real-time. The snapshot contains all the information required to restore the system to that particular point in time. To restore the system to a previous point in time do the following: o Go to Start > Programs > Accessories > System Tools > System
Restore. o Choose “Restore my computer to an earlier time” and click Next. o On the calendar on the left, choose the last day you remember that Windows operated without problems. On the right, choose the Restore Point description; if there are multiple restore points that day, choose the one you’re most certain about or choose the latest time. Click Next. o Make sure you’ve closed all open files and running programs, and click OK. oThe system will roll back to the settings of that restore point and you can continue working normally.

Windows 2000/XP
Error reporting in Windows 2000/XP is more robust, nevertheless,hen you get a BSOD, it is just as mysterious at first glance. The “Windows Stop Message”, which is the official name for the BSOD, occurs when Windows encounters a problem from which it cannot recover. At this moment Windows stops and displays the error mes­sage shown on the screen. Additionally, the contents of the system memory are dumped to a file. This memory dump file can be analysed by competent support technicians to troubleshoot the problem in depth. All the stop errors are numbered according to the circumstances that caused the error. This is a big step up from Windows 9x/ME, where the stop errors were more generalised and hence were much more dif­ficult to troubleshoot.

Problems causing the BSOD
The BSODs are generally associated with five problems faced by Windows:
o Software or device drivers may have a problem
o A hardware device is malfunction­ing, or was removed while Windows was running, or does not fully support Windows. On older machines, outdated BIOS informa­tion can also cause errors.
o Hardware or hard disk errors during installation of Windows.
o Corrupted startup files, hardware and driver software during Windows startup can also be the cause. This type of error will always require troubleshooting before Windows can start up normally.
o Intermittent errors that appear randomly. These can be caused by an overheating processor, a defective memory system, a dying or dead hard disk, or faulty software and device drivers.

Possible solutions to the BSOD
When a BSOD occurs, the first step is to note down the Stop num­ber, the ‘friendly name’ of the error and also the name of the file that is reported as the cause of the problem. The Stop number will be in hexadecimal format—something like this:

STOP : 0x0000000A (0xDB000000, 0x00000001, 0x00000002, 0xB04FB0DB)

The friendly name will be something like this:
IRQL_NOT_LESS_OR_EQUAL

If the error comes up very briefly, before you can note it down, and the system restarts, you will need to change a setting to tell Windows not to automatically reboot. Right-click My Computer, select the Advanced tab, and click “Startup and Recovery”, in Windows 2000, clear the “Automatically Reboot” checkbox. In Windows XP, click Settings and clear the “Automatic Restart” checkbox. This, of course, assumes that Windows has rebooted normally and you are able to change the setting.
If you are not able to boot normally, restart Windows and press [F8] repeatedly during the POST cycle. This will take you to the Advanced Options menu. Choose Safe Mode. Windows will attempt to load with a minimum set of drivers. If Windows is able to boot into Safe Mode, this most likely means that the problem is with a particular software, and is not hardware-related. If Windows is not able to boot into Safe Mode, restart the computer, bring up the Advanced Options screen (by pressing [F8] during POST) and select “Last Known Good Configuration”. Windows will then attempt to load the last settings where everything worked normally. If that doesn’t work, then it most likely means you have a serious hardware or critical startup system file error. If this error has occurred after any recent hardware additions, remove the hardware and try to boot again.
If you are able to boot into Safe Mode, first perform a virus and spy-ware scan using a tool such as Norton AntiVirus and Spybot S&D. Uninstall any recently added software, and remove or roll back any updated device drivers. (To roll back device drivers, go to the Properties page of the device in Device Manager, select the Driver tab, and click Roll Back Driver). In XP, you can perform one additional step—running System Restore, as explained above for Windows ME.
Restart the computer normally and check if the problem recurs. If it is an intermittent problem, and occurs at random, you can note down the error number the next time it occurs, since you disabled Automatic Restart after a crash. Boot into Safe Mode and see if you get the same random error. If you do, then the problem is likely hardware-related. Resolve the issue by following the hardware trou­bleshooting steps explained below. If the error only occurs in nor­mal mode, then it is likely a software problem. Follow the steps for software and device driver troubleshooting described below.
Look in Device Manager and troubleshoot any hardware device conflicts as explained in the Troubleshooting Hardware Device Conflicts in Windows section. You can remove or disable the device, or roll back its driver to a previous version.
If the BSOD is caused by a faulty program that crashes Windows at system startup, you can disable the software from starting up by using msconfig.exe. Type Start > Run, type in “msconfig” and press [Enter]. Select the Startup tab and disable any or all software you think may be the ones causing the problem. Better still, you could disable all the software in the list, enable them one at a time, and reboot the computer to identify the offending software.
If the BSOD is caused by faulty hardware, remove any recently added hardware—after switching off the PC, of course! If the BSOD still occurs, or there are no newly added hardware, test the RAM for errors by using a memory diagnostic program such as Windows Memory Diagnostic (http://oca.microsoft.com/en/windiag.asp). See the Memory section of this guide for further information. If the diagnostic reports errors, then you’ve found the culprit. Replace the defective RAM.
If the BSOD is due to corrupt system startup files, you can repair Windows by performing a Repair Install. Boot the PC from the Windows installation CD, press [Enter] to set up Windows XP, press [F8] to accept the license agreement, and then press [R] to start the Repair Installation. Windows will reinstall all the system files and redetect all the hardware. Note: You will have to visit the Windows Update site to reinstall any patches and Service Packs, since the repair installation will remove them.
If you are still getting BSODs, switch off the PC, open the cabinet and remove all but the essential hardware: the mouse, keyboard, hard disk, CD-ROM, display card and RAM, along with the PSU and proces­sor of course! Now, first attempt booting into Safe Mode, and if that works, reboot normally. If you are successful, the problem is with one of the peripheral devices. Add all the peripherals back one by one till you get a BSOD again—the last added peripheral is the culprit.
If you are getting BSODs during installation, then the prob­lem could be with the RAM, hard disk, processor, or one of the peripherals. Test the RAM using a memory diagnostic tool as described above, check the hard disk for errors (most hard disk manufacturers provide software utilities that can diagnose errors), verify that the CPU is not overheating by following the instructions in the Motherboard section of this guide, and remove all peripherals and run the installation with the mini­mum configuration as described above. If the installation is suc­cessful, you can troubleshoot the rest of the hardware devices from within Windows.