[17/8!!檢測blogger---對於我的部落格---有否維護___以新文章測試==]**Windows 7 / Windows 8 開机時間變慢了的解決方法~!**[!!檢測blogger---對於我的部落格---有否維護___以新文章測試==]**Windows 7 / Windows 8 開机時間變慢了的解決方法~!**[17/8!! Detection blogger --- For my blog --- whether maintenance ___ to new posts test ==] ** Windows 7 / Windows 8 boot time slower solution ~! **

**[!!檢測blogger---對於我的部落格---有否維護___
 以新文章測試==] **Windows 7 / Windows 8 開机 --
--時間變慢了的解決方法~!**[!! Detection blogger ---
 For my blog --- whether maintenance ___ to new  
 posts test ==] ** Windows 7 / Windows 8 boot time 
 slower solution~!**

***如果我們使用的 Windows 7or8 出現開機變慢的現象， 
我們可以使用 Windows 7or8 內置的事件查看器來查找導致--
--系統開機變慢的罪魁禍首，下面我們一起來了解如何利用---
---事件查看器來優化 Windows 7or8 的開機速度。

1. 查看啓動時間
首先我們在開始菜單搜索框中鍵入“事件”，或者輸入“event”，
按下回車鍵啓動事件查看器。
（注：兩者啓動的事件查看器略有不同，但操作一致）
在左欄中依次選擇“應用程序和服務日志” 
“Microsoft”“Windows”“Diagnostics-Performance”“Oprational”類別，
如下圖所示：
*If we start using Windows 7or8 slow emergence of 
 the phenomenon, we can use the built-in Windows 7or8
Event Viewer to find the culprit cause slow system boot,
 here we work together to understand how to use Event
Viewer to optimize Windows 7or8 boot speed.

A view start time
First we start menu search box, type "events", or enter 
 "event", press the Enter key to start the Event Viewer. 
 (Note: both start Event Viewer is slightly different, 
 but the operation is the same)

In the left column select "Applications and Services Logs" "Microsoft" "Windows" "Diagnostics-Performance" "Oprational" category, as shown below:*

點擊右欄中的“篩選當前日志”選項，彈出“篩選當前日志”對話框，
在“包括/排除事件ID”文本框中輸入100，如下圖所示。然後點擊確定
*Click on the right column of the "Filter Current Log" option, pop-up  
"Filter Current Log" dialog box, in the "include / exclude Event ID" text box,
enter 100, as shown below. Then click OK*

回到事件查看器主窗口，在中間一欄就可以查看到事件ID為 100 的事件，
雙擊自己感興趣的時間的事件記錄，可以打開如下圖所示的對話框 
*Back to the Event Viewer main window, in the middle of a field you can view 
 the event ID 100 event, double-click the event of interest time recording, 
 you can open the dialog box shown below*

其中“啓動持續時間”就是 Windows 7or8 的啓動時間，是以毫秒為單位，
除以 1000 就可以得到以秒為單位的啓動時間，例如Melo的電腦啓動時間--
--就是 41.154 秒。下方的“IsDegradation”是指 Windows 的啓動時間與 
平常相比是否有延遲，該值為布爾值，true為真，false為假。
點擊“詳細信息”標簽頁，可以看到啓動時間的詳細信息。
*The "start duration" is the Windows 7or8 startup time, in milliseconds, 
 by 1000 you can get in seconds start-up time, such as the author's computer startup 
time is 41.154 seconds. Below "IsDegradation" refers to the Windows startup time
and whether there is a delay than usual, the value is a Boolean value,
true is true, false is false.
Click "Details" tab, you can see detailed information startup time*

