Windows Vista Stop Errors

If you don't find the stop error you're looking for then try looking at kadaitcha.cx's list of Windows XP Stop Errors because Windows XP stop errors are still relevant for many generic problems that don't involve specific third-party software packages.

How to fix Blue Screen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly

Page Index

0x00000001 
0x0000000A IRQL_NOT_LESS_OR_EQUAL 0xA
0x00000018 REFERENCE_BY_POINTER 0x18
0x00000019 BAD_POOL_HEADER 0x19
0x0000001A MEMORY_MANAGEMENT 0x1A
0x0000001E KMODE_EXCEPTION_NOT_HANDLED 0x1E
0x00000024
0x00000027 RDR_FILE_SYSTEM
0x0000003E MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED 0x3E
0x00000040 TARGET_MDL_TOO_SMALL
0x00000044 MULTIPLE_IRP_COMPLETE_REQUESTS 0x44
0x00000050 PAGE_FAULT_IN_NONPAGED_AREA 0x50
0x0000006F SESSION3_INITIALIZATION_FAILED
0x00000077 KERNEL_STACK_INPAGE_ERROR 0x77
0x00000079 MISMATCHED_HAL or Hal_Mismatch 0x79
0x0000007A KERNEL_DATA_INPAGE_ERROR 0x7A
0x0000007B INACCESSIBLE_BOOT_DEVICE 0x7B
0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x7E
0x0000007F UNEXPECTED_KERNEL_MODE_TRAP 0x7F
0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x8E
0x0000009F DRIVER_POWER_STATE_FAILURE 0x9F
0x000000A0 INTERNAL_POWER_ERROR 0xA0
0x000000B8 ATTEMPTED_SWITCH_FROM_DPC
0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY 0xBE
0x000000C1 SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 0xC1
0x000000C2 BAD_POOL_CALLER 0xC2
0x000000C4 DRIVER_VERIFIER_DETECTED_VIOLATION 0xc4
0x000000CA PNP_DETECTED_FATAL_ERROR 0xCA
0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING 0xCE
0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0xD1
0x000000E3 RESOURCE_NOT_OWNED 0xE3
0x000000FE BUGCODE_USB_DRIVER 0xFE
0x00000101 CLOCK_WATCHDOG_TIMEOUT 0x101
0x0000010E VIDEO_MEMORY_MANAGEMENT_INTERNAL 0x10E
0x00000124
0x0000C1F5
0x1000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
0x80070246 ERROR_ILLEGAL_CHARACTER
0xC0000218 UNKNOWN_HARD_ERROR

A computer that is running Windows Server 2008 or Windows Vista receives various stop codes that cause the system to automatically restart after you enable the NetDMA feature on the new "Crystal Beach" (DMA) chip from Intel

0x00000001

	You receive a Stop error message on a Windows Vista-based computer: "Stop 0x00000001 (0x00000000, 0x7FFDC000, 0X0000FFFF, 0X00000000)" Consider the following scenario: You are using a Windows Vista-based computer. The color scheme is set to Windows Aero. You enter your credentials to unlock the computer. When you unlock the computer, you switch from a secure desktop to the default desktop. An event hook is running in the secure desktop. The event hook is registered by using the SetWinEventHook application programming interface (API). Note A secure desktop appears when the computer is locked. When a secure desktop appears, you can enter your credentials to unlock the computer. In this scenario, you receive a Stop error message that resembles the following: Stop 0x00000001 (0x00000000, 0x7FFDC000, 0X0000FFFF, 0X00000000) Note The Stop error message always has a Stop error code of 0x00000001. Also, the third parameter of the Stop error message is always 0x0000FFFF. This problem may also occur after you repeatedly put the computer to sleep.
	Stop error message when you try to print content that includes a bitmap on a Windows Vista-based computer: "Stop 0x00000001" When you try to print content that includes a bitmap on a Windows Vista-based computer, you may receive the following Stop error message: Stop 0x00000001 (Parameter1, Parameter2, Parameter3, Parameter4) This problem occurs if Windows Vista copies the bitmap from a user mode printer driver (UMPD).

0x0000000A IRQL_NOT_LESS_OR_EQUAL 0xA

	Stop error 0x0A, or Stop error 0x7E may occur on a computer that is running Windows Vista or Windows Server 2008 On a computer that is running Windows Vista or Windows Server 2008, you may receive one of the following Stop errors: 0x0000000A (<parameter1>, <parameter2>, <parameter3>, <parameter4>) IRQL_NOT_LESS_OR_EQUAL 0x0000007E (0xC0000005, <parameter2>, <parameter3>, <parameter4>) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED These Stop errors occur in the Ancillary Function Driver (AFD) driver (Afd.sys). This problem occurs when Windows Vista or Windows Server 2008 performs network related operations by using the Server Message Block (SMB) protocol.
	You randomly receive a "Stop 0x0000000A" error in Storport.sys when you start Windows Vista When you start a computer that is running Windows Vista, you randomly receive a "Stop 0x0000000A" error message that resembles the following: STOP 0x0000000A IRQL_NOT_LESS_OR_EQUAL Storport.sys You experience this problem if the following conditions are true: The computer has an NVIDIA chipset. The computer has four gigabytes (GB) or more of RAM.
	Error message when you try to install Windows Vista on a computer that uses more than 3 GB of RAM: "STOP 0x0000000A" When you try to install Windows Vista, you may receive an error message that resembles the following: STOP 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL This problem occurs if the following conditions are true: The computer uses more than 3 GB of RAM. The computer uses a storage system that is running the Storport miniport driver. The computer uses a controller that uses 32-bit direct memory access (DMA).
	FIX: Error message when you use an IEEE 1394-based scanner on a computer that is running Windows XP 64-bit, Windows Server 2003, or Windows Vista: 0x0000000A or 0x000000BE When you use an IEEE 1394-based scanner and run a 32-bit scanning program on a computer that is running Microsoft Windows XP 64-bit, Microsoft Windows Server 2003, you receive an error message on a blue screen that resembles one of the following: 0x0000000A: IRQL_NOT_LESS_OR_EQUAL 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY This problem occurs when the scanning program calls the DeviceIoControl function to send a IOCTL_SCSISCAN_CMD control code to the kernel mode driver. In Windows Vista, you may not experience the blue screen. When your scanning program calls the DeviceIoControl function to send an IOCTL_SCSISCAN_CMD control code to the kernel mode driver in Windows Vista, this call may not be completed successfully, and your scanning program does not work as expected. The exact symptom that is observed in the user interface depends on how your scanning software works when the DeviceIoControl function fails.
	Stop error message when the computer resumes from hibernation in Windows Vista: "STOP 0x0000000A" When you resume a Windows Vista-based computer from hibernation, you may receive a Stop error message that resembles the following: *** STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL
	Stop error message when you start a portable Windows Vista-based computer that has the lid closed: "STOP: 0x0000000A" When you start a portable Windows Vista-based computer that has the lid closed, you may receive a Stop error message that resembles the following: STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL Note This problem also occurs when you restart a portable Windows Vista-based computer that has the lid closed. For example, this problem may occur if you have an external monitor or TV connected to the portable computer. In this scenario, the portable computer lid may be closed when you start the computer.
	Error message when a portable Windows Vista-based computer that has an integrated or external USB camera device resumes from long-term suspend mode: "0x000000E4" or "0x0000000A" When you use a portable Windows Vista-based computer, you may receive a Stop error message that resembles one of the following: STOP: 0x000000E4 (0x00000002, parameter2, parameter3, parameter4) STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4) The parameters in the Stop error message vary, depending on the configuration of the computer and on the issue type. This problem occurs if the following conditions are true: A USB camera device is integrated into the computer, or the device is connected to the computer through a USB cable. You resume the computer from long-term suspend mode. For example, the computer has been suspended for 30 minutes or more. The value of the computer's ForceHCResetOnResume registry entry is 0
	Troubleshooting Stop error messages that may occur when you try to install Windows Vista This article discusses the Stop error messages that can occur when you try to install Windows Vista. This article describes the possible causes of each Stop error message. It also provides troubleshooting steps for each issue. Note that this article relates to several stop errors but includes an informative section on 0x0000000A IRQL_NOT_LESS_OR_EQUAL.
	Stop error when you resume a Windows Vista-based computer that is connected to a USB optical disc drive from standby "STOP: 0x000000E4" or "STOP: 0x0000000A" When you have a Windows Vista-based computer that is connected to a USB optical disc drive, and you resume the computer from Standby, you may receive a error message that resembles one of the following error messages: STOP: 0x000000E4 (parameter1, parameter2, parameter3, parameter4) STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4) The parameters in the error message vary, depending on the configuration of the computer. This issue may occur on a computer that is running Windows Vista, Windows Vista Service Pack 1 (SP1), or Windows Server 2008.
	Stop error when you try to put a Windows Vista Service Pack 1-based or Windows Server 2008-based computer into hibernation: "Stop 0x0000000A" You have a computer that runs Windows Vista Service Pack 1 or Windows Server 2008. However, when you try to put the computer into hibernation, you receive the following Stop error message: Stop 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL This problem occurs occasionally. It does not occur in the original release of Windows Vista.
	Stop error message when you run the Dynamic Partition Testing for a Hot Replace test that is included in the Windows Logo Kit in Windows Vista or Windows Server 2008: "Stop 0x0000000A" You run the Dynamic Partition Testing for a Hot Replace test that is included in the Windows Logo Kit (WLK) in Windows Vista or in Windows Server 2008. However, the system crashes after the test runs for several minutes. Additionally, you may receive a Stop error message that resembles the following: Stop 0x0000000A (Parameter1, Parameter2, Parameter3, Parameter4) IRQL_NOT_LESS_OR_EQUAL This problem only occurs if you have enabled the Force IRQL checking setting in the Driver Verifier tool (Verifier.exe) when you perform the WLK test.

