[vladv]

I should run chkdsk.exe manually for the entire disk,or only for C: partition(Windows 7)?Or should I set it to check the whole disk when I reboot?

This post has been edited by vladv: 21 March 2011 - 01:05 AM

[MagicAndre1981]

run chkdsk /r /f for all drives. I can't see which drive autochk checks.

[vladv]

Thanks for help,I will check all my partitions now. I hope next time Windows will boot faster.

[MagicAndre1981]

I checked the trace again and saw that autocheck runs for volume 7 = drive G

[nagashima]

I did what you suggested and my notebook boots faster now.

Thank you

Nagashima

[MagicAndre1981]

nice to hear that it works.

[teohenwhy]

MagicAndre,

Can you take a look at my bootlog and see if there is anything I can do to speed it up? Thanks in advance.

http://www.mediafire...wvv8iq9yajnba1a

[MagicAndre1981]

your Windows boots ok.

It takes 22s to boot to the desktop and 40s to boot completely.

I can see that the AVG services take too long to start. is this the latest version?

Also the longest delay is caused by the running tools at startup. This takes 18s. So reduce the number of of tools.

If this still doesn't speedup Windows, upload the ETL file.

[teohenwhy]

MagicAndre1981, on 29 March 2011 - 10:01 AM, said:

your Windows boots ok.

It takes 22s to boot to the desktop and 40s to boot completely.

I can see that the AVG services take too long to start. is this the latest version?

Also the longest delay is caused by the running tools at startup. This takes 18s. So reduce the number of of tools.

If this still doesn't speedup Windows, upload the ETL file.

hmmm running tools at startup? I only have a couple things in my startup settings in MSCONFIG as you can see in the attached photo.

Attached File(s)

•  3-29-2011 3-42-22 PM.jpg (146.41K)
  Number of downloads: 12

This post has been edited by teohenwhy: 29 March 2011 - 04:49 PM

[MagicAndre1981]

upload the ETL file

[Lutribu]

I'm having slow boot time in my win7 x64, specially after screen "preparing your desktop", it takes 3 minutes to apear the desktop. I have uploaded my .etl trace and the event i think is making this delay, the "preShellInit", it takes 222092ms, in this link: My link
Can you give some tips?
Please help me with possible solution to this problem.
Thanks!

[teohenwhy]

MagicAndre1981, on 29 March 2011 - 05:17 PM, said:

upload the ETL file

here you go

This post has been edited by teohenwhy: 30 March 2011 - 08:21 AM

[sirbuctin]

Hello,

I tested my boot too and i see in the .etl file that there are no activityes of processor, disk, readyboot or somthing else until second 11.
The only thing i see from second 0 to 11 is under Process Lifetime, Idle (0) System (4).
At second 11 begins all activityes and ends at second 22
The test was made on clean win7 64bit with default windows drivers.
After i install mb chipset drivers, the test have no activity anywhere from second 0 to 18
The same as first from 0 to 18 is just the process idle 0 system 4.

Can some one explain what would be the cause pls!?
The proc is phenom x4 955 3,2 , hdds are : primary sata2 raid 0 2x7200rpm secondary 1 sata2 7200 hdd, 4GB ddr 1600, video gtx260.

