Jump to content

Trace Windows 7 boot/shutdown/hibernate/standby/resume issues


MagicAndre1981

Recommended Posts

I have no idea. You have several tools which interact during logon (McAfee, Check Point Identity Agent, Validity Sensors Fingerprint).

Do the old Clean boot approach to find which 3rd party tool causes the issue:

http://support.microsoft.com/kb/929135

Link to comment
Share on other sites


I have Googled a litle but I can't find or anderstand what are exactly "Hard Faults".

Since I have some, I have randomly downloaded some user .etl and it seams that all PCs have this kind of "Hard Faults".

Do you know what this UFO is? :hello:

Link to comment
Share on other sites

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.com/u/435242/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

Edited by Woomera
Link to comment
Share on other sites

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

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:

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.

[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.

Link to comment
Share on other sites

  • 3 weeks later...

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?

Edited by fishmcfish
Link to comment
Share on other sites

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.com/u/84817323/TraceLog120606.zip

Edited by darthgrader
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...