XP Error

Error messages
You may receive one or more of the following errors when you use Network
Connections. The following error messages are not available on the Web. They are meant
to be viewed in Help and Support Center on Windows XP Professional. To view them on
your Windows XP Professional computer, click Start, click Help and Support, type
network error messages into the Search box, and then select the topic you want.
600 An operation is pending
601 An invalid port handle was detected
602 The specified port is already open
603 The caller's buffer is too small
604 Incorrect information was specified
605 The port information cannot be set
606 The specified port is not connected
607 An invalid event is detected
608 A device was specified that does not exist
609 The device type was specified that does not exist
610 An invalid buffer was specified
611 A route was specified that is not available
612 A route was specified that is not allocated
613 An invalid compression was specified
614 There were insufficient buffers available
615 The specified port was not found

616 An asynchronous request is pending
617 The modem is already disconnecting
618 The specified port is not open
619 The specified port is not connected
620 No endpoints could be determined
621 The system could not open the phonebook
622 The system could not load the phonebook
623 The system could not find the phonebook entry for this connection
624 The system could not update the phonebook file
625 The system found invalid information in the phonebook
626 A string could not be loaded
627 A key could not be found
628 The connection was closed
629 The connection was closed by the remote computer
630 The modem was disconnected due to hardware failure
631 The user disconnected the modem
632 An incorrect structure size was detected
633 The modem is already in use or is not configured for dialing out
634 Your computer could not be registered on the remote network
635 There was an unknown error
636 The device attached to the port is not the one expected
637 A string was detected that could not be converted
638 The request has timed out

639 No asynchronous net is available
640 A error has occurred involving NetBIOS
641 The server cannot allocate NetBIOS resources needed to support the client
642 One of your computer's NetBIOS names is already registered on the remote network
643 A network adapter at the server failed
644 You will not receive network message popups
645 There was an internal authentication error
646 The account is not permitted to log on at this time of day
647 The account is disabled
648 The password for this account has expired
649 The account does not have permission to dial in
650 The remote access server is not responding
651 The modem has reported an error
652 There was an unrecognized response from the modem
653 A macro required by the modem was not found in the device .INF file section
654 A command or response in the device .INF file section refers to an undefined macro
655 The <MESSAGE> macro was not found in the device .INF file section
656 The <DEFAULTOFF> macro in the device .INF file section contains an undefined
macro
657 The device .INF file could not be opened
658 The device name in the device .INF or media .INI file is too long
659 The media .INI file refers to an unknown device name
660 The device .INF file contains no responses for the command
661 The device .INF file is missing a command

662 There was an attempt to set a macro not listed in the device .INF file section
663 The media .INI file refers to an unknown device type
664 The system has run out of memory
665 The modem is not properly configured
666 The modem is not functioning
667 The system was unable to read the media .INI file
668 The connection was terminated
669 The usage parameter in the media .INI file is invalid
670 The system was unable to read the section name from the media .INI file
671 The system was unable to read the device type from the media .INI file
672 The system was unable to read the device name from the media .INI file
673 The system was unable to read the usage from the media .INI file
674 The system was unable to read the maximum connection BPS rate from the media
.INI file
675 The system was unable to read the maximum carrier connection speed from the
media .INI file
676 The phone line is busy
677 A person answered instead of a modem
678 There was no answer
679 The system could not detect the carrier
680 There was no dial tone
681 The modem reported a general error
691 Access was denied because the user name and/or password was invalid on the
domain
692 There was a hardware failure in the modem

695 The state machines are not started
696 The state machines are already started
697 The response looping did not complete
699 The modem response caused a buffer overflow
700 The expanded command in the device .INF file is too long
701 The modem moved to a connection speed not supported by the COM driver
703 The connection needs information from you, but the application does not allow user
interaction
704 The callback number is invalid
705 The authorization state is invalid
707 There was an error related to the X.25 protocol
708 The account has expired
709 There was an error changing the password on the domain. The password might have
been too short or might have matched a previously used password
710 Serial overrun errors were detected while communicating with the modem
711 The Remote Access Service Manager could not start. Additional information is
provided in the event log
712 The two-way port is initializing. Wait a few seconds and redial
713 No active ISDN lines are available
714 No ISDN channels are available to make the call
715 Too many errors occurred because of poor phone line quality
716 The remote access service IP configuration is unusable
717 No IP addresses are available in the static pool of remote access service IP addresses
718 The connection timed out waiting for a valid response from the remote computer
719 The connection was terminated by the remote computer

720 The connection attempt failed because your computer and the remote computer could
not agree on PPP control protocols
721 The remote computer is not responding
722 Invalid data was received from the remote computer. This data was ignored
723 The phone number, including prefix and suffix, is too long
726 The IPX protocol cannot be used for dial-out on more than one modem at a time
728 The system cannot find an IP adapter
729 SLIP cannot be used unless the IP protocol is installed
731 The protocol is not configured
732 Your computer and the remote computer could not agree on PPP control protocols
733 Your computer and the remote computer could not agree on PPP control protocols
734 The PPP link control protocol was terminated
735 The requested address was rejected by the server
736 The remote computer terminated the control protocol
737 Loopback detected
738 The server did not assign an address
739 The authentication protocol required by the remote server cannot use the stored
password. Redial, entering the password explicitly
740 An invalid dialing rule was detected
741 The local computer does not support the required data encryption type
742 The remote computer does not support the required data encryption type
743 The remote server requires data encryption
751 The callback number contains an invalid character. Only the following characters are
allowed: 0 to 9, T, P, W, (,), -, @, and space
752 A syntax error was encountered while processing a script

753 The connection could not be disconnected because it was created by the multi-
protocol router
754 The system could not find the multi-link bundle
755 The system cannot perform automated dial because this entry has a custom dialer
specified
756 This connection is already being dialed
757 Remote access services could not be started automatically. Additional information is
provided in the event log
758 Internet Connection Sharing is already enabled on the connection
760 An error occurred while routing capabilities were being enabled
761 An error occurred while Internet Connection Sharing was being enabled for the
connection
763 Internet Connection Sharing cannot be enabled. There are two or more LAN
connections in addition to the connection to be shared
764 No smart card reader is installed
765 Internet Connection Sharing cannot be enabled. A LAN connection is already

