Looking to optimize Vista boot
The time required to boot the operating system is quite critical for many users, especially for laptop owners. The normal time from passing the BIOS to loading the desktop in Windows Vista is on average 25-90 seconds, depending on the hardware configuration, drivers, and services. Sometimes users are faced with a situation where the system boot time is stretched to an unacceptable 5-10 minutes, which signals a problem that needs to be solved in order to avoid possible troubles with stability and possible data loss.
In this small article we will try to address the solution of such troubles with the help of built-in Vista monitoring tools. For some reason nobody has done this in Russian before.
It was possible to track the launch of Windows XP with the help of Microsoft's Bootvis utility, which clearly reflected all the details of the boot process, such as driver delays, I / O time, processor load, and many other useful data. Unfortunately, we don’t have such a program in Windows Vista, but we didn’t leave us without tools.
')
Every time the system is booted, it collects information about the speed of loading the kernel, initializing the drivers and hardware, as well as how the superprefetcher works. The fact that these data can be viewed, many people forget, but in vain.
There is a special Diagnostics-Performance log that can be opened in Administration -> Event Viewer or Control Panel -> Counters and Performance Tools -> Additional Tools -> View Performance Information in the event log .
Information is logged not only on loading, but also on the completion of Vista. Events are assigned a specific code by which their essence can be determined:
The system load data is not logged immediately, but some time after the launch, so do not be surprised that the information about the newly loaded Vista is missing in the log. Wait a few minutes.
Looking at the properties of the latest event with code 100 you can find out the details of the download. On the General tab you can see the total time spent on launch. The data of our journal is given in milliseconds, i.e. for translation in seconds, you need to remove the last three digits. The screenshot shows that the system booted for 138 seconds - almost two and a half minutes. Long!
Go to the Details tab:
In addition to duplicate information on the total load from the first tab in the BootTime parameter, we may be interested in the following:
All data on this tab can be uploaded to XML, for example, to collect statistics on multiple runs.
Immediately, you can see that (for my laptop) the drivers and the session manager were initialized for too long, so you should go back to Event Viewer and look at other events with codes 101-199 in an attempt to identify the inhibitory factor. Carefully looking through the magazine, we find the event under the code 110:
For some reason, the session manager was initialized six times longer than usual. Extra 20 seconds found, looking further. Searches detect event 109 - slow loading IDE channels:
The given example had to be created artificially for publication on Habré, but by applying the information from the Diagnostics-Performance journal in practice I was able to identify problem areas for system loading many times, such as the case of a three-minute load of the totrec.sys driver belonging to Total Recorder.
I hope this information will be useful to you. Continuing to optimize the boot of Windows Vista should ...
In this small article we will try to address the solution of such troubles with the help of built-in Vista monitoring tools. For some reason nobody has done this in Russian before.
It was possible to track the launch of Windows XP with the help of Microsoft's Bootvis utility, which clearly reflected all the details of the boot process, such as driver delays, I / O time, processor load, and many other useful data. Unfortunately, we don’t have such a program in Windows Vista, but we didn’t leave us without tools.
')
Every time the system is booted, it collects information about the speed of loading the kernel, initializing the drivers and hardware, as well as how the superprefetcher works. The fact that these data can be viewed, many people forget, but in vain.
There is a special Diagnostics-Performance log that can be opened in Administration -> Event Viewer or Control Panel -> Counters and Performance Tools -> Additional Tools -> View Performance Information in the event log .
Information is logged not only on loading, but also on the completion of Vista. Events are assigned a specific code by which their essence can be determined:
- Code 100 - load time, total
- Codes 101-199 - problematic loading of devices, services, applications, etc.
- Code 200 - Completion Time, Total
- Codes 201-299 - problem completion of processes, etc.
The system load data is not logged immediately, but some time after the launch, so do not be surprised that the information about the newly loaded Vista is missing in the log. Wait a few minutes.
Looking at the properties of the latest event with code 100 you can find out the details of the download. On the General tab you can see the total time spent on launch. The data of our journal is given in milliseconds, i.e. for translation in seconds, you need to remove the last three digits. The screenshot shows that the system booted for 138 seconds - almost two and a half minutes. Long!
Go to the Details tab:
In addition to duplicate information on the total load from the first tab in the BootTime parameter, we may be interested in the following:
- MainPathBootTime - the sum of the time for the appearance of the desktop, including all critical services and drivers necessary for the main system operation
- BootKernelInitTime - kernel initialization
- BootDriverInitTime - driver initialization
- BootDevicesInitTime - iron initialization
- BootPrefetchInitTime - Superprefaccher Time
- BootSmssInitTime - Session Manager Initialization
- BootPostBootTime - the start time of all non-critical services already with the finished desktop
All data on this tab can be uploaded to XML, for example, to collect statistics on multiple runs.
Immediately, you can see that (for my laptop) the drivers and the session manager were initialized for too long, so you should go back to Event Viewer and look at other events with codes 101-199 in an attempt to identify the inhibitory factor. Carefully looking through the magazine, we find the event under the code 110:
For some reason, the session manager was initialized six times longer than usual. Extra 20 seconds found, looking further. Searches detect event 109 - slow loading IDE channels:
The given example had to be created artificially for publication on Habré, but by applying the information from the Diagnostics-Performance journal in practice I was able to identify problem areas for system loading many times, such as the case of a three-minute load of the totrec.sys driver belonging to Total Recorder.
I hope this information will be useful to you. Continuing to optimize the boot of Windows Vista should ...
Source: https://habr.com/ru/post/42543/
All Articles