Winlogon May Cause an Access Violation with Long Environment Variables (261318)
The information in this article applies to:
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 4.0
This article was previously published under Q261318 SYMPTOMS
When you are using long environment variables, Winlogon may cause an access violation. When this occurs, you receive a "Stop 0xC000021A" error message on a blue screen. This symptom requires a number of race conditions.
CAUSE
When you are starting programs for a new user session, the function that sets up the environment for the new process uses a pointer to memory that is already freed.
RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem. To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Size File name Platform
------------------------------------------------
04/26/00 8:13 PM 160,528 Msgina.dll Alpha
04/26/00 8:15 PM 124,176 Msgina.dll Intel
WORKAROUND
To work around this behavior, modify your environment variables.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 10/19/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE KB261318 |
|---|
|