xbootmgr doesnt point out WHY an issue is happening, but CAN IT show a place in the Boot sequence where the system Locks up for a longer time.. and even fails?
Is there no way to trace where/ which driver/ file/ function is where a windows boot / shutdown errors out? esp a Failed Bootup
xbootmgr shows why boot is slow, but not why boot failed.
now with the boot report here it is the link to download it http://www.megaupload.com/?d=N5US3XQH
the trace is still incomplete, but I can see that Avast is terrible slow (29s
to start the service). primvirlaux
hat the same slowdown with Avast. Do you use a Beta version? I can't information about version 6.0.1325 only 6.0.1289. Remove Avast and try other alternatives. Also set the FontCache22.214.171.124 service to "on demand" because this service causes 5s hang of the boot (you can see this in the picture, too). Do you need the Yota Access Service (Modems) service
? if not, disable the service, too. this one takes 3s to start. The largest delay is caused by the Windows Search service. How large is your index? Try to rebuild the index and remove folders from the index.
What I can also see is a not correctly trained Prefetcher (you see a lot of cache misses (black)):
Run the optimization I linked in the first post. After doing the steps your Windows runs much faster.
3ware 9650SE-8LPML causes EventID 41 (Kernel Power) when system hibernates
ok, I thought the same, but I can't prove this idea. controllers (IDE, SATA, SCSI) and their drivers can often cause crashes and failures. Nice to hear that you figured this out. Maybe other users read this too and find the cause of their issue
Edited by MagicAndre1981, 10 October 2011 - 06:42 AM.