Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 100 Source: Microsoft-Windows-Diagnostics-Performance

Windows has started up:
Boot Duration : 130912ms
IsDegradation : false
Incident Time (UTC) : 2/6/2010 3:14:41 AM.
See EV100413 (How to troubleshoot startup and shutdown performance in Windows Vista, 7 and 8) for an article about this type of problem.
This event indicates the fact that the Windows boot time took an unusual long time. The time is recorded in milliseconds. For example, a 130912 ms boot time, means approx. 130 seconds, or 2 minutes and 10 seconds. This is quite a long time to boot and it may be an indication of a problem. This event in itself does not record the reason why the boot took that long, just that it happened. Other events in the logs may point to the cause of the problem. Some users reported that event IDs 300 and 103 specifically mentioned the drivers that were caused the boot delay - see EV100056. In many cases, the culprit is the hard disk. A chkdsk should be run against all the drives in order to detect and fix corrupted files (it may not fix that particular problem but it doesn't hurt, either) - see EV100057 for details.

Some support forums suggested a clean re-install. For those that find this acceptable, might be the quickest way back to a healthy Windows.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.