| Subject: IRPStackSize |
| Group: microsoft.public.winternals |
| Date: 12/19/2007 11:52:55 AM |
| From: Megan Kielman [Email Address Protection] |
I recently had a system run out of IRP Stack Locations. I understand that the IRPStackSize in the registry specifies how many stack locations the server service establishes for IRPs. What I don't understand is what can cause the stack locations to run out and how do you know when it is appropriate to increase the default value? |
| Back |
| Subject: Re: IRPStackSize |
| Group: microsoft.public.winternals |
| Date: 12/19/2007 12:38:32 PM |
| From: "David Craig" [Email Address Protection] |
Are you writing the driver that ran out of stack locations? If not, it is not your problem nor is it fixable by you. You may try some hacks to increase system default stack sizes, but each driver requests a specific number of stack locations and you can't change their code if it is not your driver. Read the docs that come with the WDK 6000 about stack locations. The IoManager creates an IRP with the number of stack locations requested and not some 'server service'. Some stacks may permit altering the default for that stack, but that is the exception and without more details about the driver that failed, no one can answer your question. Try writing a few drivers and how stack locations are used and by whom will become clear. It is not a subject for computer users or even application developers. This newsgroup is not appropriate for this subject. Try 'microsoft.public.development.device.drivers' instead. Wininternals is a reference to Mark Russinovich's company that Microsoft acquired when they made him a Microsoft Fellow. Sysinternals was the other web site for which he and Brian Cogswell were famous and where their free utilities could be found. Now they are on Technet, a part of Microsoft. "Process Explorer" is one of those utilities that is extremely useful and far more comprehensive than Task Manager. "Megan Kielman" <megan.kielman@gmail.com> wrote in message news:OPfYeBnQIHA.2396@TK2MSFTNGP02.phx.gbl... >I recently had a system run out of IRP Stack Locations. I understand that >the IRPStackSize in the registry specifies how many stack locations the >server service establishes for IRPs. What I don't understand is what can >cause the stack locations to run out and how do you know when it is >appropriate to increase the default value? |
| Back |
| Subject: Re: IRPStackSize |
| Group: microsoft.public.winternals |
| Date: 12/19/2007 4:51:40 PM |
| From: Megan Kielman [Email Address Protection] |
I thought it was appropriate for this newsgroup since the topic is covered in the Windows Internals book. Furthermore, I believe it is my problem (as a sys admin) if I have a system that is experiencing this problem and as a result is unable to create additional IRP's (for example: TCP connections) David Craig wrote: > Are you writing the driver that ran out of stack locations? If not, it is > not your problem nor is it fixable by you. You may try some hacks to > increase system default stack sizes, but each driver requests a specific > number of stack locations and you can't change their code if it is not your > driver. Read the docs that come with the WDK 6000 about stack locations. > The IoManager creates an IRP with the number of stack locations requested > and not some 'server service'. Some stacks may permit altering the default > for that stack, but that is the exception and without more details about the > driver that failed, no one can answer your question. > > Try writing a few drivers and how stack locations are used and by whom will > become clear. It is not a subject for computer users or even application > developers. > > This newsgroup is not appropriate for this subject. Try > 'microsoft.public.development.device.drivers' instead. > > Wininternals is a reference to Mark Russinovich's company that Microsoft > acquired when they made him a Microsoft Fellow. Sysinternals was the other > web site for which he and Brian Cogswell were famous and where their free > utilities could be found. Now they are on Technet, a part of Microsoft. > "Process Explorer" is one of those utilities that is extremely useful and > far more comprehensive than Task Manager. > > "Megan Kielman" <megan.kielman@gmail.com> wrote in message > news:OPfYeBnQIHA.2396@TK2MSFTNGP02.phx.gbl... >> I recently had a system run out of IRP Stack Locations. I understand that >> the IRPStackSize in the registry specifies how many stack locations the >> server service establishes for IRPs. What I don't understand is what can >> cause the stack locations to run out and how do you know when it is >> appropriate to increase the default value? > > |
| Back |
| Subject: Re: IRPStackSize |
| Group: microsoft.public.winternals |
| Date: 12/19/2007 6:21:50 PM |
| From: "David Craig" [Email Address Protection] |
I don't know which group is appropriate, but I suspect you won't get any useful answer here. Try a networking newsgroup since you are concerned about it as a sys admin and not a developer. "Megan Kielman" <megan.kielman@gmail.com> wrote in message news:OF6oaopQIHA.3556@TK2MSFTNGP03.phx.gbl... >I thought it was appropriate for this newsgroup since the topic is covered >in the Windows Internals book. Furthermore, I believe it is my problem (as >a sys admin) if I have a system that is experiencing this problem and as a >result is unable to create additional IRP's (for example: TCP connections) > > > David Craig wrote: >> Are you writing the driver that ran out of stack locations? If not, it >> is not your problem nor is it fixable by you. You may try some hacks to >> increase system default stack sizes, but each driver requests a specific >> number of stack locations and you can't change their code if it is not >> your driver. Read the docs that come with the WDK 6000 about stack >> locations. The IoManager creates an IRP with the number of stack >> locations requested and not some 'server service'. Some stacks may >> permit altering the default for that stack, but that is the exception and >> without more details about the driver that failed, no one can answer your >> question. >> >> Try writing a few drivers and how stack locations are used and by whom >> will become clear. It is not a subject for computer users or even >> application developers. >> >> This newsgroup is not appropriate for this subject. Try >> 'microsoft.public.development.device.drivers' instead. >> >> Wininternals is a reference to Mark Russinovich's company that Microsoft >> acquired when they made him a Microsoft Fellow. Sysinternals was the >> other web site for which he and Brian Cogswell were famous and where >> their free utilities could be found. Now they are on Technet, a part of >> Microsoft. "Process Explorer" is one of those utilities that is extremely >> useful and far more comprehensive than Task Manager. >> >> "Megan Kielman" <megan.kielman@gmail.com> wrote in message >> news:OPfYeBnQIHA.2396@TK2MSFTNGP02.phx.gbl... >>> I recently had a system run out of IRP Stack Locations. I understand >>> that the IRPStackSize in the registry specifies how many stack locations >>> the server service establishes for IRPs. What I don't understand is what >>> can cause the stack locations to run out and how do you know when it is >>> appropriate to increase the default value? >> |
| Back |