How to Allocate Non-Cached Memory for an NDIS Driver

Last reviewed: September 18, 1995
Article ID: Q124079

The information in this article applies to:

Microsoft Win32 Device Development Kit (DDK) for Windows NT, versions 3.1, 3.5, and 3.51

An NDIS driver making a call to NdisAllocateMemory faces certain restrictions when attempting to allocate non-cached memory. To safely allocate non-cached memory, you need to make the call at the IRQL < PASSIVE_LEVEL. In the NDIS environment, you can only be assured that your driver is running at this level in the initialization code. Therefore, if you anticipate the need for using non-cached memory during the execution of your driver code, make the call to NdisAllocateMemory in the initialization code.

Additional reference words: 3.10 3.50
KBCategory: kbprg
KBSubcategory:

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 18, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.