Sei sulla pagina 1di 6

Windows Server 2003 Boot Process: Common Errors & Solutions Page 1 of 10

Español  Deutsch  Careers Testimonials Get Custom Quote

Home About Us My Account Blog Conta

BLOG

July 16th, Windows Server 2003 Boot Process: Common


2008
Errors & Solutions
July 16th, 2008
Blo

Like One person likes this.

The boot process starts when you turn on your computer and ends when you
log on to Windows Server 2003. There can be various reasons for startup
failures. Some can be easily corrected, while others might require you to
Re
reinstall Windows Server 2003. July 1
Your
This article will help you understand and troubleshoot most of the errors
June
commonly occurring during the Windows Server 2003 boot process.
May
While diagnosing a server error, it is important to first determine at which INSTA
stage the error occurred. A server error can occur when the server is booting, Janua
during its running time or even when it is shutting down. Conf
Addr
The Boot Process
Janua
The boot process will slightly differ depending on whether your server is using Hype
an x86-based processor or an Itanium-based processor. This article exclusively Serve
deals with x86-based boot Process Dece
If you are running Windows Server 2003 on an x86-based platform, the boot Plugg

process consists of six major stages:


1. The pre-boot sequence

http://bobcares.com/blog/?p=28 3/16/2011
Windows Server 2003 Boot Process: Common Errors & Solutions Page 2 of 10

2. The boot sequence Septe


3. Kernel load sequence Moni
4. Kernel initialization sequence Reso
5. Logon sequence May
6. Plug and Play detection Micro
Many files are used during these stages of the boot process. The following June
sections describe the steps in each boot process stage, the files used, and the Serve

Re
errors that might occur.

Stage 1: Pre-Boot Sequence


Bobc
A normal boot process begins with the pre-boot sequence, in which your Open
computer starts up and prepares to boot the operating system. cPan
The computer will search for a boot device based on the boot order that was The q
configured in the computer’s BIOS settings. and K
Thre
Steps in the Pre-Boot Sequence
GeoI
The preboot sequence is not truly a part of windows booting process.
The pre-boot sequence consists of the following steps:
Arc
1. When the computer is powered on, it runs a power-on self-test (POST) Selec
routine. The POST detects the processor you are using, how much memory is
present, the hardware is recognized and what BIOS (Basic Input/Output
System) your computer is using.
Ca
2. The BIOS points to the boot device and the Master Boot Record (MBR) is Aster
loaded. It is also sometimes called the master boot sector or even just the
Back
boot sector.The MBR is located on the first sector of the hard disk. It contains
the partition table and master boot code, which is executable code used to BobB
locate the active partition. Sank
3. The MBR points to the Active partition. The active partition is used to Brand
specify the partition that should be used to boot the operating system. This is Clou
normally the C: drive. Once the MBR locates the active partition, the boot
cPan
sector is loaded into memory and executed.
Data
4. The Ntldr file is copied into memory and executed. The boot sector points to
the Ntldr file, and this file executes. The Ntldr file is used to initialize and Data
start the Windows Server 2003 boot process. Deve
Possible Errors & Solutions DNS
FTP
If you see errors during the pre-boot sequence, they are probably not related
Java
to Windows Server 2003, since the operating system has not yet been loaded. Linux
The following table lists some common causes for errors and solutions . kerne
Symptom Mage
Cause Solution
Mail
Corrupt There are many viruses that affect You can protect your
Migr
MBR MBR and corrupt it. system from this type of
error by using a virus- Moni
scanning software. Most of News
the commonly used virus- Artic
scanning programs can
Bobc
correct an infected MBR.
Brand
Cust

http://bobcares.com/blog/?p=28 3/16/2011
Windows Server 2003 Boot Process: Common Errors & Solutions Page 3 of 10

