Time
5 hours 33 minutes
Difficulty
Beginner
CEU/CPE
3

Video Description

Troubleshooting Operating Systems Part 1 In today's lesson we examine several issues that occur with the operating system and how we can resolve them. We begin by revisiting BSOD, the blue screen of death, and move on to boot failures what may happen to cause an improper shut down and the impact of DLLs and OS service failures. We'll discuss bad sectors on a hard disk drive, malware overloading system resources and memory errors. We'll also talk about when the BIOS would need to be configured and how to update it, when a disk sector becomes corrupt, and various causes that ca trigger the OS to shut down incorrectly. We also cover DLLs and what they are, how they work and how to trace a system or other event if they become corrupt or are considered "missing" on system boot up.

Video Transcription

00:04
Hi and welcome to Cyber. My name's Anthony and I'm your local subject matter expert here for a plus. And today we're gonna be talking about troubleshooting operating system problems with the appropriate tools. So what are some of the malfunctions that we may run into when we're trying to run our operating system? Well, one of the issues that we may have again we have a blue screen of death now are blue Screen of death are B S. O. D.
00:24
Can be a result of several different issues. Let's go through and see if we can name a couple.
00:28
We may have a hard drive, which is failing or has some bad sectors. These bad sectors may corrupt some of the data on it may corrupt some of the files that are necessary for applications or programs and made cause this blue screen.
00:40
Are you screaming also, because by applications, drivers or operating system crashes, we may have certain applications that we're trying to run which aren't fully compatible with our system or applications, which may be pulling memory and incorrect ways or trying to run. Applicants are trying to run a memory or processes and incorrect ways that's crashing. Our
00:59
operating system
01:00
are crashing our computer, and we also have drivers. We can eliminate certain drivers and applications by starting in safe mode and then seeing if running those drivers or running the program associated with those drivers are running. Those applications caused the blue screen issue.
01:15
We may also have malware, malware, overloading our computer, running lots of different processes and trying to access files and change files. That it shouldn't be in can also cause this issue.
01:26
And then we also have memory errors. We could have memory failures and problems with the memory modules on our computer, and these can cause blue screen issues and errors on our blue screen because our computer to crash
01:40
next, we have failure to boot. Failure to boot is when we can't boot into our operating system. Now this could be caused by having non bootable media in our drive. It may be a CD that that our computers trying to boot to, and this isn't proper. Our computer is trying to go to the CD,
01:57
so it's not booting toe are hard drive, not booting toe are operating system.
02:00
We may have the incorrect dr selected. We may have cable mismanagement, cables plugged in wrong in our computer, the wrong hard drives plugged in. And so our computers trying to boot to a device that doesn't have an operating system installed on him.
02:15
So this also relates to our BIOS configuration. We may need to disable certainly hard drives. We may need thio change the boot order of our devices in order to prevent this failure to boot for our computer trying to boot to a non bootable device.
02:30
Then we have our hard drive, has no boot files or it's disconnected or failed
02:36
are hard drive. It's one that we meant to insult operating system on. Maybe we have a new hard drive. May be this hard drive is fresh out of the box that we just installed in our computer. Well, typically, if we bought a hard drive as a standalone device, it's not gonna have an operating system installed on it. We need to go in. We need to install the operating system,
02:53
make sure our hard drive isn't disconnected,
02:57
and also make sure that our hard drive hasn't failed that we haven't had a head crash. We haven't had a motor. We haven't had a motor burnout, but we need to make sure that this hard drive has boot files on it and that it is working. We also need to make sure that those hard drive operating system files aren't corrupted. We are don't have corrupt sectors.
03:15
We may have made changes to our computers that inadvertently deleted. Certain files that were necessary to boot are operating system,
03:22
and this will also cause of failure to boot.
03:24
We may have had a hard drive move to a new motherboard. Are operating system is looking for a certain motherboard. It's looking to interact with a certain a certain way with a certain motherboard that it was installed with and when it doesn't find that we will have daily failure to boot. So we need to make sure that we're running the same hard drive with
03:42
computer with same motherboard that we installed it on,
03:45
or we may need to pull those files off and then using some sort of recovery utility and then reinstall that reinstalled the operating system on the hard drive with the new motherboard.
03:55
And then lastly, we have are incorrect. Master boot record. Our master boot record helps our bios helps our computer to determine which drive and to boot too, and when and how to boot to it. And so if our master boot record becomes corrupt, or maybe it becomes it becomes malformed, then we may need to run certain tools, which will talk about later
04:15
in order to correct this master boot record.
04:19
Now, we have improper shutdowns. Improper shut down is the message that you get when you start up your computer and you have a message that says your computer shut down properly the last time. And so how do you want to start? You want to start normally or you wanna start in safe mode If you want to start recovery mode and what causes this message? Well,
04:40
this message may be caused by a power failure. If the power went out in the power went out.
04:45
We don't have ah UPS backup, and our computer just stopped. When the next time we'll turn on will probably get this improper shutdown message. If we don't shut down our computer properly. If we pull out the power plug or we hold down the power button for 10 seconds toe force it to shut down We may also get this message.
05:02
If our computer crash we had a blue screen of death, then the next time we boot up, we may again. We may also see this message. So this is the type of message that will let us know that something happened to our computer while it was running That made it shut down unexpectedly. So our operating system wasn't ready for it. It might have lost some data and might have lost them work.
05:23
This could even harm operating system files.
05:25
So we need to be careful when we're shutting down our computer to make sure that we don't have that improper shut down. Then we have spontaneous shutdowns. Now, spontaneous shutdowns can be because of power issues. We mention that if we have a power outage or we have power fluctuations within our environment and our power grid on our in our building,
05:43
this can cause the spontaneous shutdowns.
05:45
We also have overheating issues. If our computer isn't properly ventilated, we have too much dust. We can also see the spontaneous shutdown issues but relating to our operating system. We may have noticed we have bad hardware or memory. There may be our drives, Maybe bad. Or it may have issues with our CPU or our memory
06:04
that may
06:05
cause the spontaneous shutdowns as well as driver issues. We may have a particular driver, which is associated with a piece of hardware, that when our computers trying to run that driver are, run the application and use that driver. It's malfunctioning and it's causing a spontaneous shut down.
06:21
Next, we have our raid not detected message during our installation.
06:26
Now, this raid, not detective message may mean that we have a bio. Smith's configured when they have some changes on our bios. That isn't That isn't allowing our installation to detect that we have raid, that we have a raid set up on our computer or that we're trying to have a raid system set up on our computer
06:43
or we may have a missing storage driver. We don't have that store Drudge driver
06:46
and our operating system can't interact. We can't use our raid system. Then we'll also get this raid not detected error. So we want to make sure that we have our storage driver installed correctly. You want to make sure that we have our we have our bios configured properly
07:01
moving on to the devices that we connect to our computer, we may get a message that the devices failed to start
07:06
s so we may have a device such as, ah, hardware device like a Web camera or a scanner plugged into our computer. But we may have a program, or we may have a service that fails, and these programs and service's or devices may fail and just let us know. Hey, devices failed and not tell us what
07:25
exactly divide the devices.
07:28
So we want to check our event viewer. We want to see what the exact error is. We want to see what program are, what application or what device caused the errors a prompt and then investigating that particular device and see if we can figure out what caused it to fail and see if we can manually start it.
07:43
Then we have a missing DLL message. A DLL is a dynamic link library. It's libraries that our computer uses when it tries to run certain applications when it tries to run certain programs. And this missing or the l l'm l'm message is a message that may pop up when we first law again when we first start the computer.
08:01
So we need Thio. Want to check and see our event long and see if we can narrow down what dll it was. If it doesn't tell us in the initial message, and we may want to try to replace the DLL from a good file or if it's an application or a a natural program,
08:18
we may want to go in and uninstalled the application, reinstall it and try to re register that deal well.
08:22
And now, moving on past our deal L we have service failed to start. Our service is our small. There are background interaction between our operating system and our applications are hardware our drivers that allow our computer to function properly.
08:41
Service's can be used for applications.
08:43
They're different applications that will run service is in the background so that they can function properly. We have our prints schooler, which is a service that runs and keeps track of print jobs and helps cue them up to send to the printer. And some of these jobs are Some of these service's may fail to start. Then they have dependencies that fail to load, and so they don't
09:03
they failed to start correctly.
09:05
So we get, make it. This service is fails to start message will want to check our event viewer and see if we can find out which service it was exactly. See if it's possible for us to manually start the service. And if not, we'll need to do some more troubleshooting digging down into that particular service and do our research to see why that service is failing. See if we can.
09:24
If we noticed any particular problems with that service and then we need to patch, I mean, we need to do a restart. Are starting to safe mode to try to get that service started up and running.

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

Instructor Profile Image
Anthony Harris
Systems Analyst and Administrator at SAIC
Instructor