In this article 7 sections
- 1. Write down the time it closed first
- 2. Open Event Viewer and find Windows Logs
- 3. Filter the current log by a time range
- 4. Read by level: check errors first
- 5. Search by event ID and source name
- 6. Preserve the records and narrow down the cause
- References
If a program suddenly closes or your PC restarts on its own, the fastest place to start is by checking the records around that time in Event Viewer. Event Viewer is a tool that reads and displays event logs recorded by Windows. However, logs accumulate many entries during normal use, so the key is to first narrow the scope by time and level.
1. Write down the time it closed first
If you do not know the exact time, the search range becomes too broad. Recall the time shown on the taskbar clock, notification history, or the time you were looking at the screen, and write down approximately between which hours it occurred. As a hypothetical example, if you write, “The PC restarted around 3:10 p.m.,” set the initial range to about 30 minutes before and after that time. This range will be used as-is in the filtering step that follows.
2. Open Event Viewer and find Windows Logs
Search for “Event Viewer” in the Start menu and open it. Expand “Windows Logs” in the tree on the left to see the Application, Security, and System logs. Microsoft Learn’s introduction to Event Viewer also describes these three logs as the representative logs in the Windows Logs section. Program errors are often recorded in the Application log, while restart- and driver- or power-related records are often recorded in the System log, so it is safer to check both.
3. Filter the current log by a time range
In the “Actions” pane on the right, click “Filter Current Log” and set the time range you noted earlier as the condition. The menu layout may vary slightly by Windows version, so follow the filter options shown on your screen. Instead of using a filter, you can also look at the date and time columns in the list and find the entries manually. In the hypothetical example, narrowing the System log to 15:08 through 15:15 reduces the entries to check from many routine items to just a few.
4. Read by level: check errors first
Events have levels indicating their importance. Microsoft’s event documentation explains that Level indicates an event’s severity or importance and is a key filtering criterion. The standard level names are Critical, Error, Warning, Information, and Verbose. In practice, check Critical and Error first, then see whether a Warning occurred at the same time. Information entries are often records of normal operation, so they can be moved lower on the list of possible causes.
5. Search by event ID and source name
When you select a Critical or Error entry, you can see the Source, event ID, and description. Making a note of these three items makes it easier to find other cases involving the same error. However, community answers are not official solutions, so verify any recommended action again in the manufacturer’s or Microsoft’s official support documentation. If the same event repeats and a driver name appears, you can also consider rolling back a recent driver update: How to roll back a Windows driver ↗.
6. Preserve the records and narrow down the cause
You can save the filtered list to a file from the “Actions” pane. Because older entries may be deleted according to the log’s size limit, note the time, event ID, and source name if the same problem recurs. It is difficult to confirm the cause from a single event. It is better to examine it together with Task Manager records or disk status from the same time: How to find the process causing a slow PC with Task Manager ↗.
References
Microsoft Learn: Windows Event Log ↗ / Microsoft Learn: Event Logging ↗ / Microsoft Learn: Introduction to Event Viewer (English) ↗ / Microsoft Learn: EVENT_DESCRIPTOR Level Field ↗
Sources and original article
Read the Korean original on Naver ↗
This article reflects public information available when it was written. Specifications, prices and schedules can change; check the linked official documentation.
This English edition was written and translated with AI assistance, with sources provided. For errors or additional information, please request a correction. Editorial policy