Anonymous_User Absent Member.
Absent Member.
3607 views

IRP Stack Locations

I've got several Dell Lattitude laptops and 2 Dell GX260 desktops that crash
at random intervals
one to 5 times a day with a blue screen that says there are No More IRP
Stack Locations.

I've tried numerous things but I now know this:
When the laptops are not connected to the network, they never
crash.
When I remove the Novell Client (4.91 SP1) and connect to the network
through the Windows client, the laptop NEVER crashes.

This strongly suggests a Novell Client problem.

Any help would be greatly appreciated.

Thanks in advance.

Max Tyler



Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: IRP Stack Locations

Max,

> I've got several Dell Lattitude laptops and 2 Dell GX260 desktops that crash
> at random intervals
> one to 5 times a day with a blue screen that says there are No More IRP
> Stack Locations.


Are these machines running the Dell OEM windows build? Many of the OEM
manufacturers include a lot of additional "stuff" into their builds -
some of which is Network hostile.

If you're running the Dell OEM image, try installing just a standard
clean install of Windows, see if the problem still exhists.

--
Hamish Speirs
Novell Support Forums Volunteer Sysop.

http://haitch.net

(Please, no email unless requested. Unsolicited support emails will
probably be ignored)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: IRP Stack Locations

These are accounting machines with tons of software and are setup very
precisely. You are asking me to spend 8 hours to build a machine on
basically a wing and a prayer.

Yes they are Dell OEM. The only OS CDs I have that I can legitimately put
on them are Dell OEM CD's.

I've been running Dell OEM images for years. The problem didn't occur until
I updated the Novell client. If I remove the Novell client the problem goes
away. I think this is a Novell problem.

Can this be escalated? I'm about to re-image 40 machines and don't want to
do that with a bad client on them!

Max Tyler

"Hamish Speirs" <hamish@haitch.net> wrote in message
news:79fc33x7lm.ln2@oes.haitch.net...
> Max,
>
>> I've got several Dell Lattitude laptops and 2 Dell GX260 desktops that
>> crash at random intervals
>> one to 5 times a day with a blue screen that says there are No More IRP
>> Stack Locations.

>
> Are these machines running the Dell OEM windows build? Many of the OEM
> manufacturers include a lot of additional "stuff" into their builds - some
> of which is Network hostile.
>
> If you're running the Dell OEM image, try installing just a standard clean
> install of Windows, see if the problem still exhists.
>
> --
> Hamish Speirs
> Novell Support Forums Volunteer Sysop.
>
> http://haitch.net
>
> (Please, no email unless requested. Unsolicited support emails will
> probably be ignored)



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: IRP Stack Locations

Max,

> These are accounting machines with tons of software and are setup very
> precisely. You are asking me to spend 8 hours to build a machine on
> basically a wing and a prayer.


No, I'm telling you that a number of the OEM images, Dell in particular,
have been problematic and created issues that can't be reproduced on a
cleanly built machine.

> Can this be escalated?


You'll need to open a call with Novell Tech support.



--
Hamish Speirs
Novell Support Forums Volunteer Sysop.

http://haitch.net

(Please, no email unless requested. Unsolicited support emails will
probably be ignored)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: IRP Stack Locations

Novell Newsgroups wrote:
> These are accounting machines with tons of software and are setup very
> precisely. You are asking me to spend 8 hours to build a machine on
> basically a wing and a prayer.
>
> Yes they are Dell OEM. The only OS CDs I have that I can legitimately put
> on them are Dell OEM CD's.
>
> I've been running Dell OEM images for years. The problem didn't occur until
> I updated the Novell client. If I remove the Novell client the problem goes
> away. I think this is a Novell problem.
>
> Can this be escalated? I'm about to re-image 40 machines and don't want to
> do that with a bad client on them!
>


The best way that I find to "convince" identify and convince someone
that their device driver is broken is via the following:

1) Download and install the the latest version of Kernel Debugging tools
for Windows (i.e. WinDBG) from:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx

2) Configure your computer to save a Memory Dump when it crashes.
On WinXP do the following:
- Control Panel -> System -> Advanced Tab -> Startup and Recovery -
Settings -> Write Debugging Information --> Make sure this is set to
either Kernel Memory Dump or Complete Memory Dump. Note --- the Complete
Memory Dump will take a snapshot of your RAM so if you have 1 GByte Ram
it will create a file of size 1 GByte.
Make a note of the location of the created dump file (usually
\windows\memory.dmp)

3) Configure WinDBG one time to use the Microsoft Symbol server to
download the kernel debug symbols it needs to decode the crash info.
Run WinDBG and issue a File -> Symbol File Path and type in something like:
SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols

You can replace the "C:\websymbols" part with a directory of your choice
on your local computer.

Save it

4) When the Blue scree occurs the next time, the MEMORY.DMP file should
be created. After reboot, run WinDBG and issue a File -> Open Crash Dump
and select the crash dump file (Memory.dmp).

It will download symbols referenced in the dump.

Then issue the following command from the kd> prompt window at the
bottom of the screen:

!analyze -v

It does a very nice BugCheck analsys Dump which shows the error in
greater detail, including the driver stack... and info regarding the
offending device driver.

Developers can use this info to find the problem.

By the way, the error "No More IRP stack locations" is most commonly
caused by a device driver whose code copies the stack location
incorrectly (which is a very common procedural thing required in Windows
device drivers).
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.