Microsoft KB Archive/134798

= Screen Saver Causes STOP 0XC000021A Under Windows NT =

Article ID: 134798

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows NT Workstation 3.51
 * Microsoft Windows NT Server 3.51

-



This article was previously published under Q134798





SYMPTOMS
When a screen saver is configured to start automatically for any user logged in that has an environment of approximately 2000 bytes or larger, Winlogon terminates with an access violation of 0xC0000005. Windows NT displays STOP 0xC000021A.



CAUSE
A invalid pointer to the environment of the process being created cause the Winlogon access violation.



WORKAROUND
To work around this problem:


 * Do not run a screen saver to run automatically.

-or-
 * Reduce the size of the environment to approximately 2000 bytes or less.

To reduce the environment size, either shorten the path statements or reduce the number of environment variables (SET commands) used. The path statements and environment variables can be set in Control Panel System and the AUTOEXEC.BAT file.

To run a screen saver manually:


 * 1) Run Control Panel.
 * 2) Click Desktop.
 * 3) Select the screen saver and then click Test.

The screen saver will continue to run until you move the mouse or press any keyboard key.



STATUS
Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem was corrected in the latest Windows NT 3.51 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Additional query words: 3.51 trap blue screen screensaver

Keywords: KB134798

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.