[MagicAndre1981]

was WPT (C:\Program Files\Microsoft Windows Performance Toolkit) added to the PATH environment variable? if not, add it:

http://www.windows7h...s-in-windows-7/

[Woomera]

yep that fixed and as you mentioned at first post i got a BSOD
gonna try the other command

[Woomera]

ok so i got an error tryin to start windows after using the second option with no drivers.
something about failing to merge a file. forgot to take screenshot is this a known issue?

edit: k so i did another reboot and got the error again, got a screen
http://dl.dropbox.co...2/wpt-error.JPG

and also after that bsod now adding the path to system variables doesnt work anymore so i opened the wpt folder and typed it there

This post has been edited by Woomera: 07 May 2012 - 03:22 PM

[MagicAndre1981]

please try the suggestions from here:

http://social.msdn.m...d6-e466c07e1a2f

[fishmcfish]

Andre,

I know you've encountered this issue with other before but I'm hoping you (or anyone else) might have a solution. When I attempt to run a boot trace

Quote

xbootmgr -trace boot -traceFlags BASE+CSWITCH+POWER -resultPath C:\TEMP\default

I receive the error message when boot trace finishing counting down after the desktop loads:

Quote

Couldn't find user-mode logger in active logger list.
Unable to stop trace.
Stopping trace...
Couldn't find kernel logger in active logger list.
Couldn't find user-mode logger in active logger list

This leaves me with unmerged .etl files. I will copy the entire xboottrace log below.

In a previous post you linked to a forum where they suggested manipulating registry entries, but I am concerned doing so may enable ReadyBoost, Superfetch, or Disk Defrag. I want to avoid this because I am using an SSD as my system disk.

Any suggestions?

Thanks.

Quote

[2012/05/12-13:29:50.812] Detected inactive Win7 physical (ReadyBoot) prefetcher (the SysMain service start type is 4).
[2012/05/12-13:29:50.828] Registering for auto-run with a 120000 msec delay...
[2012/05/12-13:29:50.828] Completed auto-run change.
[2012/05/12-13:29:50.828] Starting trace...
[2012/05/12-13:29:50.999] Enabled boot logging to 'C:\TEMP\default\boot_BASE+CSWITCH+POWER_1_km_premerge.etl'
[2012/05/12-13:31:29.992] Detected inactive Win7 physical (ReadyBoot) prefetcher (the SysMain service start type is 4).
[2012/05/12-13:31:29.992] Stopping trace...
[2012/05/12-13:31:30.335] Stopped kernel logger.
[2012/05/12-13:31:30.335] Couldn't find user-mode logger in active logger list.
[2012/05/12-13:31:30.335] Unable to stop trace.
[2012/05/12-13:31:30.335] Stopping trace...
[2012/05/12-13:31:30.366] Couldn't find kernel logger in active logger list.
[2012/05/12-13:31:30.366] Couldn't find user-mode logger in active logger list.
[2012/05/12-13:31:30.366] Unregistering auto-run...
[2012/05/12-13:31:30.366] Completed auto-run change.

[MagicAndre1981]

Superfetch seems to be disabled. Enable the service again.

[fishmcfish]

MagicAndre1981, on 13 May 2012 - 02:20 PM, said:

Superfetch seems to be disabled. Enable the service again.

I do not want to enable Superfetch because my OS drive is an SSD.

I successfully created a boot trace about six months ago without Superfetch enabled.

Any ideas?

This post has been edited by fishmcfish: 31 May 2012 - 05:38 PM

[MagicAndre1981]

set the startyp to manual/on demand and not disabled.

[darthgrader]

I am looking for assistance in shortening my boot time to some thing reasonable.

Slow boot up with windows 7 64 bit. Asrock Z68 Extreme4 motherboard, 16 GB ram, AMD Saphire 5770 video, 240 GB OCZ Agility Sata3 SSD, 1 TB WD black internal drive, 3 TB WD30EZRX internal drive. Boots in 19 s after bios with internal drives disconnected, 22 s with 1 TB drive connected, but 97 s when 3 TB drive is added. Last bios update for MB installed. Latest Windows updates installed. No firmware update for the WD30EZRX drive that I am aware of. FWIW, I orignially used ghost to transfer the contents of a 1 TB drive to the 3 TB drive, which turned the drive into a 2 TB drive requiring a removal of partion etc to restore to a functioning 3 TB drive. I ran trace but I will admit it means little to me. It might mean more if I disconnected the 3 TB drive and ran it then so I could compare the 22 s boot to the 97 s boot with the 3 TB drive added, but this is not really my strong suit.

I believe I have attached the trace file, but if not I'm sure you will let me know.
Thanks!

Link added: http://dl.dropbox.co...ceLog120606.zip

This post has been edited by darthgrader: 11 June 2012 - 09:14 PM

[MagicAndre1981]

I can't see a link to the trace. Compress the tarce file (the large ETL) als 7z or RAR and uplaod to your SkyDrive, Dropbox, Google Drive and send me a link.

[darthgrader]