關於這些詳細信息的具體含義，請參閱Windows On/Off Transition Performance Analysis。此處我們僅僅需要關注以下三個值即可：
MainPathBootTime：
MainPathBootTime 是指啓動時 Windows 徽標出現到桌面出現經過的時間。
需要注意的是 MainPathBootTime 結束並不意味著啓動過程完全結束， 
此時雖然可以使用系統，但一些程序或服務仍然需要加載，系統響應速度較慢。
BootPostBootTime:
BootPostBootTime 是指桌面出現之後到系統完成啓動過程之間的時間，
判斷 BootPostBootTime 結束的標志是在 100ms 的時間中系統空閒時間--
--達到 80% 或以上。（注：系統完成啓動過程時硬盤讀取可能仍在繼續）
BootTime：
BootTime 就是指前面的啓動持續時間，也是 MainPathBootTime  
  和 BootPostBootTime 之和，微軟認為為計算出准確的啓動持續時間---
---需要將此時間減去 10 秒，這是由於通常在啓動結束之後還需要 10 秒--
--左右的時間使系統達到認定 BootPostBootTime 結束的標准，
即在 100ms 的時間中系統空閒時間達到 80% 或以上。
注：使用 200 作為篩選事件的標准可以查看關機時間，
使用 300 則可以查看待機時間。
2. 查找導致啓動變慢的原因
在 Windows 7or8 事件查看器中不僅記錄了 Windows 的啓動時間，
還記錄了導致啓動變慢的原因，這些原因分別用 101 到 110 這十個---
---事件ID進行記錄，在“篩選當前日志”對話框“包括/排除事件ID” 
文本框中輸入“101-110”即可查看。
盡管影響 Windows 7or8 啓動速度的事件有十種，但是比較常見的有五種，
下面我們來逐一了解，並且來探尋可能的解決之道：
*For more information about these specific meaning, see Windows On / Off Transition
Performance Analysis. Here we just need to focus on the following three values ​​can be:

MainPathBootTime:
MainPathBootTime refers to the Windows logo appears at startup time elapsed desktop appears.
Note that MainPathBootTime does not mean the end of the boot process completely finished,
although you can use the system at this time, but some programs or services still need to be loaded, 
 the system is slow to respond.

BootPostBootTime:
BootPostBootTime refers to the system desktop appears after the time between the completion
of the boot process to determine BootPostBootTime marked the end of the time of 100ms
system idle time to reach 80% or above. (Note: When the system completes the boot process
may still be hard to read)

BootTime:
BootTime refers to the front of the start duration is MainPathBootTime and
BootPostBootTime sum, Microsoft considers calculate the exact duration required to
start this time minus 10 seconds,
which is due to start after the end usually need about 10 seconds time for the system to
reach the end finds BootPostBootTime standard, that of the time of 100ms system 
idle time to reach 80% or above.
NOTE: Use 200 as a screening criteria can view the event shutdown time,
the use of 300 to view standby time.

2 Find cause reasons for slow start
Event Viewer in Windows 7or8 not only records the Windows startup time,
but also record the reasons that led to slow start, these reasons were used 101-110 to
record these ten event ID in the "Filter Current Log" dialog "includes /   
 Excludes Event ID "text box, enter" 101-110 "to view.

Despite the impact of Windows 7or8 startup speed of events has ten, but there are 
five more common, let's understand one by one, and to explore a possible solution:*

