Motherboard, RAM, CPU and Power Issues (part 1)

Video Activity

Motherboard, RAM, CPU and Power Issues Part 1 Welcome to Cybrary IT's A+ course. Today's lesson will explore various problems that occur with motherboards, RAM, CPUs, and the power supply. After this segment, you'll be able to diagnose some of the most common issues such as a checking the power or settings when getting a blank screen on boot up, or...

Join over 3 million cybersecurity professionals advancing their career
Sign up with

Already have an account? Sign In »

5 hours 33 minutes
Video Description

Motherboard, RAM, CPU and Power Issues Part 1 Welcome to Cybrary IT's A+ course. Today's lesson will explore various problems that occur with motherboards, RAM, CPUs, and the power supply. After this segment, you'll be able to diagnose some of the most common issues such as a checking the power or settings when getting a blank screen on boot up, or the boot process is interrupted because the system isn't completely on, and how to determine if you system is in sleep mode or hibernation. You'll also learn how to determine if the BIOS startup sequence is incorrect and how to reconfigure it for the desired startup sequence, and why you would need to reset the BIOS jumper settings.

Video Transcription
Hi. Welcome to cyber dot i t. My name's Anthony and I'm your local subject matter expert here for a plus. And today we're gonna be troubleshooting different common problems with motherboards, RAM, CPU and power. So in this section, we said, we're gonna talk about some of the problems that we have commonly with CPU, ram, motherboard and power issues.
Now, a lot of times, these are going to be the issues that we notice as our quote unquote big issues.
These are gonna be some of the issues that we turn out. We try to turn on our computer and it doesn't turn on. We turn on our computer and it tries to keep rebooting, rebooting and rebooting. We turn on our computer and
we get an error or boots to the wrong media. So let's take a look at some of our most common symptoms that will notice when we're having these type of errors, See if we can diagnose some of the underlying issues for what's causing these symptoms and talk a little bit on each about how we may be able to fix it.
So let's take a look. Let's say that we go to our computer and we're
try to boot our computer and we're having a blank screen on boot. Well, this may be a couple of different issues. One of our most common issue may be that the monitor is not plugged in or on or has incorrect settings. If we press the power button on our computer and it's completely booting, we hear the disk spinning. The lights are all flashing
and we still have a blank screen. We want to check
the power off for that screen, not just the power
button on the screen itself, but we want to check the power cable to the screen. We want to make sure that our that our display cables are firmly attached and screwed in, because once our computers up, we don't hear any beefs. We may hear one beep to let us know that the that everything's all good,
but we're still not getting that display on our monitor. We want to check our monitor itself, make sure it's plugged in, it's on and make sure that it's settings, maybe its brightness settings. Or maybe there's a problem with the monitors inverter. If it's a laptop
and that may be causing us to have that blank screen even though we're booting up.
Our next possible problem is that the computer is not completely on. So let's say we're pressing the power. We press the power button and the computer starts booting and maybe it it stops. Or maybe we hit the button again and it's not completely on. So we're sitting and waiting for the monitor. Come on,
we want to check and make sure that the computer is on.
Now. A lot of times, our computers will have settings up on their power settings that put them to sleep or put them in hibernate. Just because we have the power button on the front of the computer flashing may not mean it's completely on it, maybe in sleep or hibernate, and we need to press on the keyboard, move the mouse or press the power button once more
to turn the computer on fully. And that would be a reason why we would have that blank screen because the computer sleeping
and then lastly we may have a power outage. Now, this is a little bit of miss qualification. If we had a power outage, we wouldn't be able to boot the computer at all. We press the power button and nothing would happen. But that is something we do need to check not just to the computer itself, but also to the monitor.
Because if either of those components are missing power, if the computer doesn't have powder power or if the monitor does not have power or if there's a power outage in our building, when we press the power on our computer,
we won't get anything displayed on our monitor.
Next we have. Next we have our BIOS time or settings reset. So let's say we turn on our computer and we get a message that the BIOS time has been reset, or we noticed that some of our BIOS settings have been changed. Well, this is very common leave because the sea moss battery inside the computer has gone bad.
We talked a little bit about the sea moss battery, and we've talked how the sea mas battery
is essentially a small battery. On the motherboard of the computer that provides power to about two are Seamus memory, so that our bio setting stick, so that our bios time stays the same space correct. So that our bio setting state correct and so that our bios,
passwords stays, stays the same, stays unchanged.
If we noticed that perhaps the BIOS battery has been popped out or someone needed to reset the administrative password on the BIOS itself, there may remove and replace the battery, but doing so will reset our time settings, so we need to check that BIOS battery. We need to see if it's still good and possibly replace it if it has gone bad.
And then another possible scenario is that the settings were just incorrectly set. Maybe someone went into the BIOS to change a couple settings
and accidentally set the time. And now we're noticing that now that we've restart so before we go and just simply replace the sea moss battery. We also want to make sure that we're checking to see if the settings weren't inadvertantly changed. But typically see, lost batteries aren't too expensive, and those are easy and they're easy enough to replace.
So it's a good step, just in case
in order to make sure that our BIOS time doesn't keep keep and continuously resetting. Next we have our computer tries attempts to boot to an incorrect vice. So let's say we have our computer. We started up and
it's not booting. It's not booting toe are hard drive. It's trying to boot to maybe another drive we have inside our computer for data, and it keeps giving us an heir that there's no boot device,
and that's because it's it's booting to the wrong device on our computer. It's booting toe a hard drive that doesn't have an operating system on it. Or maybe it keeps trying to boot to a CD we have in the CD tray, and we don't want to do this. Well, there's a couple reasons why that may be happening.
We may have the incorrect boot sequence set up in our BIOS. If our computer is set to boot to draw a certain Dr First or it's set to boot to our CD in the CD tray first,
it's going to attempt those before it moves on to the device that we want, so we may need to change some of those settings. We may need to disable some drives in our bios settings so that those boot sequence settings are correct again, our boot sequence being the sequence of devices.
The sequence of places that are bios looks that our computer looks when it first tries to boot. And if it doesn't find something there, or if it finds something there that it can't completely boot, too,
we may run into an issue.
We may have bootable media in our CD trade. Let's maybe we installed are upgraded our computer to a new version of Windows, and we accidentally left the CD in that CD tray and now our computers trying to boot to that media. Or maybe we put a hard drive in
way stuck in it. We stuck a second hard drive in the computer
that we pulled out of a different computer because it was having issues that we need to pull data off of that drive and that other computer had an operating system and sold on that hard drive. So there's bootable media. There's a bootable operating system on that hard drive that our computers trying to boot, too. So we need to go in,
change those settings and say, No, I don't want you to boot to the CD are if we need to remove the CD, we can do that. I don't want you to boot to this other hard drive. I want you to boot to this drive that has
my operating system on it.
There may be no, there may be no boot petition on the drive. We're trying to boot to. Let's say we have our We have our hard drive in the bay. We have all of our bios settings, correct, but it's not booting to our drive. What's going on? Well,
it may not be booting to our drive because it may get to that step and may try to boot to our dr
and then fail and then try to move to a different drive. So maybe that our BIOS settings are correct, that our boot sequence is correct. But that first setting that first drive that it looks at for operating system. It's not finding an operating system on. Maybe our operating system was corrupt, maybe reformatted our disc. Maybe it's a brand new disk that doesn't have
operating system on it hard drive that doesn't have an operating system on it. So we need to check and make sure that it's not
the fault of the hard drive. It's not. The default is not the fault of the device that we're trying to boot to, that
we're not able to boot to the correct device. And then, lastly, we have incorrect cabling,
are different Seita and paid a connections as well as our scuzzy drives. All have different cabling, cabling, sequences that we need to put our drives on in order to boot to the correct one. We have automatic switch settings on our pay two drives that let let our computer No,
which Dr is the master that it wants to try to boot to and which one is the secondary drive that it will try to pull information from? We may have some incorrect jumpers there. We may have the drives
put on the incorrect
cable selector. We have our blue, black and our gray. We want to make sure that we have are correct, dr. On the correct connector on our chain to make sure that our computers booting to the right device. If we have our say to connect or if we have our state of connections,
then we may need to swap some which say the connector is going into which Dr
on a lot of our motherboards are blue Seita connector on the motherboard, and maybe the R is typically the one that will our computer will try to boot to first. It'll be our drive zero where we'll look for our first operating system. So if it is color coded blue, we may want to try to use that one in order to connect to our
bootable hard drive. Or if they're not color coded, then we may want we may just try to connect our hard drive with an operating system on it to the state, a connector that was
first in there when we got the computer. So we bought a computer. It came with a hard drive pre installed, and the state of cable was plugged into a certain state, a port on the hard on the motherboard. That port is probably the port that our mother board's gonna pull and look for an operating system on that drive that's plug into that port.
So if we don't if we don't know which point is
exactly the one that are motherboard that our BIOS is trying to boot from, we may need to check our documentation for our computer. We may need to do a little bit of process of elimination by trying some different ports and redoing some cabling inside of our computer.
And now our next symptom is our computer is continuously rebooting. We press the power button on our computer and it starts up and then it reboots and it starts up and it reboots.
Well, this may be a couple of different issues. We may have some buyer bios slash jumper setting issues on our computer that we need to reset. Maybe there's some incorrect jumper settings on the motherboard, that it's making our computer not pull power properly,
or we have some incorrect bio settings that
aren't that aren't compatible with our with our computer set up. And we need to change, maybe reverting those bios settings back to the default. Or we need to take a look at those further at those bios settings, and they may be what's causing our computer to continuously reboot. We may have a stuck power, but as silly as it sounds,
we may push in our power button and it's
get stuck in, and it's continuously holding down our power button. So we press the power button. The power button gets stuck, and then it's holding it down and then stopping our computer. And so then the next time we press it, we UN jam and that region and the power button, and it's making our computer start and then
reboot again. So we need to check our power button
and or we may even have a corrupt boot device or bad hardware or bad driver actually, on the hard drive itself, we may be booting, and we may be getting getting past our bios and maybe getting past post. But then, when our computer starts to try to boot to the hard drive, starts trying to boot to a device,
the hardware sailing or there's a corrupt file and so it's not fully booting and then it just stops and it tries to restart in order to try to re initialize the boot. But it just continually does that over and over and over.
So we want to take a look at that. Will want to remain possibly reset our bios or our jumper settings, check our manufacturers, check our manufacturers or our owner's manual for our computer to see what those different jumper settings on our mother born mean
check our power button or check our boot device and see if there's any problem going on with the actual boot device itself or the hardware, possibly maybe even motherboard issue. We have our motherboard failing to see if we can narrow down and determine what, why, which of these reasons or more wire computer might be continuously rebooting.
Up Next
Troubleshoot Critical Systems

Diagnosing system malfunctions and finding a solution is an important skill for help desk professionals to develop. Expand your knowledge of the troubleshooting theory in less than an hour.

Instructed By