PC HARDWARE TROUBLESHOOTING

PC HARDWARE

TROUBLESHOOTING

BEATRICE MICHAEL
NURSYAMIMI AFIQAH SASTRA
NURZAIHAN ISMAWI

PC HARDWARE

TROUBLESHOOTING

i

COPYRIGHT

Published By :
POLITEKNIK MUKAH
KM7.5, JALAN OYA
96400 MUKAH, SARAWAK

Tel : +6084-874001
Fax : +6084-874005
Website: https://www.pmu.edu.my/v5/

PC Hardware Troubleshooting

ISBN: 000-000-000

Authors:
1.BEATRICE MICHAEL
2.NURSYAMIMI AFIQAH SASTRA
3.NURZAIHAN ISMAWI

2021 edition

All rights reserved. This publication is protected by copyright and
permission should be obtained from the publisher prior to any
prohibited reproduction, storage in a retrieval system, or
transmission in any form or by any means, electronic, mechanical,
photocopying, recording or likewise.

ii

PREFACE

Students will learn hardware troubleshooting techniques used to
identify and rectify computer faults.

iii

THE AUTHORS

The authors of the book are currently in-service lecturers
of Politeknik Mukah, Sarawak.

BEATRICE MICHAEL
NURSYAMIMI AFIQAH SASTRA
NURZAIHAN ISMAWI

iv

PC HARDWARE TROUBLESHOOTING

STNETNOC FO ELBAT TITLE PAGE i
COPYRIGHT ii
PREFACE iii
THE AUTHORS iv

TROUBLESHOOTING PROCESS STEPS 3

Introduction To Troubleshooting 3
Data protecting 4

Identify The Problem 5

Establish a theory of probable course 6
Test the theory to determine cause 7

Establish a Plan Of Action to resolve the problem 8
and implement the solution

Verify full system functionality and if applicable, 9
implement preventive measures

Document findings, actions and outcomes 10

TROUBLESHOOT PROBLEMS RELATED TO PC 11
HARDWARES

Troubleshooting Hard Drives Issues 12

Troubleshooting RAID Arrays Issues 14

Troubleshooting Motherboards Issues 16
Troubleshooting RAM Issues 18

Troubleshooting CPUs Issues 20

Troubleshooting Power Supply Issues 21

TROUBLESHOOT VIDEO, PROJECTOR AND DISPLAY 23
ISSUES

TROUBLESHOOT COMMON MOBILE DEVICE ISSUES 27

Mobile Device Overheating 28

Disassembling Processes for Proper Reassembly 30

TROUBLESHOOT COMMON WIRED AND WIRELESS 31
NETWORK PROBLEMS

REFERENCES v

v

PC HARDWARE

TROUBLESHOOTING

“IF I HAD AN HOUR TO SOLVE
A PROBLEM, I’D SPEND 55 MINUTES ON THE PROBLEM AND 5

MINUTES ON THE SOLUTION.” -ALBERT EINSTEIN

LEARNING OUTCOME

PC HARDWARE TROUBLESHOOTING

1 Understand troubleshooting process steps.
2 Understand to troubleshoot hard drives and RAID arrays

and problems related to motherboards, RAM, power.

3 Understand to troubleshoot video, projector, and display
issues.

4 Understand to troubleshoot common mobile device
issues.

5 Understand to troubleshoot common wired and wireless
network problems.

2

PC HARDWARE TROUBLESHOOTING

TROUBLESHOOTING PROCESS
STEPS

Introduction To Troubleshooting

The aims of troubleshooting are to resolve physical and/or logical
problems and issues within computing hardware. Hardware
troubleshooting is the process of reviewing, diagnosing, and
identifying operational or technical issues within a hardware device
or equipment. (www.technopedia.com)

Step

1

Identify the problem

Follow an organized and Step
logical procedure.
Eliminate variables one at 2
a time.
Troubleshooting is a skill Establish a theory of
that is refined over time. probable course
The first and last steps
involve effectively Step Test the theory to
communicating with the determine cause
customer. 3
Step
Step
Establish a Plan Of 4
5
Action to resolve the

