C000021a Fatal System Error The Session Manager Initialization System Process
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Tue, 04 Oct 2016 23:31:52 GMT by s_hv972 (squid/3.5.20)
List Welcome Guide More BleepingComputer.com → Microsoft Windows Support → Windows 7 Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript http://www.bleepingcomputer.com/forums/t/468773/stop-c000021a-fatal-system-error/ to access full functionality. Register a free account to unlock additional http://www.thinkoholic.com/2013/09/12/windows-xp-solution-bluescreen-death-error-c000021a-fatal-system-error/ features at BleepingComputer.com Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create fatal system a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site. Click here to Register a free account now! or read our Welcome Guide to learn how to use this site. STOP: c000021a Fatal System fatal system error Error Started by Gorf1 , Sep 16 2012 04:32 PM Please log in to reply 11 replies to this topic #1 Gorf1 Gorf1 Members 26 posts OFFLINE Local time:07:46 AM Posted 16 September 2012 - 04:32 PM As always, it's a long story, so I'll try to stick to just the pertinent details. Apologies in advance if I miss anything or if it's a bit disjointed.I have a 120GB SSD (OCZ) to replace the 300GB HDD in my laptop. I've copied the files over and tried to rebuild all the boot records etc. I'm now getting the BSoD:STOP: c000021a {Fatal System Error} The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000003a (0x00000000 0x00000000). The system has been shut down.It is a single partition on the SSD drive. It starts at a 2MB offset. Going into the Startup Repair simply yields "Checking Disk for Errors"* then tells me Startup Repair cannot repair this computer automatically.When I do sfc /scannow /offbootdir=C:\ /offwindir=C:\WindowsIt tells me it may take some time before saying "Windows Resource Protection could not perform the requested operation" -
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, and just restart. booting into safe mode didn't work either. using the boot 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). 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) 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 "