configured with the IP address required for automatic IP addressing
766 The system could not find any certificate
767 Internet Connection Sharing cannot be enabled. The LAN connection selected on the
private network has more than one IP address configured. Reconfigure the LAN
connection with a single IP address before enabling Internet Connection Sharing
768 The connection attempt failed because of failure to encrypt data
769 The specified destination is not reachable
770 The remote machine rejected the connection attempt
771 The connection attempt failed because the network is busy
772 The remote computer's network hardware is incompatible with the type of call
requested
773 The connection attempt failed because the destination number has changed
774 The connection attempt failed because of a temporary failure. Try connecting again
775 The call was blocked by the remote computer
776 The call could not be connected because the destination has invoked the Do Not
Disturb feature
777 The connection attempt failed because the modem on the remote computer is out of
order
778 It was not possible to verify the identity of the server
779 To dial out using this connection, you must use a smart card
780 An attempted function is not valid for this connection
781 The encryption attempt failed because no valid certificate was found
782 Network Address Translation (NAT) is currently installed as a routing protocol, and
must be removed before enabling Internet Connection Sharing
783 Internet Connection Sharing cannot be enabled. The LAN connection selected as the
private network is either not present, or is disconnected from the network. Please ensure
that the LAN adapter is connected before enabling Internet Connection Sharing
784 You cannot dial using this connection at logon time, because it is configured to use a
user name different than the one on the smart card. If you want to use it at logon time,
you must configure it to use the user name on the smart card
785 You cannot dial using this connection at logon time, because it is not configured to
use a smart card. If you want to use it at logon time, you must edit the properties of this
connection so that it uses a smart card
786 The L2TP connection attempt failed because there is no valid machine certificate on
your computer for security authentication
787 The L2TP connection attempt failed because the security layer could not authenticate
the remote computer
788 The L2TP connection attempt failed because the security layer could not negotiate
compatible parameters with the remote computer
789 The L2TP connection attempt failed because the security layer encountered a
processing error during initial negotiations with the remote computer
790 The L2TP connection attempt failed because certificate validation on the remote
computer failed
791 The L2TP connection attempt failed because security policy for the connection was
not found
792 The L2TP connection attempt failed because security negotiation timed out
793 The L2TP connection attempt failed because an error occurred while negotiating
security
794 The Framed Protocol RADIUS attribute for this user is not PPP
795 The Tunnel Type RADIUS attribute for this user is not correct
796 The Service Type RADIUS attribute for this user is neither Framed nor Callback
Framed
797 A connection to the remote computer could not be established because the modem
was not found or was busy
798 A certificate could not be found that can be used with this Extensible Authentication
Protocol
799 Internet Connection Sharing (ICS) cannot be enabled due to an IP address conflict on
the network. ICS requires the host be configured to use 192.168.0.1. Please ensure that no
other client on the network is configured to use 192.168.0.1
800 Unable to establish the VPN connection. The VPN server may be un-reachable, or
security parameters may not be configured properly for this connection
Error Message: Connection Successful!

Solution: Does not require any repairs.
• Error #2
Error Message: System cannot find specified file

Solution: You should reinstall NCP & DUN
• Error #5
Error Message: Access Denied
Solution:
1. Ensure that you have entered the right username and password in the field labeled
"domain" for NT/2k.
2. Check that the option "accept any authentication including clear text" is activated.
• Error #5
Error Message: Invalid Procedure Call

Solution: Dialup and Network components must be installed again
• Error #6
Error Message: Stack Overflow

Solution:
1. Try cold booting your computer.
2. If this does not work, the problem might come from your RAM or the Swap file.
• Error #20
Error Message: The system cannot find the specified device

Solution:
1. Ensure that the right modem has been selected.
2. If it does not respond, try to reinstall it.
3. You can also try to reinstall NCP/DUN/RAS.
• Error #71
Error Message: No more connections is allowed

Solution:
1. Someone else might have connected under your account.
2. If you have been ghosted on the server, your Internet Service Provider can bump the
ghost program off.
• Error #380
Error Message: Invalid Proper Value

Solution:
1. Autodial should be pointed to the correct dialer.
2. Else, set up the dialer again.
• Error #600
Error Message: An operation is pending

Solution:
1. You should first try to reboot your computer.
2. Ensure that no other program is using your modem.
3. Else press Ctrl-Alt-Delete and if RNAAPP loads, contact a technician to fix this
problem.
4. Make sure that your computer is Spyware free.
• Error #601
Error Message: The port handle is invalid

Solution:
1. Select the modem's COM port and under the Diagnosis section, open More InfoYou
should reboot your computer if you are able to get Ati# responses. Hence, remove the
erroneous init string or enter ATZ as the init.
2. You can also reinstall your modem
problem.
4. Your Dialup Networking should be installed again together with its components
5. Your modem might not be working properly. You should then consult your computer
manufacturer.
• Error #602
Error Message: The port is already open

Solution:
1. Try to reboot your computer
2. Ensure that no other program is using the modem
problem
4. Try uninstalling the AOL Adapters in the Network Control panel and reboot your
computer. Install your Dialup Adapter again.
5. Remove the erroneous init string or enter ATZ as the init.
6. If you have Quicken 2000, deactivate the Quicken Download Manager.
7. You should maybe install your modem again.
8. Make sure that your computer is Spyware free.
• Error #603
Error Message: Caller's buffer is too small

Solution:
1. Ensure that your port speed is not configured to a low speed
2. In your "Port Settings", ensure that FIFO is not set to low.
3. Your Dialup Networking should perhaps be installed again together with its
components
4. If you are still having problems, contact your computer manufacturer.
• Error #604
Error Message: Wrong information specified.

Solution:
1. Ensure that the are no outages within your area
2. Try to enter the username and password again
3. Set up the dialer again
5. You can also try to reinstall your modem
• Error #605
Error Message: Cannot set port information.

Solution:
1. Ensure that the are no outages within your area
2. Try to enter the username and password again
3. Set up the dialer again
5. You can also try to reinstall your modem
• Error #606
Error Message: The port is not connected.

Solution:
1. Select the modem's COM port and under the Diagnosis section, open "More Info". You
should reboot your computer if you are able to get Ati# responses. Hence, remove the
erroneous init string or enter ATZ as the init.
2. You can also reinstall your modem
problem.
4. Your modem might not be working properly. You should then consult your computer
manufacturer if the problem persists.
• Error #607
Error Message: The event is invalid.
Solution:
1. If this problem arises while dialing up to the internet, verify that the settings of the
event log have been correctly set.
2. Try rebooting your system and ensure that the dialer/network settings have been
correctly configured
3. Else, install RAS/DUN again.
• Error #608
Error Message: The device does not exist.

Solution:
1. Check that the right modem is set in the dialer
2. Ensure that you are using the right modem drivers by checking the modem diagnostics.
If it's not the case, set up the correct drivers.
3. Remove and install the dialer again
4. Your modem might not be working properly; try to install it again.
5. You should then consult your computer manufacturer if the problem persists.
• Error #609
Error Message: The device type does not exist.

Solution:
1. Check that the right modem is selected in the dialer
2. Ensure that you are using the right modem drivers by checking the modem diagnostics.
If it's not the case, set up the correct drivers.
3. Your modem might not be working properly; try to install it again.
• Error #610
Error Message: The buffer is invalid.

