A Winsock name service provider API was called before a successful NSPStartup() or after a balancing successful NSPCleanup() call was made

A call was made to a Winsock name service provider API before a successful NSPStartup() or after a balancing successful NSPCleanup() call. This is generally pointing to a fault to a specific Winsock name service provider (NSP) layered between the application and Winsock. NSPStartup is required to provide a reference count by any NSP using Winsock to guarantee initialization for Winsock name service provider API usage. An unbalanced NSPStartup/NSPCleanup call pattern by an NSP can lead to undefined behavior because 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 NSPStartup call by the NSP in violation.

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

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

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

Parameter 1 - Last successful NSPStartup call by the NSP in violation.

Parameter 2 - Last successful NSPCleanup call by the NSP in violation.

Parameter 3 - Last successful NSPStartup call made by any NSP in the process.

Parameter 4 - Last successful NSPCleanup call made by any NSP in the process.

Test Layer:�Net Verifier

Stop code:�E109

Severity:�Error

One-time error:�No

Non Continuable:�Yes

Error report:�Yes

Log to file:�Yes

Create backtrace:�Yes