1.6 Hardware troubleshooting

Question 1

What are the steps you must follow when you think there is a problem?

Answer 1

1.) Identify the problem2.) Create a theory and test it using troubleshooting tests3.) Create a troubleshooting plan and record each step. Make sure the system works after each step.4.) Create a finding document for future reference.

Question 2

What is everything you should document?

Answer 2

• The fault itself.- The system in question.- User logged in at the time of the issue.- Exact date and time of the problem.- Symptoms of the issue.- Problem history.- Back up all the documentation aswell.

Question 3

What are all 3 troubleshooting tools?

Answer 3

• Event Viewer.- Power On Self Test (POST)- Ping Test

Question 4

What is event viewer?

Answer 4

A software that lists detailed information about an error when one occurs. Can be used to work out how to fix the issue. Will display major and minor faults.

Question 5

What is POST?

Answer 5

• Power On Self Test- When starting up the POST checks memory, power, hardware and cooling systems are all working properly. Then beep codes will signal if there is an issue. 1 beep is okay but multiple beeps means there is an error that has been detected.

Question 6

What is the Ping Test?

Answer 6

Connectivity test between two computers. A message is sent to the ‘destination computer’ and then waits for an ‘echo reply’. This procedure is repeated until the problem is detected from the computer that doesn’t reply.