I think this subject is taboo but . . . . .

[grits]

I've let it slide all this time because it always said "False" but this morning it says "True" so am now a bit concerned even though everyone says "don't pay any attention to Event Viewer".

 

[whs]

That is a very slow boot. Disable all startups and see what happens. You find Event 100 in

Eventvwr
Applications and Service Logs
Microsoft
Windows
Diagnostics - performance
Operational
Event ID 100

Just drill down this chain.

 

[carwiz]

We need to see the details to determine where the delay is occurring.

 

[grits]

@whs, My only startup is Avast. Don't know what you mean by "just drill down this chain".
@carwiz, Do you mean the 'Details tab' as shown in my shot? If so, I'm not sure of how to do that.

 

[carwiz]

Yes, the Details will list the timed areas of the Windows' boot process. These are given in milliseconds.

 

[carwiz]

I wouldn't just arbitrarily disable Start Up apps to see what happens. Some may be required by Windows and/or your hardware. To see the Start Up programs, Click on the Orb (Start), type msconfig in the search box then Enter. Click on the Startup tab along the top.

 

[whs]

I wouldn't just arbitrarily disable Start Up apps to see what happens. Some may be required by Windows and/or your hardware. To see the Start Up programs, Click on the Orb (Start), type msconfig in the search box then Enter. Click on the Startup tab along the top.

I have yet to see a startup that is required - except the AV. When needed, the disabled programs will start.

 

[carwiz]

Perhaps Wolfgang but I never took the chance. Does that hold true for USB3 and SATA drivers?

 

[whs]

Drivers are usually not in the startups.

 

[carwiz]

Oh contraire.

 

[whs]

Where are those drivers hiding. I have disabled most stuff anyhow.

 

[carwiz]

I must say, that's quite list. (Or was)

I have a Renesas USB3 monitor that runs at startup. Not sure if it's really needed but I have a disk drive attached to USB3. I can run a test later and find out. I also have a front display that needs a driver at startup. It's part of the IR remote control system I have. There's other types of hardware that need startup drivers too. Most of these are User Mode drivers (Non-kernel). One I used to have was a digital scientific scale. All I'm saying is that you can't make a general statement that covers all users without seeing the list.

Items like HotKeys, IAStore, Igfxtray and Igfxpers aren't really necessary for many folks but they have very little overhead and are fast to start. The convenience is worth the half second it takes to start those. The big guzzlers are Google update and other "phone home" starters.

 

[grits]

Here's the details from that day but today's is False again as it is most of the time.