I have uploaded the 2 test (with and without drivers installed at http://allschematics.com/results.zip ) filesize is 6MB

Thanks for help

[MagicAndre1981]

teohenwhy, on 30 March 2011 - 07:55 AM, said:

here you go

you have a lot of tools at startup:

"C:\Program Files (x86)\MSI Afterburner\MSIAfterburner.exe" /s
"C:\Program Files (x86)\Google\Update\GoogleUpdate.exe" /c
"C:\Program Files (x86)\Coretemp\Core Temp.exe"
"C:\Program Files (x86)\RocketDock\RocketDock.exe"
"C:\Program Files (x86)\RivaTuner v2.24 MSI Master Overclocking Arena 2009 edition\RivaTuner.exe" -T
"C:\Users\Tony Ly\AppData\Local\Microsoft\Windows Sidebar\Gadgets\GPUMonitor[1].gadget\GPUMonitor.exe"

and I can see that the AVG driver/service slows down the boot. Do you use the latest version?

[MagicAndre1981]

Lutribu, on 29 March 2011 - 09:05 PM, said:

Can you give some tips?

<timing bootDoneViaExplorer="254314" bootDoneViaPostBoot="281214" 

Your Windows takes 254 seconds to boot to the desktop and 271 seconds to boot completely.

 <interval name="WinlogonInit" startTime="14322" endTime="248822" duration="234499">

The WinlogonInit takes too long. I saw that restoring the network connection takes most time:

RestoringNetConnections:

22.643866982 (start)
248.484303871 (stop)

I saw that the NFS driver has long delays. Do you connect NFS drives? Are they available? Connect the drivers after the boot with net use /permanent:NO from a cmd you start to avoid this hang.

[MagicAndre1981]

sirbuctin, on 30 March 2011 - 05:13 PM, said:

I have uploaded the 2 test (with and without drivers installed at http://allschematics.com/results.zip ) filesize is 6MB

Thanks for help

ok, the first delay is here:

interval name="PreSMSS" startTime="0" endTime="20665" duration="20665">

and I saw that this device takes too long to enumerate connected drives:

pnpObject name="PCI\VEN_1002+DEV_4393+SUBSYS_B0021458+REV_00\3+2b8e0b4b+0+88" type="Device" activity="Enum" startTime="7380" endTime="17486" duration="10106" prePendTime="10106" description="AMD AHCI Compatible RAID Controller" friendlyName="" /> 

How many HDDs have you connected to the RAID controller? I can only see this in the trace sys config: AMD 2+0 Stripe/RAID0 SCSI Disk Device

the trace doesn't have all data. Run the normal trace from my other guide and add this to the command line:

-postBootDelay 300

this traces 5 minutes (300 seconds) after the boot is finished.

Upload the new traces, please.

[sirbuctin]

Hello,

i have run this command from your other guide.. (i think you refered to this command)
xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -postBootDelay 300 -resultPath C:\WPA

i have uploaded the result : http://allschematics.com/result.zip

The drives connected in raid 0 are only 2 HDD. i have also a single hdd connected as IDE mode (throught sata too) and a dvd-ram conected as Sata mode i think.

All drives are sata2 (i think the raid controller handle all drives. even if they are not in raid. All 6 sata2 ports are handled by amd RD750 chipset i think, southbridge)
I hope its not the number of drives that giveing the delay, cause i am expecting today for another 2 drives for the raid array.
Also, the bios is building the raid array before windows is loading ( and its detected fast,,, about 3 second).

Thank you

[teohenwhy]

Magic Andre can you tell me what this is and why it takes so long?
process name="xbootmgrSleep.exe" startTime="30200" endTime="150369" lifetime="120168" />

[MagicAndre1981]

teohenwhy, on 31 March 2011 - 07:29 PM, said:

Magic Andre can you tell me what this is and why it takes so long?
process name="xbootmgrSleep.exe" startTime="30200" endTime="150369" lifetime="120168" />

this is the default 120 wait time of xbootmgr after you get to the desktop.

[MagicAndre1981]

sirbuctin, on 31 March 2011 - 05:24 PM, said:

i have run this command from your other guide.. (i think you refered to this command)
xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -postBootDelay 300 -resultPath C:\WPA

i have uploaded the result : http://allschematics.com/result.zip

yes, this was ok so.

your boot is no much faster:

timing bootDoneViaExplorer="25391" bootDoneViaPostBoot="36391" osLoaderDuration="1527"  postBootDisturbance="1000"

Windows boots in 25s to the desktop and is loaded in 26s (1s startup programs delay) completely.

But the main issue still occurs:

phase name="bootStart" startTime="34" endTime="15282" duration="15248">
  <pnpObject name="PCI\VEN_1002+DEV_4393+SUBSYS_B0021458+REV_00\3+2b8e0b4b+0+88" type="Device" activity="[b]Enum[/b]" startTime="4811" endTime="14911" [b]duration="10100" [/b][i]prePendTime="10100"[/i] description="AMD AHCI Compatible RAID Controller" friendlyName="" /> 

the RAID controller still takes 10s to enum. I found this in the documentation about the prePendTime:

Quote

The PrePendTime in each instance is equal to the duration. The prePendTime indicates how long the driver processed the IRP in its start or enumeration dispatch routine before it returned STATUS_PENDING. This value should be as close to 0 as possible. If it equals the duration, the driver did not pend the IRP.

so try a newer AMD Raid driver and if this doesn't fix it, contact the AMD support for an updated driver which does it faster.

This post has been edited by MagicAndre1981: 01 April 2011 - 08:46 AM