Discussion Locked

NT Memory dump on shutdonw

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I may have sent this question twice. My apologies if that happened.
I have an Windows NT PC with sp5 installed and it has been working fine for the last 6 months or more, now suddenly in the last 2 weeks, the user gets a memory dump when he goes toshutdown his pc. This has happened at least twice in the last 2 weeks.
Question: How can I avoid this happening and what issues should I be addressing to resolve this problem. Is it a warning of future trouble?
Thanks Claudette

3 replies

by fossil

My guess is that the user has installed a new service that is not terminating gracefully at shutdown. If you have the time (and inclination), examine antoher PC that operates "normally". From ControlPanel, start the servicess applet and make note of the installed services and, of those, which have a status of "started". Once equipped with the list, check the same info on the problem machine. The problem could be caused by one of the "delta" items that is active only on the problem machine.To indentify it, manually stop the unknown services, one at a time, rebooting, untoil you get a shutdown that's problem free. You'll know that the lsat service you tried was the culprit. Next move is up to you and the user as to whether or not it's essentioatl to have that running.

by shanghai sam

The user is not able to install new services so that elminates that part of the problem. I know for sure nothing new has been installed. Maybe is will
check the service pack level to see if I am up to date.
Thanks for your reply..
claudette

by curacao_dejavu

First install sp6a and the SRP rollup.
(could be that something is corrupted, the sp will clear this).
2 right click on my computer, properties, startup and shutdown, and select "write event to system log" and "write debugging information to".
From the event log you will be able to see the eventnumber and some codes, you will be able to track it down on the Microsft KB.
From the debugging mode you can contact MS for info regarding that (I never needed to do that yet).

Success

Leopold

This discussion is closed to new replies.