Log Name: Microsoft-Windows-Diagnostics-Performance/Operational
Source: Microsoft-Windows-Diagnostics-Performance
Date: 11/27/2013 6:02:10 AM
Event ID: 100
Task Category: Boot Performance Monitoring
Level: Critical
Keywords: Event Log
User: LOCAL SERVICE
Computer: suzeq-PC
Description:
Windows has started up:
Boot Duration : 109282ms
IsDegradation : true
Incident Time (UTC) : ‎2013‎-‎11‎-‎27T12:59:45.624800000Z
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" />
<EventID>100</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>4002</Task>
<Opcode>34</Opcode>
<Keywords>0x8000000000010000</Keywords>
<TimeCreated SystemTime="2013-11-27T13:02:10.909200000Z" />
<EventRecordID>5170</EventRecordID>
<Correlation ActivityID="{02F15C40-F800-0000-C24C-E58B70EBCE01}" />
<Execution ProcessID="1556" ThreadID="2772" />
<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
<Computer>suzeq-PC</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="BootTsVersion">2</Data>
<Data Name="BootStartTime">2013-11-27T12:59:45.624800000Z</Data>
<Data Name="BootEndTime">2013-11-27T13:02:08.631600000Z</Data>
<Data Name="SystemBootInstance">469</Data>
<Data Name="UserBootInstance">455</Data>
<Data Name="BootTime">109282</Data>
<Data Name="MainPathBootTime">37582</Data>
<Data Name="BootKernelInitTime">17</Data>
<Data Name="BootDriverInitTime">5761</Data>
<Data Name="BootDevicesInitTime">1852</Data>
<Data Name="BootPrefetchInitTime">15272</Data>
<Data Name="BootPrefetchBytes">378671104</Data>
<Data Name="BootAutoChkTime">0</Data>
<Data Name="BootSmssInitTime">6521</Data>
<Data Name="BootCriticalServicesInitTime">1830</Data>
<Data Name="BootUserProfileProcessingTime">2289</Data>
<Data Name="BootMachineProfileProcessingTime">0</Data>
<Data Name="BootExplorerInitTime">15423</Data>
<Data Name="BootNumStartupApps">1</Data>
<Data Name="BootPostBootTime">71700</Data>
<Data Name="BootIsRebootAfterInstall">false</Data>
<Data Name="BootRootCauseStepImprovementBits">0</Data>
<Data Name="BootRootCauseGradualImprovementBits">0</Data>
<Data Name="BootRootCauseStepDegradationBits">13631488</Data>
<Data Name="BootRootCauseGradualDegradationBits">1048576</Data>
<Data Name="BootIsDegradation">true</Data>
<Data Name="BootIsStepDegradation">true</Data>
<Data Name="BootIsGradualDegradation">true</Data>
<Data Name="BootImprovementDelta">0</Data>
<Data Name="BootDegradationDelta">63846</Data>
<Data Name="BootIsRootCauseIdentified">true</Data>
<Data Name="OSLoaderDuration">2083</Data>
<Data Name="BootPNPInitStartTimeMS">17</Data>
<Data Name="BootPNPInitDuration">7237</Data>
<Data Name="OtherKernelInitDuration">719</Data>
<Data Name="SystemPNPInitStartTimeMS">7331</Data>
<Data Name="SystemPNPInitDuration">376</Data>
<Data Name="SessionInitStartTimeMS">8333</Data>
<Data Name="Session0InitDuration">2983</Data>
<Data Name="Session1InitDuration">383</Data>
<Data Name="SessionInitOtherDuration">3154</Data>
<Data Name="WinLogonStartTimeMS">14854</Data>
<Data Name="OtherLogonInitActivityDuration">5014</Data>
<Data Name="UserLogonWaitDuration">1325</Data>
</EventData>
</Event>

 

[grits]

I did msconfig a year or so ago.

 

[kbrady1979]

I had nothing but problems with Avast!.....nothing.but.problems.

 

[carwiz]

I've extracted and highlighted a few items that are unusually high. The OS load time is a little high but normal if you don't have a SSD. It looks like Prefetch is consuming a good chunk even though it's only loading 378Mb. You need to make sure your system HDD is being Defraged on a regular basis.

The next item is Windows Explorer start up. This could be caused by a library hold from Prefetch or just scattered files.
You can try this hot fix for a library hold: An update that improves the startup performance of Windows 7 and of Windows Server 2008 R2 is available

The balance of your startup time is Post Boot. It accounts for to nearly 72 seconds of your boot time. This can be caused by a large number of desktop items, user drivers or Windows Management Instrumentation (WMI) Service. To verify if it's WMI, check this Hot Fix Link. Don't do the hot fix unless you verify in your application event log that WMI is rebuilding.

 

[carwiz]

Also, this TechNet article is a good read and holds a lot of info on slow boots.
Root Causes for Slow Boots and Logons (sbsl) - TechNet Articles - United States (English) - TechNet Wiki

 

[grits]

Thanks carwiz, I'm not ignoring you, just need some time to check some of this out, although the TechNet article is pretty much over my head. Most likely my problem is my desktop, I've never taken time to plan out a filing system & save most things to desktop. I believe I've seen reference to drivers in several of the Event Viewer logs & think I saw WMI a time or so too.
Will get on this tomorrow.

 

[Britton30]

USB 3.0 and SATA drivers would be Services, not start up applications. I leave them to start with w7.