Improperly If the POST cannot recognize your Recheck your device Edito
configured hard drive, the pre-boot stage will configuration, driver Even
hardware fail. This error can occur even if the settings. Also check for any Expe
device was working properly and hardware malfunction and
Fun Z
you haven’t changed your failure.
configuration. Host
Insta
No partition This can happen if you used the If the partition is FAT16 or
is marked as Fdisk utility and did not create a FAT32 and on a basic disk, Press
active partition from all of the free space. you can boot the computer Qual
If you created your partitions as a to DOS or Windows 9x with Secu
part of the Windows Server 2003 a boot disk. Then run Fdisk
SEO W
installation and have dynamic and mark a partition as
disks, marking an active partition is active. Serve
done for you during installation. Spec
Corrupt or There are chances that, Ntldr file You can restore this file Word
missing may be corrupted or deleted by through Automated System Othe
Ntldr file virus attack. . Recovery or a Windows PHP
Server 2003 boot disk.
Plesk
Back to the Top Rout
Secu
Stage 2: Boot Sequence
Serve
When the pre-boot sequence is completed, the boot sequence begins. Ntldr Virtu
switches the CPU to protected mode, which is used by Windows Server 2003 Web
and starts the appropriate file systems. Web
Adve
The contents of the Boot.ini file are read and the information is used to build
Web
the initial boot menu selections. When Windows Server 2003 is selected,
Web
Ntdetect.com gathers the system’s basic hardware configuration data and
Webh
passes the collected information back to Ntldr. The system also checks to see if
Webs
more than one hardware profile is detected; if so, the hardware profile Wind
selection menu will be displayed as a part of the startup process.

Possible Errors & Solutions Tags


The following table lists some common causes for errors during the boot stage.
Apach
Symptom Cause Solution Brand
Datab
Missing or corrupt If Ntldr, Boot.ini, You can restore these files
boot files Bootsect.dos, Ntdetect.com, through Automated System Hosti
or Ntoskrnl.exe is corrupt or Recovery. Kerne
missing (by a virus or New
malicious intent), the boot Qualit
sequence will fail. You will see Search
an error message that SEO S
indicates which file is missing
softwa
or corrupt.
Virtua
Improperly It can occur when you Recheck your configuration. Web 
configured manually edit Boot.ini or if Websi
Boot.ini file you have made any changes
to your disk configuration.
Unrecognizable or If the error that appears is Best method to trouble
improperly due to Ntdetect.com, the shoot it is to remove all the RSS

http://bobcares.com/blog/?p=28 3/16/2011
Windows Server 2003 Boot Process: Common Errors & Solutions Page 4 of 10

configured issue is surely due to hardware that is not


hardware hardware problems. required to boot the
computer. Add each piece
one by one and boot your
computer. This will help you
to identify the culprit.
 
Important Files

Along with the Ntldr file, which was described in the previous section, the Facilit
following files are used during the boot sequence:

Boot.ini

This is used to build the operating system menu choices that are displayed
during the boot process. It is also used to specify the location of the boot
partition. This file is located in the root of the system partition. It has the file
attributes of System and Hidden.

Bootsect.dos

An optional file that is loaded if you choose to load an operating system other
than Windows Server 2003, Windows 2000, or Windows NT. It is used only in
dual- boot or multi-boot computers. This file is located in the root of the system
partition. It has the file attributes of System and Hidden.

Ntdetect.com

Used to detect any hardware that is installed and add that information about
the hardware to the Registry. This file is located in the root of the system
partition. It has the file attributes of System, Hidden, and Read-only.

Ntoskrnl.exe

Used to load the Windows Server 2003 operating system. This file is located in
WindirSystem32 and has no file attributes.

Steps in the Boot Sequence

The boot sequence consists of the following steps:


1. Ntldr switches the processor from real mode to protected mode. Then it
starts file system drivers which supports your computer’s file system.
2. Ntldr is responsible for reading Boot.ini file. It displays a “boot menu
which lets users to choose the operating system to load.If we choose an
operating system other than Windows server 2003 say Windows 2000, or
Windows NT, the Bootsect.dos file is used to load the alternate operating
system, and the Windows Server 2003 boot process terminates.
3. Ntdetect.com file performs a hardware scan/detection and any hardware
that is detected is added to registry in the HKEY_LOCAL_MACHINE key.
The hardware that Ntdetect.com will recognize includes communication and
parallel ports, the keyboard, the floppy disk drive, the mouse, the SCSI
adapter, and the video adapter.
4. Control is passed to Ntoskrnl.exe to start the kernel load process.

Back to the Top

