Troubleshooting XP x64 Problems
This page is specific to problems experienced in 64-bit editions of XP. There are a number of 32-bit XP and Windows Server 2003 specific articles scattered throughout this site that also apply to x64 so these have been gathered together at the end of this page for your convenience.
 | List of limitations in 64-Bit Windows This article lists some limitations in 64-bit Windows.  |
 | Setup and installation considerations for Windows x64 Edition-based computers This article describes how the Microsoft Windows x64 Edition-based operating system installation process has changed from the Windows x86 installation process. | ||
 | A description of the x64-based versions of Windows Server 2003 and of Windows XP Professional x64 Edition This article lists and briefly describes Microsoft Windows XP Professional x64 Edition and the x64-based versions of Microsoft Windows Server 2003. Windows XP Professional x64 Edition and the x64-based versions of Windows Server 2003 support Advanced Micro Devices (AMD) AMD64 processors and Intel Extended Memory 64 Technology (EM64T) processors. The underlying architecture of these operating systems is based on 64-bit extensions to the standard x86 instruction set. Therefore, you can run 32-bit and 64-bit programs on x64-processor-based computers that are running Windows XP Professional x64 Edition or an x64-based version of Windows Server 2003. | ||
| A description of the driver support in x64-based versions of Windows Server 2003 and in Windows XP Professional x64 Edition x64-based versions of Microsoft Windows Server 2003 and Microsoft Windows XP Professional x64 Edition require 64-bit device drivers for hardware devices and peripherals. The requirement for 64-bit drivers applies to kernel mode components and to user mode components. |  |  |
 | How to use the 32-bit Control Panel items on a computer that is running an x64-based version of Windows Server 2003 or of Windows XP The x64-based versions of Microsoft Windows Server 2003 and of Microsoft Windows XP are designed to use the 64-bit Control Panel items. However, these operating systems do have 32-bit Control Panel items available for use. This article tells how to use the 32-bit Control Panel items on a computer that is running an x64-based version of Windows Server 2003 or of Windows XP. | ||
