-: In this section of the course,
we're going to talk all about
how to troubleshoot hardware issues,
including power issues, post issues, crash screens,
cooling issues, physical component damage,
performance issues
and inaccurate system date and time issues.
So, as we move into this section,
we're going to be focused on domain five,
hardware and network troubleshooting
as we fully cover objective 5.2.
Objective 5.2 states, given a scenario
you must be able to troubleshoot problems
related to motherboards, RAM, CPU and power.
Now, one of the most common things that you're going to need
to troubleshoot on a system is when that system
fails to boot properly.
Now, to question the obvious,
we would first check is there any power issues,
such as the system not being plugged into the wall outlet
or the main board power connector coming loose
or even a faulty power supply.
Now, if all of that isn't the issue,
then we're going to need to move on into the power on self test
or the post to determine if there's a problem
with one of our other hardware components.
In addition to boot issues, sometimes a computer
will fail to operate properly and it will crash
if a component fails as well.
For example, if one of your memory modules becomes faulty,
this can cause a blue screen of death to occur
and this happens inside of a Windows operating environment.
As you're soon going to see in this section of the course,
there are lots of potential hardware issues
that you're going to encounter as a technician in the field.
So, let's get started with our coverage
of how to troubleshoot hardware issues
in this section of the course.