William has been working on a problem with a computer at his company for several hours and still can't ascertain the problem. The computer will not turn on, and William has tried everything he can think of to fix the computer. He has replaced the power cord, the power supply, and even the power strip the computer is plugged into. William decides that it must be the motherboard and takes the computer to his shop to replace the motherboard on the computer. When he plugs the computer in, it turns on. The problem was not the computer-someone had turned off the switch for the wall outlet that the power strip was plugged into. Where in the troubleshooting process could William have discovered this problem?

Question

Computers & Technology

Elwood

19 August, 03:58

William has been working on a problem with a computer at his company for several hours and still can't ascertain the problem. The computer will not turn on, and William has tried everything he can think of to fix the computer. He has replaced the power cord, the power supply, and even the power strip the computer is plugged into. William decides that it must be the motherboard and takes the computer to his shop to replace the motherboard on the computer. When he plugs the computer in, it turns on. The problem was not the computer-someone had turned off the switch for the wall outlet that the power strip was plugged into. Where in the troubleshooting process could William have discovered this problem?

+4

Answers (1)

Know the Answer?

Robert Melendez · Answer 1

The third stage, which is testing the theoretic causes to confirm the actual cause.

Explanation:

There are six stages in computer system troubleshooting. This stages are;

1. Identifying the problem. The system user experiences a fault in the computer and narrates the problem observed to the technician.

2. The technician create a list of theoretic causes of the problem with the knowledge or experience he has.

3. The technician runs test on each of the theoretic causes to determine the actual cause of the problem

4. The problem is resolved.

5. The functionality of the system is tested,

6. The process and problem is documented for future reference.