Solution:
1. Ensure that your port speed is set to low in the modem properties.
2. In your "Port Settings", check that FIFO is not set to low.
3. Remove and install the dialer again.
4. Else, install RAS/DUN again.
• Error #611
Error Message: The route is not available.
Solution:
2. Ensure that you set the right configurations for the dialer and network settings.
3. Else, install the network components again.
4. If you are using a LAN connection, consult your system administrator.
• Error #612
Error Message: The route is not allocated.

Solution:
1. Reboot your computer
2. Ensure that you set the right configurations for the dialer and network settings.
• Error #613
Error Message: Invalid compression specified.

Solution:
2. Else, add &K3 to the extra settings.
3. If this still does not solve the problem, add &K3
4. You can also try to reinstall the modem.
• Error #614
Error Message: Out of buffers.

Solution:
1. Ensure that our port speed is not too low.
2. Try to install your modem again.
• Error #615
Error Message: The port was not found.

Solution: Try to install your modem drivers.
• Error #616
Error Message: An asynchronous request is pending.

Solution:
1. Reboot your computer.
2. Try to install your modem drivers again.
• Error #617
Error Message: The port or device is already disconnecting

Solution:
1. Wait until your modem disconnects properly.
2. If this operation is taking too long, reboot your computer.
• Error #618
Error Message: The port is not open.

Solution:
2. Ensure that no other program is making use of the modem.
• Error #619
Error Message: The port is disconnected.

Solution:
2. Ensure that no other program is making use of the modem.
• Error #621
Error Message: Cannot open the phone book file.

Solution: Install Blue Frog connection software again.
• Error #622
Error Message: Cannot load the phone book file.

Solution: Install Blue Frog connection software again
• Error #623
Error Message: Cannot find the book entry.

• Error #626
Error Message: Cannot load a string
Solution:
1. Try to reboot your system.
2. Install Blue Frog connection software again
• Error #627
Error Message: Cannot find key

• Error #628
Error Message: The port was disconnected

Solution:
• Error #629
Error Message: The port was disconnected by the remote machine.

Solution:
2. Try to enter an alternate Access Number
• Error #630
Error Message: The port was disconnected due to hardware failure.

Solution:
2. Try to reinstall your modem drivers.
3. Try to use an alternate modem.
4. Else, replace your current modem with a new one.
• Error #631
Error Message: The port was disconnected by the user.

Solution:
1. Ensure that the right Access Number is being dialed.
2. Try to reboot your computer.
• Error #632
Error Message: The structure size is incorrect.

Solution:
• Error #633
Error Message: The port is already in use or is not configured for Remote Access
dialout.
Solution:
Try to reboot your computer
Else try to reinstall your modem drivers.
• Error #634
Error Message: Cannot register your computer on the remote network

Solution:
Try to check your network settings and modify your computer name.
Install the network control panel again.
• Error #635
Error Message: Unknown Error

Solution:
3. Else try to reinstall your modem drivers.
• Error #636
Error Message: The wrong device is attached to the port

Solution: Check in your settings if you have chosen the right modem.
• Error #637
Error Message: The string could not be converted

Solution:
Install Blue Frog connection software again
• Error #638
Error Message: The request has timed out.

Solution:
• Error #645
Error Message: Internal authentication error.

Solution:
3. Else try to reinstall your modem drivers.
• Error #650
Error Message: The Remote Access server is not responding.

Solution:
Check that your connection and network settings have correctly been configured.
Ensure that the modem has been correctly set up and look for updated drivers.
Set FIFO buffers to a lower speed and ensure that you have unchecked the option "Only
connect at this speed".
• Error #676
Error Message: The line is busy

Solution: Ensure that your Access Number is still active and is correctly dialed.
• Error #678
Error Message: There is no answer.

Solution:
1. First of all check that your phone lines are correctly plugged in.
2. Ensure that the Access Number is correct
3. Else, try another Access number
4. If you are trying to make use of your connection in a bad weather, this might be the
source of the problem. Wait until it calms down and try again.
5. Else, install your modem drivers again.
6. If the problem persists, you might need to contact your ISP.
• Error #680
Error Message: There is no dial tone.

Solution:
First of all check that your phone lines are correctly plugged in.
The phone lines might be damaged. Replace them and try again.
Else, install your modem drivers again.
If the problem persists, you might need to contact your ISP or a technician.
• Error #691
Error Message: Access denied because username and/or password is invalid on the
domain.
Solution:
1. Ensure that you have entered the right username and password.
2. Make sure that your account is active and turned on.
3. You might also try to enter another Access Number.
4. If the problem persists, you might need to contact your ISP.
• Error #692
Error Message: Hardware failure in port or attached device.

Solution:
Browse for and remove any Blue Frog init strings.
Else, install your modem drivers again.
• Error #718
Error Message: PPP Timeout

Solution:
2. Ensure that you have entered the right username and password
3. You might try another Access Number
5. Else, install your modem drivers again.
• Error #721
Error Message: Remote PPP peer is not responding.
Solution: For Windows 2000/XP/Vista operating systems, ensure that the security setting
for the dialer reads "Allow unsecured Password"
• Error #734
Error Message: The PPP link control protocol terminated.

Solution: For Windows 2000/XP/Vista operating systems, ensure that the security setting
for the dialer reads "Allow unsecured Password"
• Error #777
Error Message: The connection attempt failed because the modem on the remote
computer is out of order.
Solution:
2. Try an alternate modem
3. Install your modem drivers again
4. Else, install a new modem
• Error #778
Error Message: It was not possible to verify the identity of the server.
Solution:
1. Ensure that you are dialing the correct phone number
2. Verify the connection and Network settings
3. ensure that you do not have any outrage on the phone number
4. Ensure that you have correctly installed your modem and check for updated drivers.
5. Set FIFO buffers to a lower speed and ensure that you have unchecked the option
"Only connect at this speed".
• Error #779
Error Message: To dial out using this connection, you must use a smart card.
Solution:
1. Ensure that all auth is allowed in your connection settings in the Security section.
2. Verify that you have correctly set the other dialer settings.
3. Else, create the dialer again.
4. You might need to use the Smart Card Reader as initially setup by the Network
Administrator.
• Error #780
Error Message: An attempted function is not valid for this connection.

Solution: Ensure that the dialer, not the one set up for LAN use though, has been
properly installed and has the right settings.
• Error #781
Error Message: The encryption attempt failed because no valid certificate was found.
Solution: You have to get a valid certificate by registering to the website
http://windows.microsoft.com/...
NOTE: The solution for the following problems is already provided in the error
messages. If you are still facing problems with them, either contact your ISP or a
technician to fix the problem.
• Error #782
Error Message: Network Address Translation (NAT) is currently installed as a routing

