• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
MagicAndre1981

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

1,275 posts in this topic

It worked, should I post the log or should I zip it? Where would I upload it to?

0

Share this post


Link to post
Share on other sites

Zip it up with the archiver of your choice, such as 7-Zip, then upload it to the online service of your choice, such as MediaFire, then post the link here.

Cheers and Regards

0

Share this post


Link to post
Share on other sites

your HDD is busy and so it the bootleneck:

HDD.png

replace the HDD with a SSD to speed up boot a lot.

0

Share this post


Link to post
Share on other sites

Great post. Thanks for the info. I am profiling the boot process with a restricted user. I login as the user but do not get the post login box. Therefore, I never get the completed trace file. I get the boot_1_km_premerge.etl and the boot_1_um_premerge.etl files bit not the final boot_1.etl file. Is there anyway around this? Thanks.

0

Share this post


Link to post
Share on other sites

you need to be admin user to use the tools.

0

Share this post


Link to post
Share on other sites

So that is the only thing you could see then? The only cure is to spend a few hundred dollars on an ssd? That stinks.. But thanks for checking it out for me andre I really appreciate it

0

Share this post


Link to post
Share on other sites

no, there is no other fix. Your Seagate Momentus 5400.6 500GB (ST9500325AS) is very slow.

Replace the HDD with the 120GB Samsung 840 Evo for 90$ (http://www.newegg.com/Product/Product.aspx?Item=9SIA2W01AZ5378), buy HDD caddy, remove the DVD drive and put the caddy + your old HDD in the slot of the old DVD drive.

Install Win7+ important programs on the SSD and store all data on the HDD.

0

Share this post


Link to post
Share on other sites

your slow HDD is the cause and busiy for over 70s:

disk_utilization.png

Well I reformatted, reinstalled all my software exactly like before and its been a few weeks. Boot up is 47 seconds and all my tray programs load in 5 seconds vs 25 seconds before.

My advice, if your going to run this boot optimization make sure you have a good backup handy, you'll eventually need it.

0

Share this post


Link to post
Share on other sites

Andre,
I hear you are THE guy to talk to about slow bootup/start issues. If you can help out, I'd really appreciate it.

Working on my parents' computer (Dell XPS 435MT X58/ICH10R w/ i7-920, 6GB RAM DDR3-1066, HDS721075KLA330, Win7 SP1 Home Premium x64) and I noticed starting from cold boot is DARN slow. (Attempting to talk them into an SSD upgrade to get them by until they can afford their next PC...)

Shutdown's not a problem, and they don't normally hibernate or sleep that often... but cold boot is terrible! Many, many minutes.

Attached trace hosted on mediafire. Is it supposed to be this huge?!
http://www.mediafire.com/download/5kkoqclzujz8xm1/schade_trace.zip

I attempted to run xperf on the trace but it gave me the following warning:

xperf: warning: applying restriction of access for trace processing97993 Events were lost in this trace.Data may be unreliable. This is usually caused by insufficient disk bandwidth for ETW logging.Please try increasing the minimum and maximum number of buffers and/or the buffer size.Doubling these values would be a good first attempt.Please note, though, that this action increases the amount of memory reserved for ETW buffers, increasing memory pressure on your scenario.See "xperf -help start" for the associated command line options.

FWIW, Dell has restricted their BIOS to only listing IDE/RAID as interface choices, and it is currently operating in IDE mode - but I hear if I load the RAID drivers and switch the BIOS to RAID, it will effectively activate AHCI for all SATA ports, even if running JBOD.

I've installed the hotfixes you mentioned for Windows 7. Aside from switching to AHCI mode for the HDD, and running the BootVis-like xbootmgr optimization on the HDD, and eventually switching to a SSD... please let me know if you see further optimizations.

(I've been suspicious the HDS721075KLA330 might be running at a reduced speed for a while, due to error/issues/age/miconfiguration?)

0

Share this post


Link to post
Share on other sites

starting the device ("USB\VID_0644&PID_0201 - CAB-200) takes very long:

StartDevice.png

What is this?

0

Share this post


Link to post
Share on other sites

What is this?

Just in case:

[strings]

PRODUCT_COMPANY = "TEAC"

PRODUCT_SERVICE = "USB Card Reader Driver"

SOURCEDISK_DESC = "Source Disk #1"

USB\VID_0644&PID_0201.DeviceDesc = "CAB-200"

USB\VID_0644&PID_0200.DeviceDesc = "CA-200"

jaclaz

0

Share this post


Link to post
Share on other sites

starting the device ("USB\VID_0644&PID_0201 - CAB-200) takes very long:

StartDevice.png

What is this?

Thanks for looking!

I noticed that the other day and actually know about it, but hadn't thought about it slowing down boot, it's a USB device that's currently Code 10 (Device failed to start).

CAB-200 is TEAC CAB-200, part of a USB multifunction device built into that Dell Studio XPS (as well as others). It's a 3.5" front-panel-accessible drive that connects to the motherboard using a Dell proprietary connector. It provides Bluetooth 2.0+EDR and is also a 4-slot 19-in-1 memory card reader.

I was going to try the suggested things here to try to solve the Code 10:

http://en.community.dell.com/support-forums/desktop/f/3514/t/19243511.aspx?pi21953=1

Which are basically:

1. Make sure you're using the newest Dell-specific firmware/drivers for the device (roll back any non-Dell drivers installed by Windows Update or otherwise.)

2. Mess around with the USB connector

3. Properly ground the drive (correcting a design flaw) using a longer screw or grounding wire.

4. Worst case scenario, replace the drive.

That said, my dad over the years (this is a 2009 machine) found the Dell bundled Bluetooth keyboard/mouse too finicky and stopped using them, favoring wired USB input devices. (and that's all he uses the Bluetooth for.)

Furthermore, the 19-in-1 front bay memory card reader no longer supports the memory cards he uses from his Canon DSLR so he mostly favors a Sandisk 52-in-1 USB memory card reader he has.

So I may be safe to unplug the device!

---

Can you tell me about anything else? I'm headed over there in a few hours. :-)

0

Share this post


Link to post
Share on other sites

disable it and give me a new trace

0

Share this post


Link to post
Share on other sites

Since I was over there this evening for once (it is infrequent), although realizingti it is not scientific, I decided to do a bunch of changes:
- fix or disable the Bluetooth/Memory card reader combo device
- update all the drivers (video/audio/network/etc.)
- update some programs
- convert over to "RAID" (which supposedly enables AHCI in this BIOS)

I was able to fix the combo device, and boot time was noticeably improved. If you still think it must be disabled, let me know.

However, now I have become victim to the BSOD-on-startup-drivertrace.

At the links below you can find traces even though it recovered from BSOD during the boot

schade_trace2.zip (suffered from one BSOD): http://www.mediafire.com/download/53m5vlj5zb9y9dy/schade_trace2.zip

schade_trace3.zip (suffered from two BSOD's!): http://www.mediafire.com/download/pbmewcqxqzwfo5e/schade_trace3.zip

schade_trace4.zip (no drivers traced, no BSOD's): http://www.mediafire.com/download/65wipf6gk3gahyq/schade_trace4.zip

With no xpmboot trace running, there is no BSOD.

Not sure where it's stashing the memory minidumps (it's not %Systemroot%\minidump like the settings are)

0

Share this post


Link to post
Share on other sites

Started with a long boot, 6min to desktop idle, i made some changes to services in use watching at traces in WPA, up to reducing boot to about 4min. Sometimes doing myself, I.e., the searchindexer is slower if set to automatic/delayed than to automatic start.

By the way, I could be satisfied, the WPA tools are effective in pointing to retarding services.

But...

I cannot understand why the Services traces are blank for long, about 2min complessive, in the middle of postboot.

What is the boot schedule doing in this empty events?

Of course, the system hard disk is slight fragmented and slow, 5400rpm, but i could not believe it could produce the 2min lag.

This feeling, the computer is hiding a starving cpu program, must be added to other in normal operation, like a dumb responsiveness while low cpu usage is shown in taskmanager. And also, to slow scan of folders when selected into explorer panes.

Notice that system is cleaned with major a-malawares, found only tracing cookies, no viruses, no pup.

Any suggestion?

0

Share this post


Link to post
Share on other sites

the BSODs come from the DRIVERS flag.

In tarce4 the disk is busy all the time:

HDD_bootleneck.png

The queue depth at 91 is bad. Get a faster disk like a SSD.

0

Share this post


Link to post
Share on other sites

@teebe

run this command, this captures waitings and some DISK and File IO data:

xbootmgr -trace boot -traceFlags BASE+LATENCY+DISPATCHER+FILE_IO+FILE_IO_INIT+FILENAME -stackwalk profile+CSwitch+ReadyThread -resultPath C:\TEMP

Zip the ETL file and give it to me.

0

Share this post


Link to post
Share on other sites

the BSODs come from the DRIVERS flag.

 

In tarce4 the disk is busy all the time:

 

HDD_bootleneck.png

 

The queue depth at 91 is bad. Get a faster disk like a SSD.

Okay, guess I'm done optimizing then... thanks!

I'll try to convince my parents to purchase an SSD or buy a new computer.

0

Share this post


Link to post
Share on other sites

Hi MagicAndre.

 

Can you help me with my boot? It takes a long time in the 'Loading Windows' screen, almost 20 sec and its a new install on a new SSD. I see the problem should be in the PreSMSS or SMSSInit.

Heres my trace: http://www.firedrive.com/file/3B93FE1743672C7D

 

Thanks!

PD: Sorry for my english :}

0

Share this post


Link to post
Share on other sites

Enumerating the IDE channels causes the PreSMSS and running autochk.exe (chkdsk) the SMSSInit dealay.

0

Share this post


Link to post
Share on other sites

Hello,

 

Newly created Windows 7 image is taking around 3-5 minutes or so to log off and then shutdown (some computers a lot longer).  Our machines are apart of a domain.

 

I have tested to see if this was a page file issue, but even with disabling the page file completely, I still have the same issue.

 

So I created a trace using the Windows Kits. 

 

From the trace analysis I can see that:

 

logonui.exe has a start time of 5.08 secs and end time of 230.03 secs (end of log).

WMIADAP.exe has a start time of 17.24 secs and end time of 93.199 secs.

SearchFilterHost.exe has a start time of 39.99 secs and end time of  145.02 secs.

 

Everything else is really quick.  I went through about 6-7 pages on this forum and didn't recognize my issue.

 

Please help - this is a very annoying problem as you know and my users are getting frustrated.

 

Any help would be very much appreciated.

 

- Kyle

0

Share this post


Link to post
Share on other sites

I need the ETL to see more.

0

Share this post


Link to post
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.