problem and implement

the solution

Verify full system Step
functionality and if
applicable, implement 6
preventive measures

Document findings,
actions and outcomes

3

PC HARDWARE TROUBLESHOOTING

Data Protecting

Before troubleshooting problems, always follow the necessary
precautions to protect data on a computer.
If unsure that a backup has been done, do not attempt any
troubleshooting activities until the following are verified:

Date of the last backup
Contents of the backup
Data integrity of the backup
Availability of all backup media for data restore
If no backup can be created, ask a customer to sign a release
form.

4

PC HARDWARE TROUBLESHOOTING

Step

1

Identify The Problem

During the troubleshooting process, gather as much information
from the customer as possible but always be respectful. Use the
following strategy during this step:

QUESTION THE USER

1 Ask the person who reported the problem
detailed questions about the issue.

IDENTIFY ANY CHANGES MADE TO THE COMPUTER

2 Look at the computer. See if any new hardware
has been installed or plugged in.

REVIEW LOG FILES

3 Review any log files that you have access to that
can tell you more information about the problem.

INQUIRE AS TO ANY ENVIRONMENTAL OR INFRASTRUCTURAL CHANGE

4 Perhaps there was a change on the computer
network, or a new authentication scheme is in place.

REVIEW DOCUMENTATION

5 Your company might have electronic or written
documentation that logs past problems and

solutions.

5

PC HARDWARE TROUBLESHOOTING

Step

2

Establish a theory of probable course

Create a list of the most common reasons why the error would
occur. Start with the easiest or most obvious causes at the top.

1 Device is powered off

Power switch for an outlet is turned off

2

3 Surge protector is turned off

Loose external cable connections

4

Non-bootable disk in the designated boot drive

5

6 Incorrect boot order in BIOS setup

6

PC HARDWARE TROUBLESHOOTING

Step

3

Test the theory to determine cause

Determine the exact cause by testing the theories of probable cause
one at a time, starting with the quickest and easiest. After
identifying the exact cause of the problem, determine the steps to
resolve the problem. If the exact cause of the problem has not been
determined after all theories have been tested, establish a new
theory of probable causes and test it.

Common steps to determine causes :

1 Ensure the device is powered on

2 Ensure the power switch for an outlet is turned on

3 Ensure the surge protector is turned on

4 Ensure external cable connections are secure

5 Ensure that the designated boot drive is bootable

6 Verify the boot order in BIOS setup

7

PC HARDWARE TROUBLESHOOTING

Step

4

Establish a Plan Of Action to resolve the

problem and implement the solution

After the exact cause of the problem is determined, establish a plan
of action to resolve the problem and implement the solution.
Sometimes quick procedures can determine the exact cause of the
problem or even correct the problem.
If no solution is achieved in the previous step, further research is
needed to implement the solution :

Helpdesk repair logs

1

2 Other technicians

3 Manufacturer FAQ websites
4 Technical websites

5 News groups

6 Computer manuals

7 Device manuals

8 Online forums

9 Internet search

8

PC HARDWARE TROUBLESHOOTING

Step

5

Verify full system functionality and if

applicable, implement preventive

measures

Verify full system functionality and implement any preventive
measures if needed. Ensure that you have not created another
problem while repairing the computer.

1 Reboot the computer

2 Ensure multiple applications work properly

3 Verify network and internet connections

Print a document from one application

4

5 Ensure all attached devices work properly

6 Ensure no error messages are received

9

PC HARDWARE TROUBLESHOOTING

Step

6

Document findings, actions and
outcomes

Discuss the solution with the customer. Have the customer confirm
that the problem has been solved.

Document the process:

1 Problem description

2 Steps to resolve the problem

3 Components used in the repair

10

PC HARDWARE TROUBLESHOOTING

TROUBLESHOOT PROBLEMS
RELATED TO PC HARDWARE

THE HARDWARE TROUBLESHOOTING
There are lots of best practice approaches to troubleshooting
hardware you can use to fix the issues. In this lesson, we'll show you
some basic techniques to try when troubleshooting, as well as how
to solve common problems you may encounter.
The list of troubleshooting to be discussed are as follows:

