Use Windows 7 Event Viewer to track down issues that cause slower boot times

  • Thread starter Thread starter mrk
  • Start date Start date

mrk

mrk

Man of Honour
Joined
18 Oct 2002
Posts
105,023
Location
South Coast
I've noticed many people asking the same old question about boot times and what's good/bad and how to monitor boot time.

Various recommendations on timing and using utilities to time etc have been mentioned and all are sound but those running Windows 7 have the ability to use the powerful Event Viewer to drill down quite extensively to see how long various things took to load and how much degradation the slowness has had to the usual loading times of that item in question.

I came across this article which I found to be very helpful in not only explaining which aspects to keep an eye on in the detailed outputs Windows records but also what to look out for trends wise.

http://www.techrepublic.com/blog/wi...down-issues-that-cause-slower-boot-times/3253

On mine in the degradation custom view I noted 9 entries and that on the 17th November, STEAM took 13 seconds to load which was 3 seconds slower than what it normally takes. Origin on the 14th October took 6.7 which was 1.7 longer than normal. Everything else was less than 3 seconds. It's worth noting that the entry for STEAM was the day I installed the SSD, now STEAM loads within seconds and since that date STEAM has no further entry, since October Origin also has no further entry.

This kind of detail is useful to know because it goes to show that apps considered to be commonly slow and boot time increasing, actually aren't when you have them on an SSD.

It's worth noting the bit where he mentions that in the boot time custom view that MS adds on an additonal 10 seconds to account for processing.

I looked back to before I got my SSD (Force 4 120GB) and had a WD Black 500GB SATA-II and cloned the install over, I was getting:

MainPathBootTime
(Time between Windows logo and Desktop loading, it seems this does not factor in the time it takes to enter password on the logon screen?)
21.9secs
BootPostBootTime
(BootPostBootTime represents the amount of time that elapses between the time that the desktop appears and the time that you can actually begin using the system)
88.7secs
BootTime
(Sum of MainPathBootTime and BootPostBootTime, inc 10 additonal secs)
110secs



Whereas now I am getting:

MainPathBootTime
8secs
BootPostBootTime
26secs
BootTime
(This has the additonal 10secs remember)
34secs

I know it looks like quite a lot of info to take in but once you've added the custom view (takes 2 minutes) it really does make sense and is pee easy to read quickly every now and then if you feel something might be wrong if a boot took longer than usual.
 
Last edited:
You can't "not" reboot after installing new drivers or after a Patch Tuesday. It's also nice to know that there aren't any issues with your boot time either ;) But if there are then this is the only 100% fool proof way to find the problem and address it.
 
Yes it's amazing just how much information Win7 keeps a record of just waiting to be tapped through the various Administrative tools built in to itself.
 
Having set this up I get the following with my latest boot then.

MainPathBootTime
8secs
BootPostBootTime
10secs
BootTime
18secs

Not too bad.
 
Back
Top Bottom