Stop Error 0x0000001e (0xc0000005 etc...

Well this is what MS has to say about it.

"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:

Exception code that was not handled
Address at which the exception occurred
Parameter 0 of the exception
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 Windows 2000 Device Driver 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).

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 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 and the system partition is formatted with NTFS file system, you might be able to use safe mode to rename or delete the faulty driver. 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.

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 deleting the offending system service file.

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 should also 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 should rarely occur. 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 Support Web site, using the keywords winnt and 0x0000001E."


The Crazy One

I suggest replacing your RAM.  I have a Thinkpad 570E with 192MB RAM 64 onboard and 128 Additional.  I have encountered stop errors like this and removing the additional RAM and restarting usually gets the system up and running.  I shut down and put my 128 in again and I am good to go.

If you did any kind of hardware upgrade/change recently, this may be the source of your problem.

DapperYout

DapperYout makes a good point about the RAM. You can also use the following utility to test the RAM with.

DocMemory PC RAM
Diagnostic Software
http://www.simmtester.com/PAGE/products/doc/docinfo.asp

Also sometimes a device like a network, sound, video card etc can have a small defect in it the it causes intermittent problems.

Hi merrillie,
- This question is still open and needs to be closed. If any of the comments above helped you, please accept it as an answer. If not please send an update about your issue so that the question can be finalised.

- **** PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER ****


- Experts, please feel free to add any comments before the question is closed.


- If no comment is added to this question, question can be deleted and points might very well be removed.


Thanks,


Pasha

Cleanup Volunteer

Hi all,

Thanks for the help above. After much reading and searching I tracked the problem down to my firewall, which was a pc-cillin firewall. The driver error was the pc-cillin firewall driver. I contacted them and they sent me a patch, which only increased the frequency of crashes. I uninstalled my pc-cillin and have not had the problem since. I now use nortons.

Thank you I had already come across tis information in my searches but you verified I was on the right track.

:>)