no_more_irp_stack_locations

Hello all!

Some of you may remember that, back in February, a friend had problems with his computer. I ended up changing the Motherboard, Graphics Card and RAM. The processor (2.0 GHz P4), hard disks and opticals were reused. I reinstalled everything from square one including all High Priority updates released at that time (including the January batch).

A few weeks ago, he had the first BSOD and the message was:

NO_MORE_IRP_STACK_LOCATIONS
STOP ERROR: 0x00000035 (0x81C92008, 0x00000000, 0x00000000, 0x00000000)

When rebooting, it gets as far as the black Windows XP screen and then it BSODs. I restored a Ghost Image, created after the fresh installation in February and installed all High Priority updates released after that time.

Yesterday, it BSODed again with the same error message and I did the Ghost drill once again to get it going.

I started reviewing the updates released after January and KB929338 caught my attention. It was released as a High Priority update and installed by automatic update. Strangely, to download manually, validation is required which indicates that it is not critical (labeled "a reliability update "). No matter what, it is installed and my question is if there might be a connection?

Thanks for your time,
Christer

By the way, I have KB929338 installed on my system with no problems. The difference is that I have downloaded it manually and installed from the local hard disk.

 

Hi Christer

Have you see the description of 0x00000035: NO_MORE_IRP_STACK_LOCATIONS here ....

http://aumha.org/a/stop.htm

and here ....

http://msdn2.microsoft.com/en-gb/library/ms793675.aspx

I don't see that KB929338 - Stop error message in Windows XP with Service Pack 2: "STOP 0x0000001a: MEMORY_MANAGEMENT" or "STOP 0x0000000a: IRQL_NOT_LESS_OR_EQUAL" applies here.

 

Hi Pete!

The first two links at aumha are dealing with NT systems and are rather old. It doesn't say when they were created but they were reviewed in 2006 and 2003 respectively.

The microsoft article is too much geek for me ... ... !

Anyway, after the update was installed, it took ~2½ weeks until BSOD #1. After restoring the Ghost Image and reinstalling the update, it took another ~2½ weeks until BSOD #2. Maybe I am way off but if it happens again, which I actually expect, I will not reinstall KB929338.

The update is obviously (?) not a High Priority update but a reliability update and I'm considering telling my friend to uninstall it but I would rather roll back using Ghost and not install it at all. (If KB929338 actually is the culprit, it seems to be a slow starter and I wouldn't know how far it has gone in a day or two.)

Christer

 

Hi Christer

This was the phrase which caught my eye on aumha.org ...

 

I noticed that too but the RAM is only two months old. I understand that RAM can go bad anytime but it should happen more often than once every 2-3 weeks, I guess. Since the system had no reliability problems prior to installing that update (which is said to cure a reliability problem), I have told him to uninstall it and "wait and see ". If it does come back, I will roll back using Ghost and deny the update without ever showing it to the computer. If it comes back after that ... ... I will test the RAM.

Christer

 

Hello Whiskeyman!

Yes, I remembered reading a thread on this and my search directed me to your post.

In the beginning of April, after the first BSOD, I restored a Ghost Image and let Windows Update install what it offered. Usually, I never do that but only let WU tell me what is needed. Next, I install from the CD to which I have burnt all updates that are installed on my own computer. That is basically the procedure you recommend but this time, someone yelled "dinner is ready" and I though "well, let WU do the job while I stuff my belly ".

Last Sunday, when I did the job again after the second BSOD, I, again, made the same mistake of letting WU install the needed updates. (I need to go on a diet ... ...) I haven't been at my friends since then but we have corresponded over E-mail. The decision to let WU do the dirty work seems to have been a mistake. My friend says that, according to Add/Remove, he doesn't have KB929338 but he has two updates with no names (KB-numbers).

Something is not right and I will have to go back and do it right this time (manual labour ... ... no eating).

Christer

Edited: KB929388 is not yet identified as the culprit but it is my prime suspect!

 

I have not yet revisited my friend but he tells that his computer is running OK. I have a little feedback and a few thoughts:

First off, the two updates with no names (KB-numbers) are updates to Office XP.

On my own computer, KB929338 was offered via Windows Automatic Update in march. I assume that to be the case for my friend as well. That assumption would mean that KB929338 was installed on his system at the time of the first BSOD.

When I restored the Ghost Image from february on the first occasion and reinstalled the High Priority updates released since january, the april batch had not yet been released. I did not check in Add/Remove but I assume that KB929338 was installed again.

When I restored the Ghost Image from february on the second occasion and reinstalled the High Priority updates released since january, the april batch had been released. It was at this time my friend checked in Add/Remove and found that KB929338 was not installed.

Today, just to check, I restored a Ghost Image from february on my own computer. After reboot, Windows Automatic Update did not offer KB929338 and neither did Windows Update. This indicates that KB929338 has been withdrawn from both Windows Automatic Update and Windows Update. It also verifies that KB929338 should not appear in Add/Remove on my friends computer.

I have no idea when KB929338 was withdrawn but at the time of the april batch is my assumption. If my friends computer keeps running OK, we can argue that KB929338 was the culprit.

Well, if all my assumptions above are correct and my friends computer keeps running OK, unless I tell you otherwise, there will be no manual labour but a lot of eating and drinking ... ... !

Christer

 

Hi Christer

FWIW KB929338 is still available from the MS Download centre (I have checked ) as indicated in this article .....

Stop error message in Windows XP with Service Pack 2: "STOP 0x0000001a: MEMORY_MANAGEMENT" or "STOP 0x0000000a: IRQL_NOT_LESS_OR_EQUAL "

 

Hi Pete!

Yes, I know but you no longer get it automatically. I suppose it is there for people who experience the problems it is supposed to cure but not offered to one and all.

Christer

 

My friend called and said that his computer had blue screened again with the same error message. This means that leaving KB929338 out of the box did not help that much but it took twice the time (some progress). It differs in that he was able to restart in safe mode and an immediate restart in normal mode went well. He also said that, on an earlier occasion, when closing a window, half of it stuck on the screen and he had to restart to get rid of it.

The plot thickens ... ... !

Christer

 

Yes, Norton Internet Security 2005, Norton SystemWorks 2003 (Norton AntiVirus 2003 excluded) and Norton Ghost 2003 are installed. I have exactly the same but do not have the same symptoms. I will have a look after the weekend.

Thanks,
Christer