0x00000018 REFERENCE_BY_POINTER 0x18

	Stop errors in Windows Vista or Windows Server 2008: “Stop: 0x00000018” or “STOP: 0x000000C2” On a computer that is running Windows Vista or Windows Server 2008, the operating system randomly crashes. Additionally, you receive one of the following Stop error messages: Stop: 0x00000018 (parameter1, parameter2, parameter3, parameter4) REFERENCE_BY_POINTER STOP: 0x000000C2 (parameter1, parameter2, parameter3, parameter4) BAD_POOL_CALLER
	Stop error on a Windows Vista Service Pack 1-based or Windows Server 2008-based computer that has an integrated graphics adapter and a discrete graphics adapter: "Stop 0x00000018" Consider the following scenario: You have a computer that is running Windows Vista Service Pack 1 or Windows Server 2008. The computer has an integrated graphics adapter and a discrete graphics adapter. When you start the computer, you are using the discrete graphics adapter for the display output. You switch the display output from the discrete graphics adapter to the integrated graphics adapter. A power event occurs. For example, when your AC power cord is disconnected, the power supply system fails over to a DC power source. In this scenario, you may receive the following Stop error: Stop: 0x00000018 (parameter1, parameter2, parameter3, parameter4) REFERENCE_BY_POINTER

0x00000019 BAD_POOL_HEADER

	Stop error message in Windows Server 2008 or Windows Vista after you uninstall or reinstall a wireless network adapter driver: "0x00000019 BAD_POOL_HEADER" On a computer that is running Windows Server 2008 or Windows Vista, you receive the following Stop error message on a blue screen: 0x00000019 (parameter1 , parameter2 , parameter3 , parameter4 ) BAD_POOL_HEADER This problem occurs after you uninstall or reinstall a wireless network adapter driver.
	Stop error message when you retrieve WMI connection statistics for iSCSI after you change the iSCSI configurations on a computer that is running Windows Server 2008 or Windows Vista: "0x00000019 BAD_POOL_HEADER" On a computer that is running Windows Server 2008 or Windows Vista, you may receive the following Stop error message: 0x00000019 (00000021, parameter2, parameter3, parameter4) BAD_POOL_HEADER This behavior occurs when you change the Internet SCSI (iSCSI) configurations on the computer and retrieve some iSCSI connection statistics by using Windows Management Instrumentation(WMI).
	Error message on a computer that is running Windows Vista or on Windows Server 2008 that has the IPMI driver installed: "Stop 0x00000019" On a computer that is running Windows Vista or Windows Server 2008, some applications use the Intelligent Platform Management Interface (IPMI) driver to communicate with the baseboard management controller (BMC). However, you may receive a Stop error message on the computer occasionally. For example, you may receive the following Stop error message: Stop 0x00000019 (00000020, parameter2, parameter3, parameter4) BAD_POOL_HEADER

0x0000001A MEMORY_MANAGEMENT

Error message when you try to play a movie file that has an .mov extension by using QuickTime 7 in Windows Vista: "STOP 0x1A MEMORY_MANAGEMENT" When you try to play a movie file that has an .mov extension by using QuickTime 7 in Windows Vista, you may receive a Stop error message that resembles the following: STOP 0x0000001A (parameter1, parameter2, parameter3, parameter4) MEMORY_MANAGEMENT

0x0000001E KMODE_EXCEPTION_NOT_HANDLED 0x1E

A computer that is running an x64-based version of Windows Server 2003 or of the original release version of Windows Vista randomly restarts and then generates a Stop error A computer that is running an x64-based version of Windows Server 2003 or of the original release version of Windows Vista randomly restarts and then generates a Stop error. The Stop error code may be 0x0000001E, 0x000000D1, or another Stop error code. This problem occurs after you install update 932596 on the computer.

0x00000024

On a computer that is running Windows Vista Service Pack 1 or Windows Server 2008, you may receive a Stop error message that resembles the following: Stop 0x00000024 (parameter1, parameter2, parameter3, parameter4)

0x00000027 RDR_FILE_SYSTEM

Stop error message on a computer that is running Windows Server 2008 or Windows Vista: "0x00000027 RDR_FILE_SYSTEM" On a computer that is running Windows Server 2008 or Windows Vista, you receive the following Stop error message: Stop 0x00000027 (parameter1, parameter2, parameter3, parameter4) RDR_FILE_SYSTEM The parameters in this error message vary, depending on the configuration of the computer. When this problem occurs, the following event is logged in the system event log: Event ID: 1001 Event Type: Information Description:The computer has rebooted from a bugcheck. The bugcheck was: 0x00000027 (parameter1, parameter2, parameter3, parameter4). A dump file was saved in: <path of dump file>.

0x0000003E MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED

You receive a "Stop 0x0000003E" error message when you try to install Windows Vista Service Pack 2 or Windows Server 2008 Service Pack 2 on a computer that has certain multiple processors You are running an x64-based version of Windows Vista or of Windows Server 2008 on a computer that has multiple Intel x64 processors or has an Intel x64 multi-core processor. When you try to install Windows Vista Service Pack 2 or Windows Server 2008 Service Pack 2 on the computer, you receive the following Stop error message: Stop 0x0000003E (parameter1, parameter2, parameter3, parameter4) MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED Note When this problem occurs, parameter1 and parameter2 in this Stop error message can make the following equation valid: ((parameter1 ^ parameter2) & (0x00100000))!= 0

0x00000040 TARGET_MDL_TOO_SMALL

Stop error message when you have the TCP Chimney feature enabled and the TCP transfer buffer size is set to 32 MB in Windows Vista, Windows Server 2008, or Windows Server 2003: "Stop 0x00000040 TARGET_MDL_TOO_SMALL" On a computer that is running Windows Vista, Windows Server 2008, or Windows Server 2003, you have the TCP Chimney feature enabled, and the TCP transfer buffer size is set to 32 MB. When you perform a network operation, the system crashes. Additionally, you receive the following Stop error message: Stop 0x00000040 TARGET_MDL_TOO_SMALL For example, you start the FTP command and then use the following parameter to specify the TCP transfer buffer size: ftp -w: 33554432 FTP Server IP Address In this case, after you log on to the FTP server and perform an operation, such as "put," that generates large transfers, the system crashes, and you receive the Stop error message.

0x00000044 MULTIPLE_IRP_COMPLETE_REQUESTS

	Error message in the Usbhub.sys process when you wake a Windows Vista-based computer from sleep or from hibernation: "STOP 0x00000044" When you wake a Windows Vista-based computer from sleep or from hibernation, you receive a "Stop 0x44" error message in the Usbhub.sys process. This error message resembles the following: STOP 0x00000044(parameter1, parameter2, parameter3, parameter4) MULTIPLE_IRP_COMPLETE_REQUESTS
	Stop 0x44 (MULTIPLE_IRP_COMPLETE_REQUESTS) Disabling Idle USB Device with KMDF-based Driver When you Disable a USB device that is currently Idle, you may receive a "Stop 0x44" error message on a blue screen. This error message resembles the following: STOP 0x00000044 ( parameter1 , parameter2 , parameter3 , parameter4 ) MULTIPLE_IRP_COMPLETE_REQUESTS

0x00000050 PAGE_FAULT_IN_NONPAGED_AREA 0x50

	Error message during Windows Vista startup if the Nero InCD program is installed and if the "Special pool" feature is enabled in the Driver Verifier utility: "Stop 00000050" Consider the following scenario: You install the Nero InCD program on a Windows Vista-based computer. You enable the "Special pool" feature in the Driver Verifier utility (Verifier.exe) for a device on the computer. There is no media in the CD drive or in the DVD drive. In this scenario, Windows Vista stops unexpectedly during startup, and then you receive an error message that resembles the following: Stop 00000050 (83cb3054, 00000000, 8143cc97, 00000001)
	Error message on a Windows Vista-based computer that has a storage device inserted into a card bus adapter: "STOP: 0x00000050" When you start a Windows Vista-based computer, you may receive a Stop 0x50 error message that resembles the following: *** STOP: 0x00000050 (parameter1, parameter2, parameter3, parameter4) PAGE_FAULT_IN_NONPAGED_AREA This problem occurs on a computer that has the following hardware installed: •  A card bus adapter •  A storage device that is inserted into the card bus adapter The storage device might be one of the following: •  A secure digital (SD) card •  A compact flash (CF) card •  An external Serial Advanced Technology Attachment (eSATA) hard disk drive that is running in SATA Advanced Host Controller Interface (AHCI) mode
	Error message when you start a Windows Vista-based computer: "STOP: 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA" When you start a Windows Vista-based computer, you may receive a "Stop 0x50" error message that resembles the following: *** STOP: 0x00000050 (parameter1, parameter2, parameter3, parameter4) PAGE_FAULT_IN_NONPAGED_AREA This problem typically occurs very early in the startup process. For example, the problem may occur shortly after the splash screen appears, and you see a black screen with a moving progress bar. Specifically, this problem typically occurs when the system tries to load the i8042prt.sys driver. The problem only occurs in certain hardware configurations.
	Error message after you apply update 973879: "Stop 0x0000007e" or "Stop 0x00000050" After you apply update 973879 on a computer that is running an x64-based version of Windows Vista or of Windows Server 2008, you may receive a "Stop 0x0000007e" or "Stop 0x00000050" error message within 10 minutes after system startup.
	During user logon or logoff, you receive stop error code 0x00000050, and the system restarts automatically on a computer that is running Windows Server 2008 or Windows Vista SP1 On a computer that is running Windows Server 2008 or Windows Vista Service Pack 1 (SP1), you repeatedly encounter stop error code 0x00000050 during the user logon or logoff process. Then, the computer restarts automatically. When this issue occurs, the following event may be logged in the System log: Log Name: System Source: Microsoft-Windows-Kernel-General Date: date & time Event ID: 5 Task Category: None Level: Error Keywords: User: SYSTEM Computer: computer name Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\user name\ntuser.dat' was corrupted and it has been recovered. Some data might have been lost.
	You receive a "Stop 0x00000050" error message after you enable or disable Bluetooth Enumerator in Device Manager on a Windows Vista or Windows Server 2008-based computer On a computer that is running Windows Vista or Windows Server 2008, after you enable or disable the Microsoft Bluetooth Enumerator in Device Manager, you receive the following Stop error message: STOP 0x00000050 (parameter1, parameter2, parameter3, parameter4)
	Error message after you enable or disable Microsoft Bluetooth Enumerator in Device Manager on a Windows Vista-based computer that has Windows Vista Feature Pack for Wireless installed: "Stop 0x00000050" Consider the following scenario: You have Windows Vista Feature Pack for Wireless installed on a computer that is running Windows Vista Service Pack 1 (SP1). You enable or disable Microsoft Bluetooth Enumerator in Device Manager. In this scenario, you receive the following Stop error message: STOP 0x00000050 (parameter1, parameter2, parameter3, parameter4)
	Stop error when Windows Server 2003-based server (or Windows Vista, Windows Vista Service Pack 1) restarts unexpectedly: "Stop 0x00000050" A Windows-based computer may restart unexpectedly. Additionally, you may receive the following Stop error message: Stop 0x00000050 ( parameter1 , 00000000, parameter3 , 00000000) PAGE_FAULT_IN_NONPAGED_AREA This issue occurs when the computer is running Windows Server 2003, Windows Vista, Windows Vista Service Pack 1, Windows Server 2008.
	Stop error message when you try to update or to install AVstream device drivers on a Windows Vista-based computer: "STOP: 0x00000050" Consider the following scenario: You are running a Windows Vista-based computer. You try to update or to install video or audio AVstream device drivers. The corresponding device is in suspend mode. In this scenario, the computer crashes. Additionally, you receive the following Stop error message: STOP: 0x00000050 (0xFFFFFF94, 0x00000000, 0x8D2E3798, 0x00000000) PAGE_FAULT_IN_NONPAGED_AREA ks.sys Address 8D2E3798 base at 8D2C5000, DateStamp 4549b186 When you upgrade Windows Vista to Windows Vista Service Pack 1, the video and audio AVstream device drivers are updated. Therefore, in this situation, you may experience this issue.
	Stop error during the shutdown process on a Windows Server 2008 or Windows Vista SP1-based computer: "Stop 0x00000050" On a computer that is running Windows Vista Service Pack 1 or Windows Server 2008, you may receive a Stop error message that resembles the following: Stop 0x00000050 (parameter1, parameter2, parameter3, parameter4) PAGE_FAULT_IN_NONPAGED_AREA during the shutdown process
	Stop error if you use some OpenType fonts on a computer that is running Windows Server 2003, Windows Vista, or Windows Server 2008: "Stop 0x00000050" A computer that is running Windows Server 2003, Windows Vista, or Windows Server 2008 may restart unexpectedly. Additionally, you may receive the following Stop error message: Stop 0x00000050 (parameter1, 00000000, parameter3, 00000000) PAGE_FAULT_IN_NONPAGED_AREA This problem may occur if the computer uses some OpenType fonts that are provided by printer drivers.

