One of these may help.
You receive a "0x0000001E (0x1E)" Stop error in Win32k.sys on a Windows 2000
Server-based computer
(843254) - Fixes a problem where you receive a "0x0000001E (0x1E)" Stop
error in Win32k.sys.
http://support.microsoft.com/kb/843254/en-us
You May Receive a "Stop 0x1E" Error Message Intermittently in Windows 2000
(329801) - You may receive a "Stop 0x1E" error message intermittently.
http://support.microsoft.com/kb/329801/en-us
You Receive a "Stop 0x1E" Error Message Intermittently in Windows 2000
(330086) - You may receive a "Stop 0x1E" error message intermittently.
http://support.microsoft.com/kb/330086/en-us
Error message in Win32k.sys on a computer that is running Windows 2000 SP4:
"STOP 0x1E"
(921126) - Describes a problem where a STOP 0x1E error message may occur in
Win32k.sys on a computer that is running Windows 2000 SP4.
http://support.microsoft.com/kb/921126/en-us
You receive a "Stop 0x1E" error on a Windows 2000-based computer
(839427) - Fixes a problem that occurs when you receive a "Stop 0x1E" error,
and your Windows 2000-based computer stops unexpectedly.
http://support.microsoft.com/kb/839427/en-us
"Stop 0x1E" error message in the Sfmsrv.sys file on a Windows 2000-based
server
(835465) - Fixes a problem where you receive a "Stop 0x1E" error message in
Sfmsrv.sys on a Windows 2000-based server when more than half of the
server's users have disconnected.
http://support.microsoft.com/kb/835465/en-us
You receive a 0x0A Stop error or a 0x1E Stop error on a Windows 2000-based
computer
(833763) - Fixes the problem that occurs when a Windows 2000-based computer
stops responding and you receive either a 0x0A Stop error or a 0x1E Stop
error.
http://support.microsoft.com/kb/833763/en-us
You Sporadically Receive "Stop 0x1E" Error Message in Win32k.sys in Windows
2000
(329051) - You sporadically receive a STOP 0x1E error message in Win32k.sys.
A null pointer may be used for pwndStart if all the child windows of the
desktop are topmost windows, and this null pointer causes the access
violation. Microsoft Windows...
http://support.microsoft.com/kb/329051/en-us
"STOP 0X1E" error message after you install a PCI device in Windows 2000
(843125) - Updates Pci.sys to prevent a Stop error that occurs when you try
to restart a Windows 2000-based computer after you install or move a PCI
device.
http://support.microsoft.com/kb/843125/en-us
Stop 0x1E Error in Mup.sys After You Apply Windows 2000 SP4
(824288) - When you install Service Pack (SP) 4 on a Windows 2000-based
computer that has DFS Client turned off, you may receive the following stop
error message on a blue screen: Note The parameters may vary.
http://support.microsoft.com/kb/824288/en-us
You Receive a "STOP 0x0000001E" Error Message When You Quit a Program
(817700) - When you quit a program or close a service, you receive the
following Stop error:
http://support.microsoft.com/kb/817700/en-us
STOP 0x1E in Win32k.sys Error May Occur in Windows 2000 or Windows XP
Professional
(816047) - When you run Windows 2000 or Windows XP Professional, you may
receive the following error message: Note The last three sets of numbers in
the error message may vary.
http://support.microsoft.com/kb/816047/en-us
You receive a "Stop 0x1E" error on a Windows 2000-based computer
(835312) - Fixes a problem that occurs when a Windows 2000-based computer
generates a "Stop 0x0000001E" error on a blue screen.
http://support.microsoft.com/kb/835312/en-us
"Stop 0x1E," "Stop 0x0a," or "Stop 0x50" error message when
IopReleaseFileObjectLock() accesses a freed file object in Windows 2000
(833993) - When IopReleaseFileObjectLock() accesses a freed file object on a
Microsoft Windows 2000 Server-based computer, one of the following stop
error messages may appear on a blue screen:
http://support.microsoft.com/kb/833993/en-us
Open Handles Cause STOP 0x0000001E or STOP 0x00000024
(195857) - While shutting down an application the system may stop with a
STOP 0x0000001E or STOP 0x00000024 error message. In the case of the STOP
0x0000001E the first parameter will always be C0000005. This problem occurs
when an application opens a lot of...
http://support.microsoft.com/kb/195857/en-us
Stop 0x0000001e or Stop 0x00000050 Error in Navap.sys When You Use Norton
AutoProtect Feature
(317153) - When you use the Norton AntiVirus AutoProtect feature on Windows
Terminal Server 4.0 or Windows 2000 Server with Terminal Services, one of
the following error messages may be displayed in the Navap.sys file: -or-
The date on the Navap.sys driver may be...
http://support.microsoft.com/kb/317153/en-us
Computer restarts unexpectedly or you receive a "STOP: 0x0000001E" error
message on a blue screen
(822563) - On your Windows 2000-based system, you may experience any of the
following symptoms: Your computer automatically restarts. You receive the
following error message on a blue screen: When you view the system log in
Event Viewer, you notice an event ID...
http://support.microsoft.com/kb/822563/en-us
You receive a "STOP 0x0000001E" error after you install security update
MS05-018 on a Windows 2000-based computer
(898114) - Describes a problem that occurs in Windows 2000 after you install
security update MS05-018 (Microsoft Knowledge Base article 890859). You can
apply a hotfix to resolve this problem.
http://support.microsoft.com/kb/898114/en-us
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
When I first installed Windows 2000 a few years ago, I noticed that if
I logged in within 15-20 seconds of the logon screen appearing, then I
frequently got a BSOD within a few seconds of logging in. But if I
waited more than 15-20 seconds after the logon screen appeared, then I
never got a BSOD.
For the last couple years, I have been very good at waiting more than
20 seconds to log in, and I have never seen a BSOD in that time.
But today I wasn't paying much attention, and I think I logged in
right after the logon screen appeared. Sure enough, I got a BSOD
within a few seconds. Here is what the Event Log says for today's
BSOD (I'm pretty sure previous BSODs were different from this one):
The computer has rebooted from a bugcheck. The bugcheck was:
0x0000001e (0xc0000005, 0x8046acc8, 0x00000000, 0x00000000). Microsoft
Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump
\Mini062608-01.dmp.
Any idea why logging in too fast frequently causes a BSOD?
