CompTIA exam study guide presentations by instructor Brian Ferrill, PACE-IT (Progressive, Accelerated Certifications for Employment in Information Technology) "Funded by the Department of Labor, Employment and Training Administration, Grant #TC-23745-12-60-A-53" Learn more about the PACE-IT Online program: www.edcc.edu/pace-it

1. Troubleshooting
Windows operating
systems I.

2. Page 2
Instructor, PACE-IT Program – Edmonds Community College
Areas of Expertise Industry Certification
 PC Hardware
 Network Administration
 IT Project Management
 Network Design
 User Training
 IT Troubleshooting
Qualifications Summary
Education
 M.B.A., IT Management, Western Governor’s University
 B.S., IT Security, Western Governor’s University
Entrepreneur, executive leader, and proven manger
with 10+ years of experience turning complex issues
into efficient and effective solutions.
Strengths include developing and mentoring diverse
workforces, improving processes, analyzing
business needs and creating the solutions
required— with a focus on technology.

3. Page 3
– Common symptoms, causes, and
tools.
PACE-IT.

4. Page 4
Troubleshooting Windows operating systems I.

5. Page 5
A Windows OS is composed
of tens of millions of lines of
code. There is a lot that can
go wrong.
Because of this, it is important that you follow the
troubleshooting methodology to reduce wasted time
and effort.
Troubleshooting Windows operating systems I.

6. Page 6
– Blue screen of death (BSOD).
» Symptom is a critical stop that brings up the BSOD.
» Causes are many, but the BSOS shows a hex code that can be
used to research the problem.
» Tools include Disable Automatic Restart ON System Failure
and the Microsoft Knowledge Base.
– Failure to boot.
» Symptom is that the system will not boot and may or may not
give an error.
» Causes are many, including hardware or software error, virus,
and glitch.
» Tools include a restart, MS Knowledge Base, Last Known
Good Configuration from Advanced Boot Options, Startup
Repair, Safe Mode (run antivirus, run System Restore, verify
system files with sfc/scannow), fixboot /fixmbr for boot sector
issues, and restore from a system image.
Troubleshooting Windows operating systems I.

7. Page 7
– Improper shutdown.
» Symptom is that the PC shut down with no warning once
but can reboot with no problems.
» Cause is more than likely just a glitch or momentary
power issue—or the user just doesn’t understand.
» Tools are none and/or end user education.
– Spontaneous shutdown or restart.
» Symptoms are the same as above, but it keeps
happening and it isn’t the end user.
» Causes include virus, faulty RAM, and a failing power
supply.
» Tools include antivirus software, sfc /scannow, and
the Windows memory diagnostic tool, as well as the
procedure to troubleshoot the power supply.
Troubleshooting Windows operating systems I.

8. Page 8
– RAID not detected during installation.
» Symptoms include the RAID array not initializing on boot
up and being unavailable for use.
» Cause is usually a hardware based RAID with the
incorrect driver.
» Tool to use is Device Manager and the process is to
check and update drivers.
• A useful resource may be the RAID hardware
manufacturer’s website.
– Device fails to start.
» Symptom is that a single device fails to start when it is
supposed to.
» Cause is usually a bad driver.
» Tool to use is Device Manager and the process is to
check and/or update the driver.
Troubleshooting Windows operating systems I.

9. Page 9
– Missing DLL message.
» Symptom is that an application fails to load or function and
gives an error message.
» Cause is that the required Dynamic Link Library (DLL) file
(reusable code) is either missing or corrupted.
» Tools include sfc /scannow; if the DLL needs to be registered
from a C: use regsver32 filename.
• Do not download third party DLLs from the Internet.
– Service fails (or services fail) to start.
» Symptoms include affected function of the service(s).
» Causes are many, including incorrect setting (disabled).
» Tools include the System log in the Event Viewer; the log may
give hints as to why the service failed to start.
» The Services applet can also give insight.
• For example, is the service set to disable?
Troubleshooting Windows operating systems I.

10. Page 10
– Compatibility error.
» Symptom is that an application doesn’t start or fails to run
correctly.
» Cause is usually that the application is a legacy (older)
application that is not compatible with a newer OS.
» Tools include the Application log in the Event Viewer to see if
an error message has been logged. The usual fix is to run the
application in compatibility mode so the OS runs the
application mimicking a prior OS.
– Slow system performance.
» Symptom is that the system is running slower than normal.
» Causes include too many applications running, not enough
memory, possible process or application issue, or malware.
» Tools include Task Manager; check to see what applications
and processes are overly consuming CPU resources. You can
stop the process or lower its priority.
Troubleshooting Windows operating systems I.

11. Page 11
Troubleshooting Windows operating systems I.
Windows operating systems are very complex and symptoms can be highly
varied. Anything unexpected, unexplained shut downs, poor system
performance, or even the dreaded BSOD can be classified as a symptom
that needs to have the troubleshooting methodology employed.
Topic
Symptoms.
Summary
Due to the complexity of the Windows operating system, there are many
things that can cause it to behave unexpectedly. Causes of malfunctions in
the operating system range from poor user habits to legacy applications
and include everything in between.
Causes.
Fixboot, fixmbr, sfc, REGSRV32, Event Viewer, Safe Mode, and the
command prompt are all tools that can be used to troubleshoot the
Windows operating system.
Tools.

12. Page 12
THANK YOU!

13. This workforce solution was 100 percent funded by a $3 million grant awarded by the
U.S. Department of Labor's Employment and Training Administration. The solution was
created by the grantee and does not necessarily reflect the official position of the U.S.
Department of Labor. The Department of Labor makes no guarantees, warranties, or
assurances of any kind, express or implied, with respect to such information, including
any information on linked sites and including, but not limited to, accuracy of the
information or its completeness, timeliness, usefulness, adequacy, continued availability
or ownership. Funded by the Department of Labor, Employment and Training
Administration, Grant #TC-23745-12-60-A-53.
PACE-IT is an equal opportunity employer/program and auxiliary aids and services are
available upon request to individuals with disabilities. For those that are hearing
impaired, a video phone is available at the Services for Students with Disabilities (SSD)
office in Mountlake Terrace Hall 159. Check www.edcc.edu/ssd for office hours. Call
425.354.3113 on a video phone for more information about the PACE-IT program. For
any additional special accommodations needed, call the SSD office at 425.640.1814.
Edmonds Community College does not discriminate on the basis of race; color; religion;
national origin; sex; disability; sexual orientation; age; citizenship, marital, or veteran
status; or genetic information in its programs and activities.