0x0000006F SESSION3_INITIALIZATION_FAILED

Error message when you start a Windows Vista-based computer on which Windows ReadyBoost is running: "STOP: 0x0000006F SESSION3 INITIALIZATION FAILED" When you start a Windows Vista-based computer, you receive an error message that resembles the following: *** STOP: 0x0000006F (parameter1, parameter2, parameter3, parameter4) SESSION3_INITIALIZATION_FAILED This problem occurs if the computer is using an onboard storage device or an external flash storage device that is managed by Windows ReadyBoost. This problem occurs only in certain hardware configurations. Note Some computers may use an onboard "integrated" flash storage device that uses Windows ReadyBoost to improve system performance. On such a system, you may not be aware that Windows ReadyBoost is running, because the configuration and operation are automatic.

0x00000077 KERNEL_STACK_INPAGE_ERROR 0x77

	Stop error message when you put a computer that is running Windows Vista or Windows Server 2008 into hibernation: "STOP 0x000000A0," "STOP 0x0000007a," or "STOP 0x00000077" When you try to put a computer that is running Windows Vista or Windows Server 2008 into hibernation, you receive a Stop error message. Typically, you receive the following Stop error message: STOP 0x000000A0 (parameter1, parameter2, parameter3, parameter4) INTERNAL_POWER_ERROR (a0) You may also receive other Stop error messages such as the following: STOP 0x0000007a (parameter1, parameter2, parameter3, parameter4) KERNEL_DATA_INPAGE_ERROR STOP 0x00000077 (parameter1, parameter2, parameter3, parameter4) KERNEL_STACK_INPAGE_ERROR This problem occurs occasionally and only under certain hardware configurations. It continues to occur even after you apply the following hotfixes on the computer: 950563 - The system may crash when you put a Windows Vista-based computer into hibernation, and you may receive a Stop error message: "STOP 0x0000000A" 956871 - The system may crash when you put a Windows Vista-based computer or a Windows Server 2008-based computer into hibernation
	The system may crash when you put a Windows Vista-based computer or a Windows Server 2008-based computer into hibernation When you put a Windows Vista-based computer or a Windows Server 2008-based computer into hibernation, the system may crash. Additionally, you may receive a Stop error message that resembles one of the following messages: STOP 0x000000A0 (parameter1, parameter2, parameter3, parameter4) INTERNAL_POWER_ERROR (a0) 0x0000007a (parameter1, parameter2, parameter3, parameter4) KERNEL_DATA_INPAGE_ERROR STOP 0x00000077 (parameter1, parameter2, parameter3, parameter4) KERNEL_STACK_INPAGE_ERROR This problem occurs only occasionally. Currently, the problem is found on computers that have SB700 Southbridge chipsets installed.

0x00000079 MISMATCHED_HAL or Hal_Mismatch 0x79

How to move a Windows installation to different hardware After you restart the destination computer, you may experience the following symptoms: You receive one of the following Stop error messages: Stop 0x0000007B Inaccessible_Boot_Device STOP: 0x00000079 Hal_Mismatch The computer stops responding at startup. The computer that is running Windows crashes on startup. This occurs when the source HAL and the target HAL do not match. The computer spontaneously restarts when you receive the following message on a black screen early in the restart process: Starting Windows... You cannot configure your display settings. The network adapter does not function correctly.

