A "Stop 0xA" Error Occurs in the nwlnkspx!SpxConnConnectFindRouteComplete() Function (307338)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition SP4
  • Microsoft Windows NT Server 4.0 Terminal Server Edition SP5
  • Microsoft Windows NT Server 4.0 Terminal Server Edition SP6

This article was previously published under Q307338

SYMPTOMS

You may receive the following error message on a blue screen:
Stop: 0x0000000A (0x00000002, 0x00000002, 0x00000001, 0xf01f264b)
Note that the parameters in the error message that you receive may differ from the parameters that are listed in this article.

CAUSE

This problem occurs because a NULL parameter is handled incorrectly by the nwlnkspx!SpxConnConnectFindRouteComplete function.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date         Time   Version         Size    File name     Platform
   ------------------------------------------------------------------
   21-Oct-2001  05:39  4.0.1381.33478  58,704  Nwlnkspx.sys  x86
				
NOTE: Because of file dependencies, this hotfix requires Microsoft Windows NT 4.0 Terminal Server Edition Service Pack 6a.
Note that this hotfix is available only for Windows NT Server, Terminal Server Edition.

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0.

Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kberrmsg kbfix kbQFE KB307338