Identify the problem, Ask the user to describe the problem or symptoms, check for error messages, or recreate the problem., Identify what has changed, Establish what has changed. Most often, problems are caused by new hardware, software, or configuration changes. If necessary, ask users to recall what might have changed from the time the software worked and the time it didn't. Remember to inquire about environmental and infrastructure changes that could be relevant, Create hypothesis, With the information gathered in the preceding steps, conduct research and then develop several hypotheses that could potentially explain the problem. From your research and the information you have already gathered, narrow your hypotheses down to the one or two mostly likely causes., Determine the appropriate fix, Review knowledge bases, other websites, and your own experience to identify steps to remedy the problem. Before implementing any steps, think through all possible ramifications that might occur from the planned fixes. Often, the fix itself creates side effects that are just as bad or worse than the original issue, Implement the fix, It's finally time to implement the steps of the fix you have planned. Resist the urge to jump into troubleshooting by starting with this step., Verify functionality, After implementing the fix, verify that the fix repaired the problem. If the problem still exists or a new problem appears, start back at step one again., Document the solution, It might be tempting to move on to other problems, but be sure to document the previous six steps. This will save a lot of time and effort if the problem happens again in say a year or two.

Troubleshooting Process

만든이
인쇄
퍼가기

순위표

현재 순위표 기능을 개선하기 위해 노력하고 있습니다. 피드백을 제공하여 도움을 주세요.

피드백 제공

비주얼 스타일

옵션

현재 활동 설정을 개선하는 작업을 진행 중입니다. 여러분의 피드백을 주시면 도와주시기 바랍니다.

피드백 제공

템플릿 전환하기

자동 저장된 게임을 복구할까요?