0x0000007A KERNEL_DATA_INPAGE_ERROR 0x7A

	Stop error message when you put a computer that is running Windows Vista or Windows Server 2008 into hibernation: "STOP 0x000000A0," "STOP 0x0000007a," or "STOP 0x00000077" When you try to put a computer that is running Windows Vista or Windows Server 2008 into hibernation, you receive a Stop error message. Typically, you receive the following Stop error message: STOP 0x000000A0 (parameter1, parameter2, parameter3, parameter4) INTERNAL_POWER_ERROR (a0) You may also receive other Stop error messages such as the following: STOP 0x0000007a (parameter1, parameter2, parameter3, parameter4) KERNEL_DATA_INPAGE_ERROR STOP 0x00000077 (parameter1, parameter2, parameter3, parameter4) KERNEL_STACK_INPAGE_ERROR This problem occurs occasionally and only under certain hardware configurations. It continues to occur even after you apply the following hotfixes on the computer: 950563 - The system may crash when you put a Windows Vista-based computer into hibernation, and you may receive a Stop error message: "STOP 0x0000000A" 956871 - The system may crash when you put a Windows Vista-based computer or a Windows Server 2008-based computer into hibernation
	The system may crash when you put a Windows Vista-based computer or a Windows Server 2008-based computer into hibernation When you put a Windows Vista-based computer or a Windows Server 2008-based computer into hibernation, the system may crash. Additionally, you may receive a Stop error message that resembles one of the following messages: STOP 0x000000A0 (parameter1, parameter2, parameter3, parameter4) INTERNAL_POWER_ERROR (a0) 0x0000007a (parameter1, parameter2, parameter3, parameter4) KERNEL_DATA_INPAGE_ERROR STOP 0x00000077 (parameter1, parameter2, parameter3, parameter4) KERNEL_STACK_INPAGE_ERROR This problem occurs only occasionally. Currently, the problem is found on computers that have SB700 Southbridge chipsets installed.
	BIOS manufacturers should not clear the IDE Decode Enable bit in the _STM ACPI method An IDE channel and all attached devices are missing from the computer. If the boot drive is on the missing channel, you receive the following "Stop error" error message on a blue screen: KERNEL_DATA_INPAGE_ERROR The bugcheck is (0x0000007a (0xe15a48e8, 0xc000000e, 0xbf914cd9, 0x148a3860) in Win32k.sys where 0xC000000E STATUS_NO_SUCH_DEVICE

0x0000007B INACCESSIBLE_BOOT_DEVICE

Note that Microsoft can't make it's collective mind up if the error message is INACCESSABLE_BOOT_DEVICE or INACCESSIBLE_BOOT_DEVICE.

	How to move a Windows installation to different hardware After you restart the destination computer, you may experience the following symptoms: You receive one of the following Stop error messages: Stop 0x0000007B Inaccessible_Boot_Device STOP: 0x00000079 Hal_Mismatch The computer stops responding at startup. The computer that is running Windows crashes on startup. This occurs when the source HAL and the target HAL do not match. The computer spontaneously restarts when you receive the following message on a black screen early in the restart process: Starting Windows... You cannot configure your display settings. The network adapter does not function correctly.
	Error message when you try to install Windows Vista on a computer that includes a DELL CERC SATA 1.5/6ch RAID controller: "STOP 0x0000007B" You try to install Windows Vista on a computer that includes a DELL CERC SATA 1.5/6ch RAID controller from Dell. However, when the computer restarts, you receive an error message that resembles the following: STOP 0x0000007B (0xF9813BD8,0xC0000034,0x00000000,0x00000000) INACCESIBLE_BOOT_DEVICE
	Stop error when you try to restart a Windows PE 2.0 system that uses AMD Barcelona processor and that has the Operating System Capabilities (_OSC) method enabled in the BIOS: "STOP: 0x0000007B (INACCESSIBLE_BOOT_DEVICE)" When you try to restart a Microsoft Windows Preinstallation Environment (Windows PE) 2.0 for Windows Vista system that uses an AMD Barcelona processor and that has the Operating System Capabilities (_OSC) method enabled in the BIOS, the system will continually restart. Additionally, you may receive the following Stop error message on the screen: STOP: 0x0000007B: (parameter1, parameter2, parameter3, parameter4) INACCESSIBLE_BOOT_DEVICE Notes: The four parameters in the Stop error message vary depending on the computer's configuration. Not all "Stop 0x0000007B" error messages are caused by this problem.
	Troubleshooting Stop error messages that may occur when you try to install Windows Vista This article discusses the Stop error messages that can occur when you try to install Windows Vista. This article describes the possible causes of each Stop error message. It also provides troubleshooting steps for each issue. Note that this article relates to several stop errors but includes an informative section on 0x0000007B INACCESSIBLE_BOOT_DEVICE.
	Error message when you restart a multicore-processor computer that is running Windows Vista: "STOP 0x0000007B" When you restart a multicore-processor computer that is running Windows Vista, you may receive the following Stop error message: STOP 0x0000007B (parameter1, parameter2, parameter3, parameter4) INACCESSIBLE_BOOT_DEVICE This problem is more likely to occur on a virtual machine.
	Error message when you try to join a Windows Vista-based client computer to a top level domain (TLD) that has a purely numeric suffix: "An Active Directory Domain Controller for the domain <DNS domain name> could not be contacted" When you try to join a Windows Vista-based client computer to a top level domain (TLD) that has a purely numeric suffix, the Windows Vista-based client computer cannot join the domain. Additionally, you receive the following error message: Computer Name/Domain Changes An Active Directory Domain Controller for the domain <DNS domain name> could not be contacted. Ensure that the domain name is typed correctly. If the name is correct, click Details for troubleshooting information. When you click Details, you receive the following error message: An error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller of the domain domain name. The error was: "The filename, directory name, or volume label syntax is incorrect." (error code 0x0000007B ERROR_INVALID_NAME) The query was for the SRV record for _ldap._tcp.dc._msdcs.domain name.com If you try to join the domain by using the NetBIOS name of the domain, you are prompted for domain credentials. In this case, the client computer still cannot join the domain. Additionally, you receive the following error message: The following error occurred attempting to join the domain NetBIOS name of the domain Logon failure: unknown username or bad password.
	Stop 7B After Uninstalling Zetera ZetSFD Filter Driver Following Vista Upgrade or Service Pack Installation When you try to start a Windows Vista or Windows Server 2008-based computer after installing a Windows Service Pack and subsequently uninstalling NetGear Storage Central or Zetera Z-SAN software, you receive the following stop error message: STOP: 0x0000007B ( parameter1 , parameter2 , parameter3 , parameter4 ) INACCESSIBLE_BOOT_DEVICE This problem may occur under the following conditions: You have the NetGear Storage Central software, including the Zetera Z-SAN drivers, installed on a computer running Windows Vista or Windows Server 2008.You perform either an in-place-upgrade of your existing Windows Vista or Windows Server 2008 operating system, or install a Windows Vista or Windows Server 2008 Service Pack.You uninstall the NetGear Storage Central software or the Zetera Z-SAN drivers.You restart Windows.
	Stop error on a computer that is running an Itanium-based version of Windows Server 2008 and that has Qlogic 8-gigabyte Fibre Channel cards installed: "STOP 0x0000007B" On a computer that is running an Itanium-based version of Windows Server 2008, you may experience one of the following symptoms: You receive the following Stop error message: STOP 0x0000007B (parameter1, parameter2, parameter3, parameter4) INACCESSIBLE_BOOT_DEVICE You see a yellow exclamation mark (!) next to a device in Device Manager. Currently, this problem has been found on computers that have Qlogic 8-gigabyte Fibre Channel cards installed. However, this problem may occur on computers that have other devices installed that require more than two interrupt vectors.
	Error message when you update the SATA controller driver to the MSAHCI driver after you install Windows Vista Service Pack 1: "STOP 0x7B" Consider the following scenario. You install Windows Vista Service Pack 1 (SP1). At the time of the installation, you install a Serial ATA (SATA) controller driver other than the Microsoft Advanced Host Controller Interface (MSAHCI) driver. Then, after Windows Vista SP1 is installed, you update the existing SATA driver to the MSAHCI driver. However, when you restart the computer after you update the driver, you receive the following stop error message: STOP 0x0000007B (parameter1, parameter2, parameter3, parameter4) INACCESSIBLE_BOOT_DEVICE

0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x7E

Stop errors occur on a Windows-based computer that has 2GB or more of RAM and is using an NVIDIA nForce USB controller You may receive a Stop error message that resembles one of the following after you resume a computer from sleep or from hibernation: Error message 1: STOP 127 PAGE_NOT_ZERO_NVIDIA_USB This error occurs on a computer that uses 2 gigabytes (GB) or more of RAM and an nVidia nForce EHCI controller. Error message 2: STOP 0x1000007E usbhub.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED This error occurs because of a race condition in the Usbhub.sys driver. This condition occurs if a USB device driver tries to enter a selective suspend state when a previously canceled selective suspend request has not yet been fully processed.

	Error message after you apply update 973879: "Stop 0x0000007e" or "Stop 0x00000050" After you apply update 973879 on a computer that is running an x64-based version of Windows Vista or of Windows Server 2008, you may receive a "Stop 0x0000007e" or "Stop 0x00000050" error message within 10 minutes after system startup.
	Stop error 0x0A, or Stop error 0x7E may occur on a computer that is running Windows Vista or Windows Server 2008 On a computer that is running Windows Vista or Windows Server 2008, you may receive one of the following Stop errors: 0x0000000A (<parameter1>, <parameter2>, <parameter3>, <parameter4>) IRQL_NOT_LESS_OR_EQUAL 0x0000007E (0xC0000005, <parameter2>, <parameter3>, <parameter4>) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED These Stop errors occur in the Ancillary Function Driver (AFD) driver (Afd.sys). This problem occurs when Windows Vista or Windows Server 2008 performs network related operations by using the Server Message Block (SMB) protocol.
	You may receive a "Stop 0x0000007E" error message after you enable the BitLocker Drive Encryption feature in Windows Vista After you enable the BitLocker Drive Encryption feature in Windows Vista, you may receive a "Stop 0x0000007E" error message that resembles the following: STOP 0x0000007E (parameter1, parameter2, parameter3, parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
	FIX: You receive a Stop 0x0000007e error message on a blue screen when the AppPoolCredentials attribute is set to true and you use a domain account as the application pool identity in IIS 7.0 Consider the following scenario: You have a Web application that is running in Internet Information Services (IIS) 7.0 on a Windows Vista-based computer or on a Windows Server 2008-based computer. You have both Windows Authentication and Kernel Mode authentication enabled. Note This is by default. You have the useAppPoolCredentials attribute set to true in the authentication section in the Applicationhost.config file. You may have added this attribute to allow the use of Kerberos authentication when you use a domain account for the application pool identity. For example, this attribute must be added when you are running a Microsoft Office SharePoint Server site. The authentication section resembles the following: <windowsAuthentication enabled="true" useKernelMode="true" useAppPoolCredentials="true"/> In this scenario, the operating system may crash. Additionally, you receive a Stop 0x0000007e error message on a blue screen. This problem typically occurs on Web servers that host Office SharePoint Server 2007. This problem occurs because of the configuration requirements of Office SharePoint Server 2007 when Kerberos authentication is used. However, the problem may occur for any kind of Web site that is using Kernel Mode authentication, Kerberos authentication, and a domain account as the custom application pool identity.
	Error message when you start a multiprocessor computer that runs Windows Vista: "STOP: 0x0000007E" When you start a multiprocessor computer that runs Windows Vista, you may receive the following Stop error message: STOP: 0x0000007E (parameter1, parameter2, parameter3, parameter4) NETIO.SYS This problem typically occurs after a driver for a third-party network adapter is installed.
	Occasional error message on a portable Windows Vista-based computer that wakes from sleep to perform network-related tasks: "STOP 0x0000007E" On a portable Windows Vista-based computer, you occasionally receive an error message that resembles the following: STOP 0x0000007E(c0000005, 0, a16bb8d4, a16bb5d0) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED This problem occurs if the following conditions are true: The computer is running a program or a service that periodically wakes the computer from sleep to perform tasks and then puts the computer to sleep again. The tasks are network-related or require network connectivity. The computer uses a wireless connection for network connectivity.
	Error message when you repeatedly restart a Windows Vista-based computer: "Stop 0x0000007E" When you repeatedly restart a Windows Vista-based computer, you receive a "Stop 0x0000007E" error message.
	After the Terminal Services mirror driver is disconnected from a Windows Server 2008-based or Windows Vista-based remote computer, you receive a Stop error on the remote computer: "Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" You use a Terminal Services mirror driver to access a Windows Vista-based or a Windows Server 2008-based remote computer. After you disconnect the mirror driver from the remote computer, the remote computer may crash. In this case, you receive the following error message on the remote computer: Stop 0x0000007E (c0000005, Parameter2, Parameter3, Parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED For example, assume that you use Live Mesh to access a Windows Vista-based remote computer. After you disconnect the Live Mesh remote session from the remote computer, the remote computer crashes, and you receive the Stop error message.
	Stop error when a registry management problem occurs on a Windows Server 2008 or Windows Vista SP1-based computer: "0x0000007E" On a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008, you receive the following Stop error message: STOP 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) Additionally, the following event is logged in the System log: Source: Microsoft-Windows-WER-SystemErrorReporting Event ID: 1001 Task Category: None Level: Information Keywords: Classic Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xc0000005, <address>, <address>, <address>). A dump was saved in: <file path>.
	You receive a Stop error message and the computer automatically restarts after you move IIS logs directory to a mount point on a Windows Server 2008-based or Windows Vista SP1-based computer: "0x0000007E" Consider the following scenario: You create a mount point on a volume on a Windows Server 2008-based computer or on a Windows Vista SP1-based computer. You configure an Internet Information Services (IIS) log directory on this mount point. In this scenario, the Windows Server 2008-based computer or the Windows Vista SP1-based computer restarts unexpectedly, and you receive a "0x0000007E" Stop error message.
	Troubleshooting Stop error messages that may occur when you try to install Windows Vista This article discusses the Stop error messages that can occur when you try to install Windows Vista. This article describes the possible causes of each Stop error message. It also provides troubleshooting steps for each issue. Note that this article relates to several stop errors but includes an informative section on Stop: 0x0000007E.
	Stop error message when you plug a USB storage device into the USB port of a Windows Vista SP1-based or Windows Server 2008-based computer: "Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" When you plug a universal serial bus (USB) storage device into the USB port of a Windows Vista Service Pack 1 (SP1) or Windows Server 2008-based computer, the operating system may crash. Additionally, you may receive the following Stop error message: Stop 0x0000007E (Parameter1, Parameter2, Parameter3, Parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
	Stop error message after you add a new device that supports MSI-X interrupts on a computer that is running Windows Vista or Windows Server 2008: "0x0000007E" On a computer that is running Windows Vista or Windows Server 2008, you add a new device that supports MSI-X interrupts. However, after you do this, you occasionally receive the following Stop error message: Stop 0x0000007E (0xC0000005, parameter2, parameter3, parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED This problem may occur when a Plug and Play (PNP) resource rebalance occurs. A PNP resource rebalance may be triggered in many scenarios. For example, this behavior may occur when you install the driver for a device that supports MSI-X interrupts, or when you restart the computer after you install a new MSI-X supported device.
	Stop error when you attach a Niveus Ice Vault Disc Changer to a Windows Vista SP1-based computer or to a Windows Server 2008-based computer: "STOP: 0x0000007E" On a Windows Vista SP1-based computer or on a Windows Server 2008-based computer, you have update 941649 or update 944020 installed. When you try to attach a Niveus Ice Vault Disc Changer to this computer, the operating system may stop responding. Additionally, you receive the following Stop error message: STOP: 0x0000007E (C0000005, Parameter2, Parameter3, Parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
	A Windows Vista or Windows Server 2008 portable computer does not automatically re-enter sleep mode after you undock the computer when it is asleep Consider the following scenario: You run Windows Vista or Windows Server 2008 on a portable computer that is equipped with a docking station. The portable computer is docked, and a USB mouse is plugged into the docking station. You put the computer to sleep, and then you undock the computer. In this scenario, the computer is not undocked correctly. When you undock the computer while it is asleep, the computer should resume and then automatically re-enter sleep mode. The computer resumes as expected, but does not automatically re-enter sleep mode. Eventually, the LCD screen turns blank. Sometimes, you receive the following Stop error message: Stop 0x0000007E (c0000005, parameter2, parameter3, parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

0x0000007F UNEXPECTED_KERNEL_MODE_TRAP 0x7F

	Error message when you try to print after you install the GDI security update 925902: "Stop 0x0000007F" Microsoft is aware of an issue that affects a limited number of printer drivers. When you try to print by using one of these drivers after you install security update 925902, you may experience the following symptoms. Your computer automatically restarts. After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. If the error message still appears, and you want to see the data that the error report contains, click the click here link at the bottom of the message box. You see error signature information that may resemble the following: BCCode : 0x0000007f (0x00000000, 0x00000000, 0x00000000, 0x00000000) OSVer : 5_1_2600 SP : 0_0 Product : 256_1 You receive the following Stop error message: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: *** Stop 0x0000007f (0x00000000, 0x00000000, 0x00000000, 0x00000000) UNEXPECTED_KERNEL_MODE_TRAP When you view the System log in Event Viewer, you notice an Event ID 1003 entry that contains information that resembles the following: Date: date Source: System Error Time: time Category: (102) Type: Error Event ID: 1003 User: N/A Computer: computer name Description: Error code 0x0000007f (0x00000000, 0x00000000, 0x00000000, 0x00000000). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 30 30 30 30 30 30 35 00000MN 0020: 30 20 20 50 61 72 61 6d 0 Param 0028: 65 74 65 72 73 20 66 66 eters ff 0030: 66 66 66 66 64 31 2c
	Stop error when you put a Windows Vista SP1-based that has update 942567 into Sleep mode: "STOP: 0x0000007F" On a Windows Vista SP1-based computer, you have the Feature Pack for Wireless (update 942567) installed. On this computer, after you scan for about 25 Bluetooth devices, you try to put the computer into Sleep (S3) mode. In this scenario, you receive a Stop error message that resembles the following: STOP: 0x0000007F (0x00000008, parameter2, parameter3, parameter4) UNEXPECTED_KERNEL_MODE_TRAP
	Stop error when multiple third-party network drivers are installed on a computer that is running Windows Server 2008 or Windows Vista: "0x0000007F" or "0x0000008E" On a computer that is running Windows Server 2008 or Windows Vista, the system generates one of the following stop error codes and then restarts: 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP) 0x0000008E (KERNEL_MODE_EXCEPTION_NOT_HANDLED) This problem typically occurs when multiple third-party network drivers are installed on the computer. For example, this problem may occur when the following drivers are installed: •  VPN client drivers •  Firewall drivers •  Modem/ISDN drivers •  Other network security filter drivers
	Stop error message on a computer that is running Windows Vista or Windows Server 2008: "STOP: 0x0000007F"
	Stop error after you install KB951376, you use the Add Bluetooth Device Wizard, you find many Bluetooth devices, and then you try to put a Windows Vista-based or Windows Server 2008-based computer to sleep: "STOP 0x0000007F" Consider the following scenario. On a Windows Vista-based or Windows Server 2008-based computer, you install the hotfix that is described in KB951376. You use the Add Bluetooth Device Wizard to search for new devices, and you find many Bluetooth devices. Then, you try to put the computer to sleep (S3). In this scenario, you receive a Stop error that resembles the following: *** STOP: 0x0000007F (0x00000008, parameter2, parameter3, parameter4) UNEXPECTED_KERNEL_MODE_TRAP
	You receive occasional Stop errors after you install a driver that manages on-board flash memory on a Windows Vista-based computer On a Windows Vista-based computer, you install a third-party driver that manages on-board flash memory for ReadyDrive. After you install this third-party driver, you occasionally receive a Stop error message that resembles the following: *** STOP: 0x0000007F (parameter1, parameter2, parameter3, parameter4) UNEXPECTED_KERNEL_MODE_TRAP

0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x8E

	Stop error when multiple third-party network drivers are installed on a computer that is running Windows Server 2008 or Windows Vista: "0x0000007F" or "0x0000008E" On a computer that is running Windows Server 2008 or Windows Vista, the system generates one of the following stop error codes and then restarts: 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP) 0x0000008E (KERNEL_MODE_EXCEPTION_NOT_HANDLED) This problem typically occurs when multiple third-party network drivers are installed on the computer. For example, this problem may occur when the following drivers are installed: •  VPN client drivers •  Firewall drivers •  Modem/ISDN drivers •  Other network security filter drivers
	Error message when you try to shut down or to restart a Windows Vista-based portable computer that has Bluetooth devices installed: “Stop: 0x0000008E” Consider the following scenario: You are running a Windows Vista-based portable computer that has Bluetooth devices installed. You hot-plug a PCI ExpressCard device into the computer. You try to shut down or to restart the computer. In this scenario, you may receive the following error message: Stop: 0x0000008E (0xC0000005, 0x8A317B80, 0xA624B9E8, 0x00000000) bthport.sys - Address 8A317B80 base at 8A2F6000, DataStamp 4578eb6e
	Stop error when an application calls the NtGdiBitBlt function on a Windows Server 2008 or Windows Vista Service Pack 1-based computer: "0x0000008E" Consider the following scenario: You are running a Windows Server 2008 or Windows Vista SP1-based computer. An application on the computer calls the NtGdiBitBlt function in the Win32k.sys module. In this scenario, you receive a Stop error message that resembles the following: STOP 0x0000008E (parameter1, parameter2, parameter3, parameter4) KERNEL_MODE_EXCEPTION_NOT_HANDLED
	Error message when you run an application on a terminal server that is running Windows Server 2008 or Windows Vista with Service Pack 1: "Stop 0x0000008E" You use a Remote Desktop Protocol (RDP) session to log on to a terminal server that is running Windows Server 2008 or Windows Vista with Service Pack 1 (SP1). However, when you run an application, such as a Microsoft Visual FoxPro application, the terminal server may randomly crash. Additionally, you receive an error message that resembles the following: Stop 0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED

0x0000009F DRIVER_POWER_STATE_FAILURE 0x9F

	Error message when you put a Windows Vista-based computer to sleep while a PPP connection is active: "STOP 0x0000009F" You are using Point-toPoint Protocol (PPP) to connect to a network or to the Internet from a Windows Vista-based computer. If you put the computer to sleep while the PPP connection is active, the screen goes black. After approximately 10 minutes, your computer may restart, or you may receive a Stop error message that resembles the following: STOP 0x0000009F (parameter1, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE Alternatively, you are using PPP to connect to a network or to the Internet from a Windows Vista-based computer. When you are connected, if you try to install a firewall product or a VPN client software, the installation will fail. When your computer tries to sleep the screen goes black. After approximately 10 minutes, your computer may restart or you may receive a Stop error message that resembles the following: STOP 0x0000009F (parameter1, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE When this problem occurs, you may be using a traditional modem, an ADSL modem, or a cellular telephone to connect to a network or to the Internet.
	Stop error message when you run the "Common Scenario Stress with IO" test, print to a shared printer on the network, or perform a power management operation on a Windows Vista-based computer: "Stop 0x0000009F" You perform one of the following operations on a Windows Vista-based computer: •  Connect to a shared printer on the network, and then run the "Common Scenario Stress with IO" test in Driver Test Manager (DTM). •  Print to a shared printer on the network. •  Perform a power management operation. For example, you put the computer to sleep or into hibernation. Or, you wake the computer from sleep or from hibernation. In this scenario, you receive a Stop error message that resembles the following: *** STOP: 0x0000009F (parameter1, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE
	You receive a Stop error message when you put a Windows Vista-based computer to sleep or into hibernation, or when you resume the computer from sleep or from hibernation: "0x0000009F DRIVER_POWER_STATE_FAILURE" When you put a Windows Vista-based computer to sleep or into hibernation, or when you resume the computer from sleep or from hibernation, you receive a Stop error message that resembles the following: *** STOP: 0x0000009F (parameter1, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE
	Stop error message when you try to put a Windows Vista-based computer to sleep while a dial-up network connection is active: "STOP: 0x0000009F" When you try to put a Windows Vista-based computer to sleep while a dial-up network connection is active, the computer may crash. Additionally, you receive a Stop error message that resembles the following: STOP: 0x0000009F (parameter1, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE
	You receive a Stop 0x9F error when you wake a Windows Vista-based computer that is connected to an IEEE 1394-based device When you wake a Windows Vista-based computer from sleep, you may receive a Stop 0x9F error message that resembles the following: STOP 0x0000009F (parameter1, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE This problem occurs when a device that uses an Institute of Electrical and Electronics Engineering (IEEE) 1394 connection is connected to the computer. For example, the device may be a Maxtor One Touch II 300GB model external hard disk, an Apple iPod, or some other IEEE 1394-based device.
	A Windows Vista-based computer that uses a PCI-E graphics device may stop responding when you wake the computer from sleep When you wake a Windows Vista-based computer from sleep (S3), the computer may stop responding (hang). When this problem occurs, the screen first becomes black. Then, you may eventually receive a Stop error message that resembles the following: *** STOP: 0x0000009F(parameter1, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE This problem may occur if the following conditions are true: •  The computer is using a PCI-Express (PCI-E) graphics device. •  The computer's firmware grants native support to the operating system for PCI-E features. •  PCI-E Active State Power Management (ASPM) is enabled on the PCI-E graphics device. This problem may occur intermittently
	Error message when you put a Windows Vista-based or aWindows Server 2008-based computer to sleep, or you wake the computer up: "STOP: 0x0000009F" When you put a Windows Vista-based or a Windows Server 2008-based computer to sleep, or you wake the computer up from sleep, you may receive a Stop error message that resembles the following: *** STOP: 0x0000009F (parameter1, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE
	Error message when you try to resume a computer that is running Windows Vista or Windows Server 2008 from hibernation: "STOP 0x0000009F" Consider the following scenario: You have a computer that is running Windows Vista or Windows Server 2008. A compact flash (CF) card is plugged into a CF card slot on the computer. You try to resume the computer from hibernation (S4). In this scenario, the computer may stop responding instead of resuming correctly. Eventually, you may receive the following Stop error message: *** STOP: 0x0000009F (parameter1, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE This problem occurs only occasionally.
	The shutdown process does not finish, and you receive an error message on a computer that is running Windows Vista or Windows Server 2008: "Stop 0x0000009F" Consider the following scenario: You have a computer that is running Windows Vista or Windows Server 2008. A universal serial bus (USB) device is connected to the computer. You put the computer to sleep or into hibernation while a client application or driver is communicating with the USB device. You resume the computer and then try to shut down the computer. In this scenario, the system seems to be shutting down, but the shutdown process does not finish. The power LED does not go out even though the signal to the screen is already turned off and even though there is very little or no disk activity. Eventually, you receive the following Stop error message: Stop 0x0000009F (00000003, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE
	Various problems may occur after you disconnect a PCMCIA storage device when a Windows Vista-based computer is asleep Consider the following scenario. You connect a PCMCIA storage device to a Windows Vista-based computer. For example, the device may be a PCMCIA card reader. Next, you put the computer to sleep, disconnect the device from the computer, and then wake the computer from sleep. In this scenario, you may experience one of the following problems: The PCMCIA storage device is still listed in Windows Explorer, even though the device was disconnected. When you reconnect the PCMCIA storage device, the device does not work. The computer stops responding (hangs). After the computer has been running for a while, you receive a Stop error message that resembles the following: STOP 0x0000009F (parameter1, parameter2, parameter3, parameter4) DRIVER_POWER_STATE_FAILURE

0x000000A5 ACPI_BIOS_ERROR 0xA5

	Troubleshooting Stop error messages that may occur when you try to install Windows Vista This article discusses the Stop error messages that can occur when you try to install Windows Vista. This article describes the possible causes of each Stop error message. It also provides troubleshooting steps for each issue. Note that this article relates to several stop errors but includes an informative section on Stop: 0x000000A5.
	A Windows XP-based computer becomes unresponsive or displays a "STOP 0x000000A5" error message during system shutdown Note that the above article relates to Windows XP, however the article states that a similar issue can occur in Windows Vista, even though the Vista article does not mention Stop: 0x000000A5. The related Vista article is In Windows Vista Service Pack 1 or in Windows Server 2008, Secure Digital Input Output device drivers reload and may behave incorrectly after you resume the computer from hibernation or from sleep

0x000000A0 INTERNAL_POWER_ERROR 0xA0

	Stop error message when you put a Windows Vista-based computer in hibernation: "STOP: 0x000000A0 (0x00000009, 0xc0000001, 0x00000001, 0x00000000) INTERNAL_POWER_ERROR (a0)" When you put a Windows Vista-based computer in hibernation, Windows Vista may stop responding (hang). Additionally, you may receive a Stop error message that resembles the following: STOP: 0x000000A0 (0x00000009, 0xc0000001, 0x00000001, 0x00000000) INTERNAL_POWER_ERROR (a0) Arg1: 00000009, A fatal error occurred while preparing the hibernate file. Arg2: c0000001, Status code Arg3: 00000001, Mirroring phase Arg4: 00000000 This issue occurs if the computer has Intel 82801G ICH7-M Serial ATA storage controllers that are connected to the 2.5-inch hard disks.
	Stop error message when you try to put a Windows Vista-based computer or a Windows Server 2008-based computer into hibernation: "STOP: 0x000000A0 (0x00000009, 0xc000009a, 0x00000000, 0x00000000) INTERNAL_POWER_ERROR (a0)" When you try put a Windows Vista x86-based computer or a Windows Server 2008 x86-based computer into hibernation, you receive the following Stop error: Bugcheck code STOP: 0x000000A0 INTERNAL_POWER_ERROR (a0) The power policy manager experienced a fatal error. Arguments Arg1: 00000009, A fatal error occurred while preparing the hibernate file. Arg2: c000009a, Status Code: STATUS_INSUFFICIENT_RESOURCES. Virtual memory cannot be allocated Arg3: 00000000, Mirroring phase Arg4: 00000000

0x000000B8 ATTEMPTED_SWITCH_FROM_DPC

Error message when you wake Windows Vista from sleep: "STOP: 0x000000B8" When you wake a Windows Vista-based computer from sleep, you may receive a Stop error message that resembles the following: *** STOP: 0x000000B8 (parameter1, parameter2, parameter3, parameter4) ATTEMPTED_SWITCH_FROM_DPC This problem occurs if you have installed the update that is described in the following Microsoft Knowledge Base article: 929762 You receive a Stop 0x9F error when you wake a Windows Vista-based computer that is connected to an IEEE 1394-based device

0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY 0xBE

	FIX: Error message when you use an IEEE 1394-based scanner on a computer that is running Windows XP 64-bit, Windows Server 2003, or Windows Vista: 0x0000000A or 0x000000BE When you use an IEEE 1394-based scanner and run a 32-bit scanning program on a computer that is running Microsoft Windows XP 64-bit, Microsoft Windows Server 2003, you receive an error message on a blue screen that resembles one of the following: 0x0000000A: IRQL_NOT_LESS_OR_EQUAL 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY This problem occurs when the scanning program calls the DeviceIoControl function to send a IOCTL_SCSISCAN_CMD control code to the kernel mode driver. In Windows Vista, you may not experience the blue screen. When your scanning program calls the DeviceIoControl function to send an IOCTL_SCSISCAN_CMD control code to the kernel mode driver in Windows Vista, this call may not be completed successfully, and your scanning program does not work as expected. The exact symptom that is observed in the user interface depends on how your scanning software works when the DeviceIoControl function fails.
	Stop error when Windows Server 2008 or Windows Vista SP1 is running in a virtual machine, and the computer that is running the virtual machine has multiple processors: "0x000000BE" Consider the following scenario: Windows Server 2008 or a Windows Vista SP1 is running in a virtual machine. The computer that is running the virtual machine has multiple processors. In this scenario, the virtual machine may restart unexpectedly. Additionally, you may receive the following Stop error code: 0x000000BE

0x000000C1 SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

You receive a "STOP 0x0000010E" or "STOP 0x000000C1" error message on a Windows Vista-based computer or on a Windows Server 2008-based computer A Windows Vista-based computer or a Windows Server 2008-based computer may restart unexpectedly. Additionally, you may receive a Stop error message that resembles one of the following error messages: *** STOP: 0x0000010E (0x00000002, 0x00000001, 0x00000000, 0x00000000) VIDEO_MEMORY_MANAGEMENT_INTERNAL ***STOP: 0x000000C1 (0x9944efd0, 0x00000000, 0x00000030, 0x000000022} SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) This problem typically occurs when you are running an application that requires lots of graphics processing. For example, this problem may occur when you play a video game on the computer.

0x000000C2 BAD_POOL_CALLER 0xC2

Stop errors in Windows Vista or Windows Server 2008: “Stop: 0x00000018” or “STOP: 0x000000C2” On a computer that is running Windows Vista or Windows Server 2008, the operating system randomly crashes. Additionally, you receive one of the following Stop error messages: Stop: 0x00000018 (parameter1, parameter2, parameter3, parameter4) REFERENCE_BY_POINTER STOP: 0x000000C2 (parameter1, parameter2, parameter3, parameter4) BAD_POOL_CALLER

0x000000C4 DRIVER_VERIFIER_DETECTED_VIOLATION 0xc4

A memory leak occurs when you plug in and then unplug a USB camera from a computer that is running Windows Vista or Windows Server 2008 Consider the following scenario: You connect a universal serial bus (USB) camera to a computer that is running Windows Vista or Windows Server 2008. You plug in and then unplug the USB camera from the computer several times. In this scenario, system performance is slow. If you use the Driver Verifier (Verifier.exe) tool to verify the USB camera driver (Usbcamd2.sys), the computer crashes when you unplug the camera. Additionally, you receive the following Stop error message: *** Fatal System Error: 0x000000C4 (parameter1, parameter2, parameter3, parameter4) DRIVER_VERIFIER_DETECTED_VIOLATION

0x000000CA PNP_DETECTED_FATAL_ERROR

Stop error when you plug two infrared (IR) receivers into a computer that is running Windows Vista or Windows Server 2008: "STOP: 0x000000CA" When you plug two infrared (IR) receivers into a computer that is running Windows Vista or Windows Server 2008, the computer crashes. Additionally, you receive a Stop error that resembles the following: STOP: 0x000000CA (parameter1, parameter2, parameter3, parameter4) PNP_DETECTED_FATAL_ERROR

0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING 0xCE

You cannot install Windows Server 2008 on a computer that uses the Intel Xeon processor and that has the WHEA feature enabled Note that the article is for Windows Vista (SP1) even though title refers only to Windows Server 2008. When you try to install Windows Server 2008 on a computer that uses the Intel Xeon processor, the installation fails. This problem occurs if you have enabled the Windows Hardware Error Architecture (WHEA) feature on the computer. When this problem occurs, you receive the following stop error: 0x000000CE (parameter1, parameter2, parameter3, parameter4) DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS This issue affects the Bensley and FoxCove Intel platforms.

0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0xD1

	Troubleshooting Stop error messages that may occur when you try to install Windows Vista This article discusses the Stop error messages that can occur when you try to install Windows Vista. This article describes the possible causes of each Stop error message. It also provides troubleshooting steps for each issue. Note that this article relates to several stop errors but includes an informative section on 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL.
	Error message when you use an IPsec tunnel mode connection to communicate from a Windows Vista-based computer to another computer: "STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL" When you use an Internet Protocol security (IPsec) tunnel mode connection to communicate from a Windows Vista-based computer to another computer, the Windows Vista-based computer may restart. Also, you may receive an error message that resembles the following: STOP 0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL This problem occurs if you install antivirus filter drivers on the Windows Vista-based computer.
	Stop error message in Windows Server 2008, in Windows Vista, or in Windows Vista SP1: "0x000000D1" On a computer that is running Windows Server 2008, Windows Vista, or Windows Vista Service Pack 1 (SP1), you may receive the following Stop error message: 0x000000D1 ( parameter1 , parameter2 , parameter3 , parameter4 ) DRIVER_IRQL_NOT_LESS_OR_EQUAL
	Stop error message on a Windows Vista-based computer when you unplug the network cable: "STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL" You access the network from a Windows Vista-based computer. When your wireless network status is changing or when you unplug the physical network cable, the computer may crash. Additionally, you may receive a Stop error message that resembles the following: STOP 0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL
	Error message when you bring the computer out of the "Hibernate system" power state in Windows Vista: "Stop 0x000000D1" Consider the following scenario: You are running a Windows Vista-based portable computer that has multiple USB devices or that has a docking station that has multiple USB devices. You put the computer into the "Hibernate system" power state (S4). You bring the computer out of the S4 power state. In this scenario, you may receive the following error message on a blue screen: Stop 0x000000D1 ( parameter1 , parameter2 , parameter3 , parameter4 ) DRIVER_IRQL_NOT_LESS_OR_EQUAL Depending on the computer settings, the Windows Vista-based portable computer may restart automatically after the error message appears on the blue screen.
	Error message when multiple network adapters are configured to use static IP addresses on a computer that is running Windows Server 2008 SP2 or Windows Vista SP2: "0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL" Consider the following scenario: You have a computer that is running Windows Server 2008 Service Pack 2 (SP2) or Windows Vista SP2. The computer has multiple network adapters. Each network adapter is configured to use a static IP address. The TCP/IP Forwarding feature is enabled on this computer. In this scenario, a Stop error occurs and the operating system automatically restarts. Then, you receive the following Stop error: 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL This problem typically occurs when you restart the computer or when third-party teaming software switches the active network adapter.
	In Virtual Server 2005 R2, virtual machines that are running Windows Vista guest operating systems display a "Stop 0x000000D1" error message and then restart unexpectedly Consider the following scenario: Some virtual machines in a Microsoft Virtual Server 2005 R2 environment are running Windows Vista guest operating systems. The latest version of Virtual Machine Additions is installed on these virtual machines. You restart multiple Windows Vista guest operating systems at the same time. In this scenario, the Windows Vista guest operating systems restart unexpectedly after the following Stop error message is displayed: Stop 0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL
	Stop error when you execute some common Plug and Play functions on a Windows Vista-based or a Windows Server 2008-based computer: "STOP 0x000000D1" or "STOP 0x000000FE" On a Windows Vista-based or a Windows Server 2008-based computer, you use the Driver Verifier Manager (verifier.exe) tool to verify the USBSer.sys driver. When you execute some common Plug and Play (PnP) functions, such as the following functions, the operating system crashes: •  The remove function •  The surprise remove function •  The rebalance function Additionally, you receive one of the following Stop error messages: STOP 0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP 0x000000FE (parameter1, parameter2, parameter3, parameter4) BUGCODE_USB_DRIVER
	Stop error 0xD1 may occur on a computer that is running Windows Vista or Windows Server 2008 On a computer that is running Windows Server 2008 or Windows Vista, you may receive the following Stop error: STOP 0x000000D1 (<parameter1>, <parameter2>, <parameter3>, <parameter4>) DRIVER_IRQL_NOT_LESS_OR_EQUAL This problem usually occurs when the Netbt.sys driver is loaded and unloaded frequently.
	A computer that is running an x64-based version of Windows Server 2003 or of the original release version of Windows Vista randomly restarts and then generates a Stop error A computer that is running an x64-based version of Windows Server 2003 or of the original release version of Windows Vista randomly restarts and then generates a Stop error. The Stop error code may be 0x0000001E, 0x000000D1, or another Stop error code. This problem occurs after you install update 932596 on the computer.
	An isochronous data transfer through an IEEE 1394 device suddenly stops in Windows Vista or in Windows Server 2008 When you perform an isochronous data transfer to or from an IEEE 1394 device on a computer that is running Windows Vista or Windows Server 2008, the isochronous data transfer suddenly stops. If you have enabled the Driver Verifier for the driver that the device uses to perform the isochronous data transfer, the operating system crashes. Additionally, you receive the following Stop error message on a blue screen: STOP 0x000000D1 (parameter1, 00000002, 00000001, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL ohci1394.sys
	A computer that is running Windows Server 2008 or Windows Vista may restart repeatedly with different Stop error codes when multicast forwarding is enabled Consider the following scenario: You have a computer that is running Windows Server 2008 or Windows Vista. Multicast forwarding is enabled. In this scenario, the system may restart repeatedly with different Stop error codes, such as 0x0000001E or 0x000000D1. Or, the system may stop responding. This problem does not occur if you disable multicast forwarding.

0x000000E3 RESOURCE_NOT_OWNED 0xE3

You receive a "Stop 0x000000E3" error message when Symantec Endpoint Protection MR2 quarantines a file in Windows Vista or in Windows Server 2008 You may receive a "Stop 0x000000E3" error message that resembles the following on a computer that is running Windows Vista or Windows Server 2008: STOP: 0x000000E3 (parameter1, parameter2, parameter3, parameter4) The RESOURCE_NOT_OWNED This problem may occur on a computer that is running Symantec Endpoint Protection version 11.0 Maintenance Release 2 (MR2). This problem occurs when the Symantec program quarantines a file.

0x000000FE BUGCODE_USB_DRIVER

	Stop error when you execute some common Plug and Play functions on a Windows Vista-based or a Windows Server 2008-based computer: "STOP 0x000000D1" or "STOP 0x000000FE" On a Windows Vista-based or a Windows Server 2008-based computer, you use the Driver Verifier Manager (verifier.exe) tool to verify the USBSer.sys driver. When you execute some common Plug and Play (PnP) functions, such as the following functions, the operating system crashes: •  The remove function •  The surprise remove function •  The rebalance function Additionally, you receive one of the following Stop error messages: STOP 0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP 0x000000FE (parameter1, parameter2, parameter3, parameter4) BUGCODE_USB_DRIVER
	Error message when you try to put a Windows Vista-based computer to sleep or into hibernation: "STOP 0x000000FE BUGCODE_USB_DRIVER" When you try to put a Windows Vista-based computer to sleep or into hibernation, you receive an error message that resembles the following: STOP 0x000000FE(parameter1, parameter2, parameter3, parameter4) BUGCODE_USB_DRIVER
	Error message when you connect a portable Windows Vista-based computer to a docking station: "STOP: 0x000000fe" When you connect a portable Windows Vista-based computer to a docking station, you may receive a Stop error message that resembles the following: *** STOP: 0x000000fe (0x00000006, parameter2, 0x48676643, 0x00000000) BUGCODE_USB_DRIVER This problem occurs if at least one of the following conditions is true: The computer uses a built-in charge-coupled device (CCD) or a built-in card-reader. A digital camera is connected to the computer through a universal serial bus (USB) cable.
	Error message on a Windows Vista-based computer that is running a USB composite device: "STOP 0x000000FE" On a Windows Vista-based computer that is running a USB composite device, you may receive a Stop error message that resembles the following: STOP 0x000000FE (parameter1, parameter2, parameter3, parameter4) BUGCODE_USB_DRIVER This problem may occur if the USB composite device has the Selective Suspend feature enabled. This problem occurs even though the USB composite device supports the Selective Suspend feature.
	Error message when you bring the computer out of the "Hibernate system" power state in Windows Vista: "Stop 0x000000FE" Consider the following scenario: You are running a Windows Vista-based portable computer that has multiple USB devices or that has a docking station that has multiple USB devices. You put the computer into the "Hibernate system" (S4) power state. You bring the computer out of the S4 power state. In this scenario, you may receive the following stop error message on a blue screen: Stop 0x000000FE (parameter1, parameter2, parameter3, parameter4) BUGCODE_USB_DRIVER
	Stop error when you resume a computer that is running Windows Vista from standby: "STOP 0x000000FE (parameter1, parameter2, parameter3, parameter4)" Consider the following scenario: You use some embedded USB devices on a computer that is running Windows Vista. You put the system into standby. You resume the computer from standby. In this scenario, you may receive a Stop error that resembles the following: STOP 0x000000FE (parameter1, parameter2, parameter3, parameter4)
	Stop error when a Windows Vista-based or Windows Server 2008-based computer enters sleep mode: "Stop 0x000000FE BUGCODE_USB_DRIVER" You are running a Windows Vista-based or a Windows Server 2008-based computer that has an internal USB device installed. When the computer enters sleep mode, the computer may stop responding. Additionally, you may receive the following Stop error: Stop 0x000000FE (00000008, 00000006, 00000002, parameter4) BUGCODE_USB_DRIVER
	Stop error message on a Windows Vista-based or Windows Server 2008-based computer when you resume the system from sleep: Stop 0x000000FE On a computer that is running Windows Vista or Windows Server 2008, you receive the following Stop error message when you resume the system from sleep mode: Stop 0x000000FE (00000008, 00000006, 00000001, parameter4) BUGCODE_USB_DRIVER The parameters in this Stop error message may vary, depending on the configuration of your computer. Typically, the first three parameters are 8, 6 and 1. However, the fourth parameter varies. The symptoms of the Stop error may vary, depending on your computer's system failure options. For example, your computer may restart when the Stop error occurs.
	Stop error after you upgrade from Windows Vista Service Pack 1 to Windows Vista Service Pack 2 or from Windows Server 2008 to Windows Server 2008 Service Pack 2: "Stop 0x000000FE BUGCODE_USB_DRIVER" After you upgrade from Windows Vista Service Pack 1 (SP1) to Windows Vista SP2 or from Windows Server 2008 to Windows Server 2008 SP2, your computer crashes frequently and you receive the following stop error message: Stop 0x000000FE (parameter1, parameter2, parameter3, parameter4) BUGCODE_USB_DRIVER This problem usually occurs on computers that have NVIDIA chipsets. Additionally, this problem may occur when you perform very basic operations, such as plugging in a USB keyboard.
	A computer that is running Windows Vista or Windows Server 2008 restarts automatically and generates a Stop error after you repeatedly plug and hot-unplug a USB device: "0x000000FE" Consider the following scenario: A USB device is installed on a computer that is running Windows Vista or Windows Server 2008. The USB device works correctly. You plug and then hot-unplug (surprise remove) this USB device several times. After you plug the USB device into the USB port in this scenario, the device does not appear in Device Manager. Additionally, the device does not work. If you try to shut down the computer on the Start menu, or if you make additional surprise removal attempts, the system generates the following Stop error message and then automatically restarts: Stop 0x000000FE (Parameter1, Parameter2, Parameter3, Parameter4)
	A USB-connected Portable Media Center device no longer works after you resume a Windows Vista-based computer from sleep After you resume a Windows Vista-based computer from sleep, a USB-connected Portable Media Center device no longer works. This problem occurs after you install the hotfix that is described in either of the following Microsoft Knowledge Base articles: 930568 Error message when you try to put a Windows Vista-based computer to sleep or into hibernation: "STOP 0x000000FE BUGCODE_USB_DRIVER" 929734 You may experience problems after you resume a Windows Vista-based computer from sleep or from hibernation When this problem occurs, you may receive an error message in Device Manager. This error message resembles the following: Windows has stopped this device because it has reported problems. (Code 43) Recommended resolution One of the drivers controlling the device notified the operating system that the device failed in some manner. For more information about how to diagnose the problem, see the hardware documentation.
	Stop error message when a Windows Vista-based computer that has a USB device attached resumes from standby or from hibernation: "Stop 0x000000FE ( 00000008 , 00000006 , 00000001 , parameter4 )" Consider the following scenario: You are running a Windows Vista-based computer. This computer has a USB device, such as a USB fingerprint reader, attached. You resume the computer from standby or from hibernation, In this scenario, you may receive the following Stop error message: Stop 0x000000FE ( 00000008 , 00000006 , 00000001 , parameter4 ) BUGCODE_USB_DRIVER Note In this error, the value of the Parameter4 placeholder may vary.

0x00000101 CLOCK_WATCHDOG_TIMEOUT

Stop error message on a Windows Vista or Windows Server 2008-based computer that has multiple processors installed: "STOP: 0x00000101 CLOCK_WATCHDOG_TIMEOUT" On a Windows Vista or Windows Server 2008-based computer that has multiple processors installed, you may encounter a system crash problem. When this problem occurs, you may receive a Stop error message which resembles the following: *** STOP: 0x00000101 (Prameter1, Prameter2, Prameter3, Prameter4) CLOCK_WATCHDOG_TIMEOUT

0x0000010E VIDEO_MEMORY_MANAGEMENT_INTERNAL

You receive a "STOP 0x0000010E" or "STOP 0x000000C1" error message on a Windows Vista-based computer or on a Windows Server 2008-based computer A Windows Vista-based computer or a Windows Server 2008-based computer may restart unexpectedly. Additionally, you may receive a Stop error message that resembles one of the following error messages: *** STOP: 0x0000010E (0x00000002, 0x00000001, 0x00000000, 0x00000000) VIDEO_MEMORY_MANAGEMENT_INTERNAL ***STOP: 0x000000C1 (0x9944efd0, 0x00000000, 0x00000030, 0x000000022} SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) This problem typically occurs when you are running an application that requires lots of graphics processing. For example, this problem may occur when you play a video game on the computer.

0x00000124

	A "0x00000124" Stop error message occurs when you use the "hot plugging" feature to add or to remove a PCI Express device on a Windows Server 2008-based computer or on a Windows Vista-based computer Consider the following scenario: You have a Peripheral Component Interconnect (PCI) Express interface that supports the "hot plugging" feature on a Windows Server 2008-based computer or on a Windows Vista-based computer. You connect a device to the root port of the PCI Express interface. You use the "hot plugging" feature to add or to remove a PCI Express device on the computer. In this scenario, the Windows Server 2008-based computer or the Windows Vista-based computer may be restarted unexpectedly. Additionally, you receive the following error message: 0x00000124 When you restart a Windows Server 2008-based computer or a Windows Vista-based computer, the issue may also occur if a PCI device is connected to the root port of the PCI-Express bus on the computer.
	Stop error message when you use the Safely Remove Hardware option to remove a PCI Express device that supports hot plugging on a computer that is running Windows Server 2008 or Windows Vista: "0x00000124" Consider the following scenario: You have a computer that is running Windows Server 2008 or Windows Vista. You have a Peripheral Component Interconnect (PCI) Express device that supports hot plugging. Note With Windows Server 2008 and with Windows Vista, you can add a device to a computer while the computer is running, and the operating system automatically recognizes the change. This is known as hot plugging. You connect the PCI Express device to the computer. In this scenario, when you use the Safely Remove Hardware option to remove the PCI Express device, you receive the following Stop error message: 0x00000124 Additionally, the computer may restart unexpectedly.

0x0000C1F5

	Stop error message when you start a Windows Vista-based computer: "0x0000C1F5" When you start a Windows Vista-based computer, you receive the following Stop error message on a blue screen: 0x0000C1F5
	Stop error when you start a Windows Vista-based computer even though hotfix 946084 is installed on the computer: "0x0000C1F5" When you start a Windows Vista-based computer, you receive the following Stop error message on a blue screen even though hotfix 946084 is installed on the computer: 0x0000C1F5 This problem also occurs when you start Windows Vista from a Microsoft Windows Preinstallation Environment (Windows PE) 2.1 image. Note This issue occurs if the $TxfLog file is corrupted. When this issue occurs, you have to remove the hard disk that contains the corrupted $TxfLog file to start the computer.
	How to work around Stop Error 0x0000C1F5 on a Windows Vista-based computer When you start a Windows Vista-based computer, you receive the following Stop error message on a blue screen: 0x0000C1F5

0x1000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

Stop error message when you send or receive e-mail messages on a Windows Vista-based computer that has e-mail scanning software installed: "STOP: 0x1000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED_M" Consider the following scenario: You are running a Windows Vista Service Pack 1 (SP1)-based computer. Antivirus and antispyware with e-mail scanning software is installed on the computer. An e-mail client, such as Microsoft Office Outlook or Windows Mail, is configured to receive POP3 or SMTP e-mail messages. When you start the e-mail client, or when you try to send or receive e-mail messages, Windows Vista crashes. Additionally, you receive the following Stop error message: STOP: 0x1000008E (Parameter1, Parameter2, Parameter3, Parameter4) In TCPIP.SYS KERNEL_MODE_EXCEPTION_NOT_HANDLED_M Note This issue does not occur if one of the following conditions is true: •  The e-mail client is configured to receive HTTP e-mail messages instead of POP3 or SMTP e-mail messages. •  The e-mail client works offline.

0x80070246 ERROR_ILLEGAL_CHARACTER

Stop error when you try to download updates from Windows Update on a computer that is running Windows Vista: "0x80070246" When you try to download updates from Windows Update on a computer that is running Windows Vista, you may receive the following Stop error message: STOP 0x80070246 ERROR_ILLEGAL_CHARACTER Additionally, the following entry may be logged in the WindowsUpdate.log file: Automatic Updates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070246: "Name of Update"

0xC0000218 UNKNOWN_HARD_ERROR

Registry troubleshooting steps for advanced users This article describes how to troubleshoot registry corruption issues. If your computer does not restart, the registry hives may be corrupted. The error messages may vary. They can include any of the following: Windows could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced Windows could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEM Windows could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SOFTWARE System hive error Stop 0xc0000218 (0xe11a30e8, 0x00000000, 0x000000000, 0x00000000) UNKNOWN_HARD_ERROR Stop: 0xc0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\CorruptHive or its log or alternate. It is corrupt, absent, or not writable.