heeeelllllllllpp

[Gaurav]

I have been facing this same problem for the last 3 months and it keeps on appearing again and again. I get it after the windows xp screen with progress bar. The BSOD error is as follows

STOP: c000021a{fatal system Error}
The Session manager Initialization system process terminated unexpectedly with a status of 0xc000026c (0x00000000 0x00000000)
The System has been shut down.

The problem is solved only through a reinstall upon the existing one. After the reinstall is complete my CD writer is not detected by the windows and the device manager shows a red exclamation mark on the secondary channel. This device manager problem is solved only when I format my harddisk (long procedure ) and reinstall everything.
I have tried many tricks to eliminate the problem but none of them helped at all.
anybody have idea why the same problem keeps on appearing everytime.

Using WindowsXP professional SP2
autopatcher XP september 2005

please help me. The proble is driving me nuts.

The same error is displayed in the microsoft's support section but it says that the error comes in windows 2000 or windows xp.

help help help...

 

[LordDJ]

You probably have a faulty ROM drive or cable connections. See if xp works fine without the drive. Then try swapping it for a friend's. I had a similar problem with my lan card. Later found that it was faulty.

Do post your results.

 

[Gaurav]

the drive problem is okay.

but what about the stop error. why is it appearing

 

[swatkat]

Hi,
These KB's might help you:
*support.microsoft.com/?kbid=316503

*support.microsoft.com/default.aspx?scid=kb;en-us;156669&Product=winxp

 

[Gaurav]

Though i have found the problem on the microsoft's troubleshooting section , but the solution applies to only windows NT systems only.

I don't whether te solution provided by them will work or not.

 

[swatkat]

Hi,
This happens when either Winlogon.exe or Csrss.exe fails to do its job correctly. Since these two processes are essential for User mode operation of the OS, if any one of them fails to execute, the Windows Kernel reboots/shuts down the System.

To rectify this problem, we have to find out whether its Winlogon.exe or is it Csrss.exe which is failing to execute. To know this, we have to boot into system atleast once!

Do you get this error on every restart?

If you can login atleast once to your System, then you can run this batch file to get the Registry extract:-
Open the NotePad and copy the contents of the below "Code" box to it:-

regedit /e C:\test.txt "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"

Go to File Menu (in NotePad) > Save As and type the filename as Winlog.BAT and save it. Exit from NotePad.

Double-click on the file, a DOS type window should appear and close by itself. There would be a file called Test.txt in C:\ drive. Open it and copy its contents and paste it here.

 

[godsownman]

Hi,

Swatkat just for my knowledge . I am not facing this problem.

I tried out what you said. I got a notepad file also.

What is the reason behind this. What will you understand. Even I would like to know.

Please explain

 

[swatkat]

Hi,
We should know a bit about how the startup and login procedure takes place in Windows XP. There are three important processes we should take a look at:-
1] Smss.exe ---> Sessions Manager Subsystem Service.

2] Winlogon.exe --> Responsible for login and authentication process.

3] Csrss.exe --> Client Server Runtime Server Subsystem


When Windows switches from Kernel mode to User mode, Smss.exe is the process which is executed first.

Smss.exe in turn creates two other processes namely Csrss.exe and Winlogon.exe.

Hence, these two can be regarded as child processes of Smss.exe.

Smss.exe also closely monitors these two processes and if any one (or both) of them fails to execute for some reason, Smss.exe reboots/shuts down the PC. Because Windows relies on the existance of these two processes.
When any of these two processes fail, Smss.exe, as stated above, crashes the System giving an error code of C000021A.


The same thing is happening in Gaurav's PC!


We have to find out which process is failing to execute, whether its Csrss.exe or Winlogon.exe.

For that, we have to look at the tasks performed by both of them.

Once Winlogon.exe is executed, it performs the login authentication functions, starts Services.exe etc. It also loads some DLL files specified in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon. If there's something wrong in the DLL files which is being loaded by the Winlogon, they can kill Winlogon which subsequently results in System crash.
The most important DLL which is loaded by Winlogon is MSGina.DLL. This stands for Microsoft Graphical Identification and Authentication DLL. This DLL is responsible for performing the user login and authentication process and loading Windows shell. This DLL is present in\ Windows\System32 folder.
But the interseting part is, it can be replaced by any other third party GINA DLL file to perform customised login process. In order to load this third party file instead of MSGIna.dll, one has to make an entry of that file in the Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GinaDLL. By this, Winlogon loads this third party DLL file instead of MSGina.dll.
If there's something wrong with this GINA file, then it can crash the Winlogon which results in System crash.
I wanted to see whether there's an entry of any third party GINA file in Winlogon key, thats why i asked him to run the batch file which would give the Registry extract.

Now, let's come to Csrss.exe. As far as i know, this can crash due to some hardware inconsistencies or due to a Microsoft Hotfix 890859 ( *www.microsoft.com/technet/security/Bulletin/MS05-018.mspx ) (Apart from Norton GoBack, in some cases, as given in MS KB article).
As he has installed Autopathcer, it may include this HotFix and it can be responsible for this crash. So, the remedy is to remove that HotFix in Recover Console mode (as described here).
If there are any hardware problems or conflicts, then the things to do are to load Default settings in BIOS, checking IDE cables and checking/cleaning RAM slots.

Hope this helps to trace the problem

 

[godsownman]

My God , How did you learn all this.

Its unbelievable, you have done a detailed study of the Windows OS.

Thank You for taking the time out and explaining it to me.

If you dont mind can you tell me how you learnt it and from where, Please.

Regards

 

[Gaurav]

Hi,
thanks for your reply, but when i receive this error message I am not able to log into windows. Please tell me the solution of the problem (not the cause). Don't mind my words but this error has made me mad, . helllllppp. helllllppp. helllllppp. helllllppp.

Hi,
This happens when either Winlogon.exe or Csrss.exe fails to do its job correctly. Since these two processes are essential for User mode operation of the OS, if any one of them fails to execute, the Windows Kernel reboots/shuts down the System.

To rectify this problem, we have to find out whether its Winlogon.exe or is it Csrss.exe which is failing to execute. To know this, we have to boot into system atleast once!

Do you get this error on every restart?

If you can login atleast once to your System, then you can run this batch file to get the Registry extract:-
Open the NotePad and copy the contents of the below "Code" box to it:-

regedit /e C:\test.txt "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"

Go to File Menu (in NotePad) > Save As and type the filename as Winlog.BAT and save it. Exit from NotePad.

Double-click on the file, a DOS type window should appear and close by itself. There would be a file called Test.txt in C:\ drive. Open it and copy its contents and paste it here.

 

[swatkat]

Hi,
This thread will help you
*www.thinkdigit.com/forum/viewtopic.php?t=32676