Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Boot Times - Monitor with Event Viewer


Boot Times - Monitor with Event Viewer

How to Monitor Boot Times in Event Viewer
Published by seavixen32
12 Jul 2011
Published by

Overview
Windows 7's Event Viewer has a new category of event logs that are known as Applications & Services Logs. This new category has a series of sub-categories that can be used to keep an eye on important events in the operating system.

Most of these sub-categories have an event log type named Operational, which is used to monitor events that can be used for diagnosing problems with your computer.

One of the sub-categories is titled Diagnostic-Performance and nested within it is an operational log that looks after the boot performance monitoring. The Event IDs related to this log are numbered 100 through 110 and by investigating all the Event ID 100 events, you can keep track of how long it takes your system to boot up, while Event IDs 101 through 110 will give you an indication of how your boot times have degraded since Windows was first installed.


Launching Event Viewer

There are two ways in which you can start Windows 7's Event Viewer:
  1. Navigate through Start/System & Security/Administrative Tools/Event Viewer.
  2. Click Start and type Event in the Search field then press Enter when you see Event Viewer highlighted at the top of the list under Programs.
-ev1.png]





Creating a Custom View
1. Go to the Action menu in the right-hand pane of the main Event Viewer window and click on Create Custom View, which will open the Create Custom View window.

2. Make sure the Logged option is set to the default setting of Any Time and ensure all the Event Level check boxes are checked.

-ev2.png
3. Next, select the By Log option button if it isn't already selected and click the drop-down arrow and choose Applications & Services Logs.

-ev3.png
4. Drill down through Applications & Services Logs/Microsoft/Windows/Diagnostics-Performance.

-ev4.png
5. Expand the Diagnostics-Performance branch and check the Operational check box.

-ev5.png
6. Click on a blank space in the main Event Viewer window then type 100 in the Includes/Excludes Event IDs box.

-ev6.png
7. Click OK to bring up the Save Filter to Custom View dialog box and give the view a meaningful name such as Boot Times with an appropriate description in the text box below. Make sure Custom View is highlighted then click OK to save your new custom view.

-ev7.png
8. Repeat the above steps to create another custom view (good practice for you!) but this time type 101-110 in the Includes/Excludes Event IDs box and name the new custom view Boot Degradation Times with an appropriate description again.



Investigating Boot Times
1. Go the left-hand pane of the main Event Viewer window and expand the Custom Views tree then click the new custom view Boot Times.

-ev8.png


2. By looking at this custom view and clicking the Details tab, we can see the following:
  • The computer has been booted 41 times with an event recorded for each time.
  • The date of the first boot was 10th July 2011.
  • The boot time was 63.9 seconds (63914/1000).
-ev9.png


3. If we now look at a critical event, we can see a different picture emerge:
  • The date of this event was 11 July 2011.
  • The boot time had increased to 93.7 seconds (93748/1000)
-ev10.png


4. The information under the Details tab can be very useful in determining an increase in boot times, but of course, there are several normal reasons why they vary:
  • Windows Updates
  • Microsoft Updates
  • Driver Installations
  • Software Installations


Investigating Boot Time Degradation