protocol, and must be removed before enabling Internet Connection Sharing
• Error #783
Error Message: Internet Connection Sharing cannot be enabled. The LAN connection
selected as the private network is either not present, or is disconnected from the network.
Please ensure that the LAN adapter is connected before enabling Internet Connection
Sharing.
• Error #784
Error Message: You cannot dial using this connection at logon time, because it is
configured to use a user name different than the one on the smart card. If you want to use
it at logon time, you must configure it to use the user name on the smart card.
• Error #785
Error Message: You cannot dial using this connection at logon time, because it is not
configured to use a smart card. If you want to use it at logon time, you must edit the
properties of this connection so that it uses a smart card.
• Error #786
Error Message: The L2TP connection attempt failed because there is no valid machine
certificate on your computer for security authentication.
• Error #787
Error Message: The L2TP connection attempt failed because the security layer could not
authenticate the remote computer.
• Error #788
Error Message: The L2TP connection attempt failed because the security layer could not
negotiate compatible parameters with the remote computer.
• Error #789
Error Message: The L2TP connection attempt failed because the security layer
encountered a processing error during initial negotiations with the remote computer.
• Error #790
Error Message: The L2TP connection attempt failed because certificate validation on
the remote computer failed.
• Error #791
Error Message: The L2TP connection attempt failed because security policy for the
connection was not found.
• Error #792
Error Message: The L2TP connection attempt failed because security negotiation timed
out.
• Error #793
Error Message: The L2TP connection attempt failed because an error occurred while
negotiating security.
• Error #794
Error Message: The Framed Protocol RADIUS attribute for this user is not PPP.
• Error #795
Error Message: The Tunnel Type RADIUS attribute for this user is not correct.
• Error #796
Error Message: The Service Type RADIUS attribute for this user is neither Framed nor
Callback Framed.
• Error #797
Error Message: A connection to the remote computer could not be established because
the modem was not found or was busy.
• Error #798
Error Message: A certificate could not be found that can be used with this Extensible
Authentication Protocol.
• Error #799
Error Message: Internet Connection Sharing (ICS) cannot be enabled due to an IP

address conflict on the network. ICS requires the host be configured to use 192.168.0.1.
Please ensure that no other client on the network is configured to use 192.168.0.1
• Error #800
Error Message: Unable to establish the VPN connection. The VPN server may be un-
reachable, or security parameters may not be configured properly for this connection
Solution:
1. Check your ADSL line as it is probably not synched.
2. Verify that your Security Options are correctly set in your connection options.
3. Either your Network Card or your modem might not work properly. Contact a
technician if the problem persists.
• Error #995
Error Message: Operation aborted.
• Error #1382
Error Message: Maximum length exceeded.
• Error #1793
Error Message: Account expired.
• Error #2250
Error Message: Network connection does not exist.

Index
Tips to Help Track the Problem Down
0x00000003 UNSYNCHRONIZED_ACCESS
0x05 INVALID_PROCESS_ATTACH_ATTEMPT
0x0000000A IRQL_NOT_LESS_OR_EQUAL 0xA
0x0000001E KMODE_EXCEPTION_NOT_HANDLED 0x1E
0x00000023 FAT_FILE_SYSTEM & 0x00000024 NTFS_FILE_SYSTEM
0x0000002E DATA_BUS_ERROR 0x2E
0x0000003F NO_MORE_SYSTEM_PTES 0x3F
0x00000044 MULTIPLE_IRP_COMPLETE_REQUESTS
0x00000050 PAGE_FAULT_IN_NONPAGED_AREA 0x50
0x00000051- 0x51
0x0000006B PROCESS1_INITIALIZATION_FAILED
0x00000073 CONFIG_LIST_FAILED 0x73
0x00000074 BAD_SYSTEM_CONFIG_INFO 0x74
0x00000076 PROCESS_HAS_LOCKED_PAGES
0x00000077 KERNEL_STACK_INPAGE_ERROR 0x77
0x00000079 MISMATCHED_HAL 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
0x0000009C MACHINE_CHECK_EXCEPTION 0x9C
0x0000009F DRIVER_POWER_STATE_FAILURE 0x9F
0x000000A5 - 0xA5
0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY 0xBE
0x000000C2 BAD_POOL_CALLER 0xC2
0x000000C4 DRIVER_VERIFIER_DETECTED_VIOLATION
0x000000CA PNP_DETECTED_FATAL_ERROR
0x000000CB
0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING... 0xCE
0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0xD1
0x000000D5 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000D8 DRIVER_USED_EXCESSIVE_PTES 0xD8
0x000000DA SYSTEM_PTE_MISUSE
0x000000E3 - 0xE3
0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER 0xEA
0x000000ED UNMOUNTABLE_BOOT_VOLUME 0xED
0x000000F2 HARDWARE_INTERRUPT_STORM 0xF2
0x000000F4 - 0xF4
0x000000FE BUGCODE_USB_DRIVER - 0xFE
0x4000008A
0xC0000218 UNKNOWN_HARD_ERROR 0x218 & C0000135
0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED 0x21A
0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH 0x221
0xC0000244 STATUS_AUDIT_FAILED
0xC000026C
0xC0000415
Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
The Stop 0xA message indicates that a kernel-mode process or driver attempted to access
a memory location to which it did not have permission, or at a kernel interrupt request
level (IRQL) that was too high. A kernel-mode process can access only other processes
that have an IRQL lower than, or equal to, its own. This Stop message is typically due to
faulty or incompatible hardware or software.
Possible Resolutions:
# A Stop 0xA message might occur after installing a faulty device driver, system service,
or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the
driver to correct the problem. If disabling or removing drivers resolves the issues, contact
the manufacturer about a possible update. Using updated software is especially important
for multimedia applications, antivirus scanners, and CD mastering tools.
# A Stop 0xA message might also be due to failing or defective hardware. If a Stop
message points to a category of devices (video or disk adapters, for example), try
removing or replacing the hardware to determine if it is causing the problem.
# If you encounter a Stop 0xA message while upgrading to Windows XPl, the problem
might be due to an incompatible driver, system service, virus scanner, or backup. To
avoid problems while upgrading, simplify your hardware configuration and remove all
third-party device drivers and system services (including virus scanners) prior to running
setup. After you have successfully installed Windows XP, contact the hardware
manufacturer to obtain compatible updates.
Microsoft KB articles:
Troubleshooting a Stop 0x0000000A Error in Windows XP

STOP 0x0000000A Error Message When You Change from AC Power to DC Power
STOP 0x0000000A Error Message When You Fast Switch Between Users
STOP 0x0000000A Irql_Not_Less_or... During Windows XP Upgrade
STOP 0x0000000A Windows XP restarts when you try to shut down your computer
STOP 0x0000000A Computer automatically restarts after upgrade to XP
Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
The Stop 0x1E message indicates that the Windows XP kernel detected an illegal or
unknown processor instruction. The problems that cause Stop 0x1E messages share
similarities with those that generate Stop 0xA errors in that they can be due to invalid
memory and access violations. This default Windows XP error handler typically
intercepts these problems if error-handling routines are not present in the code itself.
# Stop 0x1E messages typically occur after installing faulty drivers or system services, or
they can indicate hardware problems, such as memory and IRQ conflicts. If a Stop
message lists a driver by name, disable, remove, or roll it back to correct the problem. If
disabling or removing applications and drivers resolves the issue, contact the hardware
manufacturer about a possible update. Using updated software is especially important for
multimedia applications, antivirus scanners, and CD mastering tools.
# If the Stop message mentions the file Win32k.sys, the source of the error might be a
third-party "remote control" program. If such software is installed, you might be able to
disable it by starting the system in safe mode. If not, use Recovery Console to manually
delete the system service file that is causing the problem.
# Problems can result from system firmware incompatibilities. Many Advanced

Configuration and Power Interface (ACPI) issues can be resolved by updating to the
latest firmware.
# Other possible causes include insufficient disk space while installing applications or
performing certain functions that require more memory. You can free up space by
deleting unneeded files. Use Disk Cleanup to increase available disk space. From
Recovery Console, remove temporary files (those with .tmp file extensions), Internet
cache files, application backup files, and .tmp files generated by Chkdsk.exe or
Autochk.exe. You can also choose to install additional applications to another hard disk
with more free space or move data files, paging files, and so on.
# The problem might be due to a memory leak caused by an application or service that is
not releasing memory correctly. Poolmon (Poolmon.exe) helps you to isolate the
components that are causing kernel memory leaks. For more information about
troubleshooting memory leaks, see Microsoft Knowledgebase articles Q177415, "How to
Use Poolmon to Troubleshoot Kernel Mode Memory Leaks," and Q298102, "Finding
Pool Tags Used by Third Party Files Without Using the Debugger."
Stop 0x00000024 or NTFS_FILE_SYSTEM
The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file
that allows the system to read and write to NTFS file system drives. A similar Stop
message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.
# Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or

drivers can also adversely affect the system's ability to read and write to disk, causing
errors. If using SCSI hard disks, check for cabling and termination problems between the
SCSI controller and the disks. Periodically check Event Viewer for error messages
related to SCSI or FASTFAT in the System log or Autochk in the Application log.
# Verify that the tools you use to continually monitor your system, such as virus
scanners, backup programs, or disk defragmenters are compatible with Windows XP.
Some disks and adapters come packaged with diagnostic software that you can use to run
hardware tests.
To test hard disk or volume integrity
Method 1:
1. In the Run dialog box, in the Open box type:
cmd
2. Start the Chkdsk tool, which detects and attempts to resolve file system structural
corruption. At the command prompt type:
chkdsk drive: /f
Method 2:
1. Double-click My Computer, and then select the hard disk you want to check.
2. On the File menu, click Properties.
3. Click the Tools tab.
4. In the Error-checking box, click Check Now.
5. In Check disk options, select the Scan for and attempt recovery of bad sectors check
box. You can also select the Automatically fix file system errors check box.
If the volume you are checking is in use, a message asks whether you want to delay disk
error checking until the next time you restart your computer. After you restart, disk error
checking runs and the volume chosen is not available to run other tasks during this
process. If you cannot restart the computer due to the error, use safe mode or Recovery
Console.
If you are not using the NTFS file system, and the system partition is formatted with the
file allocation table (FAT16 or FAT32) file system, long file name (LFN) information
can be lost if hard disk tools are started from an MS-DOS command prompt. A command
prompt appears when using a startup floppy disk or when using the command prompt
startup option on multiple boot systems that use FAT16 or FAT32 partitions with
Microsoft Windows 95 OEM Service Release 2 (OSR2), Microsoft Windows 98, or
Microsoft Windows Millennium Edition (Me) installed. Do not use tools meant for other
operating systems on Windows XP partitions!
# Nonpaged pool memory might be depleted, which can cause the system to stop. You
can resolve this situation by adding more RAM, which increases the quantity of
nonpaged pool memory available to the kernel.
Troubleshooting Stop 0x24 or NTFS_FILE_SYSTEM Error Messages

STOP 0x23 (or STOP 0x24) When restarting PC after installing PC-Magic Encrypted
Magic Folders
Stop 0x0000002E or DATA_BUS_ERROR
The Stop 0x2E

message indicates a system memory parity error. The cause is typically failed or defective
RAM (including motherboard, Level 2 cache, or video memory), incompatible or
mismatched memory hardware, or when a device driver attempts to access an address in
the 0x8xxxxxxx range that does not exist (does not map to a physical address). A Stop
0x2E message can also indicate hard disk damage caused by viruses or other problems.
# Stop 0x2E is typically due to defective, malfunctioning, or failed memory hardware,

such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you
added new hardware recently, remove and replace it to determine if it is causing or
contributing to the problem. Run diagnostics software supplied by the system
manufacturer to determine if the component has failed.
# Stop 0x2E messages can also occur after installing faulty drivers or system services. If
a file name is given, you need to disable, remove, or roll back that driver. Disable the
service or application and confirm that this resolves the error. If so, contact the hardware
backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
# Hard disk corruption can also cause this Stop message.
# The problem might also be due to cracks, scratched traces, or defective components on
the motherboard. If all else fails, take the system motherboard to a repair facility for
diagnostic testing.
Stop 0x0000003F or NO_MORE_SYSTEM_PTES
The Stop 0x3F message indicates one or more of the following problems:
# The system Page Table Entries (PTEs) are depleted or fragmented due to the system
performing a large number of input/output (I/O) actions.
# A faulty device driver is not managing memory properly.
# An application, such as a backup program, is improperly allocating large amounts of

