From: "Geo." 

"Chris Robinson"  wrote in
message news:3DD2862F.CC1D4163{at}NOSPAMtotalise.co.uk...

> The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e
> (0x80000003, 0x80455d67, 0x00000000, 0xbb4d08cc). Microsoft Windows 2000
> [v15.2195].

This may help.

Geo.

Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED

This Stop message, also known as Stop 0x1E, indicates that a kernel-mode
process tried to execute an illegal or unknown processor instruction. This
error handler is a default error handler that catches errors not associated
with other specific error handlers. Interpreting the Message

The four parameters listed in the message are defined in order of
appearance as follows:
1. Exception code that was not handled 2. Address at which the exception
occurred 3. Parameter 0 of the exception
4. Parameter 1 of the exception
The first parameter is a Windows 2000 error code, which is defined by the
type of error encountered in the file Ntstatus.h of the MicrosoftR Windows
2000 Device Driver Development Kit (DDK). For information about the DDK,
see "Additional Resources" at the end of this chapter. The second
parameter identifies the address of the module in which the error occurred.
Frequently, the address points to an individual driver or piece of faulty
hardware, which is generally listed on the third line of the Stop message.
Always make a note of this address, as well as the link date of the driver
or image that contains it. The last two parameters vary, depending upon the
exception that has occurred. You can typically find a description of the
parameters that are included with the name of error code in Ntstatus.h. If
the error code has no parameters, the last two parameters are listed as
0x00000000.
Resolving the Problem

Hardware incompatibility. First, make sure that any new hardware installed
is listed on the Windows 2000 Hardware Compatibility List (HCL). For more
information about the HCL, see "Additional Resources" at the end
of this chapter.
Buggy device driver or system service. In addition, a buggy device driver
or system service might be responsible for this error. Hardware issues,
such as memory conflicts and interrupt request (IRQ) conflicts, can also
generate this error.
If a driver is listed by name within the Stop message, disable or remove
that driver. Disable or remove any drivers or services that were recently
added. If the error occurs during the startup sequence, restart the
computer using Safe Mode to rename or delete the file. If the driver is
used as part of the system startup process in Safe Mode, you need to start
the computer by using the Recovery Console to access the file. For more
information about Safe Mode and the Recovery Console, see
"Troubleshooting Tools and Strategies" in this book.
If the problem is associated with Win32k.sys, the source of the error might
be a third-party remote control program. If such software is installed, the
service can be removed by starting the system using the Recovery Console
and disabling the offending system service. Check the System Log in Event
Viewer for additional error messages that might help pinpoint the device or
driver that is causing Stop 0x1E. Disabling memory caching of the BIOS
might also resolve the error. You also need to run hardware diagnostics,
especially the memory scanner, supplied by the system manufacturer. For
details on these procedures, see the owner's manual for your computer.
One type of this kind of error displays exception code 0x80000003. This
error indicates a hard-coded breakpoint or assertion was hit, but the
system was started with the /NODEBUG switch. This problem rarely occurs. If
it occurs repeatedly, make sure a kernel debugger is connected and the
system is started with the /DEBUG switch.
The error that generates this message can occur after the first restart
during Windows 2000 Setup, or after setup is finished. A possible cause of
the error is lack of disk space for installation and system BIOS
incompatibilities. For problems during Windows 2000 installation that are
associated with a lack of disk space, reduce the number of files on the
target hard disk. Check for and delete any unneeded temporary files,
Internet cache files, application backup files, and CHK files containing
saved file fragments from disk scans. You can also use another hard disk
with more free space for the installation. BIOS problems can be resolved by
upgrading the system BIOS version.
For more troubleshooting information about the 0x1E Stop message, refer to
the Microsoft Knowledge Base link, using the keywords winnt and 0x0000001E.
For information about this resource, see "Additional Resources"
at the end of this chapter.

--- BBBS/NT v4.01 Flag-4