Common windows xp error codes

Insufficient memory available. An application used a Windows Sockets function that directly maps to a Windows function. The Windows function is indicating a lack of required memory resources. One or more parameters are invalid. An application used a Windows Sockets function which directly maps to a Windows function. The Windows function is indicating a problem with one or more parameters. Overlapped operation aborted.

The application has tried to determine the status of an overlapped operation which is not yet completed. Overlapped operations will complete later. The application has initiated an overlapped operation that cannot be completed immediately.

A completion indication will be given later when the operation has been completed. Interrupted function call. File handle is not valid. The file handle supplied is not valid.

Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. Such exclusive access is a new feature of Windows NT 4.

Bad address. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small.

For instance, if the length of an argument, which is a sockaddr structure, is smaller than the sizeof sockaddr. Invalid argument. Some invalid argument was supplied for example, specifying an invalid level to the setsockopt function. In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening. Too many open files. Too many open sockets.

Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread. Resource temporarily unavailable. This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later.

Operation now in progress. A blocking operation is currently executing. Operation already in progress. An operation was attempted on a nonblocking socket with an operation already in progress—that is, calling connect a second time on a nonblocking socket that is already connecting, or canceling an asynchronous request WSAAsyncGetXbyY that has already been canceled or completed.

Socket operation on nonsocket. An operation was attempted on something that is not a socket. Destination address required. A required address was omitted from an operation on a socket. Message too long. A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself.

Protocol wrong type for socket. A protocol was specified in the socket function call that does not support the semantics of the socket type requested. Bad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call. Protocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. Socket type not supported. The support for the specified socket type does not exist in this address family.

Operation not supported. The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket.

Protocol family not supported. The protocol family has not been configured into the system or no implementation for it exists. Address family not supported by protocol family. An address incompatible with the requested protocol was used. This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto.

Address already in use. Client applications usually need not call bind at all— connect chooses an unused port automatically. Cannot assign requested address. The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system that is, the protocol stack that the Windows Sockets DLL runs over , the network interface, or the local network itself.

Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host. Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.

Software caused connection abort. An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.

Connection reset by peer. An existing connection was forcibly closed by the remote host. This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. No buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

They are often accompanied by a numerical code that helps identify which problem is being experienced. Far too many to go into detail here. No longer just a blue screen with numerical error codes, you can identify this screen by the frowny face accompanied by the basic message Your PC ran into a problem… typically followed by an error code.

This can make troubleshooting the error a bit complicated. The chances are, whichever change you made right before the error occurred is probably the culprit. Depending on what it was that was changed, you can choose to reboot using the last known good configuration, via System Restore , or by rolling back the device driver. Ensure that you have all Windows service packs and updates applied, update all hardware drivers and software updates, and do a virus scan.

For a hardware issue, update the firmware or replace the component. The errors mentioned barely scratch the surface of the many that you can encounter while using Windows If you encounter a specific error not covered in this post and it has an error code present, a quick Google search could prove useful in understanding why it happened and how best to fix it.

Joseph has over 10 years experience in the IT industry as both an analyst and communications expert. He's a night owl and an avid Red Bull consumer who spends most of his downtime enthralled by online gaming and website building.

Read Joseph's Full Bio. Your email address will not be published. We hate spam too, unsubscribe at any time. Alternatively, contact the manufacturer. When you receive the following message, press R to start the Recovery Console. This part of the Setup program prepares Windows XP to run on your computer. Then, press 1 to access your primary drive installation by using the Recovery Console.

When you are prompted, type the administrator password. Rename the following files by using the REN command. For example, use the following command for the Wpa. To work around this problem, use one of the following methods. Note If the methods in this section are unsuitable for your situation, then use the methods in the "Workaround for an error code that is not in this list" section, and begin with Method 1. To resolve this problem, you must remove the whole contents of the MountedDevices registry key.

This key is located in the following registry subkey:. These hard-coded paths may not load. Then, that behavior provokes the WPA-related error code.

To reset the default security provider in Windows XP, delete the relevant registry keys from the registry. Click Start , click Run , type regedit, and then click OK. Use Registry Editor to change the drive letter of the system drive back to its original value. Edit the following registry key to change the value of the system drive:. To work around this problem, uninstall the service pack that you installed.

Then, reinstall the service pack. To work around this problem, replace the Dpcdll. Note To obtain the clean Dpcdll. Note In most scenarios, the WinTools third-party software causes this problem. To work around this problem, follow these steps:. Restart your computer, and then press F8 during the initial startup to start your computer in safe mode with a command prompt.

Click Start , click Run , type regedit, and the click OK. Delete the registry key that has a WinTools value. Delete the all the files that have Wtools or Wsup in the name. To work around this problem, run the chkdsk command. For more information about the chkdsk command , visit the following Microsoft Web site:.

If you want to force activation in Windows XP again, rename the Wpa. Consider the following scenario. You receive an error code that states that you must start Windows XP.