kernel memory.
# Stop 0x3F messages can occur after installing faulty drivers or system services. If a file
name is given, you need to disable, remove, or roll back that driver. Disable the service or
application and confirm that this resolves the error. If so, contact the hardware
backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
# The system might not actually be out of PTEs, but a contiguous memory block of
sufficient size is not available to satisfy a driver or application request. Check for the
availability of updated driver or application files and consult the hardware or program
documentation for minimum system requirements.
# Another cause is excessive demands for system PTE by applications. This situation is
more common in server environments. Windows XP Professional provides a registry
entry, SystemPages, that you can use to increase the number of PTEs allocated.
Caution:
Do not edit the registry unless you have no alternative. The registry editor bypasses
standard safeguards, allowing settings that can damage your system, or even require you
to reinstall Windows. If you must edit the registry, back it up first...
To increase the number of PTEs allocated in the registry
1. In the Run dialog box, and in the Open box, type: regedit
2. In the registry editor, navigate to the subkey

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory Management.
3. Double-click on PagedPoolSize and SystemPages to view the value for each entry.
4. If PagedPoolSize is not zero, assign a value of 0.
5. If SystemPages is not zero, assign a value of 40000 for systems with 128 MB (or less)
of memory, or 110000 for systems with 128 MB to 256 MB of memory. For systems with
more memory, do not increase the SystemPages value above 110000 without contacting
Microsoft technical support.
6. Click OK, and then close the registry editor.
7. Restart your computer.
Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
The Stop 0x50 message indicates that requested data was not in memory. The system
generates an exception error when using a reference to an invalid system memory
address. Defective memory (including main memory, L2 RAM cache, video RAM) or
incompatible software (including remote control and antivirus software) might cause Stop
0x50 messages.
# If you added new hardware recently, remove and replace the hardware to determine if it
is causing or contributing to the problem. Run diagnostics software supplied by the
hardware manufacturer to determine if the component has failed.
# Stop 0x50 messages can also occur after installing faulty drivers or system services. If
the file name is listed, you need to disable, remove, or roll back that driver. If not, disable
the recently installed service or application to determine if this resolves the error. If this
does not resolve the problem, contact the hardware manufacturer for updates. Using
updated drivers and software is especially important for network interface cards, video
adapters, backup programs, multimedia applications, antivirus scanners, and CD
mastering tools. If an updated driver is not available, attempt to use a driver from a
similar device in the same family. For example, if printing to a Model 1100C printer
causes Stop 0x50 errors, using a printer driver meant for a Model 1100A or Model 1000
might temporarily resolve the problem.
STOP 0x00000050 PrtSeqRd deferencing null device object

STOP 0x50 Error starting Windows after connecting a scanner
Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR

The Stop 0x77 message indicates that a page of kernel data requested from the paging
(virtual memory) file could not be found or read into memory. This Stop message can
also indicate disk hardware failure, disk data corruption, or possible virus infection.
# Stop 0x77 messages can be caused by bad sectors in the virtual memory paging file or a
disk controller error. In extremely rare cases, depleted nonpaged pool resources can cause
this error. If the first and third parameters are zero, the stack signature in the kernel stack
is missing, which is an error typically caused by defective hardware. If the I/O status is
0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination
issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested
data could not be found. You can try to correct this by restarting the computer. If a
problem with disk integrity exists, Autochk, a program that attempts to mark bad disk
sectors as defective so that they are not used in the future, starts automatically. If
Autochk fails to run, you can manually perform the integrity check yourself by following
the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM"
earlier in this list.
# Another cause of Stop 0x77 messages is defective, malfunctioning, or failed memory

hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM.
If you added new hardware recently, remove and replace it to determine if it is causing or
diagnostic testing.
# Problems that cause Stop 0x77 messages can also cause Stop 0x7A messages. For more
information about Stop 0x7A messages, see "Stop 0x0000007A or
KERNEL_DATA_INPAGE_ERROR" later in this list.
Troubleshooting Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
Stop 0x00000079 or MISMATCHED_HAL
The Stop 0x79 message indicates that the hardware abstraction layer (HAL) and the
kernel type for the computer do not match. This error most often occurs when ACPI
firmware settings are changed. For example, you might install Windows XP on an x86-
based computer with the firmware ACPI enable option enabled and later decide to disable
it. This error can also result when mismatched single and multi-processor configuration
files are copied to the system.
# A Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl.exe or
Hal.dll files. This can occur after manual repairs that involve copying incorrect files to
the system. This error also occurs when using mismatched files, such as copying a
multiprocessor HAL on to a system using a single-processor kernel (or vice versa). The
kernel and HAL files for single-processor and multiprocessor systems are stored on the
Windows XP Professional operating system CD using two different file names. For
example, the single and multi-processor versions of the kernel, named Ntoskrnl.exe and
Ntkrnlmp.exe respectively. Setup copies either Ntoskrnl.exe or Ntkrnlmp.exe to your
system as Ntoskrnl.exe. In Recovery Console, you can use the Copy command to copy
the correct HAL or kernel files from the CD to the appropriate folder on the hard disk.
# If you experience Stop 0x79 messages after changing firmware settings, restore the
original settings used during Windows XP Professional Setup.
Because systems that use the ACPI HAL ignore IRQ assignments stored in firmware, you
can only manually change IRQ settings for non-ACPI (Standard PC HAL) systems. Some
x86-based provide the option to toggle ACPI functionality. To disable or re-enable ACPI,
you must change firmware settings and reinstall Windows XP. Because of the numerous
registry and system file changes required, you must run Setup again (an upgrade
installation does not work).
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
The Stop 0x7A message indicates that a page of kernel data was not found in the paging
(virtual memory) file and could not be read into memory. This might be due to
incompatible disk or controller drivers, firmware, or hardware.
Frequently, the cause of this error can be determined from the second parameter, the I/O
status code. Some common status codes are:
# 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of

nonpaged pool resources
# 0xC000009C, or STATUS_DEVICE_DATA_ERROR, indicates bad blocks (sectors)

on the hard disk
# 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or

loose data or power cables, a problem with SCSI termination, or improper controller or
disk configuration
# 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks
(sectors) on the hard disk
# 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination,

defective storage controller hardware, or defective disk cabling, or two devices
attempting to use the same resources.
# Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk
controller error, virus infection, or memory hardware problems. In extremely rare cases,
depleted nonpaged pool resources can cause this error. If the first and third parameters
are zero, the stack signature in the kernel stack is missing, an error typically caused by
defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk,
check for cabling and termination issues. An I/O status code of 0xC000009C or
0xC000016A indicates that the requested data could not be found. You can try to correct
this by restarting the computer. If a problem with disk integrity exists, Autochk, a
program that attempts to mark bad disk sectors as defective so that they are not used in
the future, starts automatically. If Autochk fails to run, you can manually perform the
integrity check yourself by following the instructions to run Chkdsk provided in "Stop
0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix.
# Another cause of Stop 0x7A messages is defective, malfunctioning, or failed memory

hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM.
If you added new hardware recently, remove and replace it to determine if it is causing or
# Check the hardware manufacturer's Web site for updates to disk adapter firmware or
drivers that improve compatibility. Verify that your disks and controller support the same
set of advanced features, such as higher transfer rates. If necessary, select a slower
transfer rate if an update is not yet available. Consult your hardware or device
documentation for more information.
Important
- You can install disk controller drivers not present on the Windows XP Professional
operating system CD by responding to the following prompt shortly after starting Setup:
- Press F6 if you need to install a third party SCSI or RAID driver.
- Press F6, and when prompted, provide the appropriate storage controller driver (ATA or
SCSI) supplied by the manufacturer.
diagnostic testing.
# Problems that cause Stop 0x7A messages can also cause Stop 0x77 messages. For more
information about Stop 0x77 messages, see "Stop 0x00000077 or
KERNEL_STACK_INPAGE_ERROR" earlier in this list.
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
The Stop 0x7B message indicates that Windows XP has lost access to the system
partition or boot volume during the startup process. Installing incorrect device drivers
when installing or upgrading storage adapter hardware typically causes stop 0x7B errors.
Stop 0x7B errors could also indicate possible virus infection.
The second parameter is very important because it can indicate whether the 0x7B Stop
message was caused by file system issues or problems with storage hardware and drivers.
Values of 0xC000034 or 0xC000000E typically indicate:
# Disks or storage controllers that are failing, defective, or improperly configured.
# Storage-related drivers or programs (tape management software, for example) that are
not fully compatible with Windows XP Professional.
# During I/O system initialization, the controller or driver for the startup device (typically
the hard disk) might have failed to initialize the necessary hardware. File system
initialization might have failed because of disk or controller failure, or because the file
system did not recognize the data on the boot device.
# Repartitioning disks, adding new disks, or upgrading to a new disk controller might
cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this
Stop message occurs after installing new disks to your system, edit the Boot.ini file or
adjust the Boot Manager parameters to allow the system to start. If the error occurs after
upgrading the disk controller, verify that the new hardware is functioning and correctly
configured.
# Verify that the system firmware and disk controller BIOS settings are correct and that
the storage device was properly installed. If you are unsure, consult your computer's
documentation about restoring default firmware settings or configuring your system to
auto-detect settings. If the error occurs during Windows XP Professional setup, the
problem might be due to unsupported disk controller hardware. In some cases, drivers for
new hardware are not in the Windows XP Professional Driver.cab library, and you need
to provide additional drivers to complete the Windows XP setup successfully. If this is
the case, follow the hardware manufacturer's instructions when installing drivers.
Periodically check for driver and firmware updates.
# Hard disk corruption can also cause this Stop message. For more information about
checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or
NTFS_FILE_SYSTEM" earlier in this list.
# Problems that cause 0x7B errors might also cause Stop 0xED errors. For more
information about 0xED Stop messages, see "Stop 0x0000007B or
INACCESSIBLE_BOOT_DEVICE" later in this list.
- Troubleshooting STOP 0x0000007B or 0x4,0,0,0 Error

- STOP 0x0000007B Error After You Move the Windows XP System Disk to Another
Computer
- STOP 0x0000007B Error Message When You Restart Computer
- STOP 0x0000007B Caused by Missing [SysprepMassStorage] Section on Windows XP
sysprep Images
- STOP 0x0000007B Error Occurs When You Press F6 to Load Drivers During
Unattended Windows Setup
Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP
The Stop 0x7F message indicates that one of three types of problems occurred in kernel-
mode:
# A condition that the kernel is not allowed to have or intercept (also known as a bound
trap)
# Software problems
# Hardware failures
# Stop 0x7F messages are typically due to defective, malfunctioning, or failed memory
hardware. If you added new hardware recently, remove and replace it to determine if it is
causing or contributing to the problem. Run diagnostics software supplied by the system
# Running the CPU beyond the rated specification, known as "overclocking," can cause
Stop 0x7F or other error messages due to heat buildup. When diagnosing problems on
overclocked systems, first restore all clock and bus speed settings to the manufacturer
recommended values to determine if this resolves the issues.
diagnostic testing.
# Stop 0x7F messages can occur after installing incompatible applications, drivers, or
system services. Contact the software manufacturer about possible Windows XP specific
updates. Using updated software is especially important for backup programs, multimedia
applications, antivirus scanners, and CD mastering tools.
STOP 0x0000007F Errors - General Causes

STOP 0x0000007F Computer Turns Off During Text-Mode Setup if it is too hot
STOP 0x0000007F During Setup on Hewlet Packard Pavilion 7840
Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE
The Stop 0x9F message indicates that a driver is in an inconsistent or invalid power state.
# Stop 0x9F messages can occur after installing faulty applications or drivers or system
services. If a file is listed by name and you can associate it with an application, uninstall
the application. For drivers, disable, remove, or roll back that driver to to determine if
this resolves the error. If it does, contact the hardware manufacturer for a possible update.
Using updated software is especially important for backup programs, multimedia
applications, antivirus scanners, and CD mastering tools.
# For information about troubleshooting standby and hibernate mode issues, see KB
article Q266169, "How to Troubleshoot Problems with Standby Mode, Hibernate Mode,
and Shutting Down Your Computer in Windows 2000."
Troubleshooting a Stop 0x9F Error in Windows XP

STOP 0X0000009F Computer hangs at shutdown or "Cannot find enough resources"
Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY
The Stop 0xBE message indicates that a driver attempted to write to read-only memory.
# A Stop 0xBE message might occur after installing a faulty device driver, system
service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll
back the driver to correct the problem. If disabling or removing drivers resolves the
issues, contact the manufacturer about a possible update. Using updated software is
especially important for multimedia applications, antivirus scanners, DVD playback, and
CD mastering tools.
STOP 0xBE Qwestdex Dex Toolbar not totally compatible with Windows XP
Stop 0xC2 or BAD_POOL_CALLER
The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly
attempted to perform memory operations in the following ways:
# By allocating a memory pool size of zero bytes.

# By allocating a memory pool that does not exist.
# By attempting to free a memory pool that is already free.
# By allocating or freeing a memory pool at an IRQL that was too high.
This Stop message is typically due to a faulty driver or software.
# A Stop 0xC2 messages might occur after installing a faulty device driver, system
service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll
back the driver to correct the problem. If disabling or removing drivers resolves the
issues, contact the manufacturer about a possible update. Using updated software is
especially important for multimedia applications, antivirus scanners, DVD playback, and
CD mastering tools.
# A Stop 0xC2 messages might also be due to failing or defective hardware. If a Stop
message points to a category of devices (such as disk controllers, for example), try
removing or replacing the hardware to determine if it is causing the problem.
# If you encounter a Stop 0xC2 message while upgrading to Windows XP, the problem
might be due to an incompatible driver, system service, virus scanner, or backup. To
avoid problems while upgrading, simplify your hardware configuration and remove all
third-party device drivers and system services (including virus scanners) prior to running
setup. After you have successfully installed Windows XP, contact the hardware
manufacturer to obtain compatible updates.
How to Debug Stop 0xC2 or Stop 0x000000C2 Error Messages

