WSPCleanup aborted and closed existing service provider SOCKET handles underneath the code that owned those SOCKETs |
Application Verifier break message
WSPCleanup aborted and closed existing service provider SOCKET handles underneath the code that owned those SOCKETs
Probable cause
WSPCleanup was called by a layered service provider (LSP), decrementing the Winsock reference count to 0, while open SOCKET handles existed in the process. Winsock closes any open SOCKET handles when the reference count reaches zero.This is typically a bug in the LSP that decrements the Winsock reference count too often (by calling WSPCleanup unbalanced with WSPStartup) or incorrectly tracks (leaks) SOCKET handles.
Troubleshooting steps
Enter k to find the caller that decremented the WSPStartup/WSPCleanup count to 0.
Information displayed by Application Verifier
Parameter 1 - Number of outstanding service provider sockets
Parameter 2 - Not Used
Parameter 3 - Not Used
Parameter 4 - Not Used
Additional information
Test Layer:�Net Verifier
Stop code:�E10C
Severity:�Error
One-time error:�No
Non Continuable:�Yes
Error report:�None
Log to file:�Yes
Create backtrace:�Yes