General discussion

Locked

Windows XP Client Problems on Win2k Netw

By vandean ·
I am getting the following error on my WinXP clients logging into my Windows 2k network. They are running group policies from the servers. They get this error logging on, logging off, or sometimes during the day while working. These are all Dell Optiplex systems. All brand new.

STOP: c000021a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with a status of 0x0000005 (0x00000000 0x00000000).

Really need assistance with this, so lots of points to whoever solves it.

Let me know if more info is needed.

This conversation is currently closed to new comments.

12 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Windows XP Client Problems on Win2k Netw

by TimTheToolMan In reply to Windows XP Client Problem ...

Hi,

Try this...

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q307866

(remove spaces from the above URL)

Cheers,
Tim.

Collapse -

Windows XP Client Problems on Win2k Netw

by vandean In reply to Windows XP Client Problem ...

Poster rated this answer

Collapse -

Windows XP Client Problems on Win2k Netw

by Joseph Moore In reply to Windows XP Client Problem ...

To me, this sounds like a NTFS security rights issue. GP is trying to implement changes to the XP clients, but their NTFS security is preventing this.
So, I would check the security settings on the clients, especially in the System32 folder and itssubfolders.
Here is a Microsoft white paper on default ACL settings in Win2K (should be the same for XP)
http://www.microsoft.com/WINDOWS2000/techinfo/planning/security/secdefs.asp
(please remove any spaces)

If not there, then check the Registry security settings. To change these easier, I would try the Security Configuration snap-in. Maybe run the BASICWKS.INF security setting (which is basic workstation security). Here is another Technet article, Q266118, on doing this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q266118
(again, remove spaces)

hope this helps

Collapse -

Windows XP Client Problems on Win2k Netw

by vandean In reply to Windows XP Client Problem ...

Poster rated this answer

Collapse -

Windows XP Client Problems on Win2k Netw

by curlergirl In reply to Windows XP Client Problem ...

The TechNet articles I've read on this error seem to indicate that it relates to an application problem (as opposed to a driver conflict), so they advise troubleshooting it from that standpoint. Since these are Dell systems, you might want to look at any customized software that they have loaded. Have you tried contacting them to see if they have any tech notes on it? Other than that, my advice would be to take one system that is having the problem, back it up or even dump an image of it somewhere if you can. Then start removing stuff that is non-standard. If you can pinpoint a time when this problem started, remove everything that was installed after that point in time. If not, just start with the most recently installed apps and work backward until you don't see the problem any more. The other approach, which is much more drastic, would be to wipe the system completely (after doing your backup or image dump) and then start rebuilding it from scratch. If you can get a clean system that doesn't have this problem but has all of the apps, etc., that your users need, you could then use Ghost (or other imaging software) to restore the image to all the other machines that have the same problem. Hope this helps!

Collapse -

Windows XP Client Problems on Win2k Netw

by vandean In reply to Windows XP Client Problem ...

There is no software running at the time this happens. It happens at startup, shutdown, or any random time.

Thanks anyways

Collapse -

Windows XP Client Problems on Win2k Netw

by ChrisSaw In reply to Windows XP Client Problem ...

Hi,
I had the same problem with every Dell that come pre-installed from them. When I called Dell to have an answer about that, they told me to re-install Windows 2000. And effectively it works if you only re-install W2K without installing Dell CD utility. If you install their CD, you will have the same problem.

Hope it help.

Christian

Collapse -

Windows XP Client Problems on Win2k Netw

by vandean In reply to Windows XP Client Problem ...

I installed fresh copies of XP on each machine. No dell utilities. Thanks for the answer though.

Collapse -

Windows XP Client Problems on Win2k Netw

by hjs In reply to Windows XP Client Problem ...

This is from my Windows XP Pro resource kit:

Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATEDThe Stop 0xC000021A message occurs when Windows XP Professional switches into kernel mode and a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is compromised and security can no longer be guaranteed. Because Windows XP Professional cannot run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can cause the system to stop responding. You cannot use the kernel debugger in this situation because the error occurred in a user-mode process.

A Stop 0xC000021A message can also occur when the computer is restarted after a system administrator has modified permissions in such a way that the SYSTEM account no longer has adequate permissions to access system files and folders.

Interpreting the Message
This Stop message has three parameters:

Status code.
This value is 0x00000000 (zero).
This value is 0x00000000 (zero).
For information about all possible status codes that might be returned, see the Ntstatus.h file of the Windows XP Professional Driver Development Kit (DDK). For more information about the DDK, see the Driver Development Kits link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources.

Resolving the Problem
The following suggestions are specific to Stop 0x21A errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

Collapse -

Windows XP Client Problems on Win2k Netw

by hjs In reply to Windows XP Client Problem ...

Stop 0xC000021A messages occur in a user-mode process and the most common causes are third-party applications. If the error occurred after installing a new or updated device driver, system service, or third-party application, you need to remove, disable, or roll back the driver, or uninstall the new software. Contact the software manufacturer about a possible update.
System file mismatch caused by partially restoring the system from backup media might cause this error (some backup programs donot restore files that they determine are in use). Always use backup software that is Windows XP Professional compatible.
If SYSTEM account permissions were altered, follow the procedures below to regain access to the boot partition:
Perform a parallel Windows XP Professional installation onto a separate partition or drive. Do not use the original drive and folder names because the new Windows XP Professional installation overwrites previous settings. Complete the second installation.
In the Run dialog box, in the Open box, type: c:
Right-click the original Windows XP Professional systemroot folder, and then click Properties.
Click the Security tab, and then grant the local SECURITY account full control of the systemroot folder and its subfolders.
Restart the system, and then select the original Windows XP Professional installation from the startup menu.
For more information about Stop 0xC000021A messages, see the Microsoft Knowledge Base link on the Web Resources page athttp://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt and 0xC000021A.

Back to Windows Forum
12 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums