STOP: c000021a (session manager)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I found out what was causing the stop error. To reproduce the error start
regedit and goto
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment
Open (Default) and just press enter. Now the Data column will change from
"(value not set)" into blank ""
If you restart the computer a blue screen of death with error message
_STOP: c000021a {Fatal System Error}
The Session Manager Initialization system process terminated unexpectedly
with a
status of 0x000000d (0x00000000 0x00000000).
The system has been shut down._

You can now restore the registry with last known good or if you have
WinInternals ERD, delete the key you pressed enter on before.

I would like to report this as a bug for Windows XP sp2. What are my options?
 
MS is only going to issue 'security' fixes on XP. If you asked them about
this, they would pretty much tell you to fix it by upgrading to Vista. MS has
said they only have a five year suppoort window for their 'previous'
operating systems.
 
I get what you mean. Run Vista! It would be interesting to see if the same
stop error occurs on vista? ;-)
Is it possible to add this solution to the ms kb? If yes; how?
 
Mark

Run Vista with all the issues it creates? I am not sure they are winning
the Vista argument. If I were buying a new system I might just opt for a
proven as opposed to a non-proven system.

I am sure you are right about the response by Microsoft but it would be
inviting a raspberry. Do these spokepersons know the difference between
spin and the truth?

--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Yes, you're right, but when spin keeps you the job you went to school for
years to get, it starts looking a lot truer :/ I quit MVP because the spin
was making me dizzy.
MS is just another bureaucracy, where the rules are more important than the
truth. You would think the example of I.B.M. would have taught them
something about that.

On another subject, thank you very much for all the help you give around
here.
 
We try Mark.


--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Hello guys. I encountered this message on my laptop a few days ago. Your
discussion seems to be the only one that specifically addresses my error
which was:

Stop c000021a {Fatal System Error}
The session manager initialization system process terminated unexpectedly
with a status of 0xc0000034 (0x00000000, 0x0000000) The system has been shut
down.

Here is the sequence of events leading to the problem.

1) Removed hard drive to get manufacturer part number for upgrade.
2) Computer rebooted fine and used machine subsequently.
3) Upgraded TrendMicro Virus/Spyware software pattern files. This included
running an update that gave the option to replace some drivers in the Windows
System32 folder and got a warning about replacing current drivers with
unknown version. I accepted the changes

On the next reboot the system hung when the agp440.sys driver was being
loaded failed with the message above.

The system will not boot in Safe Mode or with Last Known Good Configuration.
I tried to boot from DVD drive, but Recovery Console is not available on the
OEM disk.

Here is what I have done so far.

1) Backed up Document & Settings, Program files, Email files (Netscape)
folders by plugging drive into desktop unit and using Backup Utility.
2) Searched for driver files in System32 folders which were modified or
created on the night of the TrendMicro update and replaced with older
versions from
Export folder in System32 folder.
3) Rebooted system in Prompt Mode. Dot same result

I eventually deleted the agp4440.sys file and tried to reboot, but now the
system hangs at the previous driver (MUP)

I am trying to save my system without wiping the drive if possible. I have
some important programs that I don’t want to lose. I have downloaded several
articles from the MS KB and other Web resources, but I don’t want to chase my
tail. So, I am trying to do this in a logical manner.

Can you say if the results so far indicate a HW or SW problem?
Does the error code above point to a specific problem that can get me
straight to the problem?
What is the next step in the boot sequence where the system hangs?

I have a system restore CD that I had from another OEM from my previous
desktop crash. I am going to try and run it next to see if it will work with
my laptop. I would like any other additional suggestions on how to go about
this. Thanks for your help.
 
Back
Top