事件ID 101：
101 事件是指某個應用程序啓動花費的時間超過正常時間，
導致系統啓動變慢。其中“總計時間”是指該程序啓動的總時間，
而“降級時間”是指該程序啓動比平常啓動多花費的時間。
程序升級等原因可能導致某些程序偶爾拖慢了系統啓動，因此偶爾某個--
--程序導致 101 事件是正常的。但是如果某個程序經常導致 101 事件，
那麽可以考慮升級該程序，或者將其卸載重裝甚至尋找替代軟件，
如果不需要開機自動啓動的話還可以取消其開機自動啓動。
事件ID 102：
102 事件是指某個驅動程序啓動花費的時間超過正常時間，導致系統啓動變慢。
如果之前進行了驅動升級，那麽出現 102 事件是正常的。
但是如果某個特定驅動程序經常導致 102 事件的話，
建議將其升級為最新版本，如果當前版本已經為最新版本的話，
請嘗試重新卸載安裝。
事件ID 103：
103 事件是指某個服務啓動花費的時間超過正常時間，導致系統啓動變慢。
偶爾出現 103 事件是正常的，但是如果某個特定服務經常導致 103 事件的話，
可以將其啓動類型修改為“自動（延遲啓動）”或者“手動”。
事件ID 106：
106 事件是指背景優化花費較長時間完成，導致系統啓動變慢。
通常來說這是由於預獲取導致的，通常而言出現該情況是正常的。
但是如果 106 事件經常出現的話，可以嘗試清空預獲取緩存。
事件ID 109：
109 事件是指某項設備導致系統啓動變慢，如果 109 事件經常出現的話，
請檢查相應設備是否出現問題。
通過 Windows 7or8 的事件查看器，我們就可以找出導致系統啓動--
變慢的元凶，從而提高系統啓動速度。
注：將事件ID 首位的 1 替換為 2 或 3 可以考察影響關機時間和待機時間的因素    ***

*Event ID 101:
101 event is an application startup takes longer than normal time, 
 cause the system to slow start. The "total time" refers to the total time 
 the program starts, and the "downgrade time" means the program has started 
 to spend more than usual start time.
Program upgrades and other factors may cause some programs occasionally
slow down the boot, so occasionally a program leading 101 events are normal.
However, if a program often leads to 101 events, then you can consider upgrading
the program or uninstall it or even look for alternative software reloading, 
 if you do not boot automatically activated, then you can cancel their startup.

Event ID 102:
102 event is a driver startup takes longer than normal time, cause the system to slow start.
If a driver update before, then there is a normal event 102. However, if a particular driver 
 often results in 102 events, it is recommended to upgrade to the latest version if the 
current version is already the latest version, please try uninstalling the installation.

Event ID 103:
103 event is a service startup takes longer than normal time, cause the system to slow start.
Occasional 103 event is normal, but if a particular service often results in 103 events,
you can modify its startup type to "Automatic (Delayed Start)" or "Manual."

Event ID 106:
106 event is background optimization takes longer time to complete,
cause the system to slow start.
Typically, this is obtained as a result of the pre-, Typically this situation occurs is normal.
However, if the 106 events often appear, then you can try to empty the prefetch cache.

Event ID 109:
109 event is a device causes the system to start slow, if 109 events often appear, 
 please check the appropriate equipment is a problem.
Through Windows 7or8 Event Viewer, we can identify the culprit cause system slow
start to improve system boot speed.

Note: The first in an event ID replaces two or three effects can be investigated shutdown
time and standby time factor*

*真是被它的系統"玩到傻"---現在可以寫作也可更新![差點被哪個系統氣到爆炸了]
只剩我的滑鼠左鍵--不能用於寫作文章上,若果它忽然又可用的話-----哪就太好了~!!
既然可以寫作....我當然是不搬了~!!哪我又要回頭去把那二百六十多篇文章回復發佈囉~~{真是命苦喔~!!}*
*It really is a system "play dumb" --- can now also be writing updates! 
 [Which system was almost the gas to explode] only my left mouse button - can not be used 
for writing articles on it if the suddenly it is available ----- which would be great ~!! 
Since writing .... of course, I can not move the ~!! which I have to go back and put that 
over two hundred sixty articles published reply Hello ~ ~ {really unlucky Oh!!}*
*정말 시스템이 "바보를 플레이"--- 이제 업데이트를 작성 할 수 있습니다
단지 내 왼쪽 마우스 버튼이 [어떤 시스템이 폭발하는 거의 가스습니다] - 
그 기사를 쓰기 위해 사용할 수없는 경우 갑자기 위대한 ~ 것 어떤 사용할 -----
 입니다! 쓰기 때문에 .... 물론, 내가 ~을 이동할 수 있습니다! 난 다시 가서 
예순 2 백 기사 회신을 게시 한 넣어야 할 어떤 ~ ~
{정말 재수 오!} 안녕하세요*
*

*
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&