The problem occurs when this function is executed in a separate thread foreach attached network, on Windows NT computers that are attached tomultiple networks.
After the second thread completes, it attempts to destroy the clientcontext handle, using the same handle that was closed by the first thread.This causes the function to generate the access violation.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
AV sid multiple nics multi-homed dr watson crash crashes