¿Cómo depuro el Visor de eventos?

How do I debug Event Viewer?

Procedure

1. Start the Microsoft Event Viewer. Click Start.
2. Select View > Show Analytic and Debug Logs.
3. In the navigation pane: Expand Applications and Services Logs.
4. In the Actions pane, click Enable Log.
5. In the navigation pane, click Debug.
6. In the Actions pane, click Enable Log.

To clear the system log:

1. Choose Start > Control Panel.
2. Double-click Administrative Tools, and then double-click Event Viewer.
3. In either pane of the Event Viewer window, right-click System and then select Clear All Events.

The faulting offset is the memory location inside the loaded faulting module i.e. it gives us the exact crash location in the faulting module mentioned in the log.

To access the Event Viewer in Windows 8.1, Windows 10, and Server 2012 R2:

1. Right click on the Start button and select Control Panel > System & Security and double-click Administrative tools.
2. Double-click Event Viewer.
3. Select the type of logs that you wish to review (ex: Application, System)

Open Event Viewer (Administrative Tools –> Event Viewer) Expand the “Application and Service Logs” Expand “Microsoft”, and expand “Windows” Expand “IIS-Configuration”, and right click on “Operational”, and choose “Enable Log”

To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window select Windows Logs and System. Place the cursor on System, right click and select Filter Current Log. Check the box before Error and click on OK and you see only Error reports.

To delete a log entry or set of log entries, select the entry or entries, as Figure 2 shows, then click Delete events and Exit. (You can use the Shift or Ctrl keys to select multiple entries.) The utility deletes the entries when you reboot the system. Security log entries, rename or delete the file secevent.

In this article we will learn how to log in to event viewer or log file using c#. In many of our .NET projects, we need to log exceptions/errors/information in either Windows event log or a custom text Log file for debugging/review/reporting purposes.

Once you get hold of the application event log from the customer, check the faulting module name, path and faulting offset, then launch the application on your machine and attach it to the debugger. Find the starting memory address of the loaded faulting module and add the faulting offset to this address.

The operating system logs the following error, warning, and informational events during the download or processing of a device metadata package: An error was detected with one of the components of a device metadata package. This event log message contains the following information:

In recent years I have started using Event Viewer to check logs of various warnings, errors registered on a particular machine. I observed that an application or program crash is logged in the Application Event logs and has sufficient information to get hold of the crash or problem location most of the times.