STOP error message (Win XP HOME)

**trebor** · 2005-03-19 19:16

A friend has a relatively new DELL running Windows XP Home edition. This morning, when she turned on the system she is getting the following BSOD; STOP: c000021a [Fatal System Error] The windows logon process system process terminated unexpectedly with a status of 0xc0000135 (0x00000000 0x00000000) The system has been shut down.

I have been doing google searches but have not found this specific error. Open to any and all suggestions.

**Leif** · 2005-03-19 19:26

How old is 'relatively new'?
Is it still under warranty?

How far through the bootup process do you get before the BSOD?

Have you checked Dell support for the error message?

**trebor** · 2005-03-19 19:41

It is one month past the one year warranty.

It goes to the DELL window, then to the Windows Splash screen and then to the BSOD.

I have not checked DELL Support but will do so now.

**Leif** · 2005-03-19 19:53

Have a look at MSKB 318159: Damaged Registry Repair and Recovery in Windows XP which seems to fit the description.

**trebor** · 2005-03-19 20:06

Hey Leif, I found that KB article too but all it says is to "get SERVICE PACK 2. How can I "get" SP2 when the system will not boot up.

I have pulled the HD out of the DELL and will install it as a slave so I can back up my friend's files, address book, etc. Then I am thinking about trying a REPAIR installation of XP.

What are your thoughts?

**Leif** · 2005-03-19 20:17

It seems a logical plan unless someone can chip in with an alternative.

It would be worth running a thorough chkdsk on the drive in case the corruption in the registry - if that's what it is - is caused by a fault on the hard drive itself.

**trebor** · 2005-03-19 20:30

At this stage, how do I run the chkdsk?

**Leif** · 2005-03-19 20:38

Sorry - I meant when you had installed it as a slave and prior to running a repair.

Presumably it won't boot up in safe mode?

**trebor** · 2005-03-19 20:44

No it won't boot up to SAFE MODE. Guess I will just try the Repair Installation and see what happens.

**trebor** · 2005-03-19 22:45

Hey Leif,

I did the REPAIR installation (after one false start when the keyboard would not work) and all seemed to go well. Computer is now starting up without the error message, albeit somewhat slowly. I ran CHKDSK - the first time it did not seem to run all 5 stages. So I ran it a second time and it found some orphaned files, including a DLL file. I am running CHKDSK a third time as I type this and all seems to be going well. Will run DEFRAG and then just see how the system functions. Do you have any suggestions as to what I can tell my friend as to the cause of the BSOD error message. She keeps saying that she did nothing, turned the system off last night and then on this morning to find the problem.

Thanks for your help.

**Leif** · 2005-03-19 23:37

If chkdsk found a problem, it's possible it was down to a bit of corruption on the hard disk affecting the registry, but what caused that may remain a mystery - especially if the last shutdown was clean (i.e. not just switching off the power!)

It may be worth running a regular chkdsk over the next week or so just in case the HD isn't on it's way out - and make sure that important data is backed up! If it isn't already, formatting the drive to NTFS may give you a more reliable drive - a quick search in this forum for 'NTFS' should bring up the various pro's and con's of doing so.

Thread: STOP error message (Win XP HOME)

Thread Tools