How to speed up boot process under Windows Vista or Windows 7

[compsavvy]

Another thing, just checked that the lanmanserver corresponds to server service of windows which is responsible for file sharing etc. I am generally not connected to a home network but use file/hardware sharing occassionally. However, I am always connected to a wireless access point used to connect to the internet. So, what do you suggest?? Should I disable the service?

[MagicAndre1981]

set the service starttyp to "manual - on demand" . Create a Task with the Taskscheduler which starts the service (command: C:\Windows\System32\net.exe, parameter start LanmanWorkstation) and run it on demand when you need the file sharing/network drives.

I've explained this here in detail:

http://www.msfn.org/board/index.php?showtopic=135472

[compsavvy]

Thanks for your help

It has helped greatly in improving the boot time by 3-4 secs

[MagicAndre1981]

Thanks for your help

You're welcome

[compsavvy]

@andrei

I was trying to run boot trace with drivers flag on win 7 x64 but I got a BSOD. It appears there seems to be a issue with wpt.

Do you know of any workaround??

[MagicAndre1981]

no. I emailed this to a MSFT employee who works on WPT, but he has not answered. Xperf is the CLI tool to start traces. The functions to start traces are in the Windows kernel. So it is an issue with Windows. Can you open the dmp with WinDbg and look if you also get the USB issue?

[compsavvy]

I have downloaded debugging tools but dont know how to analyse the dump for the information you require

[MagicAndre1981]

in WinDbg press CTRL+S and add the symbol path:

SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

open the dmp and run !analyze -v and post the output here.

[compsavvy]

@andrei

When I wanted a trace, windows gave me a bsod and when I wanted a BSOD, it gave me a trace.

Somehow, I managed to perform a boot trace with drivers flag and without any bsod. I am attaching for your perusal. Two drivers seem to delay the boot- fltmgr.sys and bowser.sys whose details I could not find

By the way, the only thing I changed was upgrade the xbootmgr (I installed the windows 7.1 sdk(upgraded from ver 7.0)). So, see if it resolves the problem for you.

http://dl.dropbox.com/u/17753307/bootlog2.7z

P.S. I have observed that system activity is zero during the first 3-4 secs. No disk utilisation, no processor usage... What areyour comments on that??

[MagicAndre1981]

the trace is not complete. I can't see when it is finished.

Read my trace guide and you see that the first steps is to load all boot relevat drivers. in oyur case it takes to load the SPTD driver (Demon tools) and the IDE controller. that's why you see no activity.

You should really remove MSE and try a different tool. MSE is still slow.

[compsavvy]

http://dl.dropbox.com/u/17753307/bootlog3.7z

I uninstalled sptd.sys and updated my sata drivers and the boot process seems much more streamlined. Thanks for pointing it out.

Now, I guess I would leave windows to itself.

Did you have any success with the drivers flag??

[MagicAndre1981]

your Windows is much faster now. 23s to boot to the desktop and 32s to boot completely. This is fine.

Have you found the crash dump (in C:\Windows\Minidump)? Can you share them? The MSFT employee replied and I need the STOP Code.

[compsavvy]

Sorry, the minidump folder is empty. I could not reproduce the problem after the initial BSOD.

http://social.msdn.microsoft.com/Forums/en/wptk_v4/thread/9fafc08b-e914-4094-960b-722f97a7f59b

I think you might have seen this and this shows that you are right about the problem with the usb driver.

[MagicAndre1981]

yes, I know this topic. I replied to it, too.

The MSFT employee looks at it to see more.

[compsavvy]

BugCheck 1000007E, {ffffffffc0000005, fffff800031bde87, fffff880033bd128, fffff880033bc990}

Probably caused by : usbvideo.sys ( usbvideo+3783 )

Followup: MachineOwner

---------

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Some common problems are exception code 0x80000003. This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG. This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG. This will let us see why this breakpoint is

happening.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff800031bde87, The address that the exception occurred at

Arg3: fffff880033bd128, Exception Record Address

Arg4: fffff880033bc990, Context Record Address

Debugging Details:

------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:

nt!IopPerfCompleteRequest+47

fffff800`031bde87 488b5008 mov rdx,qword ptr [rax+8]

EXCEPTION_RECORD: fffff880033bd128 -- (.exr 0xfffff880033bd128)

ExceptionAddress: fffff800031bde87 (nt!IopPerfCompleteRequest+0x0000000000000047)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

CONTEXT: fffff880033bc990 -- (.cxr 0xfffff880033bc990)

rax=09010100e4e1c000 rbx=fffffa80198f0b70 rcx=0000000000000000

rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80198f0740

rip=fffff800031bde87 rsp=fffff880033bd360 rbp=fffffa80198cbc80

r8=fffffa8003bd9058 r9=fffffa8004c31000 r10=0000000000401802

r11=fffff880033bd400 r12=fffffa80198c7a00 r13=fffffa80198c8d60

r14=0000000000000476 r15=0000000000000000

iopl=0 nv up ei pl nz na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206

nt!IopPerfCompleteRequest+0x47:

fffff800`031bde87 488b5008 mov rdx,qword ptr [rax+8] ds:002b:09010100`e4e1c008=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f30e0

ffffffffffffffff

FOLLOWUP_IP:

usbvideo+3783

fffff880`00dd3783 ?? ???

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88000dd3783 to fffff800031bde87

STACK_TEXT:

fffff880`033bd360 fffff880`00dd3783 : fffffa80`198f0740 fffffa80`198cbc80 00000000`00000000 fffffa80`198ea3c0 : nt!IopPerfCompleteRequest+0x47

fffff880`033bd410 fffffa80`198f0740 : fffffa80`198cbc80 00000000`00000000 fffffa80`198ea3c0 00000000`00000001 : usbvideo+0x3783

fffff880`033bd418 fffffa80`198cbc80 : 00000000`00000000 fffffa80`198ea3c0 00000000`00000001 00000000`00000001 : 0xfffffa80`198f0740

fffff880`033bd420 00000000`00000000 : fffffa80`198ea3c0 00000000`00000001 00000000`00000001 fffffa80`198cbd01 : 0xfffffa80`198cbc80

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: usbvideo+3783

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbvideo

IMAGE_NAME: usbvideo.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b8f39d9

STACK_COMMAND: .cxr 0xfffff880033bc990 ; kb

FAILURE_BUCKET_ID: X64_0x7E_usbvideo+3783

BUCKET_ID: X64_0x7E_usbvideo+3783

I was able to replicate the problem. Most likely the issue is with webcam drivers