http://bobcares.com/blog/?p=28 3/16/2011
Windows Server 2003 Boot Process: Common Errors & Solutions Page 5 of 10

Stage 3: Kernel Load Sequence


All of the information that is collected by Ntdetect.com is passed to
Ntoskrnl.exe.
The kernel load sequence consists of the following steps:
1. The Ntoskrnl.exe file is loaded and initialized.
◦ Initializes executive subsystems and boot system-start device drivers.

NOTE: By executive subsystems, I meant Process and Thread Manager, The


Virtual Memory Manager, The Input/Output Manager, The Object Manager,
Runtime Libraries which all runs in kernel mode.

◦ Prepares the system for running native applications.

NOTE: If you are not familiar with native applications, then it needs
explanation. Windows provide two type of API. Well known Windows API (All
Windows programs must interact with the Windows API regardless of the
language.) and Native API. Native API is used by some windows components
like kernel level drivers and system process aka csrss.exe

◦ runs Smss.exe.

The function of Ntoskrnl.exe:


2. The Hardware Abstraction Layer (or HAL) is loaded. The HAL is a kernel
mode library (HAL.DLL) that provides a low-level interface with the hardware.
Windows components and third-party device drivers communicate with the
hardware through the HAL.
3. The control for the operating system is loaded. The control set is used to
control system configuration information such as a list of device drivers that
should be loaded.
4. Low-level device drivers, such as disk drivers are loaded.
Possible Errors & Solutions:

If you have problems loading the Windows Server 2003 kernel, you will most
likely need to reinstall the operating system.
Back to the Top

Stage 4: Kernel Initialization Sequence


In the kernel initialization sequence, the HKEY_LOCAL_MACHINEHARDWARE
Registry is created, device drivers are initialized, and high-order subsystems
and services are loaded.
The kernel initialization sequence consists of the following steps:
1. Once the kernel has been successfully loaded, the Registry key
HKEY_LOCAL_MACHINE HARDWARE is created. This Registry key is used to
specify the hardware configuration of hardware components when the
computer is started.
2. The device drivers that were loaded during the kernel load phase are
initialized.

http://bobcares.com/blog/?p=28 3/16/2011
Windows Server 2003 Boot Process: Common Errors & Solutions Page 6 of 10

3. Higher-order subsystems and services are loaded.


Note: Higher order subsystem include, POSIX Subsystem, OS/2 subsystem.

Possible Errors & Solutions:

If you have problems during the kernel initialization sequence, you may trying
booting to the Last Known Good configuration.
Back to the Top

Stage 5: Logon Sequence


Session Manager Subsystem or smss.exe plays a vital role in logon sequence.
Its main function include.
1. It creates environment variables in the operating system.
2. It Starts the kernel and user modes of the Win32 subsystem (win32k.sys
and csrss.exe). It then starts other subsystems that are listed in
HKLMSystemCurrentControlSetControlSession ManagerSubSystems Registry
key.
3. smss.exe starts winlogon.exe, the Windows logon manager.
winlogon.exe is a system service that enables logging on and off of users. It is
also responsible for loading user profile.
It invokes GINA( Graphical Identification and Authentication) which displays
login prompt. The GINA accepts the user login credentials and passes it back to
Winlogon.
Winlogon then Starts Lsass.exe (the Local Security Authority) and passes login
credentials to LSA. LSA determine which user account databases is to be used
for authentication eg: Local SAM or Active Directory in case you are in a
windows domain.
4. smss.exe finally starts the Services subsystem (Services.exe), also known as
the Service Control Manager (SCM). It executes and performs a final scan of
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices to see if there are
any remaining services that need to be loaded.

Possible Errors & Solutions


1. If logon errors occurs, they are usually due to an incorrect username or
password or to the unavailability of a DNS server or a domain controller to
authenticate the request (if the computer is a part of a domain).
2. Errors can also occur if a service cannot be loaded. If a service fails to load,
you will see a message in the System Log of Event Viewer.

Back to the Top

Stage 6: Plug and Play Device Detection Phase


If Windows Server 2003 has detected any new devices during the startup
process, they will automatically be assigned system resources.

http://bobcares.com/blog/?p=28 3/16/2011

Potrebbero piacerti anche