0

Long Pause During Windows Startup Process

Symptoms
After you choose to start Windows from the Boot menu, you may experience a long delay (or pause) before your computer finishes starting. Note that this delay may range from 10 seconds to a minute. Also, this delay occurs before the Starting Windows progress bar appears, and your computer may appear to stop responding (hang) during this time.

Cause
This behavior can occur if Windows is installed on a drive or a partition to which Windows cannot gain access with normal Basic Input/Output System (BIOS) INT-13 or INT-13 extension calls. When Windows Setup determines it cannot use BIOS calls to start, it uses scsi() or signature() syntax in the Boot.ini file instead of multi() syntax.

When booting a system that requires scsi() or signature() syntax, Ntldr loads an additional device driver (Ntbootdd.sys) to initialize and interrogate the boot controllers in your computer. Ntldr then seeks the associated boot drive attached to the controller to finish loading the kernel. These additional operations take more time in Windows because of the Plug and Play nature of the operating system.

This behavior is expected, however, Windows Setup may use scsi() or signature() syntax, even if your computer can boot using the normal BIOS calls. This may occur on Integrated Drive Electronics-based computers when using a large capacity boot drive. In this case, you can try adding an additional entry in the Boot.ini file and use multi() syntax on the new entry to boot from. Note that if this works, your computer starts without pausing.

4
Contributors
4
Replies
7
Views
13 Years
Discussion Span
Last Post by packrtz
0

This is yet another "fix" on another forum that someone only took the time time do a cut and paste from the microsft website. THIS IS NO HELP AT ALL!!!! and by the way isn't this plagiarism?


Long Pause During Windows Startup Process

Symptoms
After you choose to start Windows from the Boot menu, you may experience a long delay (or pause) before your computer finishes starting. Note that this delay may range from 10 seconds to a minute. Also, this delay occurs before the Starting Windows progress bar appears, and your computer may appear to stop responding (hang) during this time.

Cause
This behavior can occur if Windows is installed on a drive or a partition to which Windows cannot gain access with normal Basic Input/Output System (BIOS) INT-13 or INT-13 extension calls. When Windows Setup determines it cannot use BIOS calls to start, it uses scsi() or signature() syntax in the Boot.ini file instead of multi() syntax.

When booting a system that requires scsi() or signature() syntax, Ntldr loads an additional device driver (Ntbootdd.sys) to initialize and interrogate the boot controllers in your computer. Ntldr then seeks the associated boot drive attached to the controller to finish loading the kernel. These additional operations take more time in Windows because of the Plug and Play nature of the operating system.

This behavior is expected, however, Windows Setup may use scsi() or signature() syntax, even if your computer can boot using the normal BIOS calls. This may occur on Integrated Drive Electronics-based computers when using a large capacity boot drive. In this case, you can try adding an additional entry in the Boot.ini file and use multi() syntax on the new entry to boot from. Note that if this works, your computer starts without pausing.

0

yes it is plagiarism, yes it is no help, no the auther who posted it here probably doesn't understand it.

This isn't a tweak nor a fix..wrong forum

0

Wow. I apologize for this. This was sent in to me by a member as a tweak - I guess I didn't really read it but just took their word for it. I had no idea it was straight off of the Microsoft website. Moving it to the Windows tech support forum. And yes, now that I read it, I do understand it ;)

0

I spent a great deal of time looking for a software problem that was causing me to have 2 MINUTE delay on boot. I got a tip from someone (unfortunately I lost my system for some other reason before I had time to thank the tipster) who suggested I RESEAT my MEMORY chips! I did this and, magically, the two minute delay was completly GONE> I can only hypothesize that some piece of software was "searching for something" and took two minutes of time - EVERY BOOT! The tip? Try reseating your memory chips!!.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.