Discussion Locked

IRP STACK LOCATIONS?

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
A coworker of mine was opening his outlook when his PC all of a sudden turned off. When he restarted it had a bunch of lines going horizontally. I thought it might have something to do with the video. Upon restart it came up with a blue screen saying something about k mode? I went in to last known good configuration and it started without a problem. However, this morning it did it again, instead saying something about no more IRP Stack locations. Any help?

5 replies

by parbo

Check these technet articles Event ID 2506 Error Message When You Start Windows 2000 [Q238316] and Antivirus Software May Cause Event ID 2011 [Q177078]
Hope this helps...

by saihib

NO_MORE_IRP_STACK_LOCATIONS (0x35)
A higher level driver has attempted to call a lower level driver through the
IoCallDriver() interface, but there are no more stack locations in the
packet, so the lower level driver would not be able to access its
parameters, as there are no parameters for it. This is a disastrous
situation, since the higher level driver thinks it has filled in the
parameters for the lower level driver (something it MUST do before calling
the lower level driver); however, since there is no stack location for the
latter driver, the former has written off of the end of the packet. This
means that some other memory has probably been corrupted.

With this code, if you've added a new virus scanner or someone has accessed a shared volume over the network for the first time on the machine, the Server device driver can be at fault. The Server device driver constructs I/O request packets with a slot for every device driver on the path to the disk. Sometimes the number of I/O request packets the Server device driver allocates is insufficient, resulting in this Stop Code. Try increasing the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ServicesLanmanServer\IrpStackSize setting to a number higher than 4 (or whatever it's set to) and see whether the problem goes away.

This discussion is closed to new replies.