A Winsock service provider API was called before a successful WSPStartup() or after a balancing successful WSPCleanup() call was made

A call was made to a Winsock name service provider API before a successful WSPStarup() or after a balancing successful WSPCleanup() call. This is generally pointing to a fault to a specific Winsock layered service provider (LSP) layered between the application and Winsock. WSPStartup is required to provide a reference count by any LSP using Winsock to guarantee initialization for Winsock service provider API usage. An unbalanced WSPStartup/WSPCleanup call pattern by an LSP can lead to undefined behavior as this can cause the Winsock layer to unload libraries and release resources while still being used.

If Parameter 1 is not NULL, enter dps Parameter 1 to dump the stack for the last successful WSPStartup call by the LSP in violation.

If Parameter 2 is not NULL, enter dps Parameter 2 to dump the stack for the last successful WSPCleanup call by the LSP in violation.

If Parameter 2 is not NULL, enter dps Parameter 3 to dump the stack for the last successful WSPStartup call made by any service provider in the process.

If Parameter 4 is not NULL, enter dps Parameter 4 to dump the stack for the last successful WSPCleanup call made by any service provider in the process.

Parameter 1 - Last successful WSPStartup call made by the LSP in violation.

Parameter 2 - Last successful WSPCleanup call made by the LSP in violation.

Parameter 3 - Last successful WSPStartup call made by any service provider in the process.

Parameter 4 - Last successful WSPCleanup call made by any service provider in the process.

Test Layer:�Net Verifier

Stop code:�E108

Severity: Error

One-time error:�No

Non Continuable:�Yes

Error report:�Yes

Log to file:�Yes

Create backtrace:�Yes