STOP 0x000000c2 Computer with ATI FURY MAXX hangs after upgrade to Windows
XP STOP 0x000000c2 After you install IomegaWare
STOP 0xC2 Bad_Pool_Caller When you upgrade from Windows 2000
Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT_CANCELLING

_PENDING_OPERATIONS
This Stop messages indicates that a driver failed to cancel pending operations before
exiting.
# Stop 0xCE messages can occur after installing faulty drivers or system services. If a
driver is listed by name, disable, remove, or roll back that driver to confirm that this
resolves the error. If so, contact the manufacturer about a possible update. Using updated
software is especially important for backup programs, multimedia applications, antivirus
scanners, DVD playback, and CD mastering tools.
STOP 0x000000CE in Dxapi.sys Error on Blue Screen

STOP 0x000000CE When you stop SFU 2.0 NFS Client Service on Windows-XP Based
Computer
Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
The Stop 0xD1 messages indicates that the system attempted to access pageable memory
using a kernel process IRQL that was too high. Drivers that have used improper
addresses typically cause this error.
# Stop 0xD1 messages can occur after installing faulty drivers or system services. If a
driver is listed by name, disable, remove, or roll back that driver to confirm that this
resolves the error. If so, contact the manufacturer about a possible update. Using updated
software is especially important for backup programs, multimedia applications, antivirus
scanners, DVD playback, and CD mastering tools.
STOP 0x000000D1 Error Message When You Turn Your Computer Off
STOP 0xD1 Error Message When You Start Windows XP
STOP 0xD1 Second Mylex AcceleRAID SCSI Controller Causes Error Message
STOP 0x000000D1 WRQ AtGuard Program causes error message in Windows XP
Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER
A device driver problem is causing the system to pause indefinitely. Typically, this
problem is caused by a display driver waiting for the video hardware to enter an idle
state. This might indicate a hardware problem with the video adapter or a faulty video
driver.
# Stop 0xD1 messages can occur after installing faulty drivers (especially video drivers)
or system services. If a driver is listed by name, disable, remove, or roll back that driver
to confirm that this resolves the error. If so, contact the manufacturer about a possible
update. Using updated software is especially important for backup programs, multimedia
applications, antivirus scanners, DVD playback, and CD mastering tools.
STOP 0x000000EA ErrMsg Running Video-Intensive Programs

STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME
The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This
error might also occur during an upgrade to Windows XP Professional on systems that
use higher throughput ATA disks or controllers with incorrect cabling. In some cases,
your system might appear to work normally after you restart.
# If using higher throughput ATA disks and controllers, those capable of data transfer
rates above 33.3 megabytes per second, replace the standard 40-pin cable with an 80-pin
cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3
megabytes per second, but is mandatory for higher transfer rates. The additional
grounded pins are required to avoid data loss.
# Some firmware enables you to force higher transfer rates even when you are using the
incorrect cable type. Your firmware might issue a warning but allow the startup process
to proceed. Restore the default firmware setting for ATA cable detection.
# Problems that cause 0xED errors might also cause Stop 0x7B errors. For more
information about 0x7B Stop messages, see "Stop 0x0000007B or
INACCESSIBLE_BOOT_DEVICE" earlier in this appendix.
STOP 0x000000ED Error Message When Volume on IDE Drive with Caching Enabled
Is Mounted
STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME Error Message
Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
This Stop message indicates driver, system file, or disk corruption problems (such as a
damaged paging file). Faulty memory hardware can also cause this Stop message to
appear.
# You can use Driver Rollback or System Restore from safe mode, to restore a previous
driver. You can also use Windows XP Professional recovery features such as the Last
Known Good Configuration startup option, Backup, or Automated System Recovery to
restore a previous working configuration. After restoring from backup media, you might
need to reapply service packs or hotfixes, depending on when the backups were made.
# If the Stop message names the specific file, try replacing it manually with a fresh copy
from the Windows XP Professional operating system CD using safe mode or Recovery
Console. For systems using the FAT16 or FAT32 file system, you have the option of
using a Windows 98 or Windows Millennium Edition Emergency Boot Disk to access the
hard disk.
If the original file from the operating system CD has a file name that ends with an
underscore (_) character, you cannot use the file until it is uncompressed. The Recovery
Console's Copy command is ideal for copying compressed files because it detects and
expands them. If you do not specify a destination file name, you must rename the
expanded file with the correct extension before using it. From safe mode or Recovery
Console, you can use the Expand command to uncompress and copy a file to a
destination location. In Recovery Console, the expanded file is given the correct name
after being copied to the destination location. For more information about the Copy or
Expand commands, see Windows XP Help and Support Centre.
STOP C0000221 Unknown Hard Error

STOP 0xc000026C or Stop 0xc0000221 Unable to Load Device Driver Error Occurs
When You Start Windows XP
I hope this article on XP Stop Messages was useful?

XP Error

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

XP Error

Caricato da

Copyright:

Formati disponibili

Error messages

600 An operation is pending

601 An invalid port handle was detected

602 The specified port is already open

603 The caller's buffer is too small

604 Incorrect information was specified

605 The port information cannot be set

606 The specified port is not connected

607 An invalid event is detected

608 A device was specified that does not exist

610 An invalid buffer was specified

611 A route was specified that is not available

612 A route was specified that is not allocated

613 An invalid compression was specified

614 There were insufficient buffers available

615 The specified port was not found

617 The modem is already disconnecting

618 The specified port is not open

619 The specified port is not connected

620 No endpoints could be determined

621 The system could not open the phonebook

622 The system could not load the phonebook

624 The system could not update the phonebook file

625 The system found invalid information in the phonebook

626 A string could not be loaded

627 A key could not be found

628 The connection was closed

629 The connection was closed by the remote computer

630 The modem was disconnected due to hardware failure

631 The user disconnected the modem

632 An incorrect structure size was detected

634 Your computer could not be registered on the remote network

635 There was an unknown error

637 A string was detected that could not be converted

638 The request has timed out

640 A error has occurred involving NetBIOS

643 A network adapter at the server failed

644 You will not receive network message popups

645 There was an internal authentication error

646 The account is not permitted to log on at this time of day

647 The account is disabled

648 The password for this account has expired

649 The account does not have permission to dial in

650 The remote access server is not responding

651 The modem has reported an error

652 There was an unrecognized response from the modem

657 The device .INF file could not be opened

659 The media .INI file refers to an unknown device name

661 The device .INF file is missing a command

663 The media .INI file refers to an unknown device type

664 The system has run out of memory

665 The modem is not properly configured

666 The modem is not functioning

668 The connection was terminated

669 The usage parameter in the media .INI file is invalid

676 The phone line is busy

677 A person answered instead of a modem

678 There was no answer

679 The system could not detect the carrier

680 There was no dial tone

681 The modem reported a general error

692 There was a hardware failure in the modem

696 The state machines are already started