| An update is available that adds support for parallel port Zip drives in Windows XP Professional x64 Edition This article describes an update that adds support for older Iomega parallel port Zip drives in Microsoft Windows XP Professional x64 Edition. | ||
| You cannot transfer files and settings from a computer that is running a 32-bit edition of Windows XP to a computer that is running Windows XP Professional x64 Edition When you use the File and Settings Transfer Wizard on a computer that is running a 32-bit edition of Microsoft Windows XP to transfer your files and settings, and then you try to use the File and Settings Transfer Wizard on a computer that is running Microsoft Windows XP Professional x64 Edition to restore the files and settings that you copied earlier, you may receive the following error message: Your migration store was created with a previous version of File and Settings Transfer Wizard. Please collect your settings using the current version of the Files and Settings Transfer Wizard. It is available on the Windows XP x64 edition CD under Perform Additional Tasks. You can also create a wizard disk by running the wizard on your Windows XP x64 Edition computer. | ||
| You may receive an error message when you try to install a device driver on a computer that is running an x64-based version of Windows When you try to install a device driver on a computer that is running an x64-based version of Microsoft Windows, you may receive the following error message: The specified location does not contain a compatible software driver for your device. If the location contains a driver, make sure it is designed to work with the Windows x64 Edition operating system. | ||
| When you perform a custom installation of Windows Defender on x64-based versions of Windows, Windows Defender does not work correctly When you perform a custom installation of Microsoft Windows Defender or later versions on x64-based versions of Microsoft Windows, Windows Defender does not work correctly. | | |
| "WINNT32.EXE is not a valid Win32 application" error message when you try to run the Winnt32.exe program from the installation CD for x64-based versions of Windows Server 2003 and Windows XP Professional x64 Edition Assume the following scenario: You try to install an x64-based version of Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition on a computer that is already running a 32-bit version of Windows. You do this by running the Winnt32.exe program from the x64-based installation CD. In this scenario, you receive the following error message: CD_drive:\AMD64\WINNT32.EXE is not a valid Win32 application. | ||
| Processor and memory capabilities of Windows XP Professional x64 Edition and of the x64-based versions of Windows Server 2003 This article contains information about the capabilities of Microsoft Windows XP Professional x64 Edition and of the x64-based versions of Microsoft Windows Server 2003. To illustrate this information, this article compares the support that is provided by the x64-based versions to the support that is provided by the 32-bit versions of Windows Server 2003 and of Windows XP Professional in the following areas:
| ||
| Registry changes in x64-based versions of Windows Server 2003 and in Windows XP Professional x64 Edition This article describes some of the registry changes that have been made in x64-based versions of Microsoft Windows Server 2003 and Microsoft Windows XP Professional x64 Edition. Additionally, this article describes how the Windows x64 Edition operating system stores registry information for 32-bit programs and 64-bit programs. | ||
| How to determine the type of processor that your Windows Server 2003 x64-based computer or your Windows XP Professional x64-based computer uses This article describes how to determine the processor type of a computer that is running any one of the following operating systems:
| ||
| How to add processors to a computer that is running an x64-based version of Windows Server 2003 or of Windows XP Professional x64 Edition This article discusses how to add more processors to a computer that is running one of the following operating systems:
| | |
| An MMC snap-in for a program is not available in the Add Standalone Snap-in dialog box in an x64-based version of Windows You install a program that includes a Microsoft Management Console (MMC) snap-in on a computer that is running an x64-based version of Microsoft Windows. In this scenario, the MMC snap-in is not available in the Add Standalone Snap-in dialog box. | ||
| The Microsoft Speech Server 2004 Setup program cannot locate Internet Information Services on a Windows x64 Edition-based computer When you try to install Microsoft Speech Server 2004 on an x64 Edition-based version of Microsoft Windows XP or Microsoft Windows Server 2003, the Speech Server 2004 Setup program verifies all the prerequisites that are required to install Speech Engine Services. However, during the installation process, the Setup program conducts an additional prerequisite verification. During this verification, the Setup program cannot locate Microsoft Internet Information Services (IIS). | ||
| When you try to shut down or restart a computer that is running an x64-based version of Windows, the computer may stop responding When you try to shut down or restart a computer that is running an x64-based version of Microsoft Windows, the computer may stop responding. You do not receive an error message. However, you may experience one of the following symptoms:
| ||
| InstallShield installs a 32-bit program incorrectly in x64-based versions of Windows When you use InstallShield to install a 32-bit program on an x64-based version of Microsoft Windows, the program is installed incorrectly. Also, after you restart the computer, the program does not run correctly. However, the program may run correctly after you restart the computer again. | ||
| You may receive error messages when you try to use the Spelling tool in Outlook Express in the x64-based versions of Windows Server 2003 and in Windows XP Professional x64 Edition You install Microsoft Office on a computer that is running an x64-based version of Microsoft Windows Server 2003 or on a computer that is running Microsoft Windows XP Professional x64 Edition. When you try to use the Spelling tool to check the spelling of an e-mail message in Microsoft Outlook Express, you may receive the following error messages: Error message 1 An error occurred while spelling was being checked. Error message 2 Send Mail failed to send message. | | |
| How to remove Windows XP Professional x64 Edition from a computer that is also running a 32-bit edition of Windows XP After you install Windows XP Professional x64 Edition on a computer that is running a 32-bit edition of Windows XP, you may want to remove Windows XP Professional x64 Edition and continue to run the 32-bit edition of Windows XP. This article describes how to remove Microsoft Windows XP Professional x64 Edition from a computer that is also running a 32-bit Edition of Microsoft Windows XP. Note: This article applies only to a situation where you have installed Windows XP Professional x64 Edition on a separate partition from the 32-bit edition of Windows XP. | ||
| Description of the new Setup program behaviour in Windows x64-based editions and in Windows Server 2003 Service Pack 1 With the introduction of Microsoft Windows x64-based editions and Microsoft Windows Server 2003 Service Pack 1 (SP1), the Setup program now looks for an existing version of the Ntldr file and the Ntdetect.com file on the computer during an operating system installation. | ||
| A 32-bit IPX Winsock application generates a WSAEINVAL error in the x64 editions of Windows Server 2003 and Windows XP Professional On a computer that is running Microsoft Windows Server 2003 x64 Edition or Microsoft Windows XP Professional x64 Edition, a 32-bit Internetwork Packet Exchange (IPX) Windows Sockets (Winsock) application may not work. Instead, the IPX Winsock application generates a WSAEINVAL error. | ||
| You are prompted to choose between the 64-bit MMC snap-in and the 32-bit MMC snap-in when you try to open a MMC snap-in on a computer that is running an x64-based version of Windows Server 2003 or Windows XP Professional x64 Edition When you try to open a Microsoft Management Console (MMC) snap-in on a computer that is running an x64-based version of Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition, a dialog box is displayed that prompts you to choose between the 64-bit MMC snap-in and the 32-bit MMC snap-in. This behaviour occurs when both the 64-bit MMC snap-in and the 32-bit MMC snap-in exist for the same task on the same computer that is running an x64-based version of Windows Server 2003 or Windows XP Professional x64 Edition. In this case, you must choose the correct snap-in for the task that you want to perform, and then click OK. | ||
| You receive a "this system does not support a local APIC" error message when you try to install an x64-based version of Windows Server 2003 or Windows XP Professional x64 Edition When you run the Setup program to install an x64-based version of Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition, you may receive the following error message: Attempting to load an x86-64 operating system, however this system does not support a local APIC. Check the system's firmware settings. In particular, ensure that the firmware has enabled the APIC on this system. If the firmware does not have an APIC setting, please contact the system manufacturer for a firmware update to enable the local APIC. When you press a key, your computer will restart. After your computer restarts, the Setup program runs again, and you receive the same error message. | | |
| Programs become unstable or do not start after you install an x64-based version of Windows on the same partition as a 32-bit version of Windows After you install an x64-based version of Microsoft Windows on a computer that also has a 32-bit version of Windows installed, you may experience the following symptoms:
| ||
| When a hardware malfunction occurs on a computer that is running an x64 Edition version of Windows, you do not receive a Stop error message, and no memory dump file is generated On a computer that is running an x64 Edition version of Microsoft Windows, you do not receive a Stop error message when a hardware malfunction occurs. Additionally, no memory dump file (Memory.dmp) is generated. Instead, the computer just stops responding (hangs). Without the Stop error parameters or the memory dump file, you may not be able to diagnose the cause of the hardware malfunction. | ||
| Some Windows Explorer extensions and some Control Panel items are not displayed on computers that are running an x64-based version of Windows When you log on to a computer that is running an x64-based version of Microsoft Windows Server 2003 or to a computer that is running Microsoft Windows XP Professional x64 Edition or to a computer that is running an x64-based version of Windows Vista, you may notice that some program features that are available in Windows 32-bit operating systems are not available on your computer that is running an x64-based version of Windows. Specifically, you may notice the following symptoms on your computer that is running an x64-based version of Windows:
| ||
| Event ID 50, 26, or 57 is logged when you use HP SecurePath on a computer that is running Windows Server 2003 Service Pack 1 (SP1) or an x64 edition of Windows You use Hewlett-Packard (HP) SecurePath on a computer that is running Microsoft Windows Server 2003 Service Pack 1 (SP1) or an x64 edition of Windows. In this situation, one or more of the following event IDs is logged in the System log: Event Type: Warning Event Source: Ntfs Event Category: None Event ID: 50 Time: Date Time: Time User: N/A Computer: Computer_Name Description: {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. For more information, see Help and Support Center at http://support.microsoft.com. Data: 0000: 00040004 00520002 00000000 80040032 0010: 00000000 c000003c 00000000 00000000 0020: 00000000 00000000 c000003c | ||
| Errors may occur when you run a 32-bit program on a computer that is running a 64-bit version of Windows Server 2003 or on a computer that is running Windows XP Professional x64 Edition Consider the following scenario. You have a computer that is running a 64-bit version of Microsoft Windows Server 2003 or a computer that is running Microsoft Windows XP Professional x64 Edition. You run a 32-bit program that has the /LARGEADDRESSAWARE switch enabled. You run this program in a Windows on Windows 64 (WOW64) environment. When this scenario occurs, you may experience one or more of the following symptoms. Symptom 1 An access violation may occur when you run the program. Symptom 2 An access violation may occur when the program calls a CreateWindow API that has string-window class name specified. Symptom 3 A hooked function may not be called correctly. This may cause various graphical user interface (GUI) operations not to work. Additionally, an access violation may occur. Symptom 4 The MessageBox API may not work correctly. This may cause GUI items that use the MessageBox API not to work correctly. | | |
| The Intel High Definition audio functionality unexpectedly quits working in Windows Server 2003 Service Pack 1 or Windows XP Professional x64 Edition If the following conditions are true, the computer Intel High Definition audio functionality unexpectedly quits working:
| ||
| You receive an error message if you try to run a 32-bit Windows Setup program while you are running a Windows x64 Edition-based operating system If you try to run Winnt32.exe from a 32-bit Microsoft Windows operating system installation CD while you are running a Microsoft Windows x64 Edition-based operating system, you receive the following error message: Setup cannot continue because the version of Windows on your computer is newer than the version on the CD. Warning: If you decide to delete the newer version of Windows that is currently installed on your computer, the files and settings cannot be recovered. | ||
| You cannot obtain an IP address from a DHCP server after you open a PPP connection on a computer that is running Windows Server 2003 SP1 or an x64 edition of Windows After you open a Point-to-Point Protocol (PPP) connection on a computer that is running Microsoft Windows Server 2003 Service Pack 1 (SP1) or an x64 edition of Windows, you cannot obtain an IP address from a Dynamic Host Configuration Protocol (DHCP) server. | ||
| You may lose processor power management features when you update the AMD processor driver on a multiprocessor computer that is running an x64-based version of Windows Server 2003 or Windows XP When you try to update the Advanced Micro Devices (AMD) processor driver for a computer that is running an x64-based version of Microsoft Windows Server 2003 or Microsoft Windows XP, the original Microsoft in-box driver is installed. Therefore, you may lose some processor power management features if you are using a multiprocessor computer. | ||
| A custom drive icon and a drive label may not appear on a computer that is running Windows Server 2003 or Windows XP Professional x64 Edition You have connected a removable media card reader device to a computer that is running Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition. However, when you set a custom drive icon and a drive label for the device drive, the custom drive icon and the drive label may not appear. | | |
| You may be prompted to restart the computer when you upgrade a computer that is running an x64-based version of Windows Server 2003 or of Windows XP from a uniprocessor to a multiprocessor configuration When you add or change logical or physical processors to upgrade a computer that is running an x64-based version of Microsoft Windows Server 2003 or of Microsoft Windows XP from a uniprocessor to a multiprocessor configuration, you experience the following symptoms:
If you remove or change logical or physical processors to change the computer from a multiprocessor to a uniprocessor configuration and then start the computer, you may be prompted to restart the computer. | ||
| The Data Execution Prevention tab in System Properties does not show hardware-based DEP support information in x64 or Itanium-based versions of Windows Server 2003 or Windows XP Consider the following scenario. You are running an x64 or Itanium-based version of Microsoft Windows Server 2003 or Microsoft Windows XP. You click the Data Execution Prevention tab in the Performance Options dialog box. You cannot see that the computer processor or processors support hardware-based Data Execution Prevention (DEP). | ||
| You cannot open the Active Directory Users and Computers MMC snap-in from within the Active Directory Domains and Trusts MMC snap-in on a computer that is running Windows XP Professional x64 Edition You install the Microsoft Windows Server 2003 Administration Tools Pack on a computer that is running Microsoft Windows XP Professional x64 Edition. When you try to start the Active Directory Users and Computers Microsoft Management Console (MMC) snap-in from within the Active Directory Domains and Trusts MMC snap-in, you may receive the following error message: MMC cannot open the file DriveLetter:\WINDOWS\system32\dsa.msc. This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient rights to the file. | ||
| How to install the Windows Server 2003 Service Pack 1 Administration Tools Pack in Windows Server 2003 x64 Edition The Microsoft Windows Server 2003 Service Pack 1 Administration Tools Pack (Wadminpack.msi) provides server management tools that let administrators remotely manage servers. These tools let administrators remotely manage servers that are running Windows Server 2003 and servers that are running Microsoft Windows 2000 Server. You can install the Administration Tools Pack on a computer that is running Microsoft Windows XP Professional x64 Edition. However, you must install the Administration Tools Pack from a Windows Server 2003 x64 Edition CD. Note: 32-bit and 64-bit Windows Server 2003 Administration tools can be installed on 32-bit and 64-bit XP systems respectively. | ||
| Updated Remote Installation Service functionality in Windows Server 2003 Service Pack 1 and in x64-based versions of Windows Server 2003 This article describes the new Remote Installation Services (RIS) changes that are made available on a computer that is running a 64-bit version of Microsoft Windows Server 2003 Service Pack 1 (SP1) and how to deploy 64-bit operating system images in an enterprise environment. Additionally, this article describes the new features and functionality of the Risetup.exe and Riprep.exe tools, the Client Installation Wizard, and the x8664.osc screen. Note: This article also applies to Microsoft Windows XP Professional x64 Edition. | | |
| Network traffic is interrupted when you hot swap a network adapter in Windows Server 2003 or in Windows XP Professional x64 Edition When you hot swap a network adapter or a virtual network adapter, you experience the following symptoms:
Note When you remove a device and then install a replacement device of the same model in the same slot while the computer is running, this process is known as hot swapping. The operating system automatically recognizes the replacement device. When you add Virtual Local Area Networks (VLANS) to network devices, you experience the following symptoms:
| ||
| Corrupted text appears in the End User License Agreement window during the installation of Windows Server 2003 or Windows XP Professional x64 Edition When you install either of the following operating systems, corrupted text may appear in the End User License Agreement (EULA) window:
| ||
| Event 10016 may be logged in the System log on a computer that is running Windows XP Professional x64 Edition On a computer that is running Microsoft Windows XP Professional x64 Edition, events that are similar to the following may be logged in the System log: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10016 Date: Date Time: Time User: NT AUTHORITY\LOCAL SERVICE Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {AppGUID} to the user User_Name SID User_SID. This security permission can be modified using the Component Services administrative tool. Event Type: Error Event Source: DCOM Event Category: None Event ID: 10016 Date: Date Time: Time User: Network services Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {AppGUID} to the user User_Name SID User_SID. This security permission can be modified using the Component Services administrative tool. | ||
| A slow removable storage device may be very slow to respond when multiple read and write operations are performed against the device in Windows Server 2003 or in Windows XP x64 Edition Consider the following scenario:
| ||
| 64-bit versions of Windows do not support 16-bit components, 16-bit processes, or 16-bit applications The x64-based versions of the Microsoft Windows Server 2003 operating systems and Microsoft Windows XP Professional x64 Edition do not support 16-bit programs, 16-bit processes, or 16-bit components. However, these 64-bit versions of Windows may recognize some 16-bit installers and automatically convert the 16-bit installer to a 32-bit installer. Note: The only solution this article proposes for running 16-bit components is to dual boot with a 32-bit XP on a separate disk volume or separate physical hard disk, which is a bit of stretch considering that the free Virtual PC 2007 supports 64-bit hosts. | | |
| Programs that use the QueryPerformanceCounter function may perform poorly in Windows Server 2003 and in Windows XP In Microsoft Windows Server 2003 and in Microsoft Windows XP, a program that uses the QueryPerformanceCounter function to query system time may perform poorly. For example, if you run the ping command at the command prompt, you may receive low or incorrect latency values. This problem occurs on computers that are running an x64-based version of Windows or an x86-based (32-bit) version of Windows. This problem occurs when the computer has the AMD Cool'n'Quiet technology enabled in the BIOS. | ||
| How to find a compatible printer driver for a computer that is running a 64-bit version of Windows This article describes how to find a compatible printer driver for your computer that is running a 64-bit version of Microsoft Windows. The information in this article may be useful if you cannot obtain a WHQL signed printer driver from the printer manufacturer or from the Microsoft Windows Update Web site. This article also provides a method that you can use if you need a printer driver for a printer that is not supported on your computer that is running a 64-bit version of Windows. Note: To print from a computer that is running a 64-bit version of Windows, you must have a 64-bit printer driver. You cannot use a 32-bit printer driver on a computer that is running a 64-bit version of Windows. | ||
| How to switch between the 32-bit versions of ASP.NET 1.1 and the 64-bit version of ASP.NET 2.0 on a 64-bit version of Windows This article discusses how to switch between the 32-bit version of Microsoft ASP.NET 1.1 and both the 32-bit version and the 64-bit version of ASP.NET 2.0 on a 64-bit version of Microsoft Windows. When you install both versions of ASP.NET, you may receive error messages if you do not perform steps to enable each ASP.NET environment to run in Microsoft Internet Information Services (IIS) 6.0. For example, when ASP.NET is not set up correctly, you may receive the following error message from a Web page: Service Unavailable | ||
| You receive a "Cannot install on a 64 bit machine" error message when you try to install Windows Services for UNIX on a computer that is running a 64-bit operating system Depending on the version of Microsoft Windows Services for UNIX that you are trying to install, you may receive an error similar to the following when you try to install Windows Services for UNIX on a computer that is running a 64-bit operating system: Cannot install on a 64 bit machine See Note here. | ||
| You receive an error message when you add a driver for a mass storage device during setup of Windows Server 2003 or of Windows XP When you set up Microsoft Windows Server 2003 or Microsoft Windows XP, you may want to install an additional mass storage device driver. After you press F6 and then specify the driver, you receive one of the following error messages: The device associated with the following device driver will not work correctly on this computer: Path\Device_Driver.sys. The device driver is only compatible with the 32-bit version of Windows. The device driver may be required to complete Windows Setup. Please contact the device manufacturer to obtain drivers compatible with the 64-bit version of Windows The file \AMD64\Driver_Name is corrupted. Press any key. This article applies to:
| | |
| Comparison of 32-bit and 64-bit memory architecture for 64-bit editions of Windows XP and Windows Server 2003 In the following table, the increased maximum resources of computers that are based on 64-bit versions of Windows and the 64-bit Intel processor are compared with existing 32-bit resource maximums. Architectural component 64-bit Windows 32-bit Windows Virtual memory 16 terabytes 4 GB Paging file size 512 terabytes 16 terabytes Hyperspace 8 GB 4 MB Paged pool 128 GB 470 MB Non-paged pool 128 GB 256 MB System cache 1 terabyte 1 GB System PTEs 128 GB 660 MB | ||
| Some custom printer properties may be unavailable in a 64-bit version of Windows Server 2003 or Windows XP When you connect a printer to a computer that is running a 64-bit version of Microsoft Windows Server 2003 or Microsoft Windows XP, some custom printer properties may be unavailable. Because of this problem, you may experience one or more of the following symptoms:
| ||
| The Microsoft Distributed Transaction Coordinator service must run under the NT AUTHORITY\NetworkService Windows account in Windows Server 2003 and in Windows XP This article discusses the Microsoft Windows account that the Microsoft Distributed Transaction Coordinator (MSDTC) service must run under in Microsoft Windows Server 2003 and in Microsoft Windows XP. This article applies to:
| ||
| A 32-bit program may not print colors correctly when it is running on a 64-bit version of Windows Server 2003 or on a 64-bit version of Windows XP A 32-bit program may not print colors correctly when you print a file on a computer that is running a 64-bit version of Microsoft Windows Server 2003 or a 64-bit version of Microsoft Windows XP. | ||
| The Windows XP "Windows and Buttons" Settings Are Not Available for the 64-Bit Versions On the Appearance tab in the Display Properties dialog box, only Classic Windows is listed in the Windows and Buttons drop-down list; Windows XP Style is missing from the list. | | |
| How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP The 64-bit versions of Microsoft Windows Server 2003 and Microsoft Windows XP can support more RAM than the 32-bit versions of these products. When lots of memory is added to a computer, a paging file may not be required. When you use the Pages/sec counter to measure paging file use, the value that is returned may not be accurate. To obtain an accurate measurement of paging file use, you must also use other performance counters. You can use System Monitor measurements to calculate the size of the paging file that your computer requires. Windows Server 2003 Domain Controllers are not supported without a configured pagefile. Because the algorithm the LSASS database cache depends on the "transition pages repurposed/second" perfmon counter, a pagefile is required to make sure that the database cache is capable to release memory if memory is requested by other services or applications. | ||
| Access Violation Occurs When a Program Makes System Calls by Using Software Pipelining Optimization on Windows XP 64-Bit Edition When a program makes operating system calls (such as InvalidateRect), the program may generate an access violation and stop working. This problem may occur if the program uses software pipeline optimizations. | ||
| Program in the RUN Key Does Not Run at Logon A 32-bit program that is listed in the following registry key may not run at logon: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\ Windows\CurrentVersion\RUN Note: This article is for Microsoft Windows XP Professional x64 Edition. | ||
| You may receive an error message when you open a "Mini Kernel Dump" file that was generated by a 64-bit version of Windows Server 2003 or Windows XP Professional You open a "Mini Kernel Dump" file that was generated by one of the following operating systems:
Loading Dump File File_Name Mini Kernel Dump does not contain enough information to be debugged Could not open dump file File_Name, HRESULT 0x80004005 | ||
| Characters for some languages do not work correctly when you type them in a 64-bit program on a computer that is running a 64-bit version of Windows XP, Windows Server 2003 Characters for some languages do not work correctly when you try to type them in a 64-bit program on a computer that is running a 64-bit version of Microsoft Windows XP, Microsoft Windows Server 2003. For example, when you use an East Asian language Input Method Editor (IME) for your default keyboard layout, you cannot type East Asian language characters in a 64-bit program. This problem can occur when you use the 64-bit versions of the following programs:
| | |
| You cannot install 16-bit applications on Windows XP for 64-bit platforms When you attempt to install a 16-bit application on a computer that runs Windows XP for 64-bit platforms, you may not be able to do so, and you may receive one of the following error messages: Install.exe is not a valid win32 application. Setup.exe is not a valid win32 application. | ||
| Failure in initializing the telnet session. Shell process may not have been launched. When you try to use the Telnet client to connect to a Windows XP 64-Bit Professional computer that is running the Telnet service, you may receive the following error message: Failure in initializing the telnet session. Shell process may not have been launched. Telnet Server has closed the connection. Connection to host lost. | ||
| An OpenGL Program May Cause an Access Violation in Windows XP 64-Bit Edition If you run an OpenGL-based program in Windows XP 64-Bit Edition, you may receive an error message that describes an access violation. | ||
| The "FAT32" Option Is Unavailable in Disk Management When you create a partition in Disk Management, the file allocation table (FAT)32 option is unavailable in the File System menu. The only option that is available is the NTFS file system option. | ||
| How to Disable the Visual Notification Option in a 64-bit Version of Windows XP This article describes how to disable the Visual Notification option in a 64-bit version of Microsoft Windows XP. | | |
| Setup Stops Responding Upon Restart After You Install Windows XP to a Partition on an IA64 Computer When you install Windows XP to a partition on an IA64 computer that uses the GUID partition table (GPT) partitioning scheme, and you then restart the computer, the Windows XP Setup program may stop responding. | ||
| Cannot See Contents of a CD-ROM from the Extensible Firmware Interface Shell with DIR or LS Commands When you run the DIR or LS command on the contents of your CD-ROM drive from the Extensible Firmware Interface shell, the contents of the CD-ROM may not be displayed. Note: This article applies to Microsoft Windows XP Professional x64 Edition | ||
| An external monitor does not work when you connect it to a DVI port on a docking station in Windows XP Professional x64 Edition On a portable computer that is running Microsoft Windows XP Professional x64 Edition, an external monitor does not work when you connect it to a DVI port on a docking station. | ||
| A computer that is running the x64 edition of Windows Server 2003 or of Windows XP stops responding after you install the 914784 update and a product that uses hardware-assisted virtualization Consider the following scenario:
| ||
| Error message when you call the WTSQueryUserToken API function in a 32-bit application or a Windows Service that is running on an x64-based Windows system: "ERROR_INSUFFICIENT_BUFFER" Consider the following scenario. A 32-bit application or a Microsoft Windows Service is running on an x64-based Windows system. The 32-bit application or the Microsoft Windows Service has appropriate permissions. The 32-bit application or the Windows Service makes a call to the WTSQueryUserToken API function. In this scenario, the call fails. Additionally, the GetLastError API function returns the following Windows error message: ERROR_INSUFFICIENT_BUFFER The error code indicates that the data area that is passed to the system call is too small. | | |
| The WMI registry provider does not return the correct registry data for 32-bit programs on a computer that is running a 64-bit version of Windows Server 2003 or Windows XP Professional x64 Edition Consider the following scenario. You use a computer that is running a 64-bit version of Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition. You use the Windows Management Instrumentation (WMI) registry provider to query registry data for 32-bit programs. This data is located under the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node In this scenario, the WMI registry provider does not return the correct registry data. | ||
| The Volume Shadow Copy Service cannot create shadow copies on a computer that is running an x64-based version of Windows Server 2003 and a 32-bit version of SQL Server 2000 When you try to create shadow copies of local hard disks or of system state data, the Volume Shadow Copy Service cannot create the shadow copies. This problem occurs on a computer that hosts a server cluster (virtual server) and that is running the following software:
Volume shadow copy creation: Attempt 1. Timeout before function completed Error returned while creating the volume shadow copy: 0xffffffff. Error returned while creating the volume shadow copy: ffffffff Aborting Backup. If you try to run the Vssadmin.exe command-line tool, the tool stops responding and does not list the MSDE writer. Additionally, the Application log file may contain entries that resemble the following: Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize. hr = 0x80004005. SQLSTATE: 08001, Native Error: 17 Error state: 1, Severity: 16 Source: Microsoft OLE DB Provider for SQL Server Error message: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| After a COM application handles an access violation on a Windows Server 2003-based computer or on a Windows XP Professional x64 Edition-based computer, the COM application stops responding Consider the following scenario:
| ||
| When you use a 32-bit program to print a document from an x64-based version of Windows, the document may be printed incorrectly You are using a 32-bit program to print a document from an x64-based version of Microsoft Windows. When you select the option to print output that is black and white, the document may be printed incorrectly. For example, the output may be black instead of greyscale (shades of gray). | ||
| On an x64-based version of Windows, two instances of the print properties dialog box open, or Word stops responding when you try to access the printer properties, and you cannot print Consider the following scenario. You run a 32-bit program on a computer that is running one of the following operating systems:
In this scenario, two instances of the printer Properties dialog box open. Then, if you make changes in one of the dialog boxes and then click OK, the program may stop responding (hang) for about 10 seconds. Then, the second dialog box may stop responding. Additionally, when you click the X on the title bar to close the printer Properties dialog box, you receive the following error message: End Program - program This Program is not responding. When you click End Now, the Print dialog box appears, and you can access the program. However, you cannot print. Symptom 2 Consider the following scenario. You run Microsoft Word on a computer that is running one of the following operating systems:
In this scenario, Word may stop responding (hang). When you try to close Word, you receive the following error message: You cannot close Microsoft Office Word because a dialog box is open. Click OK, switch to Word, and then close the dialog box. | | |
| Recording quality is poor when you use a USB microphone on a Windows Server 2003-based computer that has 4 GB of RAM or more You record audio by using a USB microphone on a computer that is running Microsoft Windows Server 2003 or that is running Microsoft Windows XP Professional x64 Edition. However, you find that the quality of the recording is poor. For example, there may be gaps or pauses in the recording. This problem occurs on a computer that is using 4 gigabytes (GB) of RAM or more. | ||
| A console application may stop responding when you start it on a computer that is running Windows Server 2003 or Windows XP Professional x64 Edition On a computer that is running Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition, a console application may stop responding soon after you start it. When this problem occurs, the application process appears in Task Manager. However, you cannot view the application's window. Usually, this problem occurs in the following scenario:
| ||
| Programs that request lots of contiguous memory may fail after you install security update 921883 (MS06-040) on a Windows Server 2003 Service Pack 1-based computer or a Windows XP Professional x64 Edition-based computer Programs that request lots of contiguous memory, such as one gigabyte or more, may fail with an unexpected error after you install security update 921883 on a computer that is running an x64-based version of Microsoft Windows Server 2003, Microsoft Windows Server 2003 with Service Pack 1 (SP1), or Microsoft Windows XP Professional x64 Edition. This problem only affects 32-bit programs. Native 64-bit programs are not affected. | ||
| The heavy use of Winsock programs may exhaust the system's non-paged pool memory in Windows Server 2003 Under certain circumstances in Microsoft Windows Server 2003, the heavy use of Winsock programs may exhaust the system's non-paged pool memory. This behavior is likely to occur if the Winsock program is dealing with both Out-of-Band (MSG_OOB) traffic and standard TCP traffic. In this situation, you may experience various error messages and poor performance. Additionally, the system may stop responding (hang). Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| A Windows Server 2003-based or Windows XP-based computer that is using an AMD processor may stop responding A Microsoft Windows Server 2003-based or Microsoft Windows XP-based computer that is using a dual core or multiprocessor Advanced Micro Devices (AMD) processor that supports ACPI processor performance states (AMD PowerNow!) may stop responding. This problem is most likely to occur when you run a video-intensive program. However, this problem can occur whenever there is a processor performance state change. | | |
| The Volume Shadow Copy Service may leak private bytes and virtual memory when you use the service to take frequent snapshots in Windows Server 2003 or in Windows XP The Volume Shadow Copy Service (VSS) may leak private bytes and virtual memory when you use the service to take frequent snapshots in Windows Server 2003 or in Windows XP. To view the leaks in System Monitor, use the following performance counters under the Process object:
Windows XP Service Pack 2 must be the 32-bit edition because no SP2 existed at the time of writing for x64 XP. | ||
| Error message on a Windows Server 2003-based computer: "STOP: 0x000000CA (parameter1, parameter2, parameter3, parameter4) PNP_DETECTED_FATAL_ERROR On a Microsoft Windows Server 2003-based computer, you may receive an error message that resembles the following: *** STOP: 0x000000CA (parameter1, parameter2, parameter3, parameter4) PNP_DETECTED_FATAL_ERROR You may notice this problem on computers that have native PCI-Express (PCI-E) support enabled in the basic input/output system (BIOS). Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| Windows XP Installation Uses Entire 3-Gigabyte Partition When you install Windows XP on an IA-64 partition that has 3 gigabytes (GB) or less of space, Windows XP may fill the entire partition. | ||
| A hotfix is available that adds support for crash dump file generation on a Windows Server 2003-based computer that is using iSCSI Boot Initiator 2.05 This article describes a hotfix that is available for a Microsoft Windows Server 2003-based computer that is using Microsoft iSCSI Boot Initiator 2.05. This hotfix adds support for crash dump file generation. Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| You receive bad data or an error message when you perform a WMI query against a Windows Driver Model kernel provider in Windows Server 2003 In Microsoft Windows Server 2003, you perform a Windows Management Instrumentation (WMI) query against a Windows Driver Model (WDM) kernel provider. If this query uses an embedded class, you may experience either of the following symptoms:
| | |
| Event ID 49 is logged when you restart a Windows Server 2003-based computer that is using an iSCSI Boot Initiator 2.03 boot solution: "Configuring the Page file for crash dump failed" When you restart a Microsoft Windows Server 2003-based computer that is using a Microsoft iSCSI Boot Initiator 2.03 boot solution, an event is logged in the System event log that resembles the following: Event ID: 49 Source: FTDISK Description: "Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that it is large enough to contain all physical memory." Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| e-mail program stops responding when you send e-mail that has an attachment in Windows Server 2003 When you use Microsoft Collaboration Data Objects for Windows (CDOSYS) in Microsoft Windows Server 2003 to send an e-mail message that has an attachment, the e-mail program stops responding. Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| When you print a document in Word or in PowerPoint on a computer that is running a 64-bit version of Windows, Word or PowerPoint may stop responding You try to print a document in Microsoft Word or in Microsoft PowerPoint on a computer that is running a 64-bit version of Microsoft Windows. After you do this, Word or PowerPoint may stop responding. | ||
| A document that uses a mix of vertical and horizontal fonts does not print correctly on a PostScript printer in Windows Server 2003 SP1 Consider the following scenario:
Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| An "event ID 516" audit record may be incorrectly logged when an access attempt to a named pipe occurs in Windows Server 2003 or in Windows XP The following audit record may be incorrectly logged in the local Security log in Microsoft Windows Server 2003 or in Microsoft Windows XP: EventID 516 Internal resources allocated for the queuing of audit messages have been exhausted, leading to the loss of some audits. Number of audit messages discarded: 1 This symptom may occur when the following conditions are true:
| | |
| A disconnected network adapter appears connected when you run the IPCONFIG command on a Windows Server 2003-based computer that has iSCSI Boot Initiator 2.03 installed When you run the ipconfig command on a Microsoft Windows Server 2003-based computer that has Microsoft iSCSI Boot Initiator 2.03 installed, a disconnected network adapter appears connected. Note This problem occurs only if you click to select the Configure iSCSI Network Boot Support check box when you install iSCSI Boot Initiator 2.03. Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| Error message and events are logged in the System log when you try to compress a large file on an NTFS volume in Windows XP, in Windows 2000, or in Windows Server 2003: "Delayed Write Failed" Consider the following scenario. You have a computer that is running Microsoft Windows 2000, Microsoft Windows XP, or Microsoft Windows Server 2003. On this computer, you have a very large file on an NTFS file system volume. You try to compress the file by using NTFS File Compression, or you try to copy the file to an NTFS compressed folder. In this scenario, you may receive the following error message: Delayed Write Failed Note: This article applies to Microsoft Windows XP Home Edition, Microsoft Windows XP Professional (32-bit), and Microsoft Windows XP Professional x64 Edition. | ||
| A Volume Shadow Copy import operation may generate an error on a Windows Server 2003-based computer: "VSS_E_NO_SNAPSHOTS_IMPORTED" When a Volume Shadow Copy (VSS)-based application uses the IVssBackupComponents::ImportSnapshots() API to import a shadow copy that was created on a Microsoft Windows Server 2003-based computer, the ImportSnapshots() call may fail with a "VSS_E_NO_SNAPSHOTS_IMPORTED" error. This issue occurs when the shadow copy was created from volumes that span multiple partitions. Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| The Print Spooler service may stop sending print jobs to a printer that uses the standard port monitor on a Windows Server 2003-based computer The print queue on a Microsoft Windows Server 2003-based computer may stop working for a printer that uses the standard port monitor (SPM) for TCP/IP. Specifically, the Print Spooler service may stop sending print jobs to this printer, even though the spooler continues to send print jobs to other printers. In this situation, the print job in the printer's queue shows a status of "Printing." If you remove the print job from the queue, and then you try to print again, the same problem occurs. Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| My Music Folder Appears on Start Menu After You Install Windows XP 64-Bit After you install Windows XP 64-Bit Edition, the My Music folder may appear on the Start menu even though no Media Player or CD player software is installed. | | |
Other Relevant Articles
| A computer that uses an Intel EM64T processor may stop responding during startup Fixes a problem that may occur on a computer that is running an x64-based version of Windows if the computer uses multiple processors or uses more than 8 GB of RAM. Provides a hotfix to resolve the problem. | ||
| You receive the "Setup cannot install to the selected partition" error message when you try to install Windows Server 2003 or Windows XP Describes an issue where you receive an error message when you try to install Windows Server 2003, a x64-based version of Windows Server 2003, or Windows XP on a hard disk that was previously formatted as a GPT hard disk. | ||
| The Windows Firewall service in Windows XP Service Pack 2, in Windows XP Professional x64 Edition, in Windows Server 2003 SP1, and in x64-based versions of Windows Server 2003 cannot start if the DCOM Process Launcher Service is disabled You cannot ping a computer that is running Microsoft Windows XP Service Pack 2 (SP2), Microsoft Windows XP Professional x64 Edition, Microsoft Windows Server 2003 Service Pack 1 (SP1), or an x64-based version of Microsoft Windows Server 2003. If you view the Windows Firewall service in the Services snap-in, the Windows Firewall/Internet Connection Sharing service has not started. This symptom occurs even if the startup type is set to automatic. If the Windows Firewall service cannot start, all incoming connections are refused until the Windows Firewall service starts successfully. Additionally, the status of the Network Connections service and the COM+ Event System service may be in a pending state. | | |
| A USB smart card reader that is connected to a Windows Server 2003-based computer stops responding A universal serial bus (USB) smart card reader that is connected to a Microsoft Windows Server 2003-based computer stops responding (hangs). Note: This also applies to Microsoft Windows XP Professional x64 Edition. | ||
| You do not receive notification when the USB bus is overloaded on a Windows XP-based computer On a Microsoft Windows XP-based computer that uses certain ATI chipsets, you do not receive notification when the USB bus is overloaded. For example, you do not receive notification if the sum of the power requirements for the connected USB devices is more than the available power that is provided by the USB bus. Note If you have too many USB devices connected to the USB bus, one or more of these USB devices may not work. You do not receive notification when the USB bus is overloaded on a Windows Server 2003-based or a Windows XP Professional x64-based computer You do not receive notification when the USB bus is overloaded on a computer that is running Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition. For example, you do not receive notification if the sum of the power requirements for the connected USB devices is more than the available power that the USB bus provides. Note If you have too many USB devices connected to the USB bus, one or more of these USB devices may not work. Also, if the overload condition causes a USB port failure, the system may stop responding or crash. | ||
| When You Install a Scanner the Installation Program Is Unable to Locate A Driver When you install a scanner other than the Hewlett-Packard (HP) 6300 Series universal serial bus (USB)/small computer system interface (SCSI) scanner on a 64-bit Windows XP-based computer, the installation program is unable to locate any drivers and you are prompted for a driver disk. Note: This article applies to Microsoft Windows XP Professional x64 Edition. | ||
| You do not receive an overload notification when the USB bus becomes overloaded on a computer that is running Windows Server 2003 or Windows XP Professional x64 Edition and that is using an NVIDIA USB controller Consider the following scenario:
Note: If you have many USB devices that are connected to the USB bus, one or more of these USB devices may not work. Also, if the overload condition causes a USB port failure, the system may stop responding. | ||
| You do not receive notification when the USB bus is overloaded on a Windows Server 2003-based or a Windows XP Professional x64-based computer You do not receive notification when the USB bus is overloaded on a computer that is running Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition. For example, you do not receive notification if the sum of the power requirements for the connected USB devices is more than the available power that the USB bus provides. Note If you have too many USB devices connected to the USB bus, one or more of these USB devices may not work. Also, if the overload condition causes a USB port failure, the system may stop responding or crash. | | |
| A computer may stop responding on the Resuming Windows screen when the computer resumes from hibernation if the computer has three or more processors and is running an x64-based version of Windows Consider the following scenario:
| ||
| A floating-point calculation error may occur when you put the computer on standby and then you resume the computer while the calculation is in progress in Windows XP Professional x64 Edition Consider the following scenario. A Microsoft Windows XP Professional x64 Edition-based computer is running a program that is performing intense floating-point calculations. You put this computer into standby. In this scenario, a calculation error may occur when you resume the computer from standby. Note Standby is also known as sleep mode or S3 mode. Typically, you can put a computer into standby by using one of the following methods:
| ||
| You receive an "MCA_WARNING_UNKNOWN_NO_CPU" error message when you resume a computer from hibernation, and the computer is running one of the x64-based versions of Windows Server 2003 or Windows XP Professional x64 Edition You use a computer that is running one of the x64-based versions of Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition. When you resume the computer from hibernation, you may receive the following error message: MCA_WARNING_UNKNOWN_NO_CPU | ||
| A Windows Server 2003-based computer that is using an Intel dual-core processor may stop responding when you try to resume the computer from standby A Microsoft Windows Server 2003-based computer that is using an Intel dual-core processor may stop responding when you try to resume the computer from standby. Note: This article also applies to Microsoft Windows XP Professional x64 Edition. | ||
| Error message in Windows Server 2003 or in Windows XP Professional x64 Edition: "The process Lsass.exe has initiated the shutdown of computer" On a computer that is running Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition, you receive the following message: The process Lsass.exe has initiated the shutdown of computer computername After you receive this message, the computer shuts down. | | |
| You receive an error message when you try to open the Properties dialog box for a shared printer on a Windows Server 2003-based computer On a Microsoft Windows Server 2003-based computer, you to try to open the Printer Properties dialog box for a shared printer. This shared printer is connected to a Windows Server 2003-based domain controller. When you try to open this dialog box, you receive the following error message: Function address address caused a protection fault. Some or all property page(s) may not be displayed. Note: This issue affects Microsoft Windows XP Professional x64 Edition. | ||
| Differences between the 32-bit and 64-bit versions of Internet Explorer that are included in the x64-based versions of Windows Server 2003 and in Windows XP Professional x64 Edition The x64-based versions of Microsoft Windows Server 2003 and Microsoft Windows XP Professional x64 Edition include a 32-bit version and a 64-bit version of Microsoft Internet Explorer. Both versions of Internet Explorer are included to increase compatibility with existing programs and Web sites. The 32-bit version of Internet Explorer can host only native 32-bit ActiveX controls and other 32-bit Web page objects. The 64-bit version of Internet Explorer can host only native 64-bit ActiveX controls and other 64-bit Web page objects. This article describes the differences between the 32-bit and 64-bit versions of Internet Explorer that are included in the x64-based versions of Windows. | ||
| When you connect to the Windows Update Web site by using the 64-bit version of Internet Explorer, the 32-bit version of Internet Explorer opens in an x64-based version of Windows When you connect to the Microsoft Windows Update Web site by using the 64-bit version of Microsoft Internet Explorer, you receive the following message: Thank you for your interest in Windows Update We need to open a 32-bit version of Internet Explorer You can still install updates for your 64-bit version of Windows. However, you need to use a 32-bit version of the browser to view the website. If you click Open it now, the 32-bit version of Internet Explorer opens, and Windows Update continues. The following message appears in the 64-bit Internet Explorer window: Thank you for you interest in Windows Update Please close this browser window A 32-bit browser is now displaying the update website. | ||
| You receive error messages when you use a computer that is running Windows Vista to remotely install a printer driver on a computer that is acting as a print server Consider the following scenario. You use a computer that is running a 32-bit edition of Windows Vista to remotely install a printer driver on a 64-bit computer that is acting as a print server. Or, you use a computer that is running a 64-bit edition of Windows Vista to remotely install a printer driver on a 32-bit computer that is acting as a print server. In this scenario, you receive one or more of the following error messages: Error message 1 The Selected driver must be installed remotely from an x64 computer running Windows XP or Windows Server 2003. Error message 2 Unable to find a core driver package that is required by the printer driver package. | ||
| Failover process does not occur when you use TCP Offload-enabled network adapters to create a team capable of TCP Offloading on a Windows Server 2003-based computer When you use TCP Offload-enabled network adapters to create a team capable of TCP Offloading on a Microsoft Windows Server 2003-based computer, the failover process does not occur. The computer may stop responding. Note: This article applies to Microsoft Windows XP Professional x64 Edition. | | |
| Error message after you install the Windows Server 2003 Scalable Networking Pack in Windows Server 2003: "STOP 0x0000008E" or "STOP: 0x0000003B" After you install the Microsoft Windows Server 2003 Scalable Networking Pack on a Microsoft Windows Server 2003-based computer, you may receive a Stop error message that resembles one of the following: x64-based versions STOP: 0x0000003B (0xc0000005, parameter2, parameter3, parameter4) STATUS_ACCESS_VIOLATION x86-based versions STOP 0x0000008E (0xc0000005, parameter2, parameter3, parameter4) STATUS_ACCESS_VIOLATION Note: This article also applies to Microsoft Windows XP Professional x64 Edition | ||
| You receive a "Stop 0x0000009C" error message when you shut down a computer that is running the Microsoft Storport storage driver in Windows Server 2003 SP2 When you shut down a computer that is running the Microsoft Storport storage driver (Storport.sys) in Microsoft Windows Server 2003 Service Pack 2 (SP2), you may receive a "Stop 0x0000009C" error message that resembles the following: *** STOP: 0x0000009C (parameter1, parameter2, parameter3, parameter4) MACHINE_CHECK_EXCEPTION The problem also occurs if you install the updated Storport storage driver that is described in the following article: 932755 (http://support.microsoft.com/kb/932755/) An updated Storport storage driver (version 5.2.3790.4021) is available for Windows Server 2003 Note: In typical Microsoft fashion, this article is titled to target Windows Server 2003 SP2, however both the error and the fix apply to x64-based Windows XP. It is not known if this error occurs on 32-bit Windows XP, and if your problem is a Storport driver on a 32-bit XP then there is nothing to stop you from trying the driver fix for 32-bit Windows Server 2003. | ||
| Stop error that is related to the Storport.sys driver on a Windows Server 2003-based computer: "0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL" On a Windows Server 2003-based computer, you receive the following Stop error message on a blue screen: 0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL Notes: The parameters in this error message vary, depending on the computer's configuration. Not all "0x000000D1" Stop errors are caused by this problem. This problem occurs when the Storport.sys driver is called to pause or to resume an adapter in a Windows Server 2003-based computer. Additionally, storage driver developers may encounter symptoms of this issue when their drivers perform similar operations. Note: In typical Microsoft fashion, this article is titled to target Windows Server 2003 SP2, however both the error and the fix apply to x64-based Windows XP. It is not known if this error occurs on 32-bit Windows XP, and if your problem is a Storport driver on a 32-bit XP then there is nothing to stop you from trying the driver fix for 32-bit Windows Server 2003. | ||
| Windows Explorer randomly generates an access violation and closes when you refresh the wireless network list on a Windows Server 2003-based computer or on a Windows XP x64-based computer Consider the following scenario. The computer is a Microsoft Windows Server 2003-based computer or a Microsoft Windows XP x64-based computer. In Windows Explorer, you click Refresh Network List in the Properties dialog box for the wireless network connection. In this scenario, Windows Explorer randomly generates an access violation and closes. This problem only occurs when the network adapter detects one or more hidden Service Set Identifiers (SSIDs) in the wireless network. |