Memory Leak and STOP Screens Using Intermediate NDIS Drivers

When intermediate (layered) NDIS miniport drivers are in use on Windows NT 4.0, you may experience one or both of the following:

• A memory leak in kernel non-paged pool memory. Over time, memory may be depleted to the point where system stability is compromised.
• You may receive the following blue-screen STOP error message with parameters that indicate the bad instruction is in the Ndis.sys driver:
  STOP: 0x0000000A (0x00000014, 0x00000002, 0x00000000, 0xFCBA1062).
  IRQL_NOT_LESS_OR_EQUAL (* Address fcba1062 has base at fcb95000 - NDIS.SYS)

Intermediate drivers are typically add-ons that layer themselves over hardware drivers as a filter to provide additional functionality, such as data encryption or other value added services. The Ndis.sys driver included in Windows NT 4.0 has been found to have some deficiencies when such intermediate drivers are used.

You can work around this problem by removing any unnecessary filter drivers.

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 the Microsoft Knowledge Base:

For your convenience, the English version of this post-SP3 hotfix has been posted to the following Internet location. However, Microsoft recommends that you install Windows NT 4.0 Service Pack 4 to correct this problem. NOTE: Service Pack 3 must be applied to Windows NT 4.0 prior to applying this fix.

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.