WEBVTT



1

00:00:00.570 --> 00:00:01.800

<v ->In this section of the course,</v>



2

00:00:01.800 --> 00:00:02.880

we're going to talk all about



3

00:00:02.880 --> 00:00:04.680

how to troubleshoot hardware issues,



4

00:00:04.680 --> 00:00:08.130

including power issues, post issues, crash screens,



5

00:00:08.130 --> 00:00:10.530

cooling issues, physical component damage,



6

00:00:10.530 --> 00:00:11.610

performance issues



7

00:00:11.610 --> 00:00:14.220

and inaccurate system date and time issues.



8

00:00:14.220 --> 00:00:16.500

So, as we move into this section,



9

00:00:16.500 --> 00:00:18.420

we're going to be focused on domain five,



10

00:00:18.420 --> 00:00:20.130

hardware and network troubleshooting



11

00:00:20.130 --> 00:00:22.890

as we fully cover objective 5.2.



12

00:00:22.890 --> 00:00:25.830

Objective 5.2 states, given a scenario



13

00:00:25.830 --> 00:00:27.870

you must be able to troubleshoot problems



14

00:00:27.870 --> 00:00:31.740

related to motherboards, RAM, CPU and power.



15

00:00:31.740 --> 00:00:33.690

Now, one of the most common things that you're going to need



16

00:00:33.690 --> 00:00:36.030

to troubleshoot on a system is when that system



17

00:00:36.030 --> 00:00:37.860

fails to boot properly.



18

00:00:37.860 --> 00:00:39.360

Now, to question the obvious,



19

00:00:39.360 --> 00:00:41.730

we would first check is there any power issues,



20

00:00:41.730 --> 00:00:44.040

such as the system not being plugged into the wall outlet



21

00:00:44.040 --> 00:00:46.680

or the main board power connector coming loose



22

00:00:46.680 --> 00:00:49.140

or even a faulty power supply.



23

00:00:49.140 --> 00:00:50.880

Now, if all of that isn't the issue,



24

00:00:50.880 --> 00:00:53.850

then we're going to need to move on into the power on self test



25

00:00:53.850 --> 00:00:56.040

or the post to determine if there's a problem



26

00:00:56.040 --> 00:00:58.350

with one of our other hardware components.



27

00:00:58.350 --> 00:01:00.660

In addition to boot issues, sometimes a computer



28

00:01:00.660 --> 00:01:03.180

will fail to operate properly and it will crash



29

00:01:03.180 --> 00:01:05.010

if a component fails as well.



30

00:01:05.010 --> 00:01:08.130

For example, if one of your memory modules becomes faulty,



31

00:01:08.130 --> 00:01:10.320

this can cause a blue screen of death to occur



32

00:01:10.320 --> 00:01:13.620

and this happens inside of a Windows operating environment.



33

00:01:13.620 --> 00:01:15.780

As you're soon going to see in this section of the course,



34

00:01:15.780 --> 00:01:17.850

there are lots of potential hardware issues



35

00:01:17.850 --> 00:01:20.430

that you're going to encounter as a technician in the field.



36

00:01:20.430 --> 00:01:22.530

So, let's get started with our coverage



37

00:01:22.530 --> 00:01:24.210

of how to troubleshoot hardware issues



38

00:01:24.210 --> 00:01:25.710

in this section of the course.