Err Msg: STOP 0x0000000A Corrupted Data Packet Causes PPTP to Hang in Ndiswan.sys

ID: Q230177


The information in this article applies to:


SYMPTOMS

It is possible for a corrupted IP packet received over PPTP to cause your system to bugcheck. This problem only occurs when you run PPTP.


CAUSE

This problem is caused by a corrupted datapacket, where the Frame Length given in the packet header was longer than expected. This caused the code that read that frame to be confused and to corrupt memory, which in turn lead the computer to stop responding (hang). The fix verifies that the Frame Length provided in a packet is not larger than the system expects. Microsoft believes this error to be rare, and the fix to be safe.


RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual fix. For information on obtaining the latest service pack, please go to:

For information on obtaining the individual fix, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/support/supportnet/default.asp

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 5.

Additional query words:


Keywords          : nt4sp5fix 
Version           : winnt:4.0
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: May 5, 1999