Trace Windows 7 boot/shutdown/hibernate/standby/resume issues
Posted 08 March 2012 - 09:00 AM
from the trace I can see that the System process causes some high CPU usage and the causing function is:
xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER+LATENCY+DISPATCHER+PERF_COUNTER+PRIORITY+REGISTRY+FILE_IO+FILE_IO_INIT -stackWalk Profile+ProcessCreate+CSwitch+ReadyThread+Mark+ThreadCreate -resultPath C:\TEMP
this captures some more data (CSwitch, ReadyThread, CPU usage, threadcreate).
But you should still check the HDDs and your OCZ SSD. Also create a full back of the Systemdrive and install the 1.35 firmware, your 1.11 is a bit old:
Posted 08 March 2012 - 04:49 PM
Also, do you run the HDD and SSD in IDE or AHCI mode? If IDE change to AHCI.
This post has been edited by MagicAndre1981: 08 March 2012 - 05:12 PM
Posted 09 March 2012 - 03:30 AM
I have an SSD installed and disabled various services: search, prefetch, hybernate etc.
Thanks a lot!
Edit: Forgot to tell this PC is part of a domain.
This post has been edited by leof: 09 March 2012 - 03:47 AM
Posted 09 March 2012 - 05:49 AM
+ <interval name="WinlogonInit" startTime="10347" endTime="300105" duration="289757">
entering the password takes so long:
Number of downloads: 9
so type in the password faster.
Posted 09 March 2012 - 11:26 AM
I use a domain logon.
I also inform you that a reboot doesn't take much time. Resume after Standby (not hybernate) doesn't take a long time either. Unless the Standby mode has been for a longer period, i.e. more than an hour or so. In that case the resume would take several minutes.
Posted 09 March 2012 - 11:45 AM
I've been debugging a slow Windows 8 CP boot for days and can not figure it out. Symptoms are a 50 Second boot time. . .
It seems that StorPort.sys and WDF01000.sys are stalling the process but both are MS drivers so I can't disable to isolate the problem.
Boot Trace is here -
and System Summary is here -
Of course if there are any other problems that you see (I left the trace running for the full 120 seconds post boot) I would appreciate the comment!
Thanks a ton in advance,
This post has been edited by vicbyrd: 09 March 2012 - 11:46 AM
Posted 09 March 2012 - 01:05 PM
Number of downloads: 14
Number of downloads: 10
Which device have you connected to this USb3.0 controller?
Also, run WinSAT to calculate the Experience Index so that Superfetch is stopped. Currently the service runs which is not recommend for SSD drives.
Posted 09 March 2012 - 03:15 PM
Worked a treat! Disabled USB3.0 in BIOS and disabled ASMedia SUB 3.0 devices (both ports) in Device Manager. Reduced boot time to about 15 seconds.
BTW, in your previous reply, what table did you snapshot to show the offending drivers? I was not offered that view in xperfview.
Thanks - you 'da man,
Posted 10 March 2012 - 08:46 AM
You should also send this to Microsoft. Go to connect.microsoft.com, join the IE10 feedback, download the Feedback tool and install it on Windows 8 and tell MS the issue and send them the xbootmgr trace file.
look at the "boot phases" graph and you see that SMSSInit/Session Int takes some time.
Number of downloads: 16
In my first post I wrote that Windows loads all not boot relevant drivers and starts all not boot relevant devices. So make selection in the bootgraph that covers the delay, right click and select "clone selection". Go to the "Generic events" graph and make a rightclick in the highlighted area and make a rightclick and select "Summary table". Now expand the "Microsoft-Windows-Kernel-PnP" and under "DeviceStart" you can see that gap in the Time:
Number of downloads: 13
To see which device it was, I opened the "System Configuration" under "Traces" and look in the PnP table and found which devices use those IDs:
Number of downloads: 7
This was all I did. Took my 5 minutes
have you made a new trace?
Posted 12 March 2012 - 06:43 AM
Discovered something: when I typed my password while the screen was black, nothing happened at first. But when finally my monitor lit up, the desktop was displayed in stead of the logon screen!
First thing I now did was replace the monitor cable. But maybe it's a monitor problem. I have a spare one so I will go on to experiment.
I will keep you informed how this develops. In the mean time I thank you for your attention!
Posted 12 March 2012 - 02:16 PM
Thanks for the explanation of how you displayed the offending device on my machine. I've run thru the steps and now feel confident that I could troubleshoot a bad driver in the future. My machine has run flawlessly all weekend. Based on the # of reboots that one normally goes thru during a new OS install I'm guessing you saved me about 24 hours.
Thanks for all your help,