1.Troubleshooting hard drives issues
2.Troubleshooting RAID Arrays issues
3.Troubleshooting motherboards issues
4.Troubleshooting RAM issues
5.Troubleshooting CPUs issues
6.Troubleshooting power supply issues

11

PC HARDWARE TROUBLESHOOTING

Troubleshooting Hard Drives Issues

1.BIOS does not “see” the drive: If the BIOS doesn’t recognize the
drive you have installed, you can check a few things.
First, make sure the power cable is firmly connected and
oriented properly.
Next, make sure SATA data cables are fully seated in the ports
and weren’t accidentally installed upside down; if you find
one that was, consider replacing it because it might be
damaged due to incorrect installation.

2.Windows do not “see” a second drive: There are several reasons
why Windows might not see a second drive. Maybe a driver
needs to be installed for the drive or for its controller.

3.Other missing/corrupted files: Missing or corrupted files could
be the result of hard drive failure, operating system failure,
malware infection, user error, and so on.
If this happens more than once, be sure to back up the rest of
the data on the drive, and then use the preventative methods
mentioned previously, especially defragmenting and
scanning for malware.

4.Noisy drive/lockups: If your SATA magnetic disk drive starts
getting noisy, it’s a sure sign of impending drive failure.
Need to connect the drive to another computer immediately
and copy the data to a good drive.

12

PC HARDWARE TROUBLESHOOTING

hard drives will fail, so it is

important to make backups


of your data. The backup

media of choice will vary


depending on the

organization. It could be the

cloud, a secondary system,


DVD-ROM discs, even USB

flash drives. It differs based


on the scenario.

Figure 1: Troubleshooting Hard Drives Issues

13

PC HARDWARE TROUBLESHOOTING

Troubleshooting RAID Arrays Issues

They might stop working or the OS could have trouble finding them.
If you see an issue like this, check whether the hard drives are
securely connected to the controller and that the controller (if an
adapter card) is securely connected to the motherboard. Also, if you
use a RAID adapter card or external enclosure, and the motherboard
also has built-in RAID functionality of its own, make sure you disable
the motherboard RAID within the BIOS—it could cause a conflict.
Verify that the driver for the RAID device is installed and updated.
Finally, check if any of the hard drives or the RAID controller has
failed. If a RAID controller built into a motherboard fails, you will
have to purchase a RAID adapter card.

14

PC HARDWARE TROUBLESHOOTING

To configure Intel RAID a technician needs to press CTRL + I when
the system first boots up, perhaps even before the BIOS on some
systems. From there, the RAID array can be configured as shown in
the picture. There is a RAID 1 Mirror, but the status is “Degraded”.
That means that the array has failed, or has been deconstructed in
some way.

Figure 2: RAID 1 Mirror

One way to check the status of a
RAID array is to use S.M.A.R.T. For
example, in picture you can see
the S.M.A.R.T. information screen
for one of the disks in a RAID 1
mirror of a NAS device.

Figure 3: S.M.A.R.T information Screen

15

PC HARDWARE TROUBLESHOOTING

Troubleshooting Motherboards
Issues

1.First and probably the most common of these rarities are
UEFI/BIOS firmware issues.
Need to flash the motherboard’s BIOS to the latest version.
For example, a new CPU or RAM might not be recognized at
the correct clock speeds.
An adapter card might not be seen properly. Or perhaps
Windows isn’t working as it should be with the hardware in
the system.
Updating the BIOS can fix many of these issues.

2.Electrostatic discharge (ESD) and other electrical issues.
These might present themselves intermittently.
For example, the computer reboots out of nowhere or you
receive random stop errors, also known as Blue Screens of
Death (BSODs).
Swap out the motherboard with a known good one to see if
the issue happens again when running through the same
processes.
Be sure to use a surge suppressor or uninterruptible power
supply (UPS) to protect your equipment and, of course,
implement antistatic measures whenever you work inside a
system.

