- the windows logon process system process terminated unexpectedly with a status of oxcoooo135
- Replies (3)
- Windows logon process terminated unexpectedly with
- Answered by:
- Question
- Answers
- All replies
- STOP: c000021a (Fatal System Error) __The Windows Logon Process System . 0xc0000005 (0x0000000 0x00000000). The system has been shut down.
- Replies (4)
- Fix “The Windows Logon Process has Unexpectedly Terminated”
- Windows Server 2003/2008
- Windows XP, Vista, 7
the windows logon process system process terminated unexpectedly with a status of oxcoooo135
Replies (3)
Have you made any changes to the computer prior to this issue?
I would suggest you to try these methods and check the issue status.
Method 1:
Start the computer in Last Known Good Configuration and check the issue status.
Using Last Known Good Configuration.
Method 2:
If the computer unable to start in the Last Known Good Configuration, try to start the computer in safe mode.
Step 1:
Start your computer in safe mode.
Step 2:
If the computer works fine in safe mode, perform the system restore to a system restore point where the computer was working fine.
How to restore Windows XP to a previous state.
Note: Undo System Restore will not work when System Restore is invoked from Safe Mode.
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Is there some reason you are not revealing the entire error message (those are zeros BTW and not ohs).
For example, here is one such example:
STOP: c000021a
The Windows Logon Process terminated unexpectedly with a status of 0xc0000135 (0x0000000 0x0000000).
The system has been shut down.
You need to tell us exactly what your error message says and more about your system:
Since the Microsoft Answers forum implementation does not prompt for any kind of system information when a new question is asked, we know absolutely nothing about your system. Not knowing fundamental information about a problem prolongs the frustration and agony of resolving these issues.
Thank you MS Answers, for making the resolution of simple problems as frustrating and time consuming as possible.
Please provide additional information about your system as best you can:
What is your system make and model?
What is your XP Version and Service Pack?
Does your system have IDE drives or SATA drives?
Describe your current antivirus and anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc.
Was the issue preceded by a power interruption, aborted restart, or improper shutdown? (this includes plug pulling, power buttons, removing the battery, etc.)
Does the afflicted system have a working CD/DVD drive (internal or external)?
Do you have a genuine bootable XP installation CD that is the same Service Pack as your installed Service Pack (this is not the same as any Recovery CDs that came with your system)?
What do you see (exactly) that you don’t think you should be seeing and when do you see it?
If the system used to work properly, what do you think might have changed since the last time it did work properly?
I don’t think any of those Microsoft engaged Support Engineer «expert» wild goose chase ideas are going to help you since I doubt your system will boot with an error like that. Those Methods and Steps look like ideas from somebody that doesn’t understand how XP works, has very likely never seen this message before much less fixed it and will just waste your time — as you will soon discover.
That is not what Last Known Good Configuration does, that is not what it is for and that is not how it works.
And. You will not be booting into any kind of Safe Mode with that error.
Yes — your issue will still persist, so let’s see what this «expert» comes up with next.
Windows logon process terminated unexpectedly with
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I am getting this error continuously : The Windows log on process has unexpectedly terminated.
Server Configuration is
OS:Windows Server 2008 Standard Edition 64 Bit with Service pack 2
If anyone have solution pl. share
Answers
Thank you for posting in Windows Server Forum.
This error might be caused by one of the following conditions:
• System resources are inadequate or unavailable.
• The Windows registry is corrupted.
• A service failed to start.
Please check below article for solution to implement in this case.
- Marked as answer by Dharmesh S Microsoft employee Monday, June 9, 2014 8:25 AM
All replies
Thank you for posting in Windows Server Forum.
This error might be caused by one of the following conditions:
• System resources are inadequate or unavailable.
• The Windows registry is corrupted.
• A service failed to start.
Please check below article for solution to implement in this case.
- Marked as answer by Dharmesh S Microsoft employee Monday, June 9, 2014 8:25 AM
Thank you for posting in Windows Server Forum.
This error might be caused by one of the following conditions:
• System resources are inadequate or unavailable.
• The Windows registry is corrupted.
• A service failed to start.
Please check below article for solution to implement in this case.
This is of course not the solution to the problem. This is the real solution to the problem (in my case):
1. Uninstall following Windows Updates: KB2621440 and KB2667402. Restart computer
2. scannow /sfc + restart computer again. Tada!
STOP: c000021a (Fatal System Error) __The Windows Logon Process System . 0xc0000005 (0x0000000 0x00000000). The system has been shut down.
When shutting down windows or restarting, I receive an error like this
STOP: c000021a (Fatal System Error)
The Windows Logon Process System process terminated unexpectedly with a status of 0xc0000005 (0x0000000 0x00000000). The system has been shut down.
How could I solve it?
Thank you very much!
Replies (4)
When shutting down windows or restarting, I receive an error like this
STOP: c000021a (Fatal System Error)
The Windows Logon Process System process terminated unexpectedly with a status of 0xc0000005 (0x0000000 0x00000000). The system has been shut down.
How could I solve it?
Thank you very much!
There is an answer to this error code posted at:
I don’t know if it fits your particular problem but it might be a place to start. This answer has to do with corrupted user accounts and is from 2009.
There is also a good article on fixing corrupted Windows System files using a bootable Linux CD which can be found here:
This article is about error status 0xc000026c for Session Manager (which has corrupted files) and NOT error status 0xC0000005 for Logon Process (which might have corrupted Registry entries).
Please also NOTE:
The «Found.000» directory described in the article is a result of running the CHKDSK /F command (Windows Check Disk Utility), so it is not a normal Windows directory. You may or may not be able to run the CHKDSK command. If you are able to use the F8 key during startup to reach alternate boot options and can choose «SAFE MODE WITH COMMAND PROMPT» and that works for you, you might want to run the CHKDSK /F utility at the command prompt and see if the hints in this article help you.
The Knoppix CD described in the article (available at http://www.knopper.net/knoppix/index-en.html or http://www.knoppix.net ) is a downloadable, bootable disk image file. In order to use this CD/DVD you must have a second computer available with an internet connection and a CD/DVD burner with blank disks (depending on the type of image file you download) to turn the image file into an actual bootable disk for use on your PC. There are also additional disk repair and PC repair utilities available for Linux that you can download and run with Knoppix to fix a variety of computer problems, but that is a discussion for another time.
Best of luck, and I hope some of this helps.
1 person found this reply helpful
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Since there seems to be a larger number of people recently looking for solutions to this particular set of error codes, I am curious if this might not be the hint of a new virus, or other malware, beginning to spread. This could be as simple as an intentionally corrupted BOOT.INI file, or a similar kind of attack, just on a more sophisticated level.
2 people found this reply helpful
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
There usually is an exact solution to this problem:
STOP: c000021a
The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000005 (0x00000000 0x00000000).
The system has been shut down.
Does your system boot or not boot?
Why did you think downloading UPHClean would be helpful? Unless you are having the specific problems with roaming profiles that UPHClean is designed to fix, UPHClean is not going to be useful.
The problem has nothing to do with a corrupted user account.
The Knoppix Linux idea includes words like «hope, try, dangerous, risk, maybe», and even the person posting the solution says «I do not recommend this course of action» and «you risk losing everything in following the same above steps» but you can try that if you want.
Unfortunately, the Microsoft Answers forums does not prompt for enough information about problems to expedite a solution, so problems tend to drag out far longer than necessary while the needed information is rounded up.
Maybe someday the XP forums «Ask a question» dialog will ask these questions automatically when a new thread is started so I do not have to ask them every single time. It might even be possible to resolve an issue in a single reply when enough information is provided.
Please provide additional information about your system:
What is your system make and model?
What is your XP Version and Service Pack?
Describe your current antivirus and anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc.
Was the issue preceded by a power interruption, aborted restart, or improper shutdown? (this includes plug pulling, power buttons, removing the battery, etc.)
Does the afflicted system have a working CD/DVD drive?
Do you have a genuine bootable XP installation CD (this is not the same as any Recovery CDs that came with your system)?
If the system used to work properly, what do you think might have changed since the last time it did work properly?
Fix “The Windows Logon Process has Unexpectedly Terminated”
The Windows Logon process is a complicated system process that handles the Windows logon screen, user authentication, loading the user profile, locking the computer, and much more.
There are many errors assoicated with the Windows Logon process, but there are two that I have run into on many occasions.
The Windows logon process has unexpectedly terminated.
and
STOP: c000021a
The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000034.The system has been shutdown.
Depending on whether you are getting this error on Windows XP, Windows Server 2003, or Windows Server 2008, there are several ways to fix the problem. Basically, the Winlogon.exe or Csrss.exe processes have failed and therefore the system crashes.
In this post, I’ll try and walk you though several solutions that have worked in the past to solve this error.
Windows Server 2003/2008
If you’re getting this error on a server, the cause can probably be attributed to one of the following problems below. Scroll down if you are having the problem on Windows XP, Vista or 7.
- Lack of system resources (hard disk space, memory, CPU)
- Corrupted Windows registry
- Service that has failed to start
To check for lack of system resources, check the amount of free hard drive space on the partition where Windows is installed. You can also open the Task Manager and go to the Performance tab to make sure 100% of the CPU is not being used. In the Task Manager, you can also check the amount of available RAM.
If the Windows registry is corrupt, you may not even be able to log onto the computer. In that case, you will have to try and get in using Safe Mode or use the Recovery Console to run the Startup Repair utility, which I will explain below.
If a service failed to start and that’s what is causing the problem, you can click on Start, Control Panel, Administrative Tools, and then Event Viewer. Click on the System log and look for any white exclamation points in a red circle. These indicate that a service or driver failed.
Resources
To fix the first problem of lack of resources, you can either free up some hard drive space or disable some services that are taking up large amounts of memory or CPU power.
Registry
If your Windows Registry is corrupted, you will have to repair it using Startup Repair. You can do this by booting your computer from the CD/DVD and choosing the Repair Your Computer option.
Next, choose your operating system and click Next. A list of system recovery options will appear. Here you should choose Startup Repair.
Startup Repair will automatically find problems with your computer and try to repair it. Once it’s finished, restart your computer and see if your problem has gone away.
You can also repair a corrupt registry by using System Restore. Go to Start and type in systempropertiesprotection and press Enter. Click on the System Protection tab and click on System Restore.
Click on Choose a different restore point and click Next. Pick a restore point when your computer was working and click Next. After the registry is restored, restart your computer.
Services
Lastly, if a service has failed to start, you can manually try to start it by going to Start and typing in services.msc. In the Services dialog, find the service, right-click on it and choose Start.
Windows XP, Vista, 7
If you’re running any of these operating systems, you can try a couple of more things to try and fix the problem.
Last Known Good Configuration
Restart your computer and press F8 when it is booting up. This will get you the Advanced Boot Options.
This can help you recover from problems resulting from newly installed drivers that may not be compatible with your system.
Reinstall Windows
If that doesn’t work, then you may have to try reinstalling Windows. This is also called a repair install. It basically replaces all your system files, but keeps all your data and applications. You will have to reinstall all Windows updates after perform a repair.
You can read our previous post on how to perform a repair install (scroll to the bottom of the post).
GINA DLL
A lot of times the Winlogon.exe process fails due to a bad GINA DLL that has replaced the original Microsoft one. The GINA DLL file performs all authentication and identification tasks during the logon process.
You can check to see if the original file has been replaced by a third-party one by going to the following registry key:
If there is a key called Gina DLL and it’s value is not Msgina.dll, then the dll has been replaced with a third party program. If they key does not exist at all, then the system is using the default Msgina.dll file.
If there is a third-party file being used, you need to remove or disable the third party software. Usually, this is done by remote control software, so if you have any remote control programs installed, remove those.
Uninstall Windows Update
If you are getting this message right after installing the latest Windows updates, you can try to uninstall them using the recovery console.
Check out this forum post below for the steps to uninstall a particular update:
Hopefully one of these solutions will solve your problem! If not, post a comment here and I’ll try to help! Enjoy!
Founder of The Back Room Tech and managing editor. He began blogging in 2007 and quit his job in 2010 to blog full-time. He has over 15 years of industry experience in IT and holds several technical certifications. Read Aseem’s Full Bio