System Trouble Shooting
System Trouble shooting : System Trouble Shooting with step by step explanations and solutions.
System Trouble shooting
How to solve the system problems / hardware problem / software problem ?
| SNo | Problems | Remedies/Solutions |
| 1 | System down | 1. Check the AC Power in to CPU 2. While switching ON the system watch that the KB Power LED glows & similarly CPU FP LED indication. 3. Check the SMPS Unit fan is functioning or not 4. If not check the power supply & SMPS Unit (fuse) etc |
| 2 | System down but while switching ON LED glows both in KB & FP | First switch OFF the system, remove MB PWR Supply Connector & gently insert again with proper polarity AT -> Black & Black adjacently placed ATX -> As per the jack clip Unscrew the card inserted & gently reinsert the card Remove the CPU Cooler fan in the socket; then check the temperature of CPU manually by sensing. Remove the CPU (Processor) in the socket and clean for dust particles & install properly & now, fix the cooler fan. |
| 3 | System down but continuous beep sound in the PC Speaker | RAM inserted in the slot (DIMM) may be loose connection so, remove it clean for dust particles & install correctly as per the projections in the RAM. If the same problem exists, change the RAM (DIMM) position from 1->2 (or) 0->1 etc Even if it is in same condition change the RAM |
| 4 | System dead, no beep sound at all; but PWR supply ok | Clear CMOS Settings & check now If necessary change the MB battery Press gently all the IC’s in the MB which are placed in IC base including CMOS (EEPROM) IC Change the Processor to any other system & check for confirmation Checkout if there is any physical damages in the MB, Capacitor bulged, transistor or resistor or any IC burnt; If exists send to service center |
| 5 | Check CMOS settings wrong | Reconfigure all settings in CMOS & save then exit If again and again it queries checkout the jumper settings in the MB (CMOS Clearing) default in 1 & 2 position Even if it is default position change the MB battery Again the problem exists, there will be problem in the BIOS IC so send to service centre |
| 6 | CPU Settings Wrong reconfigure | Check your actual CPU speed & configure in CMOS then save & exit. Again the problem exists check that the MB supports for this CPU |
| 7 | Boot disk failure insert boot disk | Detect the hard disk drives & CD drives in CMOS settings after checking the physical connections in the system. Then check out the boot sequence Use any external boot disks (CD/Floppy) check the hard disk data If data exists so it is conformed that problem is only in the boot files. Run smartdrv & use deltree & remove windows & progra~1 folder then install windows Before doing this please conform that no data are available in the windows & progra~1 folders (Including Desktop) |
| 8 | System start to enter windows while booting but interrupted & it says windows system files not found | Change the boot sequence & do the steps from 3,4,5,6 mostly this problem arises only when improper handling of system files. |
| 9 | System boot normally, but the desktop does not appears | Check out the system condition, While booting it is initialized or not by testing the number lock key ON/OFF or CAPS lock key ON/OFF If no check the beep indication One long & one short beep – VGA loose connections Continuous long beep – RAM loose connection refer problem No. 3 If yes (initializing) restart the system & press the F8 key. A menu will appear like below: 1. Normal 2. Step - by - Step 3. Safe – mode 4. Boot & View log file 5. Command Prompt Safe – mode 6. Command prompt Now, select the 3rd option (Safe mode) And check out weather it is entering desktop. If yes remove the VGA driver file in the device manager restart & reconfigure it If no do the solution for problem no. 8 |
| 10 | Windows are working well but, one or more application s/w are not functioning well (Eg. MS-Office, V.Studio) | Insert the appropriate CD’s in the drive first remove the installed s/w. Freshly install the new s/w (no any data loss will occur at this time) |
| 11 | Any virus indications are there (Virus found in any one or more files) | Install the virus vaccine s/w’s & scan for virus after updated the latest virus definitions. While scanning i. repair/quarantine/delete ii. heal/move to virus vault/ remove First select repair/heal to rectify else quarantine/move to virus vault (keeping the virus file securely without spreading to other files) If these 2 options are not possible delete file after checking out the file is an important data/system file. |
| 12 | System often hanging | Check out the CPU & SMPS unit cooler fan Change the RAM to another one system & check Change the processor to another one system & check Check the AC PWR supply having Earthing facility or not Rare possibility in MB (Particularly in slot type CPU) |
| 13 | While accessing LAN Sys hanging & also for any other type of ADD on cards | Switch off the sys checkout the LAN card temperature, if no. of add on cards in the MB are high try to reduce Or otherwise change the card position in the slots If again exists replace the LAN card with a new one (So problem in LAN card buffer IC). |
| 14 | While connecting to internet using internal modem | Check out the temperature of the internal modem & do same procedure as in problem no. 13 Reinstall the driver files. |
| 15 | VGA, sound or any other add-on cards device driver not supporting | Conform that the device drivers having with you is the actual one & which will support to the device or not by referring the main IC in the card or in the MB Eg.: Sound ALC100 |
| 16 | While system booting a message will appear | CMOS configuring is error(for floppy disk drive) PWR & data cable of floppy drive may have some loose connections Even if the same problem occur enable floppy disk drive seek option in the advance setting of CMOS. Then check weather the FDD LED glows or not FDD data cable connected is inter changed; you can also see the FDD led glows continuously. Method – 1 Data cable red line and power cable red line both are adjacent and closer Method – 2 Data cable red line is last and power cable red line is also last |
| 17 | While accessing floppy disk it ask the user, Do you want to format the disk? | 1. Suppose if the floppy drive is a new one & nobody is opened the FDD, it is conform that problem in floppy (Older one floppy or track 0 bad) 2. If it is a older one or any person opened & changed the alignment you should have to sent service centre for proper alignment (since micro adjustment rqd.) manual adjustment is not possible 3. If the environment (surrounding) is a dusty one, use the floppy cleaning disk & clean the head surfaces 4. Checkout the proper physical movements of the sensor to check: i. Read write ii Read only iii Floppy disk availability or not |
| 18 | HDD not detecting or Boot disk failure insert boot disk | If HDD not detecting in CMOS, 1. Check the PWR & data cable connections 2. Check the CMOS settings & please refer problem no. 7 & get the solutions. 1. Check out weather noise is producing by the HDD head or any other physical moving parts if it is found change the media to another one with same capacity of HDD & check 2. If noise does not occurs change the logic board of HDD of same capacity & check now |
| 19 | CDD not detecting | 1. Check Power & data cable connections 2. Check CMOS settings whether the CD drive is detecting or not Note: CDROM detects only in the latest new configuration systems for old system, we should have to check at the time of booting Primary Master ... Primary Slave ... Secondary Master... Secondary Slave... Here the HDD, CDD details can be viewed. |
Trouble Shooting Tips
Introduction
The boot sequence of a windows operating system involves running the POST (Power on Self Test) by BIOS to make sure all the hardware is working properly.
These errors may occur due to hardware failure, bad driver, corrupt file or volume, System mis-configuration, or virus infection.
Error Messages Received while Booting
- After running the POST when the BIOS gains access to the Video subsystem, it displays information about the PC as it boots.
- some of the error messages are:
- Missing Command Interpreter or Invalid Boot disk error
- STOP: 0x0000007B Inaccessible Boot Device Missing NTLDR
- “Bad command or File name” Error
- “Stack overflow system halted” Error
- Errors associated with Himem.sys file
- 1. Missing Command Interpreter or Invalid Boot disk error. The causes for this error maybe:
- Incorrect boot sequence
- The order in which the computer looks for the OS in the storage devices is called a boot sequence. It can be configured through the BIOS settings. Recommended boot option is:
- Floppy drive
- Hard drive
- CD ROM
- A non-bootable floppy diskette or CD ROM in the drive
- In case both the floppy drive and the CD ROM are before the hard drive in the boot sequence then care should be taken to avoid inserting non bootable diskettes and CDs
- 2. The system files either missing or corrupted
- The system files such as command.com, msdos.sys, io.sys or drvspace.bin are very essential. If these files are missing they must be replaced.
- Boot from the floppy diskette and get to a A:\> prompt.
- Once at the prompt type sys c: and press enter
- The displays a message system transferred. Once the system has been transferred, remove the floppy diskette and reboot the computer.
- 3. The hard drive has bad sectors
- If, after following the above steps you continue to receive the error message then perform the following steps:
- Boot the computer with a bootable floppy diskette.
- At the prompt type fdisk /mbr and press enter
- This will return to a prompt with no message.
- Try to reboot the computer.
4. STOP: 0x0000007B Inaccessible Boot Device when this error occurs the user will not be able to boot to the OS. Even restarting the computer will not be of much use.

