Fatal System Error 0xc000026c
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 18:01:15 GMT by s_wx1127 (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 XP-based computer booted blue, noting a file error which in turn kicked off an automatic chkdsk scan/fix of my hard drive. I got some coffee and used my smart phone to address email while all this was going on. When the system was done "fixing" the broken files, it rebooted to something I'd never seen before http://answers.microsoft.com/en-us/windows/forum/windows_xp-update/stopc000021afatal-system-error-the-session-manager/e3e30d8f-8326-4096-9187-0b2162847732 - a blue screen of death with the following ubiquitous message: Stop: c000021a {Fatal System Error} 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 http://healyourchurchwebsite.com/2008/03/14/how-i-fixed-my-stop-c000021a-fatal-system-error-with-knoppix/ we brought up the Microsoft Knowledgebase file #317189 entitled "Error Message: Stop c000021a {Fatal System Error} The Session Manager Initialization System Process…" It had 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 blog
out what it was, I thought I'd add it in my tips section. From what I've been able to http://www.techforlunch.com/bsod-session-manager-initialization-fails-with-status-0xc000026c/ 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 http://www.realgeek.com/forums/fatal-system-error-a-status-of-0xc000026c-201735.html 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 fatal system 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 fatal system error 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.
> Operating Systems > Windows XP > Windows XP Performance & Maintenance > (Fatal System Error) a status of 0xc000026c (Fatal System Error) a status of 0xc000026c Posted: 10-28-2003, 11:25 PM Guest Posts: n/a Show Printable Version Email this Page Post Comment My brothers machine is running under Win XP PRO and he had a power failure will the machine was running. He unplugged the machine until the power was back on, but when he restarted the machine , he gets a Windows splash screen then the following error. Stop: c000021a (Fatal System Error) The session manager initialization system process terminated unexpectedly with a status of 0xc000026c (0x00000000, 0x00000000). The system has been shutdown. I've searched the Web, and Microsoft's own XP support, newsgroups, etc. but the only reference I get to this status does not refer to the Session Manager. It refers to a device driver being bad or missing. Since I don't get any info. on a device driver I cannot implement the fix recommended in that reference. Does anyone have any ideas? I don't know his specific versions of drivers, updates, etc. but his hardware config is as follows: AMD athlon 2000+ 256MB DDR ECS K7s5a Mainboard ATI RADEON 9000 128MB Samsung SP8004H 80GB Hard Drive (Fatal System Error) a status of 0xc000026c Responses to "(Fatal System Error) a status of 0xc000026c" Guest Posts: n/a (Fatal System Error) a status of 0xc000026c Posted: 10-28-2003, 11:59 PM I was able to fix this (mysteriously) by trying to get to the "restore from last good config" option of the restore menu. Only when I pressed F8, the CMOS screen came up. I thought maybe I pressed the F8 key too early so I rebooted and tried F8 again and the system stalled for a short period of time then simply started in WIN XP as per normal. Rebooted, with hands-off, and the system started no problem. 3 subsequent reboots and A-OK. Well, thanks for your consideration. >-----Original Message----- >My brothers machine is running under