Rebooting Rather Than Shutting Down
By far the most common shut down problem is that the system will reboot rather than shutting down. In most cases, the reboot is triggered because Windows XP is designed to reboot after a critical failure. To put it simply, if something were to go wrong during the shut down sequence, Windows may interpret the problem as a crash, and reboot the system as a result.
If you just want to band-aid the problem, you can disable the restart on system failure setting. To do so, right click on My Computer and select the Properties command from the resulting shortcut menu. When you do, you will see the System Properties sheet. Click the Advanced tab and click the Settings button found in the Startup and Recovery section. Finally, deselect the Automatically Restart check box, shown in Figure A, and click OK.
Figure A: The Automatically Restart check box allows Windows to automatically reboot after a failure
The technique that I have just shown you will prevent the system from rebooting itself, but it still doesn’t get rid of the root cause of the problem. There are several known causes of Windows shutdown problems.
Roxio Easy CD Creator
One of the most common causes of Windows shut down problems is a bug in Roxio’s Easy CD Creator (particularly version 5). Roxio does have a patch available at http://www.roxio.com/en/support/ecdc/software_updatesv5_2.jhtml Keep in mind though that the patch has been known to disable Roxio’s Take Two backup software that came with Easy CD Creator 5 Platinum. You should also keep in mind that version 5 is an old version that Roxio no longer supports. The current version is Easy Media Creator 7. If you suspect that Easy CD Creator may be causing your problem, then I recommend upgrading to a newer version rather than patching an old version.
Wake On
Another common cause of system restarts is the Wake On setting. The Wake On setting allows a computer to be automatically booted if it receives LAN packets intended for it, or if the modem line rings. Typically, the Wake on LAN settings would be adjusted through your computer’s BIOS setting. If you have checked the BIOS though and the Wake On LAN setting is disabled, it is possible that Windows might be responsible for waking the system up. To find out, open the Device Manager and locate your system’s network card. Right click on the card and select the Properties command from the resulting shortcut menu. When you do, you will see the network card’s properties sheet. Now, select the Power Management tab and verify that the Allow This Device To Bring The Computer Out Of Standby option is deselected, as shown in Figure B.
Figure B: Certain types of network traffic can wake a computer up
Hardware Issues
Another common cause of reboots during shutdown are minor hardware incompatibilities. Microsoft maintains a hardware compatibility list for Windows XP. Only hardware appearing on the list is guaranteed to be 100% compatible with Windows XP. Even so, most people don’t pay any attention to the hardware compatibility list. Most of the time, minor hardware issues go unnoticed, but they can manifest themselves in the form of reboots during shutdown.
Unfortunately, I can’t possibly tell you every piece of hardware out there that’s known to cauyse reboot problems. What I can tell you though is that pariphrial devices are especially notorious for causing the problems. This is especially true of high end keyboards and mice with lots of extra features, and of various USB devices. I have even heard of cases in which USB devices would cause the reboot problem if they were plugged directly into the system’s USB port, but the problem would go away if the devices were plugged into a USB hub instead.
Unfortunately there is no quick fix to minor hardware compatibility issues. If you think that your system’s hardware may be to blame then you will have to use trial and error to locate the offending device (or devices).
I recommend starting by unplugging any external devices. If you have a high end keyboard or mouse, then temporarily replace your keyboard and mouse with a generic set. Now boot the computer up and try to shut it down. If the system shuts down properly, then one of the devices that you disconnected was causing the problem. If the system does not shut down properly, then I recommend leaving those devices disconnected during the rest of the testing for the purpose of simplifying the system’s configuration.
The next thing that I recommend doing is to open the device manager and make note of the make and model of your system’s major hardware components. Specifically, you should pay attention to things like network cards, video cards, sound cards, and modems. After you have documented the make and model of each device, then turn off and unplug your computer. At this point, you should remove the computer’s case and verify that the hardware listed in the device manager is what’s actually in your system. Windows XP is notorious for misidentifying hardware devices. For example, I recently helped a friend install Windows onto a new computer. Windows identified his system as having a D-Link network card. When I couldn’t get the card to function, I removed the case and realized that his system actually had a Net Gear card instead.
After you have verified that the hardware listed in the device manager is what’s actually in your system, then I recommend putting your computer back together and going online. I recommend visiting each hardware manufacturer’s Web site and downloading the latest driver for the corresponding hardware device. Hardware manufacturers frequently revise drivers when bugs are discovered. While you are at it, try visiting the Web site for your system’s motherboard manufacturer. It could be that an updated BIOS is available.
Extremely Slow Shutdown
Probably the second most common shut down problem for Windows XP is that the shut down takes an excessive amount of time to complete. To understand why this happens, you must remember that the Windows operating system is not a single program, but rather a collection of individual services. Each of these services must be stopped during shut down. Therefore, a glitch related to any one of the services may prolong the shut down process or cause the shut down process to fail completely.
Many people have claimed that the Nvidia Driver Helper Service (used with Nvidia video cards) causes extremely slow shut downs. However, this is one of those cases in which an updated video driver usually solves the problem. Other people have mentioned that disabling the terminal services greatly expedites the shut down process. The Terminal Services are used for remote assistance, remote desktop, and fast user switching. If you do not use any of these features, then the Terminal Services can be safely disabled. You can access the services console by entering the SERVICES.MSC command at the Run prompt.
Another potential cause of slow system shut downs is that Windows contains an option to erase the system’s virtual memory and system hibernation cache at shut down. These security features are disabled by default because they take a long time to complete, and cause the system shutdown to look like it has frozen. Although these features are disabled by default, some privacy software will enable it.
To determine whether or not these features are enabled on your PC, enter the GPEDIT.MSC command at the Run prompt to load the Group Policy Editor. Now, navigate through the console tree to Computer Configuration Windows Settings Security Settings Local Policies Security Options. At this point, locate the Shutdown: Clear Virtual Memory Pagefile option in the column to the right and verify that it is disabled, as shown in Figure C. If this option is enabled, you can disable it by double clicking on the setting and choosing the Disabled option.
Figure C: Clearing the virtual memory file during shut down takes a lot of time.
Conclusion
In this article, I have explained that the two most common types of shut down problems are shut down reboots and shutdowns that take a long time to complete. I then went on to demonstrate various troubleshooting methods.
Troubleshooting Windows XP Shutdown Issues
08/01/2002 It's been a number of months now since Windows XP made its debut. Shutdown problems continue to be one of the primary issues haunting users. A number of solutions have been found for different scenarios, but one thing that is generally agreed on is the primary cause for most shutdown ills still relate to hardware and software compatibility and driver issues. If everyone was running the latest and greatest in hardware and software there would likely be very little discussion about shutdown problems. That isn't the case now and likely won't be in the near future, so I think it's time to update and see what has been learned about shutdown issues.
The Role of the F5 Key and Shutdown Problems
When I first put this page together I meant to include this information. Unfortunately it totally slipped my mind. One of the hazards of being an Elder(ly) Geek, but better late than never. Thanks to reader Glen M. for jogging my memory.
When XP is first installed it tries to determine what type of BIOS is available on the computer. Newer systems have what is known as Advanced Configuration and Power Interface (ACPI) capability. Unfortunately, XP doesn't always recognize a computer BIOS is ACPI capable and doesn't install the support for ACPI. Even more unfortunate is the fact that if ACPI support isn't determined at the initial install it's virtually impossible to correct this at a later time short of reinstalling XP over the top of the previous XP installation. To do so requires changing the Hardware Abstraction Layer (HAL). The chances of successfully changing a HAL after XP has been installed is pretty close to zilch.
Quite a few readers have written to say my "pretty close to zilch" comment above is incorrect; that the HAL can be successfully changed and manipulated. Perhaps this is true, if you're a gambler. I'm not. Here are three links that may help you make an informed decision.
HAL Options After Windows XP or Windows Server 2003 Setup
How to Force a Hardware Abstraction Layer During an Upgrade or New Installation of Windows XP
and one more with some salient points even if running XP
How to Troubleshoot Windows 2000 Hardware Abstraction Layer Issues
Once you drop the CD in the tray and fire up the computer to install XP, the first thing you'll see at the bottom of the screen is the option to press F6 if you need to install a SCSI or RAID controller. Don't press F6. Press F5 instead. This will take you to a separate menu of Hardware Abstraction Layer's where you can choose an appropriate HAL that supports ACPI. The choices will be:
ACPI Multiprocessor PC
ACPI Uniprocessor PC
Advanced Configuration and Power Interface (ACPI) PC
Compaq SystemPro Multiprocessor or 100% Compatible PC
MPS Uniprocessor PC
MPS Multiprocessor PC
Standard PC
Standard PC with C-Step i486
Other
Many users have written to say the only visible options they have are the last two listed above. This is an interface glitch that defaults the list to the bottom. Just use the up and down arrows to scroll through all the options.
In the majority of installations the 'Advanced Configuration and Power Interface (ACPI) PC' HAL is the one you will want to use. A few cautions are also in order:
Obtain and install the latest BIOS for your motherboard before you begin the XP installation.
Equally as important as using the proper HAL on ACPI capable systems, is NOT using it on systems that are not ACPI compatible. The install may complete but the system will almost surely fail to start when it reboots.
There are situations where it is definitely not desirable to use an ACPI HAL even if it is supported by the BIOS. This predominately applies to servers, but to ensure that an ACPI HAL will not be used or automatically detected and used, press F7 instead of F5 as discussed previously.
Considering the number of problems that users have with systems not shutting down completely I wonder why this feature is not prominently mentioned and documented. It could save many headaches, but now you know. A good piece of knowledge to have tucked away for your next XP install.
As a final note, to determine if your computer was detected as being ACPI enabled:
Right click My Computer then click Properties > Hardware > Device Manager.Expand the entry called Computer.
If the entry is 'Advanced Configuration and Power Interface (ACPI) PC' you're all set. If it says 'Standard PC' the computer BIOS was not detected as being ACPI capable.
"It's Now Safe To Turn Off Your Computer"
If the message above is the shutdown issue, stop right here. You really don't have a problem with shutdown. While it may not seem like it, shutdown has completed properly. The problem you have is with powering down or powering off the computer. Semantics, you say? Maybe, but almost without fail this can be solved as follows. If you haven't checked for an updated BIOS, that's the first step, then check the items listed below.
Click [Start] [Control Panel] [Performance and Maintenance] [Power Options]The Power Options Properties Property Sheet will open.Click the APM tab and check the box to [Enable Advanced Power Management Support]
Power Down Automatically After Shutdown I
Select the APM tab and check/uncheck [Enable Advanced Power Management Support].
It should be noted that some users have solved the shutdown problems via enabling while others have achieved success via disabling. Experimentation with the APM and ACPI settings may provide a solution.
Power Down Automatically After Shutdown II
CAUTION
03/27/2003 - In the last two days I've received e-mail from two different readers stating that when this method has been used they have been unable to boot their system; not even in safe mode. The system starts to boot, displaying the first lines and then shuts down. I'm trying to pinpoint what is causing this behavior, but to this point it remains a mystery. In all fairness, these two reports have been the only problems I've heard about with this procedure in the twelve months it has been posted.
Until this issue is resolved, use at your own risk.
If the procedure above didn't solve the problem, check the registry setting shown below.
Start Regedit and navigate toHKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WinlogonSet the value of PowerDownAfterShutdown to 1.
If the value isn't present, add it by creating the string value PowerDownAfterShutdown and setting the value to 1.
Note: The success of this registry edit is dependent on Hardware Abstraction Layer (HAL) support.
Two Valuable Items for Dealing with Shutdown Issues
Device Manager: Often times Device Manager will provide a clue to an item that may be interfering with a proper shutdown sequence. To open Device Manager:
Right click [My Computer] click [Properties] and select [Hardware] tab.Click the [Device Manager] button in the [Device Manager] section.
Device Manager use a number of different symbols to indicate potential problems with installed devices. As you might expect, Device Manager is closely tied into the drivers that are used to make individual devices functional. A problem with one of these devices or a driver supporting it are often the cause of shutdown problems. Don't assume that just because you checked Device Manager once and all was well that matters will remain that way. Check it from time to time, especially if you notice a sudden change in device behavior. The Knowledge Base articles below will help you use Device Manager effectively.
How To: Manage Devices in Windows XPTroubleshooting Device Conflicts with Device ManagerExplanation of Error Codes Generated by Device ManagerHow to Troubleshoot Unknown Devices Listed in Device Manager
Startup and Recovery Options: By default, XP is configured that when a system failure is encountered the system automatically restarts. This behavior may at times be desirable, especially if a system is unattended and and a reboot is necessary to restore a system to operation. Unfortunately, it also makes it very difficult if not impossible for a user to read the messages that are presented that may provide clues to a shutdown problem. To prevent the system from automatically restarting:
Right click [My Computer] click [Properties] and select [Advanced] tab.Click the [Settings] button in the [Startup and Recovery] section.Remove the checkmark from [Automatically Restart] in [System Failure] section.
Pay particular attention to these messages as they may provide valuable clues to shutdown issues.
Issues relating to shutdown seem to fall into certain broad categories. It would be impossible to list every piece of hardware and software which have been identified as causing a problem, but a search through some of the major search engines, newsgroups, forums, and manufacturer sites will often provide a specific solution. Read through the items mentioned below and see if any of the situations apply to your system or configurations symptoms.
Restart Instead of Shutdown and STOP Error Messages
I touched on this briefly in the Startup and Recovery Options section above. As Microsoft mentions in the article referenced below, "When you shut down your Windows XP-based computer, your computer may restart instead of shutting down, and you may see a blue screen for just a moment before the computer restarts."
Windows XP Restarts When You Try to Shut Down Your Computer
Their reference to the Blue Screen Of Death (BSOD) and the STOP error messages that are displayed is why I suggested you disable the automatic restarts. As cryptic as these messages can be, they do provide a place to begin looking for issues impacting shutdown. To make it a bit easier, I've listed the STOP messages in the table below. A detailed description of each error message is here.
Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
Stop 0x00000024 or NTFS_FILE_SYSTEM
Stop 0x0000002E or DATA_BUS_ERROR
Stop 0x0000003F or NO_MORE_SYSTEM_PTES
Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
Stop 0x00000079 or MISMATCHED_HAL
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP
Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE
Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY
Stop 0xC2 or BAD_POOL_CALLER
Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
Stop 0x000000D8 or DRIVER_USED_EXCESSIVE_PTES
Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER
Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME
Stop 0x000000F2 or HARDWARE_INTERRUPT_STORM
Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATED
Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
The majority of Win XP shutdown problems reported thus far have been that it reboots when shutdown is attempted. This may be a global symptom emerging from several distinct causes, because, by default, XP executes an automatic restart in the event of a system failure. Therefore, more or less anything compromising the operating system during the shutdown process could force this reboot. Disabling the restart on system failure feature may permit the exact cause to be isolated: Right-click on My Computer, click Properties, click the Advanced tab. Under Startup & Recovery, click Settings. Under System Failure, uncheck the box in front of System reboot.
Shutdown Does Not Complete or Hangs
Everyone that has used Windows XP has spent some time looking at the screen that says "Saving Your Settings" - waiting for it to finally decide that it's saved everything it can and move on to shutting down the system. I'm not sure if it's by design or considered a 'feature' of XP, but the closer it is to quitting time the longer it takes this transition to occur. As an added benefit, when XP does 'hang' at this point in shutdown there is no response to the Ctrl+Alt+Del sequence so the user is effectively stuck.
My guess is that a Microsoft employee eager to get out on a Friday afternoon finally decided to address this issue, but that's just speculation. Whatever the reason, this is a known issue with XP Home and Professional and has been addressed by Microsoft.
Windows XP Stops Responding (Hangs) During Windows Shutdown Q307274
How long does it take for shutdown to begin, or at least give some visible sign the system is shutting down? This varies, and often times seem to be in direct relation to software that is left running when shutdown is attempted.
The safest thing you can do is to make sure all programs have been closed before shutting down. This alone may solve your problem. Don’t overlook programs running in the system tray. It’s easy to forget these are running as we become so accustomed to seeing their icons on a daily basis. As a general rule, if you don’t see some visible shutdown activity within 1-2 minutes of initiation, something is holding up the process. One readily identifiable sign that some application or process is not terminating properly is the appearance of the "Wait, End Task, or Cancel" dialog box. The program or process listed needs to be examined as to why it isn't terminating properly. Often times a visit to a company website will provide an update to address the issue.
Windows XP uses many processes that are built into the operating system that interact with outside vendor supplied programs. These interactions don't always flow as smoothly or quickly as planned and can account for shutdown delays. Extending the amount of time a process is allowed to close before invoking the "Wait, End Task, or Cancel" dialog box can sometimes be of benefit. To get a better understanding of what this involves as well as why not to overdo the time extension, the following article may be of value.
Increase Shutdown Time So That Processes Can Quit Properly in Windows XP: Q305788
These additional articles may lead to a solution:
Computer Hangs During Shutdown or Displays a "Cannot Find Enough Free Resources" Error Message
Your Computer May Stop Responding When You Shut Down and Use Only the 802.1x Protocol for User Authentication
Hardware and Software Issues
Truthfully, it's very difficult to separate shutdown issues into tidy compartmentalized groups, even categories that are as broad as I've defined for this article. Some of the issues from the Hangs section above fit into this group just as easily. However, there is no doubt that Hardware and Software Issues can be a major factor.
When talking about hardware, think for just a minute about all the bits and pieces that go into making up your system. At the heart of the system is the motherboard. The BIOS (Basic Input/Output System) might need to be updated to function properly with XP. A check with the computer or motherboard manufacturer for an updated BIOS is well worth the time. I will add though that my viewpoint toward BIOS updates is "If it ain't broke, don't update it." That doesn't hold true however for BIOS settings. Making sure the settings are optimized and appropriate for installed devices can eliminate problems. Just be sure to note the old settings before making changes.
Video cards are another source of problems. When XP was first released it shipped with more device drivers than any previous Windows version. In spite of that, the offerings barely scratched the surface for supporting devices already in use by end users. Device drivers fall into two categories; signed and unsigned. With signed drivers, you stand a much better chance of eliminating shutdown problems. Unsigned drivers are far more likely to create problems, and if a device doesn't have a signed driver available this long after XP's release it's likely it's not going to have one issued by the device manufacturer. Mixing signed and unsigned drivers is just asking for trouble. Go for all or nothing and if that isn't possible, consider replacing the device.
This seems like a good place to talk about compatibility. Microsoft has made available two sites where you can check hardware and software compatibility. The hardware list is a good place to check existing hardware or future hardware purchases for compatibility. The Windows Catalog requires you to wade through some hype, but there is some useful info available regarding different software packages.
Microsoft Windows Hardware Compatibility ListWindows Catalog
Sound cards are notorious for causing shutdown problems. Because these devices load so many drivers and stick them in a myriad of locations, trouble shooting them can be a nightmare. Using the uninstall routines and then checking to see if the shutdown problem disappears is the easiest method. Many of the motherboards now come with onboard sound and these seem to be relatively trouble free, but legacy soundcards continue to be a nightmare.
Anytime you are dealing with new hardware or software, using System Restore can provide you with a way to turn the system back to a previous condition where the problem didn't exist. More information on System Restore is available here.
In short, any piece of hardware or software can be the cause of a shutdown problem. In dealing with these issues over the past few months, experience has taught me to check the drivers first. If XP didn't come with a generic driver, perhaps the manufacturer has released a driver specifically for XP. As much trouble as it is, stripping the machine of all devices and reinstalling them one by one while checking for shutdown problems remains the best troubleshooting method.
Miscellaneous Problems/Solutions
The items listed below are miscellaneous reports of issues that have caused shutdown problems. Perhaps one of them will be of value in troubleshooting your shutdown issue. Feel free to send along your experiences and I'll post them here.
Windows XP Professional contains the Group Policy Editor which can be used to alter settings. One security option allows the page file to be cleared at system shutdown. When enabled, this same setting forces wiping of the hibernation file. Both of these processes can be lengthy, fooling the user into thinking shutdown has hung. To verify if this setting has been enabled (it has to be set manually), perform the steps listed.
[Start] [Run] and type [gpedit.msc] then click [OK]Drill down to [Computer Configuration] [Windows Settings] [Security Settings] [Local Policies] [Security Options]Verify the proper setting in the right pane under [Shutdown: Clear Virtual Memory Pagefile]
One theory has linked the shutdown problems to the logon process. Some users have reported they solved the hanging problem at shutdown by eliminating the Welcome Screen that XP uses for logon. To eliminate the screen and revert to the legacy method of logon:
[Control Panel] [User Accounts] [Change The Way Users Log On or Off]Remove the checkmark by [Use the Welcome Screen]
All users will be required to type a username and password.
This was a problem I personally encountered using a Microsoft USB Office Keyboard. Once the box had booted and the logon screen loaded I could use the keyboard, but prior to that it was totally unavailable. It was impossible to make selections between operating systems in the boot menu, so if I wanted to load Windows 2000, I had to make the changes to the boot.ini file within XP and then shut down the entire system. Restart wasn’t possible either because the system would hang and never complete the restart. The solution was to get a USB adapter which allowed me to plug the keyboard into the standard mouse port (PS/2) rather than a USB connector. I know it’s not the right solution, but for now it works.
If you have a graphics card manufactured by Nvidia, stopping the Driver Helper service may solve the shutdown slowness. As more users have upgraded to XP a lot more reports of video problems have surfaced, not just related to Nvidia. Updated drivers are again the answer, or if they are unavailable a new video card designed for XP seems to be the answer.
To access the services running on your machine, type [services.msc] from the [Run] box.
HAL options after Windows XP or Windows Server 2003 Setup
View products that this article applies to.
This article was previously published under Q309283
On This Page
SUMMARY
MORE INFORMATION
About UpdateUPHal
Scenario 1
Scenario 2
About UpdateHal
Scenario 1
Scenario 2
Expand all Collapse all
SUMMARY
This article describes hardware abstraction layer (HAL) options that are listed...
This article describes hardware abstraction layer (HAL) options that are listed in Device Manager after you run Windows XP Setup or Windows Server 2003 Setup. The article also discusses supportability issues that involve HALs in Sysprep images.
Back to the top
MORE INFORMATION
Windows XP Device Manager and Windows Server 2003 Device Manager list limited ch...Windows XP Device Manager and Windows Server 2003 Device Manager list limited choices for changing your HAL type when you click Update Driver. Microsoft Windows 2000 Device Manager lets you select any HAL type. If you select an incorrect HAL, you may not be able to start Windows 2000, or you may have other issues. Although the selections are now limited, you should change the HAL only if you are sure that the selected HAL works on your system. The options that are presented here are known to be compatible with most systems. However, a few systems may experience problems.When you install the following HALs on a Windows XP-based or Windows Server 2003-based computer, the following device manager HAL options appear:
"Standard PC," Non-ACPI PIC HAL (Hal.dll)
Standard PC"MPS Uniprocessor PC," Non-ACPI APIC UP HAL (Halapic.dll)
Standard PC
MPS Uniprocessor
MPS Multiprocessor"MPS Multiprocessor PC," Non-ACPI APIC MP HAL (Halmps.dll)
Standard PC
MPS Multiprocessor"Advanced Configuration and Power Interface (ACPI) PC," ACPI PIC HAL (Halacpi.dll)
Standard PC
Advanced Configuration and Power Interface (ACPI) PC"ACPI Uniprocessor PC," ACPI APIC UP HAL (Halaacpi.dll)
Standard PC
Advanced Configuration and Power Interface (ACPI) PC
ACPI Uniprocessor
ACPI Multiprocessor"ACPI Multiprocessor PC," ACPI APIC MP HAL (Halmacpi.dll)
Standard PC
Advanced Configuration and Power Interface (ACPI) PC
ACPI Multiprocessor
MPS MultiprocessorNotes
A common symptom when deploying the incorrect image to a computer is that the Sysprep image stops responding on restart or reports the following error message:
Stop 0x0000007b
If an incorrect HAL is forced during Setup or by using a System Preparation Image (Sysprep), you can see the correct list of HALs only if you perform a new installation of Windows XP or Windows Server 2003. You cannot change to a HAL other than what is listed in Device Manager.
Device Manager does not permit the change from a Non-ACPI HAL to an ACPI HAL. You must use a new install of Windows XP or Windows Server 2003 for this kind of change. Change from an ACPI HAL to a Non-ACPI HAL only for troubleshooting purposes.
On Windows XP and later versions, the ACPI Uniprocessor HAL and the MPS Uniprocessor HAL recognize the existence of more than one processor and report the MP ID. Plug and Play detects that the computer devnode's hardware ID list has changed and moves the devnode back through the "found new hardware" detection process. Therefore, when you add a second processor, the MP files (HAL and kernels) are automatically installed, and you do not have to manually update the driver in Device Manager.
Microsoft does not support running a HAL other than the HAL that Windows Setup would typically install on the computer. For example, running a PIC HAL on an APIC computer is not supported. Although this configuration may appear to work, Microsoft does not test this configuration and you may have performance and interrupt issues. Microsoft also does not support swapping out the files that are used by the HAL to manually change HAL types.
Microsoft recommends that you switch HALs for troubleshooting purposes only or to workaround a hardware problem.
When you create a Sysprep image, the image must contain the correct HAL type for the target computer. The following list describes the computers that you can deploy a particular Sysprep image to based on the HAL type in the source computer:
You can deploy a Sysprep image created on a computer that uses a Standard PC, Non-ACPI PIC HAL (Hal.dll) to a computer that uses the following HAL types:
Standard PC, Non-ACPI PIC HAL (Hal.dll)
You can deploy a Sysprep image created on a computer that uses an Advanced Configuration and Power Interface (ACPI) PC, ACPI PIC HAL (Halacpi.dll) to a computer that uses the following HAL types:
Advanced Configuration and Power Interface (ACPI) PC, ACPI PIC HAL (Halacpi.dll)
You can deploy a Sysprep image created on a computer that uses a MPS Uniprocessor PC, Non-ACPI APIC UP HAL (Halapic.dll) to a computer that uses the following HAL types:
MPS Uniprocessor PC, Non-ACPI APIC UP HAL (Halapic.dll)
MPS Multiprocessor PC, Non-ACPI APIC MP HAL (Halmps.dll)
You can deploy a Sysprep image created on a computer that uses a MPS Multiprocessor PC, Non-ACPI APIC MP HAL (Halmps.dll) to a computer that uses the following HAL types:
MPS Multiprocessor PC, Non-ACPI APIC MP HAL (Halmps.dll)
MPS Uniprocessor PC, Non-ACPI APIC UP HAL (Halapic.dll)
You can deploy a Sysprep image created on a computer that uses an ACPI Uniprocessor PC, ACPI APIC UP HAL (Halaacpi.dll) to a computer that uses the following HAL types:
ACPI Uniprocessor PC, ACPI APIC UP HAL (Halaacpi.dll)
ACPI Multiprocessor PC, ACPI APIC MP HAL (Halmacpi.dll)
You can deploy a Sysprep image created on a computer that uses an ACPI Multiprocessor PC, ACPI APIC MP HAL (Halmacpi.dll) to a computer that uses the following HAL types:
ACPI Multiprocessor PC, ACPI APIC MP HAL (Halmacpi.dll)
ACPI Uniprocessor PC, ACPI APIC UP HAL (Halaacpi.dll)Note Currently, the options in Device Manager do not list an APIC version of the HAL when you change the HAL on an APIC system. Although the PIC HAL that is installed may work, you can select the preferred APIC version after you install a hotfix for computers that are running Windows Server 2003 with Service Pack 1.For more information about the hotfix for Windows Server 2003 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
923425 (http://support.microsoft.com/kb/923425/ ) You do not have the option to downgrade to a hardware abstraction layer that is set up to use a single-processor advanced programmable interrupt controller when you try to change the computer type by using Device Manager in Windows Server 2003
Back to the top
About UpdateUPHalUpdateUPHal was designed for the following scenarios.
Scenario 1
Source computer: MPS Multiprocessor (NON-ACPI APIC MP) Destination computer: MPS Uniprocessor (NON-ACPI APIC UP)To force the ACPI Uniprocessor HAL, use the following entry:
UpdateUPHal=MPS_UP, %windir%\inf\hal.inf
Scenario 2
Source computer: ACPI Multiprocessor (ACPI APIC MP) Destination computer: ACPI Uniprocessor (ACPI APIC UP)To force the Uniprocessor HAL, use the following entry:
UpdateUPHal=ACPIAPIC_UP, %windir%\inf\hal.infIn this scenario, an easier solution is to create the image on the ACPI Uniprocessor computer. Windows XP and Windows Server 2003 will automatically install the ACPI Multiprocessor HAL if the computer supports it.
Back to the top
About UpdateHalUpdateHal was designed for the following scenarios.
Scenario 1
Source computer: MPS Uniprocessor (NON-ACPI APIC UP)Destination computer: MPS Multiprocessor (NON-ACPI APIC MP)In this scenario, use the following entry:
UpdateHal=MPS_MP, %windir%\inf\hal.infNote This entry is required only for Windows 2000 Server. Windows XP and Windows Server 2003 automatically upgrade to the MPS Multiprocessor HAL.
Scenario 2
Source computer: ACPI Uniprocessor (ACPI APIC UP) Destination computer: ACPI Multiprocessor (ACPI APIC MP)In this scenario, use the following entry:
UpdateHal=ACPIAPIC_MP, %windir%\inf\hal.infNote This entry is required only for Windows 2000 Server. Windows XP and Windows Server 2003 automatically upgrade to the ACPI Multiprocessor HAL. For more information about how to force a HAL, click the following article number to view the article in the Microsoft Knowledge Base:
299340 (http://support.microsoft.com/kb/299340/ ) How to force a Hardware Abstraction Layer during an upgrade or an installation of Windows XP For more information about how to reinstall Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
315341 (http://support.microsoft.com/kb/315341/ ) How to perform an in-place upgrade (reinstallation) of Windows XP
How to force a Hardware Abstraction Layer during an upgrade or an installation of Windows XP
View products that this article applies to.
This article was previously published under Q299340
On This Page
INTRODUCTION
MORE INFORMATION
Upgrade from Microsoft Windows 2000 to Windows XP
In-place upgrade of Windows XP
Force in a system HAL
Expand all Collapse all
INTRODUCTION
This article describes how to force in a system Hardware Abstraction Layer (HAL...
This article describes how to force in a system Hardware Abstraction Layer (HAL) during an upgrade or an installation of Microsoft Windows XP. Note The procedure to change from the Standard PC HAL to the Advanced Configuration and Power Interface (ACPI) HAL differs in Windows XP from the procedure that Microsoft Windows 2000 uses.
Back to the top
MORE INFORMATION
The HAL is computer code in Windows XP that makes it possible for Windows XP to...The HAL is computer code in Windows XP that makes it possible for Windows XP to run on a variety of different computer types. The HAL manipulates the computer hardware directly. During an upgrade or an installation of Windows XP, you can “force in” a HAL by pressing the F5 key, and then selecting from the available computer types.
Back to the top
Upgrade from Microsoft Windows 2000 to Windows XPWhen you upgrade from Windows 2000 to Windows XP, the HAL is preserved. For example, if the HAL on the Windows 2000-based computer is a Standard PC HAL, that HAL is reinstalled when you upgrade to Windows XP.
Back to the top
In-place upgrade of Windows XPWhen you perform an in-place upgrade, or a reinstallation of Windows XP, if the Setup program detects that you have an unsupported HAL installed for your computer type, and the Setup program determines that a HAL that supports that computer type must be installed, it installs the correct HAL. When this issue occurs, the HAL is changed from what was previously installed.
Back to the top
Force in a system HALTo prevent Windows XP from automatically determining the system HAL during the upgrade or the installation of Windows XP, you can manually force in a system HAL. To force in a system Hardware Abstraction Layer (HAL) during an upgrade or installation of Windows XP, follow these steps:
During the Text-mode phase of the Setup program, when you receive the following message across the bottom of the screen, press F5:
Press F6 if you have to install a third-party SCSI or RAID driver.Note If you press F7, the Standard PC HAL loads and the ACPI compliance check is bypassed.
You receive the following list of computer types. A brief description of each HAL is included here:
ACPI Multiprocessor PCApplies to a multiple-processor ACPI computer.
ACPI Uniprocessor PCApplies to an ACPI multiple-processor board but with a single processor installed.
Advanced Configuration and Power Interface (ACPI) PCApplies to a single processor motherboard with single processor.
Compaq SystemPro Multiprocessor or 100% CompatibleApplies to a Compaq SystemPro computer.
MPS Uniprocessor PCApplies to non-ACPI computers dual processor motherboard with a single processor installed.
MPS Multiprocessor PCApplies to non-ACPI computers with a dual processor running.
Standard PCApplies to any Standard PC, non-ACPI, or non-MPS. The CPU may be a 386, a 486, a Pentium, a Pentium II, or a Pentium III.
Standard PC with C-Step i486
OtherNote The screen displays only two computer types at a time. To scroll up or down to view the complete list, use the arrow keys.For additional information about related topics, click the following article numbers to view the articles in the Microsoft Knowledge Base:
237556 (http://support.microsoft.com/kb/237556/ ) Troubleshooting Windows 2000 Hardware Abstraction Layer issues
309283 (http://support.microsoft.com/kb/309283/ ) HAL options after Windows XP or Windows Server 2003 Setup
How to Troubleshoot Windows 2000 Hardware Abstraction Layer Issues
View products that this article applies to.
if (!loadTOCNode) {var loadTOCNode = function(){}}
This article was previously published under Q237556
On This Page
SUMMARY
MORE INFORMATION
Determine Your Computer Type
View or Change Installed Computer Type
var sectionFilter = "type != 'notice' && type != 'securedata' && type != 'querywords'";
var tocArrow = "/library/images/support/kbgraphics/public/en-us/downarrow.gif";
var depthLimit = 10;
var depth3Limit = 10;
var depth4Limit = 5;
var depth5Limit = 3;
var tocEntryMinimum = 1;
Expand all Collapse all
if (kb_page_object)
{
kb_page_object.kb_imageExpandHoverText = 'Click to expand this image';
}
SUMMARY
In Windows 2000 there are several ways to troubleshoot issues related to the Ha...
loadTOCNode(1, 'summary');
In Windows 2000 there are several ways to troubleshoot issues related to the Hardware Abstraction Layer (HAL) that may occur as a result of misdetection, an outdated or non-compliant Advanced Configuration and Power Interface (ACPI) Basic Input/Output System (BIOS), or an incorrectly or manually installed computer type. This article describes some of the methods you can use to troubleshoot issues related to the HAL.NOTE: In this article, the term "computer type" and "HAL" have the same meaning, and may be interchanged.
Back to the top
MORE INFORMATION
Determine Your Computer Type To determine the computer type you are using: Clic...
loadTOCNode(1, 'moreinformation');
Determine Your Computer Type
loadTOCNode(2, 'moreinformation');
To determine the computer type you are using:
Click Start, point to Settings, click Control Panel, and then double-click System.
Click the Hardware tab, and then click Device Manager to view what is listed under the Computer branch. The following is the list of supported computer types. Possible values for the HAL under Standard computers include:
ACPI Multiprocessor PCACPI Uniprocessor PCAdvanced Configuration and Power Interface (ACPI) PCMPS Multiprocessor PCMPS Uniprocessor PCStandard PC Possible values for the HAL under Compaq include:
Compaq SystemPro Multiprocessor or 100% Compatible Possible values for the HAL under SGI include:
Silicon Graphics Visual Workstation
Back to the top
View or Change Installed Computer Type
loadTOCNode(2, 'moreinformation');
To view or change the installed computer type:WARNING: Note that you should not attempt to change from an ACPI HAL to a standard HAL or from a standard HAL to a ACPI HAL under any circumstances. Doing so will result in your computer not starting properly or at all. This occurs because the Plug and Play device tree that would be currently loaded is for ACPI, and it does not get reconstructed or revert to a standard HAL Plug and Play device tree. Because of this (the device tree structures being drastically different), the system is unaware of any hardware changes after the computer restarts to include the location of the boot device. Microsoft does not recommend or support this procedure as it will result in data loss.
Click Start, point to Settings, click Control Panel, and then double-click System.
Click the Hardware tab, and then click Device Manager to view what is listed under the Computer branch. As an example, "Standard PC", the detected computer type Windows 2000 installed on your computer, or an entry such as "Advanced Configuration Power Interface (ACPI) PC" may be listed.
To change the installed computer type, click the Driver tab, and then click Update Drivers.NOTE: You can only change or update your HAL from Device Manager under Computer Type when changing from a Standard PC HAL to a Standard Multiprocessor PC HAL, because changing from an ACPI HAL to a Standard HAL can result in your not being able to start your computer.If you are unable to start your computer properly as a result of the wrong computer type (HAL) being installed after Windows 2000 Setup, start the Emergency Repair process:
Start your computer by using the Windows 2000 Setup floppy disks, or with the Windows 2000 CD-ROM if your computer supports starting from a CD-ROM.
At the Welcome to Setup screen, press R to repair.
At the Windows 2000 Repair Options screen, press R to repair using the emergency repair process.
Press M to manually select repair options and ensure that "Verify Windows 2000 system files" and "Inspect startup environment" features are selected, or press F to run all repair options.
Once complete, the originally installed HAL and associated files should be restored. Remove the CD-ROM or floppy disk and then restart your computer.NOTE: The incorrectly installed computer type is still visible in Device Manager.
To ensure the correct computer type is visible in Device Manager, when you restart your computer, press F8, choose Last Known Good Configuration, and then press ENTER.
Click the appropriate hardware profile (if more than one profile exists). On the hardware profile, click Configuration Recovery, press ENTER, and then permit Windows 2000 to start.The optimum method to change from an ACPI HAL to a Standard HAL is to re-install Windows 2000 as an upgrade:
Start Windows 2000 Setup as an upgrade.
To automatically disable ACPI support and allow Windows 2000 to detect automatically or manually change and install the correct (Standard HAL) computer type that your computer supports, use either of the following methods:
To Auto detect the computer type:Press F7 when Setup generates the following informational message:
Press F6 if you need to install a third party SCSI or RAID driver. NOTE: You do not receive a visual indicator that auto detection is taking place when you press F7; proceed normally with setup until it is completed.
To Manually Select your computer type:Press F5, and then manually choose the correct Standard computer type by using the following list:
Collapse this tableExpand this table
i386 source File
Computer Type
*hal.dll
Compaq SystemPro Multiprocessor or 100% Compatible
*halapic.dll
MPS Uniprocessor PC
*halapic.dll
MPS Multiprocessor PC
*hal.dll
Standard PC
*halborg.dll
SGI mpNOTE: You do not have to use the reinstallation method to update from a Standard PC HAL to a MPS Multiprocessor PC HAL, you can use the Update Drivers feature in Device Manager for this. However, you must reinstall Windows 2000 when going to an ACPI HAL computer type on a computer that was using the Standard computer type, and then permit Windows 2000 to automatically detect the correct computer type.If the Emergency Repair process cannot locate your repair information or if the repair information is invalid, recover your Windows 2000 installation by starting the Recovery Console:
Start your computer with the Windows 2000 Setup floppy disks, or with the Windows 2000 CD-ROM if your computer supports starting from CD-ROM. At the Welcome to Setup screen, press R to repair, and then press C to start the Recovery Console.NOTE: For information about using the Recovery Console, please click the article number below to view the article in the Microsoft Knowledge Base:
229716 (http://support.microsoft.com/kb/229716/EN-US/ ) Description of the Windows 2000 Recovery Console
After you log on to your computer, from the %SystemRoot%\System32 folder of your original Windows 2000 installation, use the command console to copy and rename the following files as noted in the following lists. First determine which HAL and kernel files your computer requires by using the following list of supported computer types:NOTE: Those marked with an asterisk character are Standard computer types (non-ACPI).i386 source file: i386\driver.cab\halmacpi.dllComputer type: ACPI Multiprocessor PCCopy to this folder: winnt\System32Rename to this file name: hal.dlli386 source file: i386\driver.cab\halaacpi.dllComputer type: ACPI Uniprocessor PCCopy to this folder: winnt\System32Rename to this file name: hal.dlli386 source file: i386\driver.cab\halacpi.dllComputer type: Advanced Configuration and Power Interface (ACPI) PCCopy to this folder: winnt\System32Rename to this file name: hal.dlli386 source file: *i386\driver.cab\halsp.dllComputer type: Compaq SystemPro Multiprocessor or 100% CompatibleCopy to this folder: winnt\System32Rename to this file name: hal.dlli386 source file: *i386\driver.cab\halapic.dllComputer type: MPS Uniprocessor PCCopy to this folder: winnt\System32Rename to this file name: hal.dlli386 source file: *i386\driver.cab\halmps.dllComputer type: MPS Multiprocessor PCCopy to this folder: winnt\System32Rename to this file name: hal.dlli386 source file: *i386\driver.cab\hal.dllComputer type: Standard PCCopy to this folder: winnt\System32Rename to this file name: hal.dlli386 source file: *i386\driver.cab\halborg.dllComputer type: SGI mpCopy to this folder: winnt\System32Rename to this file name: hal.dll
As indicated in the following table, copy all the appropriate kernel files common for your system (Uniprocessor vs. Multiprocessor) and the appropriate HAL file based on your computer supported computer type from the Windows 2000 CD-ROM (i386\driver.cab) or installed service pack to the corresponding folder listed in the table under your original Windows 2000 installation, and then rename them (if required) to Ntoskrnl.exe and Hal.dll, respectively.
Collapse this tableExpand this table
Common Multiprocessor kernel files
Copy to the following directory
Rename to the following filename
i386\driver.cab\ntkrnlmp.exe
winnt\System32
ntoskrnl.exe
i386\driver.cab\ntkrpamp.exe
winnt\System32
ntkrnlpa.exe
i386\driver.cab\kernel32.dll
winnt\System32
kernel32.dll
i386\driver.cab\ntdll.dll
winnt\System32
ntdll.dll
i386\driver.cab\win32k.sys
winnt\System32\drivers
win32k.sys
i386\driver.cab\winsrv.dll
winnt\System32
winsrv.dll
Common Uniprocessor kernel files
Copy to the following directory
Rename to the following filename
i386\driver.cab\ntoskrnl.exe
winnt\System32
ntoskrnl.exe
i386\driver.cab\ntkrnlpa.exe
winnt\System32
ntkrnlpa.exe
i386\driver.cab\kernel32.dll
winnt\System32
kernel32.dll
i386\driver.cab\ntdll.dll
winnt\System32
ntdll.dll
i386\driver.cab\win32k.sys
winnt\System32
win32k.sys
i386\driver.cab\winsrv.dll
winnt\System32
winsrv.dll
Expand the Ntdll.dll file from the original Windows 2000 CD-ROM (i386\driver.cab) or installed service pack to the %SystemRoot%\system32 folder of your original Windows 2000 installation.For example:
drive:\i386\driver.cab /f:ntdll.dll c:\winnt\system32 where drive is the drive letter of your CD-ROM drive containing the Windows 2000 Server CD-ROM.
Expand the Win32k.sys file from the original Windows 2000 CD-ROM (i386\driver.cab) or installed service pack to the %SystemRoot%\system32 folder of your original Windows 2000 installation.
Expand the Kernel32.dll and Winsrv.dll from the Windows 2000 CD-ROM (i386\driver.cab) or installed service pack to the %SystemRoot%\system32 folder of your original Windows 2000 installation. For example, type the following commands expand drive:\i386\driver.cab /F:kernel32.dll %systemroot%\system32\kernel32.dllexpand drive:\i386\driver.cab /F:winsrv.dll %systemroot%\system32\winsrv.dllwhere drive is your CD-ROM drive letter.
Restart your computer.For related information, please click the article number below to view the article in the Microsoft Knowledge Base:
234558 (http://support.microsoft.com/kb/234558/EN-US/ ) How to Add Support for Multiple Processors in Windows 2000 WARNING: Windows 2000 displays the list of compatible computer types that can be installed when you use Device Manager to manually update. Doing anything beyond what is listed as compatible is likely to result in not being able to start your computer correctly or at all. If you do have "Advanced Configuration Power Interface (ACPI) PC" listed as your computer type or after updating to the latest ACPI BIOS, then you cannot update to the "ACPI Multiprocessor PC" through Device Manager and may result in not being able to start your computer correctly or at all. In the case of an ACPI HAL, for Windows 2000 to support or recognize both CPUs using an ACPI HAL, you must first update to the latest ACPI BIOS which is fully compliant, then re-install Windows 2000 as an upgrade so it can automatically detect and install ACPI Multiprocessor PC; if it does not, your BIOS in not fully compliant yet.
Windows stops responding during Windows XP shut down
View products that this article applies to.
if (!loadTOCNode) {var loadTOCNode = function(){}}
This article was previously published under Q307274
Notice
loadTOCNode(1, 'notice');
The service pack (SP) that this article describes has been replaced by a newer SP. To resolve this problem, install the most current SP for Windows XP. To install the most current SP, visit the following Microsoft Web site:
http://windowsupdate.microsoft.com (http://windowsupdate.microsoft.com)
Expand all Collapse all
if (kb_page_object)
{
kb_page_object.kb_imageExpandHoverText = 'Click to expand this image';
}
SYMPTOMS
When you shut down your Microsoft Windows XP-based computer, Windows may interm...
loadTOCNode(1, 'symptoms');
When you shut down your Microsoft Windows XP-based computer, Windows may intermittently stop responding (hang), and you receive the following message:
Saving your settings.During this time, you may be able to move the pointer, but the computer may not respond when you press CTRL+ALT+DEL.
Back to the top
CAUSE
This problem may occur if all the following conditions are true: You have East...
loadTOCNode(1, 'cause');
This problem may occur if all the following conditions are true:
You have East Asian Language support installed on your Windows XP-based computer and the Input Method Editor (IME) selected as your default input language.
You have the Welcome screen turned on.
Back to the top
RESOLUTION
To resolve this problem obtain the latest service pack for Microsoft Windows XP....
loadTOCNode(1, 'resolution');
To resolve this problem obtain the latest service pack for Microsoft Windows XP. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
322389 (http://support.microsoft.com/kb/322389/ ) How to obtain the latest Windows XP service pack
Back to the top
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that ar...
loadTOCNode(1, 'status');
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Windows XP Service Pack 1.
Advanced troubleshooting for shutdown problems in Windows XP
View products that this article applies to.
if (!loadTOCNode) {var loadTOCNode = function(){}}
This article was previously published under Q308029
On This Page
INTRODUCTION
MORE INFORMATION
You receive an error message when you shut down or restart the computer
Method 1: Configure Windows so that it does not load the file or the service mentioned in the error message
Method 2: See whether a program has recently been removed from the computer
The computer stops responding when you try to shut down or restart the computer
Method 1: Try to shut down or restart the computer from safe mode
Method 2: Use Device Manager to determine if the problem is related to a device driver
Method 3: Try to restore operation of Windows XP by using System Restore
Method 4: Try to restore operation of Windows XP by using the Last Known Good Configuration functionality
Method 5: Try to repair your installation of Windows XP by performing an in-place upgrade
Method 6: Confirm that the CMOS/BIOS settings are correct
Method 7: Confirm that your hard disk or file system is not damaged
The computer restarts unexpectedly or restarts when you try to shut down the computer
var sectionFilter = "type != 'notice' && type != 'securedata' && type != 'querywords'";
var tocArrow = "/library/images/support/kbgraphics/public/en-us/downarrow.gif";
var depthLimit = 10;
var depth3Limit = 10;
var depth4Limit = 5;
var depth5Limit = 3;
var tocEntryMinimum = 1;
Expand all Collapse all
if (kb_page_object)
{
kb_page_object.kb_imageExpandHoverText = 'Click to expand this image';
}
INTRODUCTION
This article describes how to troubleshoot difficulties that may occur when you...
loadTOCNode(1, 'summary');
This article describes how to troubleshoot difficulties that may occur when you try to shut down Windows XP. This article is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help or contact support. For information about how to contact support, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/ (http://support.microsoft.com/contactus/) Note Before you begin, make sure that the latest Service Pack and updates are installed on your computer. For more information about how to obtain the latest Windows XP service pack and updates, click the following article number to view the article in the Microsoft Knowledge Base:
322389 (http://support.microsoft.com/kb/322389/ ) How to obtain the latest Windows XP service pack
Back to the top
MORE INFORMATION
You receive an error message when you shut down or restart the computer To reso...
loadTOCNode(1, 'moreinformation');
You receive an error message when you shut down or restart the computer
loadTOCNode(2, 'moreinformation');
To resolve this issue, use either of the methods.
Method 1: Configure Windows so that it does not load the file or the service mentioned in the error message
loadTOCNode(3, 'moreinformation');
If the error message refers to a file or service, the file or service may be listed on one of the tabs in the System Configuration utility (Msconfig.exe). If the file or service is listed, follow the procedure outlined in the second article mentioned in this section to turn it off. If the file or service is not listed, continue with the next troubleshooting step in this article.For more information about disabling a file or service using the System Configuration utility, click the following article number to view the article in the Microsoft Knowledge Base:
310353 (http://support.microsoft.com/kb/310353/ ) How to perform a clean boot in Windows XP For more information about how to turn off services using Computer Management, click the following article number to view the article in the Microsoft Knowledge Base:
310602 (http://support.microsoft.com/kb/310602/ ) How to disable a service or device that prevents Windows from starting Contact the manufacturer of the faulty service for more information. Note For more information about the file or service that is causing the problem, contact a Microsoft Customer Support Services professional for help. For information about how to contact a Support Services professional, visit the following Microsoft Web site:
http://support.microsoft.com (http://support.microsoft.com/) If the OEM of your computer installed Windows XP, contact this manufacturer for help with this issue.
Method 2: See whether a program has recently been removed from the computer
loadTOCNode(3, 'moreinformation');
If you recently removed a program or a Windows component from the computer by deleting it manually, related information that is still on your computer may be causing the problem. Reinstall the program or component, and then either use the Add or Remove Programs tool or follow the manufacturer's instructions to remove it.To remove a program from the computer:
Click Start, click Control Panel, and then click Add or Remove Programs.
In the list of programs, click the program that you want to remove, and then click Change/Remove.
Click Yes when you are prompted to confirm if you want to remove the program.If the program is not listed in the Add or Remove Programs tool, contact the manufacturer to obtain instructions for removing it.
Back to the top
The computer stops responding when you try to shut down or restart the computer
loadTOCNode(2, 'moreinformation');
To resolve this problem, use any of the methods that are described in the following sections.
Method 1: Try to shut down or restart the computer from safe mode
loadTOCNode(3, 'moreinformation');
For more information about troubleshooting Windows XP by using safe mode, click the following article numbers to view the articles in the Microsoft Knowledge Base:
315222 (http://support.microsoft.com/kb/315222/ ) A description of the safe mode boot options in Windows XP
310602 (http://support.microsoft.com/kb/310602/ ) How to disable a service or device that prevents Windows from starting Note If you can shut down or restart your computer from safe mode, continue to the next section to troubleshoot possible driver issues.
Method 2: Use Device Manager to determine if the problem is related to a device driver
loadTOCNode(3, 'moreinformation');
You can use Device Manager to examine and change devices that are configured by software. Note that if the hardware device uses jumper pins or dip switches, you must configure the device manually. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
310126 (http://support.microsoft.com/kb/310126/ ) Troubleshooting device conflicts with Device Manager
314464 (http://support.microsoft.com/kb/314464/ ) How to troubleshoot unknown devices listed in Device Manager
Method 3: Try to restore operation of Windows XP by using System Restore
loadTOCNode(3, 'moreinformation');
You can use the System Restore tool to return your computer to a previous working state. System Restore takes a "snapshot" of critical system files and some program files and stores this information as restore points. You can use these restore points to return Windows XP to a previous state. For more information about using the System Restore tool, click the following article number to view the article in the Microsoft Knowledge Base:
306084 (http://support.microsoft.com/kb/306084/ ) How to restore the operating system to a previous state in Windows XP For additional information about System Restore, click Help and Support on the Start menu. In the Search box, type system restore, and then press ENTER.
Method 4: Try to restore operation of Windows XP by using the Last Known Good Configuration functionality
loadTOCNode(3, 'moreinformation');
If Windows does not start, restart Windows by using the Last Known Good Configuration functionality:
Start the computer, and when Windows begins to start, press F8 to make the Windows Advanced Options menu appear.
Use the arrow keys to select Last Known Good Configuration (your most recent settings that worked), and then press ENTER.
If a Boot menu appears, use the arrow keys to select Microsoft Windows XP, and then press ENTER. Windows XP starts your computer by using the registry information that was saved at the last shutdown.
Method 5: Try to repair your installation of Windows XP by performing an in-place upgrade
loadTOCNode(3, 'moreinformation');
You can repair a damaged Windows installation if you run Windows Setup from the Windows XP CD-ROM.For more information about how to perform an in-place upgrade of Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
315341 (http://support.microsoft.com/kb/315341/ ) How to perform an in-place upgrade (reinstallation) of Windows XP
Method 6: Confirm that the CMOS/BIOS settings are correct
loadTOCNode(3, 'moreinformation');
Warning This procedure may involve changing the complementary metal oxide semiconductor (CMOS) settings and modifying the basic input/output system (BIOS) settings. Incorrect changes to your computer's BIOS can result in serious problems. Microsoft cannot guarantee that problems resulting from changes to your BIOS can be solved. Change your CMOS settings at your own risk.Incorrect or corrupted CMOS and BIOS settings can cause startup and shutdown problems. Microsoft cannot provide specific instructions to change your CMOS and BIOS settings, because these settings are specific to your computer.For information about the correct CMOS and BIOS settings for your computer and about how to check and change these settings, see your computer documentation or contact the manufacturer of your computer. Note A damaged or insufficiently charged internal battery can corrupt CMOS or BIOS settings.
Method 7: Confirm that your hard disk or file system is not damaged
loadTOCNode(3, 'moreinformation');
You may be able to resolve the problem if you start your computer from the Windows XP CD-ROM, load the Microsoft Recovery Console, and then use the Chkdsk command line utility.Important Microsoft recommends that only advanced users or administrators use the Recovery Console. You must know the administrator's password to use the Recovery Console.For more information about how to check and repair a damaged hard disk using Chkdsk, see the 'Using the Recovery Console' and 'Using the Recovery Console Command Prompt' sections in the following article, click the following article number to view the article in the Microsoft Knowledge Base:
307654 (http://support.microsoft.com/kb/307654/ ) How to install and use the Recovery Console in Windows XP Note If the Chkdsk command reports that it cannot access your hard disk, you may have a hardware failure. Check all of your cable connections and any jumper settings on your drive. Ask either a computer repair professional or the manufacturer of your computer for more help. If the chkdsk command reports that it was unable to fix all hard drive problems, your file system or Master Boot Record (MBR) may be damaged or be no longer accessible. Explore appropriate Recovery Console commands such as fixmbr and fixboot, contact a data recovery service, or repartition and reformat your hard disk. Note If you repartition and reformat your hard disk, you will lose all of the information on the disk.Important For more help with this issue, contact either your computer manufacturer or a Microsoft Product Support Services professional. Microsoft recommends that you ask only qualified personnel to repair your computer. Computer repair performed by non-qualified personnel can void your computer's warranty.
Back to the top
The computer restarts unexpectedly or restarts when you try to shut down the computer
loadTOCNode(2, 'moreinformation');
For more information about unexpected restarts in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
320299 (http://support.microsoft.com/kb/320299/ ) Windows XP restarts unexpectedly or restarts when you shut down the computer
WINDOWS XPSHUTDOWN & RESTARTTROUBLESHOOTINGVersion 13.8 — March 5, 2007Hold mouse here for list of most recent changes.Receive notice whenever this page is updated.
“With its rock-solid foundation and ground-breaking new features, Windows XP Professional won’t quit working, even when your workday is done.” — Microsoft(Did they know what they were saying?)
Shutdown problems in Windows XP can be caused by many factors, just like earlier versions of Windows. These included: a damaged exit sound file; incorrectly configured, damaged, or incompatible hardware; conflicting programs, or an incompatible, damaged, or conflicting device driver.
For a step-by-step troubleshooting method that applies to all versions of Windows 9x, see the generic Windows Shutdown Troubleshooter. Some of its steps may be found to apply to Windows XP as well, though many will not. -->
Windows XP shutdown issues mostly center around a very few issues, especially legacy hardware and software compatibility issues.Currently, the leading cause of Windows XP shutdown problems is hardware incompatibility, including driver issues. These are detailed below where known. However, it is impossible to list every possible hardware or driver issue individually. My best advice is: Check all drivers for all hardware devices to ensure that they are the current best for Windows XP.
REBOOT INSTEAD OF SHUTDOWN
Most Win XP shutdown problems reported thus far have been that it reboots when shutdown is attempted. This may be a global symptom emerging from several distinct causes, because, by default, XP executes an automatic restart in the event of a system failure. Therefore, more or less anything compromising the operating system during the shutdown process could force this reboot.
Disabling the “restart on system failure” feature may permit the exact cause to be isolated: Right-click on My Computer, click Properties, click the Advanced tab. Under “Startup & Recovery,” click Settings. Under “System Failure,” uncheck the box in front of “Automatically restart.”
Here are some things that have produced this reboot-instead-of-shutdown symptom:
By now, the Roxio/Adeptec Easy CD / Direct CD software is well documented as being the major cause of this undesirable shutdown behavior. SOLUTION: Roxio has released new drivers (here) to solve this problem in both the Platinum and Basic editions of Easy CD Creator 5. As expected, at least half of the Win XP shutdown problems went away with the release of these patches.One warning about this patch comes from correspondent Bert Smith: Be sure to read the directions! “Roxio Easy CD Creator Platinum 5.0 can be a real hassle to get working under Win XP,” Bert wrote, “and there is the risk of your computer not booting if you blindly go ahead and install it without first consulting the Roxio Web site.” Bert also mentioned that Roxio’s “Take Two” backup program (normally part of Easy CD Creator 5 Platinum) is uninstalled when the Roxio patch is applied.
Direct CD. Many Easy CD users (but not all) found that installing Easy CD 5.0 does not cause the shutdown problem, provided they do not install the Direct CD component.
UDFRINST. Several people solved this reboot-on-shutdown problem by deleting the UDFRINST file. This file is part of the Roxio CD-RW software for systems not using Direct CD.
CDRALW2K.SYS. Correspondent Larry Blumette identified the CDRALW2K.SYS file (version 1.0.0.1048) as the Roxio file causing his shutdown problems and error conditions. When he deleted or renamed this one file, his problems went away. (Of course, you lose your CD functionality that way, too.)
Video Pack 5. Roxio’s Video Pack 5 causes the same problem because it contains includes the main parts of Easy CD 5. SOLUTION: Uninstall Video Pack 5 and also delete CDRALW2K.SYS (Tip from Christian Männchen). However, this solution may also have the side-effect of disabling access to your CD or DVD drive. SOLUTION TO THE SIDE-EFFECT: Apply one of the repair methods in MSKB Article 270008, Code 31 Messages Occur After Removing Adaptec Easy CD Creator 4.02c in Windows 2000 (Tip from Peter Kingsley).
Whether or not APM is enabled makes a difference — but the effect could go two ways. Some users report that XP reboots on shutdown if APM is enabled, but shuts Windows down just fine if APM is disabled. Other users report exactly the opposite behavior. According to Jack Dunne, this is similar to a known Windows 2000 problem. The issue seems related to the computer’s specific hardware or BIOS — so, as with all NT operating systems, stick to the Hardware Compatibility List where possible.
USB Connections As can be seen from remarks in the Misc. Hardware Issues section below, several different USB-related issues can impact shutdown. One of the most concrete examples was a “reboot on shutdown” problem contributed by correspondent Rick Bross. If his several USB devices (PDA cradle, flash card reader, etc) were plugged into the motherboard’s USB ports, his computer would reboot on an attempted shutdown; but when, instead, he plugged them into an external USB 2.0 hub, shutdown went just fine. (This was with Win XP Professional SP1 on a Supermicro X5DAE dual Xeon motherboard. The same devices plugged into an Asus A7M-266D dual AMD 2000MP system on the same OS worked without problem.)
“Wake on” power settings Power-management settings that have the computer “wake” on LAN, USB, modem, or (for that matter) probably anything else may also trigger a restart after shutdown. Correspondent Simon Wei provided this tip after a friend of his found an old old Logitech USB mouse would trigger “wake on USB” after every Windows shutdown. Their solution was to remove that particular mouse and all worked fine. The principle is much more far-reaching than this one example.
Hidden “wake on” power settings If you have an Ethernet card integrated into your motherboard, you may have hidden “wake on” settings that are harder to find. Site visitor Jim Porter found that his Asus P5GDC-V Deluxe motherboard had a “wake on” setting in Device Manager Properties Advanced rather than in the BIOS or Power Management settings. (The Asus P5AD2 and P5GD2 boards have this also.)
Y-SB3 Logitech Internet Keyboard can also cause this problem. If you use it as a simple generic keyboard, there’s no problem; but, if you install the Key Commander software that drives the special Internet functions, Win XP will restart instead of shut down. Unfortunately, Logitech has decided that they will not be updating this driver for this keyboard. (Tip from Jan K. Haak.)
Logitech MouseWare 8.6. Windows reboots when shutdown is attempted. The software caused a BSOD with KBDCLASS.SYS. Removing the software solved the BSOD the problem. (Tip from Pablo Cheng.) MouseWare 9.0 and 9.1 also have been linked to reboot-instead-of-shutdown in Win XP. Removing the software resolves the problem. (Tip from Aswin Kindts, Greg Williams, and others)
Webstar DPX USB cable modem. In the one case known to me, the problem was solved by switching the modem’s connector from the USB 1.1 port on the motherboard to the USB 2.0 PCI card. (The modem was provided by Telewest Broadband, manufactured by Scientific Atlanta.) (Tip from Ann L. Goonan.)
SHUTDOWN HANGS ON “SAVING YOUR SETTINGS”
During shutdown or reboot, Win XP may hang (stop responding) at the “saving your settings” screen. During such a hang, there is no response to Ctrl+Alt+Del; the mouse may or may not work. The problem may be intermittent.
This is a known bug in Windows XP, for which Microsoft has a supported fix. To learn how to get this patch, see MSKB 307274, “Windows XP Stops Responding (Hangs) During Windows Shutdown.” The necessary patch is included in Windows XP Service Pack 1, and also is now available on the Windows Update site under “Recommended Updates” for Win XP Professional, titled “Restarting Windows XP.” However, to find it, you may need to reconfigure how Windows Update appears for you, by enabling the Windows Update Catalog as follows: At the Windows Update page, click Personalize Windows Update at the left, and then Enable the Windows Update Catalog. Save your settings. This adds the Windows Update Catalog link in the left box. Click this link, then click Find updates for Microsoft Windows systems. Pick Windows XP in the drop-down list, click Search, take Recommended Updates, and find the “Restarting Windows XP” patch which references Q307274.
As a workaround, newsgroup correspondent “lou” resolved this problem by dismantling the Windows XP logon Welcome screen. In the Control Panel, click User Accounts, then click “Change the way users log on or off.” Uncheck the box that says “Use the Welcome screen.” This removes the initial logon screen with individual icons for each user and, instead, pops up the classic logon prompt that requires each user to type a user name and password.
SBLive: DEVLDR32.EXE PROBLEMS
In the early days of Win ME, one of the biggest culprits for shutdown issue was the Creative Labs SoundBlaster Live. History repeated itself in the Beta phase of Win XP. SOLUTION: The SBLive drivers in the released version of Win XP solved the shutdown problem for most (but not all) SBLive users.
Here’s the commonly reported problem scenario people encountered: On attempting shutdown, nothing at all appears to happen for a prolonged period of time. Eventually, an “End Task” window appears, wanting to terminate DEVLDR32.EXE. No matter what one does, one ultimately is locked out of shutting down other than by a power switch shutoff. (NOTE: This problem exists with the SBLive in Windows 2000 also.)
You may have to do a couple of extra steps to get rid of old files so that the new drivers will install correctly (especially if you installed the final version of Win XP on top of one of the Beta versions), or to remove troublesome support software. Correspondent Sean Caldwell summarized his steps: Shutdown Windows. Remove the Creative card. Reboot in Safe Mode. In the \WINDOWS\SYSTEM32 folder, delete the DEVLDR file. Fully shutdown the computer before rebooting.
Some users report that the DEVLDR problem continues to plague them even with the new drivers. If installing the new drivers doesn’t solve your shutdown problem, try these solutions:
Correspondent Martin Sladek wrote: “I’ve run into the very same problem with SBLive Value drivers. The problem was so severe I ran without the software all together. Since then, SBLive 5.1 came out, and I had installed the 5.1 version of the software in Windows 2000 Pro. I’ve not had a single problem since.”
But updating your drivers in Win XP may not be as easy as one would hope. Some problems especially appear where multiple users are enabled on the system and one switches between users during a single Windows session. There may be numerous files with the same name (but different version numbers!) variously located in the I386, SYSTEM32, and SYSTEM32\REINSTALLBACKUPS\0000 folders. These may conflict with each other. If you rename DEVLDR32 (ver 1.0.0.22) in SYSTEM32, another one will replace it. (First, you need to press Ctrl+Alt+Del and end DEVLDR in Task Manager). But if you use DEVLDR32 (ver 1.0.0.17) from the I386 folder, this problem doesn’t occur. Reboot when finished to reinaugurate the disabled service. (Tip from Terence Shortt, aka tbone8200 on dellTalk.)
MISC. HARDWARE ISSUES
In addition to hardware issues mentioned under other specialized topics on this page, many users have written identifying specific hardware as at the root of the Windows XP shutdown issue. Here’s what they have reported:
CD-ROM DRIVE: Samsung 24x. Correspondent Y. Leroux has identified the culprit in his shutdown problem, but doesn’t yet have a permanent solution. If his Samsung CD-ROM drive is empty, Win XP hangs on shutdown. To work around the problem, he either leaves a CD-ROM in the drive, or leaves the drive door open. He wanted to share this tip with others (thanks, Y.). Does anyone have a permanent solution for this one?
DVD-RW DRIVE: Pioneer DVR-106 or DVR-108. Correspondent L. Frankenberg traced his shutdown problem to this hardware. Correspondent Bob Berberick found the same for the DVR-108, and reported that a firmware update for the DVR-108 now available from Pioneer resolved his problem. It would probably be worth trying the firmware update for the DVR-106 as well, though I have no reports from anyone as to whether this solves the shutdown problem.
MODEMS: Intel Ambient HaM Modem. Causes Win XP to hang at shutdown. Previously, this was only resolved by disabling the modem. SOLUTION: Intel subsequently issued updated drivers that resolve this issue. They can be downloaded here. (Tip from Mark Gillespie.) However, a new problem with the Ambient Ham was introduced in Windows XP SP1, detailed below.
NOTE: The same problem has been reported for the Creatix V.90 Ham PCI Modem. Correspondent Gert Verheyen wrote that Creatix has an updated driver and, more importantly, detailed instructions about manual removal of the old one and installation of the new one. Go to the Creatix support page and click on V.90 HAM (internal) at right. The removal of the old driver first seems to have been the critical detail.
MODEMS: Billion BIPAC PCI Passive ISDN-card. Reboot instead of shutdown issue conjoined with BSOD error message STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL in file SERIAL.SYS. Previously, this was only resolved by disabling the Billion ISDN card. SOLUTION: Billion has now released a new driver 3.24 that solves this problem, available here. (Tip from Leo Foederer.)
MOTHERBOARDS: Asus P2B-F, P2B-VM, or P2L97. Causes a shutdown problem because Win XP Setup doesn’t enable ACPI by default. SOLUTION: Manually enable ACPI during a Win XP install or reinstall. Correspondent Bill Anderson (based on a solution by “Willy”) gave a lengthy description of how to do this, edited a little for space reasons. (Thanks also to correspondents Ward from Belgium & Tony Gray.)
Boot the computer from the Win XP CD-ROM.
Win XP Setup says it’s checking hardware. Soon after, at the bottom of the screen, it offers the opportunity to press F5. (If offered the chance to press F6, press F5 instead! – Tip from Mick Stone) Do this at once, and cross your fingers! [Various users report difficulty with this. Apparently, sometimes it works; sometimes not. It may be in the timing of exactly when you press the key. You may have to try repeatedly, or try pressing F5 and F6 repeatedly. – JAE] When successful, you’ll see a two-paragraph instruction that begins, “To specify additional SCSI or other mass storage devices.” Press
When the small window does appear, use the up-arrow to choose “Advanced Configuration and Power Interface (ACPI).” (It’s the third from the top of the list.)
Next, you may see that two-paragraph SCSI/mass storage instruction again. If so, press
MOUSE: Logitech. If you have a Logitech mouse, and an outdated version of the MouseWare software installed, you may receive the following error message on a blue screen at shutdown: STOP 0x000000D1, (0x0000002b, 0x00000002, 0x00000000, 0xEEEE1b01) IRQL_NOT_LESS_OR_EQUAL Kbdclass.sys. SOLUTION: Update the Logitech MouseWare software. (Reference & more information: MSKB 810980.)
VIDEO CARDS: Hercules 3D Prophet 4500 and all other video cards based on the Kyro II video chip. Causes restart and shutdown issues (or, in some cases, only restart issues) until the video adapter is removed. SOLUTION: New XP-specific drivers are now available from Hercules. At present, they remain uncertified (PowerVR, who makes the Kyro II chip, is working on that), but they reportedly work just fine. Download the Kyro II drivers here. (Tip from MS-MVP Don Lebow.)
USB Devices. If you have one or more USB devices attached to your computer, you may receive the following error message on a blue screen at shutdown: Stop 0x000000D1 (0x00000040, 0x00000002, 0x00000000, 0xfc96a9dc). SOLUTION: Upgrade to the latest Win XP service pack. (Reference & more information: MSKB 317326.)
USB: Keyboard or Mouse + Selective Suspend. Some USB input devices (such as a USB keyboard or mouse) do not support the Selective Suspend power management feature. When these devices are used with Selective Suspend turned on, the computer may hang during shutdown, or otherwise not shutdown correctly. WORK-AROUND: Disable power management for your USB hub: Open Device Manager (click Start, click Run, type DEVMGMT.MSC, click OK). Double-click to expand Universal Serial Bus Controllers. Double-click USB Root Hub. Click Power Management. Uncheck the box “Allow the computer to turn off this device to save power.” OK your way out. NOTE: Doing this may significantly reduce laptop battery life. (Reference & more information: MSKB 315664.)
USB: Lexar Media Combo Digital Film Reader (USB). There is a problem with the SAUSB.SYS file, apparently part of the Win98 SE driver set for this device, retained during an upgrade to Win XP. Deleting the file solved the problem. The newer version 4.3 SAUSB.SYS driver from Lexar’s Web site works perfectly, and does not cause a shutdown problem. (Tip from correspondent Eric Brown.) Though one correspondent reported that the even newer version 4.5 driver (SAUSBI.SYS) also can be used in Win XP , Lexar says this driver doesn’t work on XP. One correspondent has confirmed that this matches his experience in trying (unsuccessfully) to use 4.5 on both Widows 2000 and XP.
“STOP” ERROR MESSAGES AT SHUTDOWN
Some users, when attempting either to shutdown or restart Win XP, get an error message similar to the following: STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE
Stop Messages literally means that Windows has stopped. (Which isn’t the same as saying it has shutdown!) See Knowledge Base Links: STOP MESSAGES for much more information that the brief remarks below. Most Stop Messages indicate hardware issues; some are caused by troublesome software or a system service problem. The links page just mentioned provides a 10-step approach to troubleshooting STOP Messages in general, then itemized analysis on the most common of these. (STOP messages are identified by an 8-digit hexadecimal number, but also commonly written in a shorthand notation; e.g., a STOP 0x0000000A may also be written Stop 0xA.)
Here are a few that may affect Win XP shutdown and restart. Stop 0x9F and Stop 0x8E are two of the most common of these at shutdown, and generally point to a bad driver. Stop 0x7B on restarting means Win XP lost access to the system partition or boot volume during the startup process, due to a bad device driver, boot sector virus, resource conflict, boot volume corruption, or other problem listed here. Stop 0xC000021A can when on restart after a system administrator has modified permissions so that the SYSTEM account no longer has adequate permissions to access system files and folders.
MS-MVP Jim Pickering advises the following as one approach to these problems: Restart the computer. Press F8 during the restart and select “ Last Known Good Configuration.” If you catch the problem when it first occurs (meaning you likely have installed only one or two drivers or new service), this will return you to a previous working condition. System Restore provides an alternate approach, especially if you need to go back further than the last known good configuration, and Device Manager provides a tool for rolling back to an earlier driver.
SHUTDOWN WORKS, BUT IT’S REAL SLOW
If it appears that Win XP is not shutting down, give it some time. Some users report a minute or longer for shutdown to visibly start. Generally, this is a consequence of software that is running when shutdown is attempted. It also may have something to do with particular hardware. If you experience this problem, be sure to close all running programs before attempting shutdown and see if this solves your problem. If so, then you can determine, by trial and error, which program(s) are involved.
Newsgroup correspondent “Sarah” provided one specific solution for this. In Control Panel Administrative Tools Services, stop the Nvidia Driver Helper service. (You can also get this by launching SERVICES.MSC from a Run box.) Many other newsgroup participants quickly confirmed that this solved this “extremely slow shutdown” problem for them (it’s the most successful solution for this problem to date). According to correspondent Gan Ming Teik, downloading and installing the new version 23.11 Nvidia driver also solves this problem.
Correspondent Ron Spruell found that disabling the Terminal Services service reduced his shutdown time from over 2 minutes (hanging at the “Windows is shutting down” screen) to about 10 seconds. To disable Terminal Services, follow the steps in the prior paragraph for launching SERVICES.MSC. Please note that Terminal Services is required in Windows XP for running Remote Assistance, Fast User Switching, and (in XP Pro) Remote Desktop.
Correspondent Graeme J.W. Smith reported a more obscure cause of slow shutdown: In Win XP Professional, the Group Policy Editor has a security option to clear the pagefile at system shutdown. The same setting also forces the hibernation file to be wiped at shutdown. These processes take long enough that users may think that shutdown has hung. To change the setting, click Start Run, type GPEDIT.MSC, click OK. Drill down to Computer Configuration Windows Settings Security Settings Local Policies Security Options. In the right pane, find “Shutdown: Clear virtual memory pagefile.” NOTE: Since someone actually has to have set this policy, the problem will be pretty rare, but is worth mentioning. However, Forum participant “roadrunner” reported that the personal security app Privacy Eraser automatically enables “Clear virtual memory pagefile,” and, therefore, may be the cause of a slow shutdown.
The Gear Software Security Service (GEARSEC.EXE), which enables iTunes for Windows to read and burn CDs, has been reported by many users to cause Windows XP to hang at the “Windows is shutting down” screen for as long as 20-30 seconds. WORK-AROUND: Stop the service prior to shutdown. One way to to this (suggested by “Thornburgh”) is to create a batch file with the one line net stop gearsecurity. You can either launch this batch file manually, or (in Win XP Professional) use GPEDIT.MSC) to specify this batch file as the shutdown script (under Computer Configuration Windows Settings Scripts Shutdown). Gear Software’s forum has a thread on this issue here. (Tip from correspondent “Andy”)
MS-MVP Gary Thorn discovered that the Event Log can slow down Win XP shutdown. Disabling event logging removed the slowdown. If this works for you, then the real troubleshooting begins: finding out, by trial and error, what item that is being logged is causing the actual slowdown. (In Gary’s case, the Telephony service was causing the problem.) To disable the Event Log, launch the Services console as detailed in No. 2 above, and disable Event Log (right-click on Event Log, click Properties, under Startup Type select “Disabled”).
In a domain environment, don’t forget to check any logoff scripts you are pushing. These can be a source of slow or hanging shutdown processes. Site visitor Tony Barkdull, for example, found that an enforced logoff script caused show shutdown for laptops that were off-site. He solved it be creating a logoff script on the local machines that deletes the Active Directory logoff group policy after it runs so that the logoff scripts are absent while a user is off-site, but are repopulated when they return. — A related cause of slow shutdowns is offline synchronization of data, which is increasingly common with mobile computing, but is usually much more obvious to the end-user.
POWERDOWN ISSUES
“Powerdown issues” are quite distinctive from “shutdown issues.” I define a shutdown problem as one wherein Windows doesn’t make it at least to the “OK to shut off your computer” screen. If Windows gets that far, or farther, then it has shut down correctly. However, the computer may not powerdown correctly after that. This is a different problem, and I encourage people reporting these issues to make a clear distinction in their labeling.
When Windows XP won’t powerdown automatically, the APM/NT Legacy Power Node may not be enabled. To enable this, right-click on the My Computer icon, click Properties Hardware Device Manager View. Check the box labeled “Show Hidden Devices.” If it’s available on your computer, there will be a red X on the APM/NT Legacy Node. Try enabling it and see if this resolves the powerdown problem (Tip from Terri Stratton). Or, to check the other side of the APM/ACPI coin, open the Power Options applet in Control Panel. If there is an APM tab, make sure the “Enable Advanced Power Management Support” box is checked. (MSKB 313290)
This should resolve the powerdown issue in most cases. However, other factors can sometimes interfere with correct powerdown functioning. In that case, consider the following tips:
Try some of the solutions on my Shutdown & Restart Shortcuts page. If you really have a hardware inability to powerdown, these won’t solve it; but for some other underlying causes of powerdown failures, they just might.
If you change the default power settings in the BIOS, it can lead to a powerdown problem. Restoring all BIOS power settings to default will likely fix it. (Tip from Kelly Theriot)
Sometimes, not all appropriate Registry settings are made when you enable all the right power management settings in Windows. You can force the critical Registry setting with the “ShutNTdown” Registry patch. Please follow sensible Registry editing protocol. Backup your Registry before the change (or run System Restore to create a restore point). After installing it, test Windows shutdown. If the fix doesn’t work for you, remove it by restoring the Registry to its prior state. (For those who want more background information, the fix provided by this patch is based on information contained in MS Knowledge Base article 155117 for Windows NT 4.0.)
On some hardware, power management features simply don’t work right. This is exceedingly rare on Windows XP when compared to any earlier version of Windows but, on some machines, especially if no BIOS upgrade is available, there seems no conclusion to reach except, “Yes, you’re right, it doesn’t work, so don’t use that feature.” Accordingly, several correspondents have noted that their Win XP computers will not powerdown correctly unless they have Turn Off Monitor, Turn Off Hard Disks, and System Standby all set to “Never” in Control Panel Power Options. (Tip from Dan Mitchell & others)
How old is your power supply? Correspondent Andrew Walsh had a computer that wouldn’t power down after a Win XP shutdown until he replaced the power supply that was a few years old. Presto! His problem was gone.
Correspondent “Snake” restored powerdown functioning by disabling his CD-ROM’s AutoRun feature. The fastest way to do this is with the “Disable AutoRun” Registry patch that you can download here.
If you have Office XP installed, the culprit may be CTFMON.EXE. This module provides the Alternate Language Bar and provides text input service support for speech recognition, handwriting recognition, keyboard, translation, and other alternative user input technologies. When you close all Office programs, this module stays active. Removing it can cause serious problems with your Office XP products, but you can effectively disable it by setting the installation state to Not Available in Office XP Setup. This isn’t as easy as it sounds though — several steps are involved. For full instructions, plus more information on the file and its function, see What Is CTFMON and What Does It Do? (Tip from Jay Jones)
VIA Apollo Pro 133 motherboards have a “USB Keyboard support” BIOS setting that can interfere with proper power management function if it is enabled — especially with respect to preventing powerdown during attempted shutdown, and also preventing the computer from waking from Stand-by. SOLUTION: Disable it. This was originally reported on the Chaintech 6ATA2, and confirmed on other VIA Apollo Pro 133 boards. (Tips from “Zef,” The Netherlands, & Robert Lin)
Toshiba laptop (model not specified). Problems of Windows XP not powering off nor going into standyby were solved by uninstalling (then reinstalling) the Toshiba Power Saver software and Toshiba Hotkey for Display Devices. After doing this and a reboot, the problem was gone. (Tip from David Flitterman)
NEW PROBLEMS INTRODUCED BY SERVICE PACK 1 (SP1)
Some new shutdown and powerdown issues have arisen in Windows XP SP1. Here are the ones I know about:
HIBERNATION/STANDY PROBLEM WITH NERO SOFTWARE. If you have Nero CD-burning software (versions 5.0-5.5) installed on your computer, and invoke Standby or Hibernation modes more than once in a Windows session, the computer will hang on the “Preparing to...” screen and not go into Standby or Hibernation. SOLUTION: Uninstall Nero completely, and keep your eyes open for a new version of the program down the road. (Reference: MSKB 331506.)
WITH SP1, DON’T REMOVE SCSI ADAPTER WHILE IN STANDBY. Service Pack 1 for Windows XP introduced a new (but pleasingly rare) shutdown problem: If you remove certain kinds of SCSI adapter while the computer is in Standby, the computer may not shut down properly. There is a “hot fix” for this available from Microsoft. (Reference: MSKB 330172.)
SP1 + AMBIENT HAM MODEM + POSSIBLE IRQ ISSUE. Site visitor Mike Redman wrote that, after installing SP1, his computer would hang on the shutdown screen. Neither the mouse nor Ctrl+Alt+Del would respond. Either uninstalling SP1 or removing his Intel Ambient Ham 50.sys (unsigned driver) internal modem would solve the problem. FINAL SOLUTION: Moving the modem from PCI slot 4 to slot 5 and reinstalling the drivers. He wrote, ”This may be an IRQ problem which SP1 was supposed to fix.”
NEW PROBLEMS INTRODUCED BY SERVICE PACK 2 (SP2)
Some new issues have arisen in Windows XP SP2. Here are the ones I know about:
AUTOMATIC WINDOWS UPDATE INSTALLATION. Windows XP SP2 checks at shutdown for any Windows Updates have been downloaded and not installed, then offers to install them as part of the shutdown process. Understandably, this can cause a very slow shutdown on that one occassion and, if something goes wrong, can even hang shutdown completely. To see if your shutdown problem is caused by this issue, look for error 0x80248011 in any of the Windows Update log files, particularly %windir%\SoftwareDistribution\ReportingEvents.log. If present, this indicates a corrupt local metadata store for Windows Update. SOLUTION: Click Start, click Run, type SERVICES.MSC, click OK. Stop the Automatic Updates service. Rename the c:\Windows\SoftwareDistribution folder to c:\Windows\SoftwareDistribution.old. Restart the Automatic Updates service. (Tip from MS-MVP Bill Castner.)
REBOOT ON SHUTDOWN WITH HARDWARE-ENFORCE DATA EXECUTION PREVENTION. If your computer uses hardware-enforced DEP, as the 64-bit AMD processors do, and you installed hardware that requires the MPEGPORT.SYS driver, there is a conflict. At shutdown, the driver tries to run from the same memory space DEP monitors. A 0xFC Stop message occurs. If your computer is set to automatically reboot on a system failure, it will simply reboot instead. The solution is a new driver. Microsoft provides a work-around in MSKB 878474.
