12 hours 9 minutes
this is less than 15 dot to troubleshooting common hardware problems.
And this lesson. We're going to go over common hardware troubleshooting steps that you would find when you're dealing with customers or computers when you're dealing with an organization and what things to look for and what things to do to resolve those issues. So let's go ahead, Jeff, right and get started.
A lot of times you're gonna come across unexpected shutdowns. Computer just totally shuts down without being initiated by the user. This could be several things that this may happen, something suddenly the power computer powers down. You want to check the event viewer. The Avenger would have a lot of details and information about what may have happened
that shut down. It could have been something that happened because of a software installed earlier on, but the event viewer will be your first place that you want to go to checked exactly to see what may have happened. Also, this could be caused by heat related issues on some systems, like gaming systems that could be because of high C, P or graphics
and the system overheated.
Check your fans and your heat sinks to make sure proper airflow is going through that system again.
Unexpected shutdowns could be caused because of heat related issues. Also, hardware related issues was something recently installed on that device. Was there a recent video card or any other type device that may have caused the shutdown?
You want to check that device, make sure it's properly seated into the computer
because that could be the root of your issue
system Lock ups. Sometimes when you're working on a system and the system would lock up or freeze, what's it's commonly called as well similar to unexpected shutdowns. Again, you're troubleshooting steps here is you want to check to see if there was any new drivers or software that had been installed recently.
Low system resource is with some time cause this
if your computer is getting close to the maximum amount of RAM, but since starting a computer or hard drive space, this could cause it as well. Another thing that you want to check for is your hardware diagnostics, something computers have software built in them that once you get this issue
resolved or you get Thesis, Tum booted back up and you're able to work on it,
go to the hardware diagnostics and to tell you a lot in those logs in those entries. As far as what may have happened, you may see a pattern of failing hardware.
Post the power on self test
post would check hardware before the operating system boots. And if you remember from earlier messages, it will give you a series of beef codes or messages on the screen. It checks the primary system components to make sure that they are, in fact, working.
Now beep Ko's will differ by manufacturer, so you want to make sure that if you're experiencing a beat coat and your computer will not *** you, what you want to do is look at the manufactures documentation to see what that beep code translates to be.
Pop quiz From an earlier lesson. What device can you use to help diagnose beat codes on your systems?
I'll give you a moment to remember and think about it from an earlier lesson that we had.
The answer is
a power on self test card. If you remember, the postcard or the power on self test card can be plugged into the motherboard and were visually display the beep code or the code that your motherboard is trying to tell you what could be the problem.
Posting boot. Sometimes your computers will boot with a blank screen up. It will listen for beeps. I could be a bad video card. It could be a BIOS configuration issue when you have a blank screen and nothing on the screen.
Sometimes you may have time issues on your computer that you may notice that the time when your computer is wrong you may physically said it, but it may resort back, which you want to do is look at the sea. Most battery placed the battery on your motherboard. That could be an indicator that that battery is weakening and needs to be changed Also. Sometimes when you boot your computer,
it will boot to the incorrect drive. Check your BIOS boot order.
Sometimes. If if you've ever had a USB device plunged into your computer, it may try to boot off of that. And it's not booting to the proper order where the system operating system is. You want to check for any devices that you may have plugged in your system when it may be a CD ROM's or DVD in the drive
or a USB plugged into one of the USB ports.
Your system is detecting that, and because it's priori in the boot order, it's putting off that first versus the regular. See Dr Checked all those before you start trouble shooting in other directions. It could be a simple as a device left in the USB or the drive.
Sometimes your computer will continuously reboot. You know, one thing you need to check for is how far does the boot process go? Is it just getting to the bios and rebooting? Or is it getting to the operating system splash screen and then rebooting? It could be bad or corrupt drivers boot into safe mode.
Um, check to see if there was a new driver software installed.
See if there is a updated need that happen or did not happen. It stalled or it did not fully and set itself up.
One thing you can try also is the last known working configuration. Windows has the option to boot from the last known unfit working configuration. So therefore you to go to the last checkpoint and and operate from there.
It also could be bad hardware, Replace drivers or a move or replace drivers. Check your connections again. It could be a loose connection off hardware that was just recently installed.
Sometimes you have no power at all. Check the power outlet. First of all, make sure you're getting power from the outlet that's feeding your computer. Then from their work backwards to the computer itself, check the power supply. Could be a bat supply. Our power supply or failing power supply. Or
your power court in the power supply itself may be loose. And maybe coming out
some devices maybe powered on the motherboard. Some devices may not be when you powered up. Is there a light on the back of the system? Is the fans running? Can you hear fans? If you look inside the case, you may see lights on the motherboard, but nothing else is working.
It could be a bad mother board. You want to check your voltages. That's when you'll get your multi meter
out and start checking for different places on the motherboard. If it's a desktop computer, we've learned in previous lessons that there is a wireless a wiring harness that will feed the motherboard So you want to check with different points to make sure that components are ginning the amount of power that they're supposed to be.
Intermittent device failure? Sometimes the hard drive works are sometimes hard drive may fail. You know, Sometimes it could be a CPU Carter of video or memory that's doing that. It will work and it will not work. Check the installation. It could be loose. It could not be seen it properly. Receipt the device. Make sure it's fastened down. Everything is
snug and fit the way it's supposed to.
One thing after that, you may want to suspect is bad. Hardware could be a poor connection. Heat and vibration has shook it loose, or the at that point. If it's still not one of those device itself could be failing.
Indicator lights are another way of telling what's going on with your system. Of course, we discuss the post codes on the motherboard Power lights on the motherboard. You know the power lights will tell you if it it's powered on or not powered on the lights. The nick card can tell you if data is being sent or if data is not being sent
some devices will tell you on the nick cart
at what speed is transferring it. If it was only 10 100 maybe orange if it was gigabit it, maybe green. Check your manufacturers detail to see what in your situation it could be.
Also, there are indicator lights on the hard drive on the front of your computer. If those are flashing, you know the hard drive is working. If those are not flashing, there could be a problem with your hard drive. The indicator lights will give you a little bit of detail of what may be going on with your system.
Smoke and burning smell. Electrical problems immediately disconnect the power from your device if your device, if you smell smoke or even see smoke, disconnect the power when the power is disconnected and after that system cools down, check to see if there was any damage components. Visually, you can inspect those to see if there was a damaged component.
Crash screens These air, sometimes called the blue screen of death. These air window stop ares
information on the screen when his displayed is very important. Try to copy that down. Take a picture of it if you can, because you may need to do research if I know exactly what's going on. Some of the information may be high level, detailed information, but you still want to record that because it will give you an indication of what could be going on.
It could be a driver. It could be a bad install. It could be in a failed update.
Any of those things were could produce this window stop here.
The Mac OS operating system had this version of the blue screen of death. It's called the Spinning Wait cursor. You may see this from time to time when you may be opening a ballot applications or switching from one application to another and you'll get the spinning wait cursor. Generally, the cursor will spin, and then after that, it will stop.
Cursor does not go away. If it does not stop and maybe an application issue. It could be bad hardware. It could be slow paging to disk if it does not stop and it's continuous speeding. What you're gonna have to do is restart the computer and check the logs when, after the computer reboots
their log entries for operating systems that will record when an event happens, and this would help you troubleshoot and Dino's. When you're having problems with your system
and Windows, it's the event viewer. The event viewer is located in Windows, and he'll tell you whenever there's an event that happened to your device that were recorded there. Whether the computers shut down unexpectedly, where there was a problem that occurred in the application or to the hardware itself, Windows will log that in the event viewer.
Also, there is Buddha blog's
When the computer boots up and it was a failed boot up or there was something that occurred during the boot up windows will log that
now you can turn it on in the system configuration utility, and those pass that it was right Those interests toe. A text file is located under C Windows in tbe t log dot t x T.
Mac OS has its form of window system utilities or logs, and it's it's records, utilities, and it's a council dot AP.
Lennox has its version as well. It's recording issues with the utilities and applications, and the path that you'll find those information is is in four slash bar for slash log
air messages. Whenever you get an error message on your screen record that air message it could help you what? Your troubleshooting steps right down and record those air message and inform your users to do the same. Sometimes those air message may not be known to you. You may not understand what they mean,
but it may mean something to a developer or vendor or keep people involved with that software
who know that application in and out. So record those air messages. It would help you. Which air troubleshooting steps.
Okay, so we went over a lot of troubleshooting steps that you will need to know off course for the A county A plus as well as when you're helping with users. And you're helping corporations and customers help troubleshooting devices and things that you need to look for. So
that was it for this lesson, and we will see you in the next lesson.
CompTIA - 220-1001 A+ Exam
220-1001 A+ Core Exam 1 Certification Package
CompTIA A+ 220-1002
In this course, you will learn the fundamentals of operating systems, security, software troubleshooting, and ...
26 CEU/CPE Hours Available
Certificate of Completion Offered