Carl’s Blog

“Stop: c000021a {Fatal System Error}
The initial session process or system process terminated unexpectedly with a status of 0×000000000 (some more hex codes)”

Can’t repair this. Trying to pinpoint source of problem.

System Restore through Repair Environment is failing. Replacing registry files with those from RegBack hasn’t helped.

Clean install of Vista, moved contents of system32\config from broken install to clean one, also moved old Users directory, and problem still exhibited. Must be a registry/configuration issue then, not system files.

Now going to try to see if I can pin it down to either System registry or Software.

Update: It is fixed. The problem was within the SOFTWARE hive. I moved all the clean install stuff (Windows , Program Files, Users, ProgramData) to a folder called “clean”, and move all the folders out of Windows.old back into C:\ , so in effect returning the machine back to its original state before the clean install. I then replaced SOFTWARE with SOFTWARE.OLD and all is well.

Something within the Software registry hive was wrong/broken. Hope this helps someone. Not sure why the SOFTWARE hive out of RegBack was no good.

At least we know from now on that  troubleshooting “Stop: c000021a {Fatal System Error}, the initial session process or system process terminated unexpectedly.” should be done from within HLKM\Software of the registry, or just replacing the Software hive with a good backup. Earlier in the process I opened regedit from the Repair Environment’s command prompt, and loaded the Software Hive, but it looked bare. There were only Microsoft subkeys, nothing else. Either this is because of the fault, or perhaps it’s a Vista security feature? (no.. it’s not a security feature – see below):

Another update: I have taken the bad software hive, and the good working one (software.old), and loaded them up into Regedit on my XP machine to compare.

Both files are around 45mb, but the bad one is completely bare except for a couple of Microsoft subkeys. I wonder what caused this? Here’s a picture of the two hives – bad-vista and good-vista:

Here the good software hive is compared against the bad one.

Perhaps I am barking up the wrong tree. Maybe the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Reliability\Srt key means “system restore”, and this bare registry is normal during a system restore. Perhaps the registry is supposed to be bare until System Restore finishes after the reboot, and the bare registry wasn’t the actual cause of the stop error. Perhaps the stop error was triggered during System Restore’s finishing up. Who knows. I suppose I could create a restore point on the machine now, and see if System Restore causes the Stop error to return. I might do that.

At least for now, the solution here was to replace software with software.old.

So, I have a customer’s laptop here, which is broken & won’t boot. I can’t get it to boot in any way shape or form. Startup Repair doesn’t work, System Restore fails, I have manually taken all registry backups from RegBack and put them in \Windows\System32\config. Still, I get the same message:

“Stop: c000021a {Fatal System Error}
The initial session process or system process terminated unexpectedly with a status of 0×000000000 (0xc00000001 0×0010034c)”

This is one of those situations where the good old repair install would fix it. This was known as an “in place upgrade”.

With Vista, an in-place upgrade can only be started from within Windows, which means the system must be bootable.

Also, the System Restore data files are not user accessible (they are VSS diffs or something, rather than just RPxx files) like they were with XP, so that’s two repair processes out the window.

In place upgrades have been a standard repair method for as long as I can remember.

I remember deleting win.com out of the Windows directory and then proceeding to re-run the OEM Win95 setup. (Or was that my trick for upgrading to Windows 95 with an OEM non upgrade disk? I can’t remember -  it’s been a while).

Does anybody remember the “clean install without reformat” technique from the Windows 95 days? You would rip out the HKLM\System\CCS\ENUM, Services and other hardware parts of the registry, then do an in-place upgrade over the top.

All the way from Windows Nothing to Windows XP SP2, in-place upgrades have been the way to “re-install over the top”.

None of this is possible now on Vista because to do an in-place upgrade on Vista requires the system to be working. How’s that for stupidity. You can only repair a working system!

I hate Vista. I wish Microsoft had not hyped it up so much, maybe then they’d let it slip on by like the Millennium Edition that it is.

So, I will install a clean copy, and then pull in the registry files and user’s data from the broken install. If that looks good I’ll go with that, if not I’ll just go clean and move data files back into place.