1. If we now look at the Boot Degradation custom view (you did create it, didn't you?) we can look at each event in detail. In this Event ID 106 we can see:
  • There have been 21 events.
  • The date of this event was 9th July 2011
  • The degradation time was 23.6 seconds (23614/1000).
  • The cause was due to the Background Prefetch Time
-ev11.png

2. Event ID 101
This indicates that an application took longer than usual to start up and is usually the result of an update of some sort.

3. Event ID 102
This shows that a driver took longer than normal to initialize and once again is normally caused by an update.

4. Event ID 106
This event records that a background task such as prefetch took longer to finish than normal.

I hope this brief tutorial has given you a better appreciation of the way in which Event Viewer can help isolate reasons why Windows slows down over a period of time.



12 Jul 2011   #1
Devux

Windows 7 Home Premium 64bit
 
 

Excellent tutorial!


My System SpecsSystem Spec
12 Jul 2011   #2
seavixen32

Windows 7 Ultimate SP1 64-Bit
 
 

Why thank you. I've just contacted Brink in a fit of desperation as I'm unhappy with the layout and wasn't quite sure how to clean it up.
My System SpecsSystem Spec
16 Jul 2011   #3
JaidynM

Windows 7 Ultimate x64/Windows 8 Consumer Preview x64/Ubuntu 11.04
 
 

Great tutorial, Andrew. Well done!

To clean it up, you should add a few things such as a title, related articles etc. Shawn however, will most likely do it for you. If you want to do it your self, take a look at one the forum BB Code. It should cover most of the important stuff.
Windows 7 Forums - BB Code List
My System SpecsSystem Spec
.

18 Aug 2011   #4
aapee

windows 7 enterprise 32-bit
 
 

Hi.
Good tutorial but I don't think Windows logs each boot in eventlog. There are registry entries under HKLM\Software\Microsoft\Windows\CurrentVersion\Diagnostics\Performance\Boot where are stated minor and major threasholds for boot. My exprerience is that eventid 100 is logged only when minor threshold is exceeded. Do you know if that is the case? I would like Windows to log each boot - even if it's a good and fast boot - to get records out of those. So far I haven't figured out how to do it as I can't seem to be able to modify the registry entries under Boot as they are controlled by TrustedInstaller service.
My System SpecsSystem Spec
19 Aug 2011   #5
seavixen32

Windows 7 Ultimate SP1 64-Bit
 
 

Quote   Quote: Originally Posted by aapee View Post
Hi.
Good tutorial but I don't think Windows logs each boot in eventlog. There are registry entries under HKLM\Software\Microsoft\Windows\CurrentVersion\Diagnostics\Performance\Boot where are stated minor and major threasholds for boot. My exprerience is that eventid 100 is logged only when minor threshold is exceeded. Do you know if that is the case? I would like Windows to log each boot - even if it's a good and fast boot - to get records out of those. So far I haven't figured out how to do it as I can't seem to be able to modify the registry entries under Boot as they are controlled by TrustedInstaller service.
Lowering the minor threshold to 1, for example, would trigger an Event ID 100 error on every boot I would imagine.

That being the case, would Windows inititiate a shut down thereby assuming that there was a major problem?
My System SpecsSystem Spec
22 Oct 2014   #6
jonnyhotchkiss

Windows 7 Ultimate 64bit
 
 

think this is a prerequisite

gpedit.msc: [comp.conf] admin.templates>system>troubleshooting>windows boot perf. (enabled).
My System SpecsSystem Spec
Comment

 Boot Times - Monitor with Event Viewer




Tutorial Tools






Similar help and support threads
Windows 7 Tutorial Category
Computer keeps restarting at random times. Event viewer report in post
My computer keeps restarting at ramdom time during the day. If I play a movie using vlc that restarts it every time. I tried running Linux to see if it was a windows problem and still happend. Tried running memtest and it goes into a infinite restart loop after 15 sec in memtest. I swapped out ram...
BSOD Help and Support
After BSOD Event Viewer Logs Event ID 3012 and 3011 every time I boot
I was running 3DMark06 and got a BSOD code 124. After that every time I boot Event Viewer logs Error Codes ID 3012 and 3011. Attached are screenshots of both. I googled this and found two different threads where someone suggested to rebuild the performance counters. Both responses were...
BSOD Help and Support
BSOD, occuring to many times as per event viewer! HELP!
Hi, good day mate. it happens to me very random at first i just ignored it i just thought it was just a glitch from a driver i've installed, but since i have already updated latest drivers for my hardware i believed that it wont occur again, but it still happened to many times now and...
BSOD Help and Support
Event viewer log showing login times when computer is off
I have noticed that my event viewer log is showing successful logins when my computer is off. Is this normal? Does the system ever "log itself in" while its off?
Performance & Maintenance
Freezing randomly at all times, Event Viewer suggests driver issue...
I know nothing about this stuff so I've been learning as I try to troubleshoot this issue. This is my build in case it matters: CPU: AMD Athlon II X4 (645) Mainboard: MSI 870-G45 RAM: 4x2 GB DDR3 GPU: AMD Radeon HD 6900 HDD: Seagate 2 TB PSU: Corsair GS 700W
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 02:45.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App