Thursday, December 25, 2008

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.