16

PC HARDWARE TROUBLESHOOTING

3. Component failures.
It is possible that a single component of the motherboard (for
example, the SATA controller) can fail, but the rest of the
motherboard works fine.
To fix a problem such as a SATA controller failure, a separate
PCIe SATA controller card can be purchased.
Then can connect the hard drives to the new controller and
disable the original integrated SATA controller in the BIOS.

4. Manufacturing defects and failed motherboard components.
Printed circuit boards (PCBs), such as motherboards, are
mass-produced at high speeds.
Problems might be found immediately when receiving a
motherboard.
If you suspect a manufacturing defect, you should return the
motherboard.
Motherboard component failure can also manifest itself over
time, such as in the form of distended capacitors.
This is when a capacitor becomes swollen and possibly leaks
electrolytic material; this bulging can cause the system to
unexpectedly restart or shut down, cause a BSOD, or cause
other errors.
The affected capacitor(s) should be replaced right away.

17

PC HARDWARE TROUBLESHOOTING

Troubleshooting RAM Issues

A lot of the issues are because a user has purchased and installed a
memory stick that is not compatible or is semi-compatible, with the
motherboard: wrong speed, incorrect capacity, improper
configuration, and so on.
Please check the RAM compatibility against the motherboard.

Figure 4: Troubleshooting RAM Issues

18

PC HARDWARE TROUBLESHOOTING

Here are some possible symptoms of a RAM issue and
corresponding troubleshooting techniques:

1.The computer will not boot/intermittently shuts down: If there
is no RAM in the computer, or if the RAM is damaged or not
installed securely, it can prevent the computer from doing
anything at all (aside from draining electricity from your AC
outlet).

2.BIOS indicates a memory error: The BIOS can indicate a memory
error through a gray message on the screen and a flashing cursor
or by beeping. If it beeps, you need to reference your
motherboard documentation for the specific beep codes.

3.Stop error, aka BSOD or Blue Screen of Death: This is a critical
system error that causes the operating system to shut down.
Most of the time, these are due to device driver errors (poor
code), but they can be associated with a physical fault in
memory.

Verify compatibility of
RAM with the

motherboard when
troubleshooting

19

PC HARDWARE TROUBLESHOOTING

Troubleshooting CPUs Issues

1.Always check the power first, just in case—the main power
connections and the 8 or 4-pin CPU power connection.

2.The fan is connected and functional: Some motherboards have
a safeguard that disables booting if the fan is defective or not
plugged in.

3.Check other major components: Remember that the CPU is a
part of a bigger system; one in which other components are
more likely to be the cause of many problems.

4.The heat sink is connected properly: Make sure that the heat
sink is flush with the CPU cap and that it is securely fastened to
the motherboard (or socket housing).

5.CPU is installed properly: Make sure it was installed flush into
the socket and that it was oriented correctly.

Figure 5: Troubleshooting CPU Issues

20

PC HARDWARE TROUBLESHOOTING

Troubleshooting Power Supply
Issues

Here are several of the issues that might encounter with power
supplies:

Fan failure
Fuse failure
Quick death
Slow death.
Your best friends when troubleshooting power supplies are going to
be a power supply tester, and your eyes and ears.
Always make sure that the power supply cable connects from the
power supply itself to a properly wired AC outlet properly before
troubleshooting further.

21

PC HARDWARE TROUBLESHOOTING

Check all of the internal power connections. Make sure they are
connected firmly. To test these connections, use a power supply
tester.
If there are error readings, error lights, no lights, or missing lights for
specific voltages on the tester, you should consider replacing the
power supply; or if it is modular, replace that particular power cable.
Remember that connections sometimes can be jarred loose inside
and outside the computer.
Check the IEC cord on both ends and all power connections inside
the computer. This includes the main motherboard connector as
well as the CPU, Molex, SATA, and PCIe connectors.
Any single loose connector can have “interesting” results on your
computer.

Figure 6: Troubleshooting Power Supply Issues

22

PC HARDWARE TROUBLESHOOTING

