Article ID: 828804
Article Last Modified on 2/21/2007
APPLIES TO
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
SYMPTOMS
When you try to use a Microsoft Windows 2000-based server that has Terminal Server enabled, the server may stop unexpectedly, and you may receive a Stop error code 0x1E on a blue screen. The parameters of the Stop error code are: {0xc0000005, 0x804ef7fd, 0x1, 0xa0dc7005}.
RESOLUTION
Hotfix Information
A 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.
File Information
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.
Date Time Version Size File name ---------------------------------------------------------- 22-Sep-2003 07:10 5.0.2195.6824 42,256 Basesrv.dll 20-Sep-2003 09:45 5.0.2195.6824 236,304 Cmd.exe 22-Sep-2003 07:10 5.0.2195.6824 222,992 Gdi32.dll 22-Sep-2003 07:10 5.0.2195.6824 711,440 Kernel32.dll 20-Sep-2003 09:36 5.0.2195.6824 29,712 Mountmgr.sys 22-Sep-2003 07:10 5.0.2195.6824 333,584 Msgina.dll 22-Sep-2003 05:10 5.0.2195.6824 1,698,432 Ntkrnlmp.exe 22-Sep-2003 05:10 5.0.2195.6824 1,697,792 Ntkrnlpa.exe 22-Sep-2003 05:10 5.0.2195.6824 1,718,464 Ntkrpamp.exe 22-Sep-2003 05:10 5.0.2195.6824 1,676,096 Ntoskrnl.exe 22-Sep-2003 07:10 5.0.2195.6824 90,232 Rdpwd.sys 20-Sep-2003 03:58 5.0.2195.6813 5,280,768 Sp3res.dll 19-Sep-2003 07:51 5.3.23.4 6,656 Spmsg.dll 20-Sep-2003 06:09 5.3.23.4 140,800 Spuninst.exe 22-Sep-2003 07:10 5.0.2195.6824 380,176 User32.dll 22-Sep-2003 07:10 5.0.2195.6824 385,808 Userenv.dll 22-Sep-2003 05:07 5.0.2195.6824 1,628,752 Win32k.sys 20-Sep-2003 09:44 5.0.2195.6824 182,032 Winlogon.exe 22-Sep-2003 07:10 5.0.2195.6824 243,984 Winsrv.dll 20-Sep-2003 06:09 5.3.23.4 22,016 Spcustom.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
MORE INFORMATION
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New Naming Schema for Microsoft Windows Hotfix Packages
Additional query words: ts 0x1E blue screen
Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB828804