Examkin

Question

Difficulty: EasyTroubleshooting Windows Performance and Application Crashes

A user reports that a graphic design application closes unexpectedly whenever a heavy rendering task is started. The helpdesk technician needs to review historic application crash logs to identify the specific faulting module. Which Windows administrative tool should the technician open?

  1. Event ViewerAnswer
  2. B
    Device Manager
  3. C
    Disk Management
  4. D
    System Configuration (msconfig)

Answer

Event Viewer is the correct tool to inspect application crash logs and identify the faulting module.
Event Viewer records application errors, warnings, and information messages under the Windows Logs > Application section. When an application crashes, Windows writes an Error entry (typically Event ID 1000) containing key diagnostic information, such as the faulting application path, exception code, and faulting module name.

Step-by-Step Solution

1
Open Windows Event Viewer by running eventvwr.msc.
The Event Viewer console opens.
Event Viewer centralized logs store software crash details.
2
Navigate to Windows Logs > Application.
A chronologically ordered list of application events is displayed.
Application crash logs (such as Event ID 1000) are recorded under the Application log category.
3
Select the Error event corresponding to the crashed application to view details.
The technician identifies the exact binary or DLL causing the application crash.
Reviewing crash log details provides actionable diagnostic evidence for application isolation.

Key Concept

Using Event Viewer to analyze application crash logs and faulting modules
Rate this question

Topics

Troubleshooting Windows Performance and Application Crashes

More questions from this topic