Dropbox took an overly long time to upload, about an hour for 110 K file! Surely there is something faster than that! If I had compressed the file would I have been able to attach it to my message instead of using Dropbox?

[MagicAndre1981]

You have issues with loading the drivers at first stage of boot (PreSMSS - read the first post to understand what this means). This takes 45s in your case:

 <interval name="PreSMSS" startTime="0" endTime="45375" duration="45375">

The Microsoft-Windows-VolumeSnapshot-Driver seems to take nearly 30s to start.

I see you use an OCZ-AGILITY3 with firmware 2.12. The latets version is v2.22. So update the frmware and look if this has an impact.

Also do you run your SSD in IDE or AHCI mode? And to which port have you connected it? To the Marvell 91xx SATA 6G Controller or to the Ports of your chipset? Try to fix this and it should fix the delays.

[darthgrader]

Since it boots in 19 s with the two WD hard drives disconnected, I am wondering how the firmware of the OCZ drive could be an issue? Also, since it boots in 22 s with the addition of the 1 TB black WD drive, it seems the issue must be directly related to the addition of the 3 TB WD green drive!! With the OCZ and 3 TB drive the boot time jumps to the 95 s mark. No drives are currently connected to the Marvell controller. Connecting the 3 TB drive to the Marvell controller made no significant difference to the boot time. Neither did changing the respective ports of the other drives on the non Marvell ports. All drives are running in AHCI mode. The OCZ drive and th 3 TB drive are both Sata 6G drives and are both connected to those ports on the MB, although I did try other ports for the 3 TB drive to no avail.

[MagicAndre1981]

Make 3 traces with this command:

xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -stackwalk profile

Now run this command when you use the SSD only, when you have 1 WD connected and when you have both WD connected.

[darthgrader]

Trace for SSD only attached.

[doveman]

Hi MagicAndre1981

I'm not sure this comes within the scope of this thread, so maybe there's another one you'd like me to take this to. The problem I have is Windows NOT going to standby for no apparent reason (Windows seems absolutely terrible at giving the user any useful information about what's preventing standby). It works half the time and then other times just doesn't, so it's not any devices that are preventing standby.


If I do powercfg - requests it shows

C:\Users\MediaPortal>powercfg -requests
DISPLAY: None.
 
SYSTEM:
[DRIVER] \FileSystem\srvnet
An active remote client has recently sent requests to this machine.
 
AWAYMODE: None.

but I've used the tweak to "Enable standby with remote opens" in Power Options and powercfg -requestsoverride shows

C:\Users\MediaPortal>powercfg -requestsoverride
[SERVICE]
 
[PROCESS]
 
[DRIVER]
\FileSystem\srvnet SYSTEM

I've got LogMeIn installed, which has an option at install to "Prevent standby when AC power is available". I'm not sure how it enforces that, but I unticked it anyway so that shouldn't be the problem. I also have TightVNC installed and both of these use mirror drivers but I don't think there's any reason why they'd prevent standby.

[darthgrader]

MagicAndre1981, on 15 June 2012 - 12:07 AM, said:

Make 3 traces with this command:

xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -stackwalk profile

Now run this command when you use the SSD only, when you have 1 WD connected and when you have both WD connected.

http://dl.dropbox.co...SSD_1TB_3TB.zip

http://dl.dropbox.co...R_1_SSD_1TB.zip

http://dl.dropbox.co...POWER_1_SSD.zip

If attaching files actually works on this site, it is not obvious how! It says it will, the files are under 500 k, as required, the files show up in the required window, then nada!

This post has been edited by darthgrader: 16 June 2012 - 06:29 AM

[Steve00]

I have red almost every post in this subject, tried every tweak which I could find on the internet and nothing, reinstalled system several times, disabled every proccess (win and no win) which could be disabled, and still shut down time on win 7 on asus laptop is to long.

Basically, I have a problem with NtShutdownSystem interval, which lasts 67,5 seconds.

If anyone have any idea, shout it out.



Here is xml summary_shutdown file:

Attached File(s)

•  summary_shutdown.xml (31.69K)
  Number of downloads: 6

[MagicAndre1981]

doveman, on 16 June 2012 - 03:43 AM, said:

I'm not sure this comes within the scope of this thread, so maybe there's another one you'd like me to take this to. The problem I have is Windows NOT going to standby for no apparent reason

please start a new topic in the forum for your Windows version.

[MagicAndre1981]

darthgrader, on 16 June 2012 - 06:26 AM, said:

http://dl.dropbox.co...SSD_1TB_3TB.zip

http://dl.dropbox.co...R_1_SSD_1TB.zip

http://dl.dropbox.co...POWER_1_SSD.zip

If attaching files actually works on this site, it is not obvious how! It says it will, the files are under 500 k, as required, the files show up in the required window, then nada!

With SSD only you have a delay in SMSS mostyl caused by the driver SiRemFil.sys:

 driver_delay.png (31.66K)
Number of downloads: 2

This is the Silicon Image SATALink controller driver. So I asked this after your first post. The detection of the drives was slow, so connect the WD and the SSD to different SATA ports on your mainbaord. Tghe same delay is also present in all other traces.