So... you think you downloaded and installed XP SP 2 correctly, eh? You've been operating several days/weeks/months with no apparent problems since the install, so everything's cool, right?
Guess again.
If one little teeny thing didn't go according to plan and, even if you got a 'successful install' confirmation, you might have a ticking timebomb just waiting to permanantly lock your computer with the dreaded blue screen of death and this STOP ERROR:
STOP: c000021a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000034 (0x00000000 0x0000000)
The system has been shutdown.
The bad news is you'll never know you have the timebomb untill it kills you. The good news is that if you can enter Safe Mode and remove XP SP 2, you can save your contents and settings. But, as you might imagine, it is one BIG, FAT time-consuming PITA. And, unless you know what you're doing mucking about in the Registry, it's probably going to cost you some $ to have fixed.
A much better idea is to ensure you took all the right steps to increase your odds of a successful XP SP 2 installation in the first place. One simple device driver update could have saved me a ton of trouble. So, if you are contemplating an upgrade with XP SP 2, I strongly suggest you check How to successfully install Windows XP Service Pack 2 before simply clicking through the installation.
If you have already installed XP SP 2, you might ultimately need to check the MS Knowledge Base Article How to troubleshoot a "STOP 0xC000021A" error . If this error first occurred after the installation of a new or updated device driver, system service, or third-party program, the new software should be removed or disabled. Contact the manufacturer of the software to see if an updated driver is available. For information about how to contact the manufacturer of the software, check:
If you are running Windows, be aware of several XP Security Patches released on 2/9/05 by Microsoft. This update represents the largest group of security patches in nearly a year, posting 12 security bulletins encompassing 19 vulnerabilities, 14 of which it marked "Critical." Among them is a vulnerability that one security vendor claims will likely lead to the biggest, baddest worm since mid-2003. I downloaded and installed all of the critical MS security 'bandaids' yesterday, without any install or subsequent issues.
Man I think that's what happened to my comp. I reinstalled everything becuase all the sudden it would go to the blue page. Damn, Bill Gates is the antichrist.
Man I think that's what happened to my comp. I reinstalled everything becuase all the sudden it would go to the blue page. Damn, Bill Gates is the antichrist.
ironrice - I have some questions for you...
- was your Windows XP (or XP Pro) Operating System PRE-INSTALLED on the computer by the manufacturer (i.e., Dell)?
- if yes, do you know if Windows XP Service Pack 1 was also installed by the manufacturer?
- did you RE-INSTALL Windows XP in the same folder by clicking "Upgrade (Recommended)" after running Winnt32.exe, or by clicking the Install Windows XP link on the "Welcome to Microsoft Windows XP" screen that appears when you insert the Windows XP CD-ROM? This is also known as performing an in-place upgrade or an in-place installation.*
- or did you REPAIR Windows XP by starting your computer from the Windows XP CD-ROM, pressing ENTER to set up Windows XP, and then pressing R to repair the selected installation?**
- did you lose any data stored in the All Users folder, default program templates and settings stored in the Default User folder, Start menu shortcuts, items in the Startup group, or any documents, pictures, or music files that were stored in the Shared Documents folder?***
* for more info, reference MS Knowledge Base Article 312369
** for more info, reference MS Knowledge Base Article 315341
*** for more info, reference MS Knowledge Base Article 312368
When it rains, it pours. Got the original issue resolved, but when starting another machine, this message now appears:
Windows could not start because the following file is missing or corrupt :
\windows\system32\config\system
You can attempt to repair this file by starting Windows setup using the original Setup CD-ROM.
Select 'r' at the first screen to start repair.
The ONLY actions I have been able to take on this computer is:
1.) turn on while tapping F8 to open Windows Advanced Options Menu
- selecting (any) Safe Mode option brings up the same error message
- in fact, selecting ANYTHING returns the same error message
2.) with the Dell supplied Operating System Restoration CD in the drive, turn on while tapping F12 to change Boot Device to CD-ROM Drive which leads me to the setup program options of:
- To setup Windows XP now, press ENTER
- To repair a Windows XP installation using Recovery Console, press R
If I select R, I can open the Recovery Console and I do get a working C:\WINDOWS prompt.
From that prompt, I ran chkdsk /r and it repaired one file, however, when I exit and restart I still got the same error message.
Then I tried the missing file replacement steps contained in MS Knowledge Base Article 830088 to no avail.
The realization that the config\system files were not simply corrupted but possibly MIA in need of replacing lead me to the MS KB Articles 315341, 312368 and 312369.
If you're still with me here, because I can't replace the files, it looks clear that I must select reinstall rather than repair, HOWEVER, obviously I don't want to experience data loss when re-installing XP if I can avoid it.
According to Article 312368:
Quote:
"[Data loss] can occur if the Undo_guimode.txt file is present in the Windows\System32 folder on the hard disk on a computer with Windows XP preinstalled by a computer manufacturer when you perform any of the actions that are listed in the "Symptoms" section of this article. The Undo_guimode.txt file is created by the wizard that runs when you first start a computer that has Windows XP preinstalled by a computer manufacturer.
Note: The Undo_guimode.txt file is created by OEM Out-of-Box Experience (OOBE) when it should not be. This file should be used only by GUI-mode Setup when Setup restarts. After OOBE creates this file, when Setup performs the upgrade, it sees this file and thinks that it is restarting Setup and deletes the profiles that are listed earlier in this article.
To resolve this problem, obtain the latest service pack for Windows XP. An update to the OEM Preinstall Kit (OPK) that resolves this issue has been distributed to computer manufacturers. This update is also available from Microsoft Product Support Services. The English version of this fix should have the following file attributes or later:
Code:
Date Time Version Size File name
-----------------------------------------------------
08-11-2001 09:12 5.1.2600.19 927,232 Syssetup.dll
MORE INFORMATION: For this hotfix to work correctly in an OEM Preinstallation environment, you must slipstream the hotfix into the installation source directory (i386) before you install the operating system. If you do not do this, the original version of the Syssetup.dll file creates the \Windows\System32\Undo_GUImode.txt file, and you experience the [data loss] symptoms that are described at the beginning of this article."
Therefore, on the slim chance you're still following this, I need to find out if that new Syssetup.dll file is already installed, or whether I need to slipstream the hotfix into the installation source directory. The ability to preserve data when reinstalling depends upon that one file's presence.
As I said earlier, I can get the Recovery Console prompt. If I type DIR I can open a Windows directory and see the file 'xpsp1hfm.log' which leads me to think that either Dell installed the update to the OEM Preinstall Kit (OPK) or I may possibly have downloaded the XP SP 1 somewhere along the line.
Either way, if the new .dll file is there, great. But I don't see it. Could it be 'hidden'? How can I see hidden win directory files in the Recovery Console environment? What really has me nervous is the SYSTEM32 file with 0 size, since I presume the hotfix .dll resides in that file.
Slipstream the hotfix my ass, I'm so friggin' pissed and confused I'm about to let it rip anyway, data be damned.
HELP! Does anybody know what I'm talking about?????
Windows installs a blank registry as a last resort backup that you can copy to the c:\WINDOWS directory if you like. I've done this before to save my arse.
If you do copy the blank registry over your non-booting problem should be resolved, but you will have some problems with programs that store data in the registry. Some programs will not run, and will require reinstallation. This is a problem if say you had warez on your computer and you lost the installers hehe
Maybe you should buy a Mac? My PowerBooks and desktop Macs have faithfully served me for as long as I've used them. Hell, I could bring my 225MHz PowerMac by sticking a G3/G4 accelerator card in it so that I can go OS X and not be stuck in the OS 8 world if I wanted to. I bought that computer in 1995 and it still hasn't suffered a major meltdown. My current Windows box has suffered 5 or 6 reformat-reinstall cycles already and it's only 2 years old.
chenga - I don't think that will work. Referring to Article 307545 - 'How to recover from a corrupted registry that prevents Windows XP from starting', when I get to Part One: Step 5: Line: 'copy c:\windows\repair\system c:\windows\system32\config\system' of the procedure, it fails to find the file. I assume that's why the Recovery Console Repair command won't work also. Maybe it's for the better anyway, as the warning in that Article sounds lik it was directed at me and my Dell installed OS.
Quote:
Warning: Do not use the procedure that is described in this article if your computer has an OEM-installed operating system. The system hive on OEM installations creates passwords and user accounts that did not exist previously. If you use the procedure that is described in this article, you may not be able to log back into the recovery console to restore the original registry hives.
That's what led me to believe I probably have to use the Dell supplied OS recovery CD-ROM to do a full reinstall option from the Recovery Console - which is fine so long as I can verify I have the SP 1 OEM fix. How can I find if I have that Syssetup.dll file using the Recovery Console??
syssetup.dll is located in c:\windows\system32. You can use the RC to check for it, navigate to that directory and dir syssetup.dll.
I had a server fail with the same c:\winnt\system32\config\system problem you had; the registry file had exceeded 16MB, the limit on x86 systems, and nothing I did to recover it worked. I finally had to reinstall, resulting in countless hours of my time and our helpdesk's time to get the 75 users who access that system via Terminal Services back up an running.
Sigh. That's what I wanted to do on my Saturday. And Sunday.
Kal.
(Edit) Note: By the way, there is a backup copy of syssetup.dll in c:\windows\system32\dllcache
Dolly, I'm not too computer smart however, I know how to reformat my drive and start over so I lost all my porn.... I mean data. And to answer your questions, I built my own computer and installed the XP myself. Hope I could help but I don't know crap about computers except for Doom3 and Counterstrike. Good luck.
Thanks for the help, but it appears the system32 files are GONE. Unless they are all hidden, I cannot find them by typing DIR at the Recovery Console prompt. It shows -0- (zero!) system32 file size. That's why the RC repair option and my attempts to copy system32 files (per Article 307545) failed, right? So I'm resigned to reinstall using the Dell supplied CD-ROM, however, since I have an OEM installed XP Pro and I can't confirm the existance of the 'new' syssetup.dll (either from the update to the OEM Preinstall Kit by Dell, or a subsequent user installed XP SP 1 download), it sounds like I must "slipstream the SP 1 hotfix into the installation source directory" first (per Article 31236 to prevent data loss. Unfortunately, looking at the procedure, that one could be beyond my comprehension and skill level.
iron - Thanks, this isn't exactly my cup of tea either!
You might consider popping the hard drive out, bringing it to a friend's place, popping it in (not as the boot drive) and then copying the files you need over. If your buddy has a proper installation the SYSTEM file will be in the recovery folder as it should be.
Taking the drive somewhere and getting the files or bringing a bootable disk (CD-ROM) with the files you need on it are my best ideas from here short of a reformat-reinstall.
Brilliant! Thanks chenga, I'm liking that idea. I do have several other Dell 4400's that were all purchesed together and configured exactly alike. I've never swapped a HD yet, but there's always a first time. I'll research the process before I try, but is there anything in particular I shouldn't do?
FYI - I've got a friend who's experienced the blue screen of death many a time. He runs double removable hard drives now. Just in case one dies he can pop the other one in and use it as the boot drive.
One is primarily to house his programs and the other he uses to primarily store information/files. Something you might want to look into in the future.
__________________
Now I'm just laid bad - G35Princess
R.I.P. MBC
I would make backups of the drive with Windows that's having trouble right now once you've got it out. Backup the WINDOWS folder and probably your Documents and Settings folders (Just to be safe. You'll only be messing with the WINDOWS folder though). At least then you can always go back to square 2 and try again instead of having to go back to square 1 and reformat to try again. Once you've got a backup of that, you can do whatever without fear of messing up too badly.
Quote:
Originally Posted by dholly
Brilliant! Thanks chenga, I'm liking that idea. I do have several other Dell 4400's that were all purchesed together and configured exactly alike. I've never swapped a HD yet, but there's always a first time. I'll research the process before I try, but is there anything in particular I shouldn't do?
You might consider popping the hard drive out, bringing it to a friend's place, popping it in (not as the boot drive) and then copying the files you need over. If your buddy has a proper installation the SYSTEM file will be in the recovery folder as it should be.
Taking the drive somewhere and getting the files or bringing a bootable disk (CD-ROM) with the files you need on it are my best ideas from here short of a reformat-reinstall.
Ok, I need to try and resolve this sh!t. Assuming I can figure out how to physically remove the HD from Dell #1 that won't start and get in into Dell #2, do I just turn it on? What's this "popping it in (not as the boot drive)" mean? Whadda I got to do?
Grrr... that NIGHTMARE named XP SP 2
Slipstream the hotfix my ass, I'm so friggin' pissed and confused I'm about to let it rip anyway, data be damned.
to prevent data loss. Unfortunately, looking at the procedure, that one could be beyond my comprehension and skill level.
