C000021a Fatal System Error 0xc000026c
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 05 Oct 2016 02:09:52 GMT by s_hv997 (squid/3.5.20)
are steps describing how I used Knoppix Linux to fix the dreaded Windows XP ‘Error Message: Stop c000021a {Fatal System Error} The Session Manager Initialization System Process…' failure. This morning, when I powered-up my computer at work, my Windows
Fatal System Error C000021a Windows Logon Process
XP-based computer booted blue, noting a file error which in turn kicked off an c000021a fatal system error windows7 automatic chkdsk scan/fix of my hard drive. I got some coffee and used my smart phone to address email while all this
C000021a Fatal System Error Résolu
was going on. When the system was done "fixing" the broken files, it rebooted to something I'd never seen before - a blue screen of death with the following ubiquitous message: Stop: c000021a {Fatal System Error} http://answers.microsoft.com/en-us/windows/forum/windows_xp-update/stopc000021afatal-system-error-the-session-manager/e3e30d8f-8326-4096-9187-0b2162847732 The Session manager initialization system process terminated unexpectedly with a status of 0xc000026c (0×00000000 0×00000000). The system has been shut down. After a few bouts with the on/off switch, it was clear, I was dead in the water. I walked down the hall to visit the IT guys, together we brought up the Microsoft Knowledgebase file #317189 entitled "Error Message: Stop c000021a {Fatal System Error} The Session Manager Initialization System Process…" It had http://healyourchurchwebsite.com/2008/03/14/how-i-fixed-my-stop-c000021a-fatal-system-error-with-knoppix/ fun advice like installing Dr.Watson, running a memory dump and then sifting through the disassembled 0′s and 1′s to figure out what broke. Of course one's machine would have to boot before that byzantine process was possible - a minor point not considered in said documentation. There were some other things about registry files, but again, I can't get to the the C:\> command line prompt then it doesn't do me much good. I did find on the Messenger Plus! Live Forums advice to run the Windows repair and replace my psapi.dll file with an older version, but again, that'd require getting onto the hard drive - and the only way I knew how to do that at this juncture would be take a route similar to the one I wrote about in 2003 in my post entitled:'Linux-based approach to fixing MSBlaster Worm infection.' So after digging through a few drawers and CD stacks, I found a Knoppix CD I had ‘burninated' back in October for my blogging-tour of Jordan. For those of you who don't know, Knoppix is a Linux distribution based on Debian GNU/Linux designed to be run directly from a CD / DVD. So I popped the Knoppix disk into the CD drive, turned on the power switch and within minutes, my
comments] i recently lost power during an automated system update, which caused a fatal windows xp error. the computer would show the bios screen, try to boot, http://www.thinkoholic.com/2013/09/12/windows-xp-solution-bluescreen-death-error-c000021a-fatal-system-error/ and just restart. booting into safe mode didn't work either. using the boot http://www.techforlunch.com/bsod-session-manager-initialization-fails-with-status-0xc000026c/ options menu (press F8 just after the bios screen goes away), i was able to deactivate the automatic system restart after serious errors, and finally was presented with the following error code: Stop: c000021a {Fatal System Error} The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000026c (0×00000000 0×00000000). fatal system The system has been shut down. (the german version says something like "der systemprozess session manager initialization wurde unerwartet beendet. das system wurde heruntergefahren.") a quick search for error code c000021a brought me to lots and lots of help pages saying "please constact your system administrator". one single page among all these meaningless "help" suggestions did contain an actual answer: your win32k.sys (located in c:/windows/system32) fatal system error has most likely been corrupted. here's how to solve this problem: use your windows xp installation cd, or any other bootable disk/flashdrive to get access to the file system. navigate to c:\windows\system32\dllcache\ and copy win32k.sys to the parent directory, c:\windows\system32. if you're using windows xp recovery console, the commands are as follows: c:
cd windows\system32\
rename win32k.sys win32kx.sys
cd dllcache
dir win32k*
copy win32k.sys ..\ renaming the original (corrupted) file is recommended so you can undo your changes if necessary. if the "dir win32k*" command doesn't show the wanted file, you may find another copy in c:\windows\ServicePackFiles\i386\. alternatively, you may be able to copy the file from a similar system (be sure to check the bit architecture (32 or 64) and service pack version first!). after the intact version of win32k.sys is copied to your system32 directory, remove the bootable cd and enter "exit", and your system should start again. Be Sociable, Share! Tweet [category: computers & technology] [tags: computers, how to, windows] 6 comments on “windows xp: solution to bluescreen of death error c000021a (fatal system error)” Eamon September 15, 2013 at 7:33 pm Thank you Thank y
out what it was, I thought I'd add it in my tips section. From what I've been able to gather, the problem occurs mostly with Windows XP SP2, but it could also be present with other variations. It was a simple service call and after everything was done, I rebooted the computer to make sure everything was ok.. well, after that, the machine never restarted. It simply kept looping, while on the windows logo screen, I could see the blue screen flashing and then it would restart. At this point, I tried safe mode in all its forms and tried "Last Known Good Configuration" etc.. nothing worked. I couldn't run System Restore because windows did not even start. So I used the F8 option to Disable auto reboot on BSOD and finally saw the actual Blue Screen message: c000021a Fatal System Error The Session Manager Initialization system process terminated unexpecedly with a status of 0xc000026c A few Googles on the subject helped piece together a solution. The problem is caused by a Windows Update known as KB925902. The patch wasn't installed recently.. it's been on the machine for at least 6 months, but something must have triggered the problem. The Solution: Apparently there are a few variations on how the problem presents itself, so if windows starts in safe mode, I would go for a System Restore or use the Add/Remove programs section to remove that update. What I had to do was to remove the update manually using the Recovery Console. here's how to do it: Boot with your original Windows XP CD. You need one which will allow you to get into the Recovery Console. Once booted, choose to use the Recovery Console, usually by pressing "r". You may need to press "enter" here to choose a different keyboard layout, otherwise you might have a hard time typing the next commands. Choose which Windows installation you need to log into. if there's only one on that machine, it will be "1″. Type in the Administrator password. Yes, there is one, you had to supply one during the Windows XP installation. Change folders using: cd WINDOWS\$NtUninstallKB925902$\spuninst Run this command in the folder: batch spuninst.txt If the command ran correctly, you should see a spuninst.tag file, using the "dir" command. reboot the computer. At this point the computer should boot properly and you should install SP3 and other patches to prevent this pro