TROUBLESHOOT VIDEO,
PROJECTOR, AND DISPLAY

ISSUES

1. Connections
If nothing is showing up on the display, first make sure that
the monitor is plugged into the video card properly (and to
the correct video port), and then verify whether the monitor
is connected to the AC outlet and is powered on.
Check which video port the monitor is configured to use by
accessing the on-screen display (OSD) with the appropriate
button on the monitor.
If necessary, try removing the video card and reseating it
carefully. Poor connectivity of cables or the video card can
also cause screen flicker.

2.Power cycle the computer, display, and any power protection
equipment
Power cycling the equipment can fix all kinds of problems
and is an easy solution to implement.
Problems such as video memory (image retention) and stuck
pixels might be easily repaired by a power cycle of the
display, the computer, and any surge suppressor that the
equipment is plugged into.
You might also need to leave a display off for a couple of
hours to fix a video memory problem.

Figure 7: Troubleshooting display Issues

23

PC HARDWARE TROUBLESHOOTING

3. Check for an onboard video setting in the UEFI/BIOS
If you install a new video card to a computer that previously
used onboard video, always check that the onboard video
setting is disabled in the UEFI or BIOS.
It can conflict with the new video card. And, of course, be
sure to plug the monitor into the new video card—not the old
onboard connection.

4. Resolution and refresh settings
If the resolution was set too high or was set to a resolution
not supported by the monitor, you might get a distorted
image or no image at all.
Boot into low-resolution VGA mode or Safe Mode. This starts
the computer with a resolution of 640×480.
Then modify the resolution setting in the Screen Resolution
window.

5. Check the driver
Maybe the driver failed, or perhaps the wrong driver was
installed during installation, or maybe an update is necessary.
Driver failures could also be the cause of BSODs.

6. Check the version of DirectX
DirectX is a Windows technology that includes video,
animation, and sound components.
It helps a computer get more performance out of
multimedia, games, and movies.

24

PC HARDWARE TROUBLESHOOTING

7. Check the temperature threshold of the video card
High-end video cards are intensely used by gamers and
designers, and they can be the hottest component in a
computer.
If the temperature surpasses the safeguards in place, it might
cause the card to throttle back the GPU speed.

8. Use software to check and repair stuck or dead pixels
When a single-pixel fails, it can be irritating.
But there are third-party software programs that can be used
to identify stuck pixels and possible dead pixels and attempt
to fix them (search “LCD repair,” “dead pixel repair,” or similar
terms).
Always try power-cycling the device as well. If you can’t repair
the stuck or dead pixel, you might have to bring the display
in for repair or for replacement, or if it is a laptop, replace it
yourself!

9. Calibrate the monitor
If you see artifacts (image distortions) or you notice incorrect
color patterns or the display just doesn’t seem to look quite
as good as it used to, try calibrating the monitor by either
resetting it with the OSD or by adjusting the contrast,
brightness, and color level.
Also, try adjusting the color depth in Windows, and check the
screen resolution.

25

PC HARDWARE TROUBLESHOOTING

10. Use a filter on the monitor
Sometimes a user will complain of eye strain. This might not
be a video issue at all; it could be due to glare. Consider using
an antiglare filter.

11. Check for newly installed applications
New applications could cause the display to malfunction or
stop working altogether. Check the application
manufacturer’s website for any known hardware
compatibility issues.

12. Check inside the computer
Check whether the card is seated properly. In areas in which
the temperature and humidity change quickly, the card
could be unseated due to thermal expansion and
contraction.
If the computer was moved recently, it could cause the card
to come out of the slot slightly.
Verify that the power connections and other cables are not
loose.
Check all other connections inside the PC to make sure it isn’t
a video problem.

26

PC HARDWARE TROUBLESHOOTING

TROUBLESHOOT COMMON
MOBILE DEVICE ISSUES