- Some of the causes for the STOP error and possible solutions are:
- 1.Cause: The computer is infected with a boot sector virus
- Solution: scan the computer for a virus, If the virus cannot be removed by an antivirus then OS needs to be reinstalled
- 2.Cause: Drive translation not being performed or changed
- Solution: The Windows NT boot partition must exist within the first 1024 cylinders of the boot device due to the restrictions of the INT-13 BIOS call. Check CMOS settings for LBA support on IDE based systems,
- 3.Cause: A conflict exists due to same IRQ assigned for two devices.
- Solution: Remove one of the hardware with the same IRQ and reconfigure it.
- 4.Cause: A conflict between the SCSI device
- Solution: Remove any non-essential SCSI devices or check to ensure each SCSI ID is unique .
- 5.Cause: Setup does not allow adding a third-party SCSI driver when booting from the SCSI CD-ROM.
- Solution: Install the device driver recommended by hardware vendor if one is available
- Missing NTLDR
- This problem may occur if the basic input/output system (BIOS) on your computer is outdated, or if one or more of the following Windows boot files are missing or damaged Ntldr Ntdetect.com Boot.ini
- Some of the causes for NTLDR to be missing or corrupted are:
- 1.Cause: Computer is booting from a non-bootable source.
- Solution: check the boot sequence in the BIOS settings. Make sure no floppy diskette is present in the floppy drive while booting.
- 2.Cause: The NTLDR and/or NTDETECT.COM file is corrupt
- Solution: If the files NTLDR and/or NTDETECT.COM are corrupt they should be replaced. In WIN 2000, copy
- NTLDR and NTDETECT.COM on a bootable floppy diskette and load them in the root directory
- 3.Cause: The boot.ini file is not configured properly
- Solution: Need to edit this file to verify if it is pointing to the correct location of the windows operating system also check if the partitions are properly defined.
- 4.Cause: The boot sector / master boot record is corrupt
- Solution: If the boot sector or the master boot record is corrupted then it results in the missing NTLDR file. It can be repaired through Microsoft Windows Recovery console
- 5.Cause: The Windows 2000 / XP version is corrupted
- Solution: Reinstall Microsoft Windows 2000 / XP
- 6.Cause: IDE/EIDE hard disk drive cables are loose or faulty
- Solution: open the computer case and check if the IDE cable is connected firmly. Disconnect and reconnect the cable.
- 6.“ Bad command or File name ” Error
- This error is displayed when the system files, autoexec.bat or config.sys file has a line that is improperly typed or missing. To solve this error, identify the line in the autoexec.bat and the config.sys file where the error is reported.
- 7.“ Stack overflow system halted ” Error
- In order to solve this error, edit the config.sys and insure that the value for the line STACKS is set at least at 12,256
Other booting errors
- The Event log is full in Event Viewer
- Cause: An event viewer gathers information about hardware and software problems and stores it in the form of a log. If the log size exceeds the allocated space an error indicates “ event log is full “
- Solution: Open the Event Viewer by clicking Start ->
- Settings -> Control Panel -> double-click
- Administrative Tools, and then double-click Event Viewer.
- The Event Viewer window displays three types of logs, namely Application log, Security log and System log.
- Click on the log you want to free.
- On the Action menu, click Clear all Events
Common Problems associated with Windows Operating System
- Blue Screen of Death (BSOD)
- It is an error screen in Windows operating system, where a blue screen displays a hexadecimal value from a core dump
- The hexadecimal value is used to identify the cause of the system error

