Hi,
I am writing a ndis miniport driver. For some reason after I send out
couple of packets. The driver hangs the Windows. I am running the driver on
Windows 2000. When I catch the hang on the debugger the hangs occurs on
NdisMIndicateReceivePacket function. I use the function to notify the
protocol driver about a recieved packet. It seems that not my code but the
protocol driver above me crashes which causes my driver to hang. The crash
has something to do with accessing an invalid address.
(IRQL_NOT_LESS_THAN_OR_EQUAL) Anyone has any ideas about what is happening or
what I might be doing wrong?

Shreyash B. Patel.

"Shreyash B. Patel" <ShreyashBPatel@discussions.microsoft.com> wrote in
message news:0E96E436-33B1-4E37-AF99-25BDA6E04BC1@microsoft.com...
Have you made sure that you have setup the first buffer correctly. The DDK
docunebtation for NdisMIndicateReceivePacket includes several detailed
requirements, including:

"The first buffer in the packet must contain the amount of data specified by
the lookahead setting plus the data size of the MAC header.".

If you don't follow this rule, then the protocol above you may crash because
the NDIS buffer doesn't fit the requirement.

There are also other requirements that you must follow, including allocating
the necessary minimum Protocol Resereved size when you allocate the packet
pool used to indicate receives.

For sure there is something in your packet construction that the higher
level is not expecting.

Thomas F. Divine, Windows DDK MVP
http://www.rawether.net