Slow booting problem resolved after BSOD

Hi. It was suggested that I post here after my slow booting problem resolved itself after a BSOD. The BSOD happened when I inadvertently unplugged a USB device whilst the PC was coming out of hibernation.

The PC is fine now, but perhaps the crash dump files (it will be the later of the two files that will be relevant) may lead someone to be able to say why the PC booted so slowly - could be useful for someone at some stage in the future?

The original thread is here:

http://www.sevenforums.com/performance-maintenance/222532-boot-trace-slow-boot-2.html

Thanks,

Martin

Well, the crashdump is just going to show you just what caused the crash, and being a minidump, it's lucky enough to go so far as to tell you that! Though in this case yes, the USB device was the problem.

The only way one could tell what was going on with your slow boot up would've been via the etl logs requested in the aforementioned thread. That's what Kaktussoft was referring too in the previous thread: to post the .etl with that huge filename for inspection, not to type it as a command.

I guess you haven't read what I have posted over the past several weeks.

1. I posted the dump file at the request of Gregcrocker, who thought there may be some information pertaining to the slow boot - possibly. If not, so be it.

2. I cannot get any meaningful etl files as my boot trace always ends in error messages. I was troubleshooting this with cluberti (who looked at the etl files I did produce, in spite of the error messages, and said they were not useful for analysis purposes), but there was no resolution. For now it is irrelevant as the PC boots just fine. We may never know why.

M

Hmm, interesting. I did take a look at other people's scenarios regarding etl dump creation. Some said turning off Windows Search service did the trick. Again, not sure on it, and we'll probably never figure it out.

Yes, I tried a number of variations on the boot string (adding +DRIVERS aleways gave a BSOD on reboot) but it always ended in an 'unable to terminate boot trace' error. Cluberti stopped replying after a while (a busy man!) so I guess the reasons for the trace failure (or evidence that it was the BSOD that cured my slow boot problem), as you say, may never surface.

M