NO_MORE_IRP_STACK_LOCATIONS

NTDEV
1

Hi everybody,

I came across the above blue screen recently. The system on which this
blue screen occured was a nt4 server service pack 6. It had my filter
driver running on it and I was copying huge data from a nt4 workstation to
it through network. The data was quiet huge somewhere around 640 mb. I
read the DDK documentation regarding the bug check code and came to know
that it occurs if a higher driver calls IoCallDriver but the IRP does not
have stack locations in it. Now what is the solution to this problem?

Regards.

2

Obiviously, allocating a IRP with enough stack locations, if you allocate
it.

Dan
----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Saturday, July 20, 2002 10:21 AM
Subject: [ntdev] NO_MORE_IRP_STACK_LOCATIONS

> Hi everybody,
>
> I came across the above blue screen recently. The system on which this
> blue screen occured was a nt4 server service pack 6. It had my filter
> driver running on it and I was copying huge data from a nt4 workstation to
> it through network. The data was quiet huge somewhere around 640 mb. I
> read the DDK documentation regarding the bug check code and came to know
> that it occurs if a higher driver calls IoCallDriver but the IRP does not
> have stack locations in it. Now what is the solution to this problem?
>
> Regards.
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>

3

Hi everybody,

But this occurs when my driver has not allocated an IRP of its own.

Regards.

4

Ok , fair enough. Your a filter driver in what stack ? Some NT componenets
have a strange way to allocate IRPs … netbt for example …

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Saturday, July 20, 2002 5:04 PM
Subject: [ntdev] Re: NO_MORE_IRP_STACK_LOCATIONS

> Hi everybody,
>
> But this occurs when my driver has not allocated an IRP of its own.
>
> Regards.
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>

5

does your filter driver run on the disk stack somewhere?

if so then there’s a parameter somewhere (I’d need to look for it but
hopefully a vague hint can get you started :slight_smile: for the Server service
which configures how many stack locations it pre-allocates in its irps
on NT4. One might hope there’s a KB article about it too.

-p

-----Original Message-----
From: xxxxx@yahoo.com [mailto:xxxxx@yahoo.com]
Sent: Saturday, July 20, 2002 12:21 AM
To: NT Developers Interest List
Subject: [ntdev] NO_MORE_IRP_STACK_LOCATIONS

Hi everybody,

I came across the above blue screen recently. The system on which this
blue screen occured was a nt4 server service pack 6. It had my filter
driver running on it and I was copying huge data from a nt4 workstation
to it through network. The data was quiet huge somewhere around 640 mb.
I read the DDK documentation regarding the bug check code and came to
know that it occurs if a higher driver calls IoCallDriver but the IRP
does not have stack locations in it. Now what is the solution to this
problem?

Regards.

You are currently subscribed to ntdev as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%

6
  1. After a driver does IoCreateDeviceObject() it should call
    IoAttachDevicetoDeviceStack() when the Iomanager initially creates an IRP
    to be sent to the upper FDO for a Drvobj the proper amount of
    IO_STACK_LOCATIONS will be allocated out of non-paged memory by the IO
    manager for the worst case that the IRP is passed all the way down the
    IO_STACK_LOCATIONS.
7

Hi all,

Its a filesystem filter driver.
I have attached the filter device to the stack by calling
IoAttachDeviceToDeviceStack only. So I am not able to get any clues
regarding the bugcheck.

Regards.