PDA

View Full Version : computer crashes


blogs
28-10-2005, 21:37
my computer crashes just as i log into windows xp it goes to a dark blue screen and says a error has occured

it comes up with this fault:

NO_MORE_IRP_STACK_LOCATIONS

technical information:
*** stop 0x00000035(0x81b4f008,0x00000000,0x00000000,0x0000 0000

then it says this

begining dump of physical memory
dumping physical memory

starts to count to 100 and then crashes again

i can get into windows thru safe mode but any other way it crashes.

any help would be great

thanks blogs

UbT
28-10-2005, 23:07
Thats the "Blue Screen of death" ask i think its known. Try either system restore Start>All progarmmes>Accessories>System Tools>System restore :) if no luck there it think youll have to reinstall your o/s. Back up files via safe mode.
Hope it works
NapsterUK

latency
28-10-2005, 23:24
Google informs me that some filter drivers (easy CD creater is a classic example) can cause this.

Try starting up in safe mode (tap f8 as the windows xp loading screen appears) and see if it's okay.

Google also hinted at deeper problems, so we'll find out if it's a trivial program causing this crash, or if there's a proper system failure.

Euphoria
29-10-2005, 02:47
EDIT: My bad! Didn't mean to post here!

Moira
29-10-2005, 19:38
Sounds like it could be a faulty driver if it's OK in safe mode. I found out this from the MS site:

The NO_MORE_IRP_STACK_LOCATIONS bug check has a value of 0x00000035. This bug check occurs when the IoCallDriver packet has no more stack locations remaining.

Cause

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. This will prevent the lower-level driver from accessing its parameters.

This is a disastrous situation, since the higher level driver is proceeding as if it has filled in the parameters for the lower level driver (as required). But since there is no stack location for the latter driver, the former has actually written off the end of the packet. This means that some other memory has been corrupted as well.

You could try increasing the IRPStackSize. Browse to:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\l anmanserver\IRPStackSize

in the registry, and give it a higher value. Mine's set at 21.