| Networking API called before a successful WSAStartup() or after a balancing successful WSACleanup() call was made |
Application Verifier break message
Networking API called before a successful WSAStartup() or after a balancing successful WSACleanup() call was made
Probable cause
A call was made to a networking API before a successful WSAStatrup() or after a balancing successful WSACleanup() call. WSAStartup is required to provide a reference count by any component using Winsock to guarantee initialization for Winsock API usage. An unbalanced WSAStartup/WSACleanup call pattern by a component can lead to undefined behavior because this can cause the Winsock layer to unload libraries and release resources that are still being used.
Troubleshooting steps
If Parameter 1 is not NULL, enter dps Parameter 1 to dump the stack for the last successful WSAStartup call by the DLL in violation.
If Parameter 2 is not NULL, enter dps Parameter 2 to dump the stack for the last successful WSACleanup call by the DLL in violation.
If Parameter 3 is not NULL, enter dps Parameter 3 to dump the stack for the last successful WSAStartup call made by any DLL in the process.
If Parameter 4 is not NULL, enter dps Parameter 4 to dump the stack for the last successful WSACleanup call by any DLL in the process.
Information displayed by Application Verifier
Parameter 1 - Last successful WSAStartup call by this DLL in violation.
Parameter 2 - Last successful WSACleanup call by the DLL in violation.
Parameter 3 - Last successful WSAStartup call in the process.
Parameter 4 - Last successful WSACleanup call in the process.
Additional information
Test Layer:�Net Verifier
Stop code:�E107
Severity:�Error
One-time error:�No
Non Continuable:�Yes
Error report:�Yes
Log to file:�Yes
Create backtrace:�Yes