1.The display might look dim.
This could be because the brightness level is too low in the
display settings.
Or it could be that automatic brightness was enabled and
perhaps it doesn’t react well in highly lit areas.
Or perhaps auto-brightness isn’t calibrated properly; perhaps
it was initially enabled in a very bright (or very dark)
environment.
To recalibrate the device’s light sensor, turn off auto-
brightness and then go to an unlit room and set the
brightness to the lowest setting.
Finally, turn auto-brightness back on and leave the unlit
room. The device should now make better use of its light
sensors and auto-brightness should function better.

2.No display or what appears to be no display.
This could simply be that the device is in sleep mode (or off).
Take the device to a dark area to fix it or hold it under a desk
or table to be able to see the screen until it is fixed.
The brightness might have been turned down by accident,
the user might have turned it down the night before
(because it was dark out), or a virus could affect the slider
that controls the brightness.
It could be that the display connection is loose, or the display
is damaged. The device will have to be opened to
repair/replace the display.

27

PC HARDWARE TROUBLESHOOTING

Mobile Device Overheating

Overheating can be caused by a number of things:
Poorly written applications
Excessive use of applications
Excessive browsing
Old batteries / damaged batteries
The simple fact that the device is very small and that there is an
inherent lack of ventilation

A user can do the following to increase the lifespan of their battery:
Avoid draining the battery: Charge the device often, before it
gets too low. The more the battery is discharged below 50
percent, and especially below 10 percent, the less shelf life it will
have in general.
Conserve power: Set sleep mode to 1 minute or less. Decrease
brightness. Disable or remove unnecessary functions and apps.
Restart the phone at least once a day to stop any running apps
(this is a big power saver). Consider putting the device into
airplane mode at night.
Keep the device away from heat sources: For example, if the
device is mounted near a vehicle’s air vent during the dead of
winter, it’s bound to run hot. Sarcasm aside, this can actually
cause battery wear and damage over time. Keep it out of direct
sunlight, too, if at all possible.
Turn off the mobile device when not in use

28

PC HARDWARE TROUBLESHOOTING

Don’t bang or throw the device: Not only can a user break the
device completely, but dropping, throwing, or banging the
device can damage the battery, which can cause it to overheat,
reduce the lifespan of the battery.
Select protective cases carefully: A protective case is a very
good idea (especially if you are prone to actions in the previous
bullet), but make sure it has good airflow. Sometimes these
cases can envelop the battery, causing it to overheat.
Clean your device: Every month or so, turn off the device, take it
out of the case, remove the battery (if it is removable), and clean
it (and the inside of the case) with a mix that is half isopropyl
alcohol and half water (applied to a dry, lint-free cloth).

29

PC HARDWARE TROUBLESHOOTING

Disassembling Processes for Proper
Reassembly

1. Document
good documentation aids inefficient planning,
proper testing, and insightful troubleshooting

Just like with bigger computers such as PCs, write as much
down as you can.
Take notes and make a little illustration
Organize any parts that have been removed
Document and label wires and cables and where they are
supposed to connect to.
Record what type of screws go where and store them
temporarily in an organized manner.
2. Make use of manufacturer resources, such as tech support via
phone or website, help forums, downloadable manuals in PDF
format, information on the disc, the list goes on.
3. Use appropriate hand tools when working with mobile devices
Make sure you are protecting against ESD—that means the
use of proper antistatic equipment.
Have the tools at the ready: miniature screwdrivers, shims,
spudgers, magnifying glass, mini-flashlight, multimeter and
other testing gear, SD and microSD card reader, and various
USB, Lightning, and other cables and adapters ready to hook
up the mobile device to a testing PC or laptop.

30

PC HARDWARE TROUBLESHOOTING

TROUBLESHOOT COMMON
WIRED AND WIRELESS
NETWORK PROBLEMS

It’s all about access to resources. If a resource—be it a data share or
printer, or whatever—is unavailable, then the user won’t be able to
get his or her work done. Efficiency decreases and the organization
loses money.
Resources can be broken down into two types:

Local resources—meaning ones on the LAN; and
Remote resources—ones that are beyond the LAN, possibly on
the Internet or another external network.
1.Local resources:

