5.1-5.4
Diagnose System Lockups
1.Shut down the system, remove and reinstall memory, and remove dust from the modules, the sockets, cooling vents, and fans. 2.Ensure the right type of memory is installed. 3.If two or more modules are installed, make sure they have matching clock speed and timing specifications. 4.If the memory has been overclocked, reset the memory to factory specifications in the BIOS setup. 5.Add additional system cooling
Bus-powered USB hard disk not recognized
A bus-powered USB 2.0 or USB 3.0/3.1 hard disk needs 500mA of power to run (and some hard disks temporarily use more power to spin up). Some computers don't provide enough power in their root hubs (built-in USB ports) to support a bus-powered hard disk, and bus-powered hubs can provide only 100mA of power per port. Connect the drive to another port on a different root hub (each pair of USB ports is a root hub) or a self-powered USB hub, or use a Y-cable to pull power from two USB ports.
Distended Capacitors
A faulty capacitor that becomes distended and leaks, causing system failure and sometimes physical damage to the motherboard. Capacitors are used as part of the voltage step-down circuits that provide power to the processor. Between 2002 and 2007, many motherboards were built using faulty capacitors.
Investigating reasons for loud noise coming from hard drive
A loud clicking noise is typically caused by repeated rereads of defective disk surfaces by the hard disk drive heads: This is typically a sign of a failing drive. Replace the hard disk immediately after making a backup copy. Humming noises can be caused by rapid head movement on a normally functioning hard disk: This noise can be reduced or eliminated by enabling Automatic Acoustic Management (AAM), a feature of most recent hard disks. Some vendors provide a downloadable acoustic management tool, which can reduce head speed to reduce noise and may reduce drive performance as a result.
Loud Clicking Noise (Magnetic hard disk drives)
A loud clicking noise is typically caused by repeated rereads of defective disk surfaces by the hard disk drive heads: This is typically a sign of a failing drive. Replace the hard disk immediately after making a backup copy. Humming noises can be caused by rapid head movement on a normally functioning hard disk: This noise can be reduced or eliminated by enabling Automatic Acoustic Management (AAM), a feature of most recent hard disks. Some vendors provide a downloadable acoustic management tool, which can reduce head speed to reduce noise and may reduce drive performance as a result.
Overclocking
A practice of increasing the clock rate of a computer to exceed that certified by the manufacturer.
Read/Write Failure
A storage error that can result from electronics failure, impact damage, cable damage, or other issues.
Multimeter
A tool that can be used to test both coaxial and TP cabling and AC and DC voltage. When set for DC voltage, it can be used to test computer power supplies and AC adapters. When set for continuity (CONT), it can be used as a cable tester. It can also be used to test ohm (resistance) and ampere (amp, current) levels.
Blank Screen on Bootup
Absence of video output during boot sequence. Could indicate cable or software issues.
Slow Performance
Although SATA drives can manifest slow performance, the causes and solutions for each type of drive vary widely.
OS Not Found
An error in which a computer cannot locate the OS to load it into the RAM.
Failure to Boot
An error in which a system cannot boot, possibly due to the BIOS/UEFI boot order, damage to operating system files, or other causes.
Drive Not Recognized
An error that takes place if a misconfiguration, a cable error, or another problem prevents the computer from detecting a drive.
BSOD
Blue screen of death; an error in which the screen background is blue (or sometimes black) with the error message in white text.
Causes of failure to boot errors
Boot sequence does not specify system hard disk, or lists system hard disk after other drives with nonbootable media: Use the Boot Sequence dialog in the system BIOS to configure the hard disk as either the first boot device or the second boot device, after the optical drive or USB. If a USB flash drive is listed as the first boot device and the system is started with a nonbootable USB flash drive connected, the system boot process will stop and display a boot error. CMOS settings have been corrupted and system cannot find a bootable drive: Reconfigure the CMOS settings, specify the system drive as a boot drive, and restart the system. Replace the battery if the settings continue to be corrupted. The BCD (boot configuration data) store used by Windows to control disk booting has been corrupted
Failure to Boot can caused by
Boot sequence does not specify system hard disk, or lists system hard disk after other drives with nonbootable media: Use the Boot Sequence dialog in the system BIOS to configure the hard disk as either the first boot device or the second boot device, after the optical drive or USB. If a USB flash drive is listed as the first boot device and the system is started with a nonbootable USB flash drive connected, the system boot process will stop and display a boot error. CMOS settings have been corrupted and system cannot find a bootable drive: Reconfigure the CMOS settings, specify the system drive as a boot drive, and restart the system. Replace the battery if the settings continue to be corrupted. The BCD (boot configuration data) store used by Windows to control disk booting has been corrupted
Causes of drive not recognized errors
Bus-powered USB hard disk not recognized: A bus-powered USB 2.0 or USB 3.0/3.1 hard disk needs 500mA of power to run (and some hard disks temporarily use more power to spin up). Some computers don't provide enough power in their root hubs (built-in USB ports) to support a bus-powered hard disk, and bus-powered hubs can provide only 100mA of power per port. Connect the drive to another port on a different root hub (each pair of USB ports is a root hub) or a self-powered USB hub, or use a Y-cable to pull power from two USB ports. Figure 5-21 illustrates a USB 3.0/3.1 Y-cable. USB or Thunderbolt drive not recognized: If the data cable between the drive and the port is loose, the drive will not be recognized. Reconnect the cable to both the drive and the port, and the drive should be recognized. If the drive is connected to a front-mounted port, make sure the port header is securely connected to the motherboard. SATA Hard Disk or SSD drive not recognized: Loose or missing power or data cables cause this problem. Shut down the computer, disconnect it from AC power, and reconnect power and data cables. If you use Y-splitters or converters to provide power to some drives, keep in mind that these can fail.
Resolving BSOD errors
Changing the system registry. Sometimes an automated registry repair tool can be downloaded to perform these changes for you. Whether you make the changes manually or automatically, back up the registry first! Removing a newly added component. For example, in the case of the error shown in Figure 5-11, removing a recently added memory module solved the problem. Replacing components such as memory. Upgrading an application. Downloading and installing a hotfix for your operating system.
Continuous Reboots
Check Power Good wire voltage maybe too high or too low. If Windows is configured to reboot when a STOP error occurs, the system will continuously reboot until the error is resolved
improve slow performance with SSDs
Connecting the drive to a slow SATA host adapter: Early SSDs were designed for 3Gbps SATA interfaces, but most recent models support the faster 6Gbps interface. When using an SSD on a system with a mixture of 3Gbps and 6Gbps SATA ports, be sure to use the 6Gbps ports. The partition may be misaligned: Windows automatically creates the first partition on an SSD so that it is on a page boundary to provide maximum performance. However, if you do not use the entire SSD for a single partition, additional partitions might be misaligned (starting in the middle of a page rather than on a page boundary). Misaligned partitions cause slow read/write/reallocate performance. Instead of using Disk Management to create additional partitions, use the command-line program DISKPART and specify Align=1024 as part of the Create partition command.
Unexpected Shutdowns
Dead short caused by loose screws, slot covers, or cards: Shut down the system and secure all metal components CPU overheating: Check fan speed for CPU heat sink; clean fan if it is dirty Power supply overheating: Check the power supply fan and clean it if possible; replace the power supply with a higher wattage-rated unit if problem persists. Power supply failure:Test the power supply to verify proper operation
S.M.A.R.T. Errors
Drive temperature Read retries Slow spin up Too many bad sectors
STOP Errors
Errors that can occur either during startup or after a system is running; such errors halt systems by default. Also known as blue screen of death (BSOD) errors.
S.M.A.R.T. Errors
Hard disk failure is imminent A hard drive in your system reports that it may fail Smart failure imminent, back up your data
Blank Screen on Bootup (Caused by motherboard) continue
If an HDMI, miniHDMI, DisplayPort, or miniDisplayPort cable is not completely plugged into the video port or display, the screen might be blank. Completely insert the cable into the port. If input cables and display input settings check out but the screen is still blank, shine a flashlight on the screen to see if any text or graphics are visible. If you can see text or graphics with the flashlight, the backlight on the display has failed. On an LCD-CCFL, check the inverter first. Inverter failures are much more common than backlight failures, and inverters are relatively easy to replace. On an LED display, check the LED driver board first. Keep in mind that LCD and LED display modules for laptops or complete displays for desktops are far less expensive today than they used to be, and it might make sense to replace the entire display assembly.
USB or Thunderbolt drive not recognized
If the data cable between the drive and the port is loose, the drive will not be recognized. Reconnect the cable to both the drive and the port, and the drive should be recognized. If the drive is connected to a front-mounted port, make sure the port header is securely connected to the motherboard.
investing smoke or burning smells
If you can see smoke or smell a burning odor with a chemical overtone coming from the power supply's outside vent, your power supply has died. This odor can linger for weeks. Sadly, when a power supply blows up like this, it can also destroy the motherboard, bus-powered USB devices connected to the computer, and other components. Smoke or a burning smell inside the system can also be caused by failing capacitors. The capacitors are cylindrical components near the CPU socket on the motherboard or inside the power supply. If capacitors fail or other components burn up, replace the component.
Blank Screen on Bootup (Caused by motherboard)
If you have only one display, plugging the video cable into an inactive video port on a system will cause a blank screen If a display with two or more inputs is not configured to use the correct cable, the display will be blank. Use the display's push button controls to select the correct signal input. If a DVI or VGA cable is not tightly attached to the video port or display, the screen might be blank. Secure the cable.
Causes of BSOD Errors
Incompatible or defective hardware or software: Start the system in Safe mode and uninstall the last hardware or software installed. Acquire updates before you reinstall the hardware or software. Exchange or test memory. Run SFC/scannow to check for problems with system files. Registry problems: Select Last Known Good Configuration (Windows 7) and see whether the system will start. System Restore can also be used to revert the system and registry to an earlier state Viruses: Scan for viruses and remove any that are discovered. Miscellaneous causes: Check the Windows Event Viewer and check the System log. Research the BSOD with the Microsoft Support website.
Indicator Lights
Indicator lights on the front or top of most desktop computers display power and hard drive activity. If these lights go out but the system is otherwise working properly, check the motherboard connection for the indicator lights.
Resolving indicator light issues
Indicator lights on the front or top of most desktop computers display power and hard drive activity. If these lights go out but the system is otherwise working properly, check the motherboard connection for the indicator lights.
Intermittent Device Failure
Intermittent failures of USB bus-powered devices usually happen because these devices draw power from the system's power supply via the USB port.
causes of macOS unresponsiveness
Lack of system RAM: If a macOS device frequently displays the pin wheel and the device's RAM can be upgraded, do so. Less than 10 percent free space on the macOS system drive: Free space is used as a swapfile to substitute for RAM. Remove unwanted apps and save data to external or cloud storage to free up space. Some experts suggest keeping at least 20 percent of the macOS system drive free. Damaged application: Run Disk Utility using the Verify Disk Permissions option (in OS X versions prior to El Capitan).
Log Entries and Error Messages
Logs on a device are records kept to track the history of what has happened on the device. They record the tasks the computer has performed, people who have logged in or out, applications opened, and so on. Error messages tell when something went wrong (for example, a device failure or authentication rejection)
SATA Hard Disk or SSD drive not recognized
Loose or missing power or data cables cause this problem. Shut down the computer, disconnect it from AC power, and reconnect power and data cables. If you use Y-splitters or converters to provide power to some drives, keep in mind that these can fail.
Resolving fan spinning errors
Make sure the main ATX and 12V ATX or EPS power leads are securely connected to the appropriate sockets. Make sure the CPU and memory modules are securely installed in the appropriate sockets.
Causes of OS not found errors
Nonbootable disk in USB Drive: If a USB drive is listed before the hard disk in the boot sequence and it contains a nonbootable disk, the computer displays an error message that it couldn't find the operating system. Remove the USB flash drive and restart. Boot sequence doesn't list hard disk: Restart the computer, start the BIOS setup procedure, and make sure the hard disk is listed as a bootable drive and is listed before options such as network boot. Incorrect installation of another operating system: Windows automatically sets up its own boot manager for access to more than one Windows version if you install the older version of Windows first, followed by the later version. However, if you install a newer version first and install an older version later or install a non-Windows OS later, you cannot access the newer Windows version unless you install a custom boot manager.
OS Not Found (casued by)
Nonbootable disk in USB Drive: If a USB drive is listed before the hard disk in the boot sequence and it contains a nonbootable disk, the computer displays an error message that it couldn't find the operating system. Remove the USB flash drive and restart. Boot sequence doesn't list hard disk: Restart the computer, start the BIOS setup procedure, and make sure the hard disk is listed as a bootable drive and is listed before options such as network boot. Incorrect installation of another operating system: Windows automatically sets up its own boot manager for access to more than one Windows version if you install the older version of Windows first, followed by the later version. However, if you install a newer version first and install an older version later or install a non-Windows OS later, you cannot access the newer Windows version unless you install a custom boot manager.
When Should You Check S.M.A.R.T. Attributes?
Normal condition test your hard disks every month On a portable or laptop hard disk, I recommend checking twice a month because these drives are in greater danger of being physically damaged or overheating.
Read/Write Failure (continue 2)
Overheated hard disk: The faster a hard disk turns (that is, the higher the RPM), the more likely it is that overheating will take place, especially if airflow is restricted. To prevent overheating, install a cooling fan in front of the 3.5-inch drive bays used for a hard disk(s) and make sure it pulls air into the PC. If you have two or more drives stacked on top of each other with limited airflow, move drives to other drive bays to improve airflow. Overheated CPU or chipset: Overheated CPU, chipset or other components can cause read/write failures. Double-check case fans, the power supply fan, and the CPU's and chipset's heat sinks. Remove dust and dirt from air intakes and fans. Remove loose or failed heat sinks, remove old thermal grease, and reassemble them with properly applied thermal grease.
Causes of System Overheating
Overloading Fan failure Inadequate airflow outside the system Inadequate airflow inside the system Dirt and dust
Read/Write Failure (continue)
Physical damage to the drive: Dropping any magnetic storage drive can cause damage to read/write heads and platters. The drive may start to make noise or might not spin up at all. Damaged cables: SATA cables are often included with new motherboards and are inexpensive to purchase. Swapping cables is an easy first step that often solves problems. Damaged SATA host adapter on motherboard: Most late-model motherboards have several SATA ports; if swapping a SATA cable doesn't solve a problem, use the original cable in a different SATA port on the motherboard.
Resolving continuous reboot issues
Power Good voltage is too high or too low: When the Power Good line to the motherboard carries a voltage that is too high or too low, the processor resets, shutting down the system and rebooting it. Test the power supply voltage levels; replace the power supply if Power Good tests out of specifications. See the "Multimeter" section, later in this lesson, for details. Windows configuration setting for dealing with STOP errors (blue screen of death, or BSOD, errors): If Windows is configured to reboot when a STOP error occurs, the system will continuously reboot until the error is resolved. To leave a STOP error message onscreen until you decide to restart the system, clear the Automatically Restart check box in the System Failure setting in the Startup and Recovery section of Advanced System Properties, as illustrated in Figure 5-4. This is accessed via Control Panel > System, > Advanced System settings. Under Startup and Recovery, select Settings.
Proprietary Crash Screens (BSOD/Pin Wheel)
Proprietary crash screens such as the Windows STOP error (blue screen of death, or BSOD) or the macOS pin wheel can be caused by operating system, application, or hardware errors.
RAID Stops Working
RAID 0: Determine which drive has failed. Replace it and follow the vendor's recommendations to re-create the array. Restore the latest backup. Any data that has not been backed up is lost. RAID 1, RAID 10, and RAID 5: Determine which drive has failed. Replace it. Follow the procedures provided by the RAID vendor to rebuild the array.
Resolving RAID failures
RAID 0: Determine which drive has failed. Replace it and follow the vendor's recommendations to re-create the array. Restore the latest backup. Any data that has not been backed up is lost. RAID 1, RAID 10, and RAID 5: Determine which drive has failed. Replace it. Follow the procedures provided by the RAID vendor to rebuild the array.
RAID Not Found
RAID function disabled in system BIOS: Reconfigure SATA ports used for RAID as RAID and restart the system. Power or data cables to RAID drives disconnected: Reconnect cables to RAID drive(s) and restart the system.
improve slow performance with SATA hard disks
Reduced-performance configuration of 3Gbps or 6Gbps drives: Some 3Gbps and 6Gbps SATA drives are jumpered to run at the next slower rate to enable compatibility with older host adapters. Remove the speed-reduction jumper when it is not needed; see drive documentation for details. Figure 5-20 illustrates a jumper on a 3Gbps drive that limits its performance to 1.5Gbps. Using a 3Gbps cable with a 6Gbps drive and host adapter: SATA cables made for 6Gbps drives can also be used with slower speeds.
Improving slow transfer speeds on SATA hard disks
Reduced-performance configuration of 3Gbps or 6Gbps drives: Some 3Gbps and 6Gbps SATA drives are jumpered to run at the next slower rate to enable compatibility with older host adapters. Remove the speed-reduction jumper when it is not needed; see drive documentation for details. Figure 5-20 illustrates a jumper on a 3Gbps drive that limits its performance to 1.5Gbps. Using a 3Gbps cable with a 6Gbps drive and host adapter: SATA cables made for 6Gbps drives can also be used with slower speeds. SATA host adapter configured for IDE or emulation mode: SATA host adapters can be configured by the system BIOS (conventional or UEFI) to run in IDE (emulation) mode, RAID mode, or AHCI mode. Use AHCI mode to enable full performance because this mode supports native command queuing (NCQ) and other advanced features. SATA host adapter configured to run at reduced speed: SATA host adapters on some systems can be configured to run at different speeds, such as 6.0Gbps, 3.0Gbps, or Auto. Select 6.0Gbps when using a 6.0Gbps drive and cabling. To enable the drive and host adapter to auto-negotiate the correct speed, select Auto.
improve slow performance with SATA hard disks (continue)
SATA host adapter configured for IDE or emulation mode: SATA host adapters can be configured by the system BIOS (conventional or UEFI) to run in IDE (emulation) mode, RAID mode, or AHCI mode. Use AHCI mode to enable full performance because this mode supports native command queuing (NCQ) and other advanced features. SATA host adapter configured to run at reduced speed: SATA host adapters on some systems can be configured to run at different speeds, such as 6.0Gbps, 3.0Gbps, or Auto. Select 6.0Gbps when using a 6.0Gbps drive and cabling. To enable the drive and host adapter to auto-negotiate the correct speed, select Auto.
S.M.A.R.T.
Self-Monitoring, Analysis, and Reporting Technology; a technology that monitors internal hard disks and warns of impending failure.
Troubleshooting intermittent failures of USB-powered devices
Step 1. Shut down the device (and the computer, if the device is internal) and replace the data cable with a known-working replacement. If a USB device is plugged into a front-mounted USB port or a USB port on a card bracket, check the USB header cable connections to the motherboard. Step 2. Turn on the device or computer. Step 3. Test the device over time. If the device works correctly, the problem is solved. Step 4. If Step 1-3 didn't resolve the problem, use the original data cable and try plugging it into a different internal or external port. Repeat Steps 2-3. Step 5. Try Steps 1-4 again, but this time use a replacement power connector or AC adapter. Step 6. When you find the defective component, the problem stops. If the problem is not resolved with different data cables, connectors, or power supplies/AC adapters, the device itself needs to be replaced.
step-by-step power supply troubleshooting
Step 1. Smell the power supply's outside vent. If you can detect a burning odor, the power supply has failed. Replace it. Step 2. Check the AC power to the system; a loose or disconnected power cord, a disconnected surge protector, a surge protector that has been turned off, or a dead AC wall socket will prevent a system from receiving power. If the wall socket has no power, reset the circuit breaker in the electrical service box for the location. Step 3. Check the AC voltage switch on the power supply; it should be set to 115V for North America. If the switch is set to 230V, turn off the power, reset the switch, and restart the system. Note that many desktop computer power supplies no longer require a switch selection because they are autoswitching. Step 4. If the system is older and uses a PS/2 mouse or keyboard, check the connectors; a loose keyboard connector could cause a short circuit. Step 5. Turn off the system, disconnect power, and open the system. Verify that the power leads are properly connected to the motherboard. Connect loose power leads, reconnect power, and restart the computer. Step 6. Check for loose screws or other components, such as loose slot covers, modem speakers, or other metal items that can cause short circuit. Correct them and retest. Step 7. Remove all expansion cards and disconnect power to all drives; restart the system and use a power supply tester or a multimeter to test power to the motherboard. For more details, see the "Multimeter" section, later in this lesson. Step 8. If the power tests within accepted limits with all peripherals disconnected, reinstall one card at a time and check the power. If the power tests within accepted limits, reattach one drive at a time and check the power. Step 9. If a defective card or drive has a dead short, reattaching the defective card or drive should stop the system immediately upon power-up. Replace the card or drive and retest. Step 10. Check the Power Good line at the power supply motherboard connector with a multimeter or a power supply tester.
improve slow performance with SSDs (continue)
The TRIM command is not enabled for the drive: If the drive does not support TRIM, you must periodically run a utility provided by the drive vendor to reallocate deleted drive sectors. If the drive supports TRIM and you are using it with Windows 7/8/8.1/10, Windows needs to be optimized for use with SSDs. Not optimizing the operating system for use with SSDs: Although Windows 7, 8/8.1, and 10 are designed to disable SuperFetch, defragment, and other services that can slow down SSD performance, Windows does not always detect an SSD as an SSD. Use the SSD Tweaker utility (Elpamsoft) to configure Windows for maximum performance with SSDs.
System Lockups
The apparently random freezing of an application process. Typically caused by the corruption of memory contents but repairable by using System File Checker.
Attempts to Boot to Incorrect Device
The boot sequence listed in BIOS settings determines which drives can be used to start the computer and in what order. If a non-bootable drive is in the boot sequence, the system will not start. For example, if a USB drive is listed first, and a non-bootable USB drive is plugged in, the system will not start. mChange the boot order to list the location where the operating system is installed (such as the system hard drive) and restart the computer
BIOS Time and Setting Reset
The underlying cause is nearly always a dead CMOS battery on the motherboard
POST Error Messages
These messages can indicate problems with memory, keyboards, hard drives, and other components.
Troubleshooting Methodology
Troubleshooting Methodology 1.Identify the problem. 2.Establish a theory of probable cause. 3.Test the theory to determine the cause. 4.Establish a plan of action to resolve the problem and implement the solution. 5.Verify full system functionality and, if applicable, implement preventive measures. 6.Document findings, actions, and outcomes
Items monitored by s.m.a.r.t
Typical items monitored include: Drive temperature Read retries Slow spin up Too many bad sectors
Power Supply Tester
You can use a power supply tester to determine if a power supply is working. The power supply does not need to be removed from the computer for testing.
POST code beeps
are used by many BIOS versions to indicate either fatal or serious errors
