|Error code: 0x0000001E|
As per M961799, this may be recorded when a user accesses shared files on the server by using a server message block (SMB) connection. The problem occurs because the Netbt.sys (NetBIOS) network driver incorrectly handles a buffer when a malformed packet is received from the network. A hotfix is available for Windows Server 2003 SP2.
M967228 describes a condition when this problem happens on a Windows Server 2008-based or a Windows Server 2003-based that is running Hitachi Dynamic Link Manager Software. It is happening because the hdlmdsm.sys driver is referencing the MdlAddress pointer. A hotfix is available from Hitachi.
See M275678 and "Troubleshooting specific Stop messages" for details on how to troubleshoot a STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED error message.
Generally speaking, this type of errors, might be caused by newly installed hardware. If this error appeared after new hardware has been added to the machine, remove the hardware component and test to see if the error reappears. If hardware is not to blame, then newly installed software should be the next step in troubleshooting this error. Keep an eye out for new drivers, Anti-virus programs, firewalls, etc. Remove the new software to test if the problem is caused by it. As a last resort search for updates/patches/hotfixes for the operating system and for the applications on your system.
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.
As per Microsoft:
If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.
|Links: M231330, M255928, M265353, M275678, M282228, M314451, M820767, M822563, M898114, Windows DDK, Troubleshooting specific Stop messages, Windows 2000 Stop Messages, Common Stop Messages, M961799, M967228|
Keywords: error code 0x0000001E and Bugcheck: Google - Bing - Microsoft - Yahoo
Keywords: KMODE_EXCEPTION_NOT_HANDLED: Google - Bing - Microsoft - Yahoo
|Feedback: If you have additional details about this error code, please send it to us.|