A user can’t browse the network or map network drives to
network shares, or connect to network printers, or access an
e-mail server on the LAN.
There are lots of examples, but the bottom line is this: if a
user can’t access local resources, then the network
connection needs to troubleshoot.

31

PC HARDWARE TROUBLESHOOTING

2. Internet-based resources:
If remote resources are not available to a user; for example,
websites, VPN connections, and streaming media services,
then it could be that the IP configuration (especially the
gateway and DNS settings) needs to be inspected and
possibly reconfigured.
If multiple users are having connectivity problems, then it
could be the gateway itself or the DNS server that needs to
be fixed (among other things).

3. No connectivity:
If a user complains of a problem connecting to the network
and you verify that there is indeed a problem, check that
patch cable first and verify there is a link light.
Make sure the user’s computer is actually connected to the
network.
If it appears to be a cable issue, use a patch cable tester or
cable certifier to test the cable.
If it isn’t a cable problem, make sure the network adapter is
enabled. If it’s a laptop and the user has wireless, check the
Wi-Fi switch or button.

32

PC HARDWARE TROUBLESHOOTING

4. Limited and intermittent connectivity:
If the problem is limited connectivity, attempt some pings.
First, ping the localhost to see if TCP/IP is functioning. If that
works, ping the router or another system on the network. If
that fails, then the user only has local connectivity.
Run an ipconfig /all and check the rest of the IP settings.

5. Slow transfer speeds:
If a user has dial-up and complains about slow transfer
speeds, it’s time to upgrade.
Even though dial-up can be tweaked for speed, it’s simply
easier to move up to DSL, cable, or fiber-based services.
Slow transfer speeds could also be caused by the network
equipment, patch cables, and network adapter.

6. Low RF signal:
A low radio frequency signal spells doom for wireless users.
The first thing to check is the distance of the computer from
the WAP.
Make sure the computer is within the appropriate range.

33

PC HARDWARE TROUBLESHOOTING

7. IP conflict:
An IP conflict message will pop up on the displays of both
Windows computers that are causing the conflict. Usually,
the first computer that used the IP address will continue to
function, whereas the second computer will not be able to
access the network.
The second computer will have to be reconfigured to a
different IP address and rebooted.
Reboot the first computer for good measure. IP conflicts
usually happen only when static IP addresses are being used.
If this is the case, consider using DHCP for all client
computers.

8. Link-local/APIPA address:
If a computer is showing an IPv4 link-local address such as
169.254.49.26 when you type ipconfig /all, it generally means
that the computer is attempting to obtain an IP address from
a DHCP server but is failing
IPv4 link-local addresses always start with 169.254. Microsoft
also uses the name Automatic Private IP Addressing (APIPA).
Usually, a link-local address is assigned internally, so the real
problem could be that the computer is not getting
connectivity to the network.
Check everything in the first bullet point. Also, consider using
ipconfig/release and /renew.
Finally, if these do not work, check the DHCP server to make
sure it is functional and available.

34

REFERENCES

Quentin. D. & Jon. B. (2019). CompTIA A+ Complete Study Guide: Exam Core
1220-1001 and Exam Core 2220-1002. John Wiley & Sons Inc. New York,
United States. (ISBN: 978-1-119- 51593-7)

Hajek. D. &. Herrera. C. (2019). Introduction to Computers, 2019 Edition.
Independently published. Amazon. (ISBN: 1091830002)

Cheryl. A. S. (2019), Complete CompTIA A+ Guide to IT Hardware and Software
Lab Manual. Upper Saddle River, United States: Pearson Education
(US). (ISBN: 0135380197)

Miller. M. (2019). Computer Basics Absolute Beginner's Guide, Windows 10
Edition (includes Content Update Program) 9th Edition. Que
Publishing. Seattle United State. (ISBN:0789754517)

MS PowerPoint Slide Notes, DFC10033 Introduction To Computer System(2021),
JTMK, PMU

DFC10033 Introduction To Computer System Course Outline(2021), JTMK, PMU
www.techcopedia.com
www.canva.com
https://quizizz.com/
https://www.ciscopress.com/
https://infraexam.com/it-essentials-7/

iv