This article was previously published under Q174465
This article has been archived. It is offered "as is" and will no longer be updated.
Computers running Windows NT will blue screen with a Stop 0x0000000Ashortly after the Logon Screen appears or if the computer was removed fromthe network during startup, it will blue screen approximately 10 secondsafter being put back on the network.
The blue screen will show Afd.sys, Nwlnkipx.sys, and Ntoskrnl.exe on thestack.
The first and last BugCheck parameters will vary.
This will be most evident if there are many computers running the SAPAgent.
A faulty network interface card (NIC) is broadcasting bad SAP packets onthe network with a large value for Bytes Remaining. The computer has tohave SAP Agent loaded for this to occur. It does not matter if the computeris using the Gateway Services for NetWare (GSNW) or intraNetWare clientredirector but must have either redirector loaded. The SAP Agent isallowing the packet to be passed up the stack.
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
To work around this problem, remove the computer running Windows NT fromthe network to start it up and then disable SAP Agent. After this serviceis disabled, the computer can then be put back on the network. The resourcebroadcasting the bad SAP packet must then be found and removed from thenetwork.
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 6.