Sunday, December 15, 2013

Troubleshoot Windows Server 2003: Startup Issue

A successful Windows startup includes the following phases:
  • Initial phase
  • Boot loader phase
  • Kernel phase
  • Logon phase
If a problem occurs during any of these phases, Windows may not start correctly, and you may experience the following problems:
  • The computer stops responding (hangs).
  • You receive an error message.
If a startup problem occurs after you click Microsoft Windows Server 2003 on either the boot loader menu, or when you receive the "Please select the operating system to start" message, files that the operating system needs may be missing or damaged. Windows provides several options that you can use to troubleshoot this issue, including safe mode, the Recovery Console, and an Automated System Recovery. 

If the startup problem occurs immediately after you make a change to the computer (for example, after you install a new driver), try to start the computer by using the Last Known Good Configuration feature.

When you use the Last Known Good Configuration feature, you start your computer by using the most recent settings that worked. This feature restores registry information and driver settings that were in effect the last time that the computer started successfully. Use this feature when you cannot start Windows after you make a change to the computer (for example, after you install or upgrade a device driver).

To start the computer by using Last Known Good Configuration, follow these steps:
  1. Click Start, and then click Shut Down.
  2. Click Restart, and then click OK.
  3. When you see the message Please select the operating system to start, press the F8 key.
  4. Use the arrow keys to select Last Known Good Configuration, and then press Enter.
  5. 2683283
    Note NUM LOCK must be off before the arrow keys on the numeric keypad will function.
  6. If you are running other operating systems on the computer, click Microsoft Windows Server 2003 on the list, and then press Enter.
2683283
Notes
  • By selecting Last Known Good Configuration, you can recover from problems such as a newly added driver that may be incorrect for your hardware. This feature does not solve problems caused by corrupted or missing drivers or files.
  • When you select Last Known Good Configuration, only the information in the following registry key is restored:
    HKLM\System\CurrentControlSet
    Any changes that you have made in other registry keys remain.
If you can start your computer by using the Last Known Good Configuration feature, the last change that you made to the computer (for example, the installation of a driver) may be the cause of the incorrect startup behavior. We recommend that you either remove or update the driver or program, and then test Windows to see if it starts correctly. 
To troubleshoot startup problems in safe mode, follow these steps:
  1. Click Start, and then click Shut Down.
  2. Click Restart, and then click OK.
  3. When you see the message Please select the operating system to start, press F8.
  4. On the Windows Advanced Option Menu, use the arrow keys to select Safe Mode, and then press Enter.
  • If the computer does not start in safe mode, try starting the computer by using the Recovery Console. If you still cannot start the computer, look for possible hardware problems, such as defective devices, installation problems, cabling problems, or connector problems. Remove any hardware that was added recently, and then restart the computer to see if the problem is resolved.
  • If the computer starts in safe mode, go to the next section to continue to troubleshoot the startup issue. 
View the event logs in Event Viewer for information that can help you identify and diagnose the cause of the startup problem. To view events that are recorded in the event logs, follow these steps.
  1. Do one of the following:
    • Click Start, point to Administrative Tools, and then click Event Viewer.
    • Start the Event Viewer snap-in in Microsoft Management Console (MMC).
  2. In the console tree, expand Event Viewer, and then click the log that you want to view. For example, click System log or Application log.
  3. In the details pane, double-click the event that you want to view.

    To copy the details of the event, click Copy, open a new document in the program in which you want to paste the event (for example, Microsoft Word), and then click Paste on the Edit menu.
  4. To view the description of the previous event or the next event, press the UP ARROW key or the DOWN ARROW key
The System Information tool displays a comprehensive view of the computer's hardware, the system components, and the software environment. Use this tool to help identify possible problem devices and device conflicts. To do this, follow these steps.
  1. Click Start, and then click Run.
  2. In the Open box, type msinfo32, and then click OK.
  3. Look for problem devices or device conflicts. To do this, follow these steps:
    1. In the console tree, expand Components, and then click Problem Devices
      2683283
      .

      Note any devices that are listed in the right pane.
    2. In the console tree, expand Hardware Resources, and then click Conflicts/Sharing.

      Note any resource conflicts that are listed in the right pane.
    3. If you identify a problem device, perform the appropriate action (for example, remove, disable, or reconfigure the device, or update the driver), and then restart the computer in normal mode.

      You can use Device Manager to remove or disable devices and their drivers. For more information about Device Manager, see the Use Device Manager to Identify the Cause of the Startup Problem section.

      If the computer starts correctly, that particular device may be the cause of the startup problem. 

    Device Manager displays a graphical view of the hardware that is installed on your computer. Use this tool to resolve any possible device conflicts or to identify incompatible devices that may be the cause of the startup problem.

    To start Device Manager, follow these steps.
    1. Click Start, right-click My Computer, and then click Manage.
    2. Expand System Tools, and then click Device Manager.

      The devices that are installed on your computer are listed in the right pane. If a symbol is displayed next to a device, there may be a problem with the device. For example, a black exclamation point (!) on a yellow field indicates that the device is in a problem state.

      2683283
      Note To disable a device in Device Manager, right-click the device, and then click Disable.
    3. Investigate possible device conflicts. To do this, double-click the device in the right pane, and then click the Resources tab.

      If a device conflict exists, it is listed under Conflicting device list.

      Note the Use automatic settings check box. If Windows successfully detects a device, this check box is selected, and the device functions correctly. However, if the resource settings are based on Basic Configuration n (where n is any number from 0 to 9), you may have to change the configuration. To do this, either click a different basic configuration from the list or manually change the resource settings.
      2684263
      WARNING This procedure may require you to change the computer's complementary metal oxide semiconductor (CMOS) settings and the basic input/output system (BIOS) settings. Incorrect changes to the BIOS of the computer can result in serious problems. Change the computer's CMOS settings at your own risk.

      If Windows cannot resolve a resource conflict, verify that the computer is configured to allow Windows to enumerate the devices in the computer. To do this, enable the Plug and Play OS setting in the Setup tool of the computer's BIOS. To change the computer's BIOS settings, see the computer documentation or contact your computer manufacturer.
    4. If you identify a problem device, disable it, and then restart the computer in normal mode.

      If the computer starts correctly, the device that you disabled may be the cause of the startup problem.

      Make sure that the device is listed on the Windows Server 2003 Hardware Compatibility List (HCL) and that it is installed correctly. Also, contact the manufacturer to report the behavior and to obtain information about possible updates that can resolve the startup problem.




No comments:

Post a Comment