- Blue screen are known as "Stop errors" in the Windows Resource Kit documentation Common causes of BSOD are:
- Incompatible versions of DLLs
- In Windows 95, 98 and Me, BsoD occurs when virtual device drivers need to report errors to the user
- A critical boot loader error, where the operating system is unable to access the boot partition due to incorrect storage drivers in most of these causes the best solution is to perform a clean install of the Windows.
- Troubleshooting problems related to Sound
- The problems related to sound can be classified into hardware, configuration and application problems.
- Hardware:
- Connect speakers on a good known audio device and set the volume knob to maximum.
- Click Start Settings Control Panel. In the Control Panel window click on Sound and Audio Devices. Click on the Advanced button

- The Volume Control option opens as shown in the figure.
- Keep all the volume bars at maximum and assure the mute all option is not checked.
- Play a sound file. Try playing it with another pair of speakers

Troubleshooting a CPU
- Troubleshooting a CPU
- Troubleshooting a processor is a task which is usually is done by the manufacturer. Leave alone troubleshooting,
- The identification of the problem can be only done by one method.
- The overheating might be due to various reasons like a bent pin, over-voltage.
- As troubleshooting can be done only at the chip-level, replacing the CPU is the only solution.
Troubleshooting Power Supplies
- Power supplies are used to deliver the voltages for the computer
- The main connector is connected to rear panel of the system case
- The power supply has a converter unit which down converts the AC to a +12, +5, +3.3 volts
- And then delivers it to the different components of the motherboard.
Troubleshooting ATX Power Supply
- When diagnosing power supply failures, the first thing to determine is whether the system is powering on or not.
- A live screen does not indicate that the power supply is working because monitors have separate power supplies
- If the power does not come on, check if the power source is live and working
- To do this, unplug the power supply cord and connect a lamp or any electrical appliance to the socket.
- Ensure that the correct voltage (110V/220V) is selected on the power supply based on the voltage used in your country.
- Check if the power connections to the motherboard are connected and accurate
- Ensure that the 20 pin ATX power connector and other motherboard power connections are correctly connected.
- If the monitor is connected to the PC, check if it is a live screen.
If the system is powering on but the drive is not spinning, then check the power connection to the drive’s power socket.
If the system is still not powering on, go about disconnecting all the drives one by one and attempting to power on the system each time.
Even after removing all the drives and adapters, if the system does not power on, the cause could be a motherboard short.
Troubleshooting Memory
- Troubleshooting Memory
- Memory errors can be very tricky as isolation from a faulty memory or a faulty memory slot is very difficult
- Replace the memory and see if the system works
- Memory issues need not always stop the computer from booting
- Some errors like page faults can be due to the system memory issues and not the RAM
Troubleshooting RAM, Motherboard or CPU failure
- Let us try to escalate the issue using the following steps.
- Hard error
- Soft error
- Parity and Non parity memory
- Do the Troubleshooting a Video Card Issue exercise for a dead screen now
- If the video card troubleshooting procedure has been performed, then check to see if the memory seated properly
- Another cause for the failure could be a failed CPU insertion
- Check to see if the socket CPU is sitting flat in its socket.
- The system can fail in cases where there is a stone dead CPU
- If the string of beeps is never ending, then the cause is a bad RAM
- Restore the default settings for the motherboard documentation
- If any of the standoffs are higher than the other standoffs, it will result in unacceptable stress on the motherboard.
Common Errors & Troubleshooting
| Common Errors | Solutions |
| The computer will not boot from the hard drive, but we can see drive activity | Ensure that the hard drive power connector and ribbon cable are connected |
| The drive does not spin up and the drive light doesn't light up during power-up. | Change the hard drive |
| The computer cannot communicate with the hard drive if the following error messages occur | Hard Disk Failure Hard Disk Controller Failure HDD Controller Failure |
| Hard drive runs slowly | Check for viruses Defrag the hard drive Check whether you have a slow device on the cable |
Troubleshooting Storage Devices
- Hard drive Troubleshooting
- IDE drive failure Troubleshooting
- The drive does not spin up and the drive light doesn’t light up during power-up.
- The drive spins up, but the system fails to recognize the drive.
- The drive will work as a primary drive, but not as a secondary (or vise-versa)
- Hard drive runs slowly
- Frequent drive failures
The first step in troubleshooting a IDE drive failure is to check if all the installed IDE drives are identified by BIOS
The BIOS does not register the presence of the drives, then check to see if the Master/Slave settings are done properly.
New IDE drives support the option of Cable Select (CS) by which the pin 28 connection in the cable decides which drive is the Master and which one is the Slave
If the master/slave jumper settings are done accurately
If the cables are seated properly and are new/non-defective, check to see if the hard drive spins up when the system is powered on.
Even after installing new cables and the hard drive spinning up, if the motherboard does not detect the hard drive, then the IDE controller is faulty
If the BIOS detects the installed IDE hard drives but the problem lies with the CD or DVD drive, then move on to the CD or DVD drive Troubleshooting exercise.
If the hard drive spins up but will not seek (you cannot hear the read/write head move in and out), then it is a mechanical problem.
- If the drive makes little clicking sounds and fails to start up, restart the machine via the Reset button.
- If the drive makes little clicking sounds and fails to start up, restart the machine via the Reset button.
- Check the transfer mode in the BIOS setup and transfer speed.
- If the speed and mode is correct, check to see if the drive can be accessed via FDISK to create or view partitions.
Optical storage drive troubleshooting
- One of the issue the stuck CD/DVD drive stuck tray. Check if pressing the eject button on the drive ejects the tray or not.
- Another reason why the drive will not open right away is if a disk is being actively played in the drive.
- Ensure that when installing a new drive that you use the short screws that come along with the drive
- Restart the system if the tray refuses to eject the CD/DVD
- But if the drive is registered and displayed in the CMOS setup screen, it means that the disc is indeed stuck.
- If you do manage to eject the disc, determine if the drive can read software or music discs
- Check to see if the CD and DVD drive softwares are installed on the system.
- Sometimes when the system has two physical drives, the operating system may not be reading the drive in which the CD/DVD is placed in.
- If the right drive is being read, check and see if any other disc (a factory CD in CD-ROMs or CD-Rs or a factory DVD ROM or DVD-Rs) is read.
- Try cleaning the disc with a soft bit of flannel and check for scratches
- If the drive does not read any disc at all, check to see if the drive is displayed in the operating system
- If the OS CD can be booted from this drive but the drive is not seen in the Device Manager, reinstallation of the OS is required.
Troubleshooting Mouse
| Problem | Solution |
| Mouse is not moving properly. | Clean the Mouse |
| Mouse not being detected | The drivers may not installed properly or there is some conflict with the hardware settings. |
| Mouse pointer moves on the screen randomly without any intervention of the user. | If the mouse is placed in a very bright area there are chances of stray light entering in to the case or the gaps in between the buttons. |
Troubleshooting inkjets
It deals with some common problems and possible solutions for troubleshooting inkjet printers Streaky printing Missing colors Dirty printer Drivers and wiring No connection Ink and paper Refills Paper jams
Troubleshooting Laser Printer
- Troubleshooting the problems arising with the laser printer Loose or smeared toner Vertical white area Gray mist
- Printing not dark or varied darkness
- Regularly spaced splotches
- Vertical black line at the end of the page All white page All black page
